It is possible please to have the same email validation function in the new EU region, as already existing in the US region, thanks.

in your routing, I wonder if you might be able to implement SRS on the forward() function? Perhaps forward("someone@example.com", "SRS") or some such? (Forwarded mails fail SPF at the destination without SRS).

The "paging" array in the events API should show the total number of results and the number of pages so you can iterate through multiple pages easily, knowing exactly where you are in the pagination. The current version of the API shows no count so you have to paginate through the results blindly. Not ideal and impossible to mitigate performance issues when handling many pages of results.

Currently, we are only able to filter information on the "Analytics" page by day. It would be very beneficial to be able to filter by a date range for our data under the analytics page in a similar fashion to how the "Reporting" filter works (30, 60, 90, or custom day range).

Now we have troubles with removing our domain from blacklist because of using non-secure protocol in tracking pixel: http:email.ourdomain.com/bla-bla-bla. Your system doesn't provide ability to use https now, but it would be very useful to provide it

We identified a clear need to set up some view only accounts for our developers to enable them to interrogate data and review potential issues in Mailgun.

Enable users to check the login history of their accounts/sub accounts. It's just good security, I imagine you must log this internally, just expose a limited subset of it.

If I attempt to send 100 emails to users at a single host and am rate-limited by the recipient's e-mail host, the mailgun system attempts to resend those e-mails after 10 minutes. The result is that the same 100 emails all retry at the exact same time and nearly all of them bounce again. Subsequent retries with longer delays will continue to bounce as they all attempt at once.

If retries were randomized between 5-15 minutes, deliverability in this scenario would be substantially improved with minor development effort.

While some of the existing charts/reports on the dashboard are useful, I would really like to know about delivery rates / failures by the domain we are sending to (or ideally ESP... i.e. hotmail/msn centurytel/centurylink/embarmail).

I usually end up hearing about a block or other delivery issue from our users. Short of pulling data over the API and parsing it myself I know of no way to accomplish monitoring this currently.

I want to see the contents of the email log, I find it convenient if viewing the contents of the email was sent
Thanks you

The maximum limit for routes is 5,000. Currently Mailgun does not notify you when you're close to the limit. This is especially risky if you create lots of routes programmatically via the Routes API.

This would be a useful safety feature in the event that something goes wrong in user code that is pushing messages thru mailgun.

Add some options to segment list sending, or create temporary lists based on number of list members.

When sending out to a large list, a user may sometimes wish to throttle the sends over a time period to avoid having too many responses or heavy web traffic all hitting at once.

There should be an endpoint where you can submit the MIME of a message and get a spam probability score to determine deliverability.

The new control panel doesn't allow for the ability to set a password, which means if the password is accidentally reset, we can't go back and edit it and we might have a number of applications using the previous password.

The new design looks nice but not mobile friendly. I had difficulty navigating around while on my iPhone XS.

The reason I had to use mobile was to check the logs to see if an email was sent out or not.