It should be possible to do batch sending without messing with low-level MIME or having to use mailing lists - it would be very convenient if it were possible to do batch sending through SMTP and simply supply the recipient (JSON) variables through a header field such as the current 'X-Mailgun-Variables'.

The search feature WITHIN a mailing list only seems to search on full fields. Would be nice to type "RO..." and get roy, ******, ronaldo, etc. in the search.

At the stats API, it would be helpful to be able to filter statistics by multiple tags.

An example would be seeing this response in your logs:

{"message":"'to' parameter is not a valid address. please check documentation"}

I think this is important when you send batch requests because then things aren't always as clear.

Can you please add search count of emails also on LOG page along with the date?

Count is a very important stat required on day to day basis, request you to please add that feature ASAP

Thanks

Today it is already possible for Mailgun clients to get deep linking working.

e.g.: Set up Cloudfront "in front of" Mailgun, proxying everything to malign, except the requests for association files.

This comes at one big downside. The IP resolution is now based on what ever AWS instance handled the request, not the client IP.
It should be easy to use the Client IP as given by the proxy.

For extra security, Mailgun could require the proxy to add a special header, to be sue the info is indeed coming from a trusted source.

Dear Mailgun,

Firstly, I'm all for protecting IP reputation and clean mailing lists. However, we accidentally uploaded our whole list today, not the filtered one based on use of Bounce/Unsubscribe APIs. We quickly hit a bounce limit, especially as the older records are a lot dirtier.

We completely understand a block of the domain and the halt of the distribution and any further messages, but blocking clickable links in successfully received messages is really embarrassing, particularly on behalf of a client. Ironically, recipients cannot unsubscribe either.

Keep up the good work :)

It is already possible to set a global account message limit which applies across all domains. However, it would be nice to get more control and be able to set a specific message limit for each individual domain.

I wonder if this kind of error occurs, do you have any retry principle?

It would be nice to see which domains are using X IP address. https://mailgun.com/app/domains

The current limit of 1000 mailing lists/account is insufficient.
Increase it to at least 10,000.

Our email routing logic can't be described with existing Routes rules.
It would be nice if a forward("http://...") webhook could respond with an optional list of actions to execute such as store() and forward("...@example.com")

Webhook for Disabled Domains

The new hook would let us view a list of domain that have been disabled by our outbound spam filter in the last 30 days.

I would love to be able to store my email for long term and use it as an archive of those emails.
I would be ready to pay as per storage used.

Sometimes we need the bounces to external mail address so if we can use a webhook or a rule to forward the bounces that would be perfect.

there is a webhook for "delivered" mail, but not one for when mail is "accepted" or put into the mailgun queue for delivery. One cannot determine the time a message was queued for unless they use the events API as part of the "delivered" handler to get the associated "accepted" event for the message. While this works, it would offer some more flexibility if we could hook into accepted events for a domain.

Hello, I think it would be a great option if you allowed us to sort the bounces, complaints and unsubscribes by date/time and details as well as by recipient.

To have the capability for me to set certain mailing list members as authorized sends, rather than an all or nothing situation.