Having the ability to view or download a date range of the email validation logs would in debugging and identifying abuse of the service. Currently I have to request from your support team every time I need them and the logs entries are not formatted with date/time stamps.

Allow Mailgun account email to send emails to mailing lists from Outlook without having to change the outgoing servers. This would be a step between needing to be authenticated (Read Only) and Allowing people in the mailing lists to post things.

This way the owner of the mailgun account can send emails from Outlook to their mailing lists, but no one else would be able to do this.

Mailgun provides logs where you can view even details like delivered, clicked, etc. An email can have multiple links to be clicked. I wish to know which link in the email was clicked. Right now the logs only say clicked and no details on which link was clicked.

Currently there is no convenient way to get a list for each of your domains what sending IP address(es) are assigned to them, the only way is using the website drill down into each individual domain's details.

Exposing the IP Address(es) of each domain in the /domains API endpoint seems like a good solution.

Additionally being able in the website to enter a sending IP address on the domains listing page and it would show all the domains with that sending IP address assigned.

When an email is not sent due to a Mailgun server error (e.g. 499 MX server resolution error), the retry should be much shorter than 10 minutes. Errors that are very likely transient (such as DNS resolution of a Gmail server), should be retried immediately and any error not resulting from a rate-limit should use a geometrically increasing retry interval, rather than the 10-10-15-30... interval progression.

Recipient in different list would receive only one copy of message, this is a basic ESP feature that everyone supports. But currently if a address is on more than one list than recipient will receive messages that are sent to each list, the only way to avoid this is to remove the email from other list.

Please add a workaround for this basic ESP feature.

We send a lot of emails that are custom to the individual and would like a simple way to save them. Our email generators are on 20 or so amazon instances and we spin up and shut them down as needed. So we have 3 options: save the file and hope to dl before the box dies, send bcc to a stable box, or post to a webhook on a stable box.

Would be great to define the outbound IP address (of those in my pool), for which emails will deliver, upon submitting to the API.

Hi Guys:

I have 2-factor switched on with you... super-hi secure. I don't even allow the texting version - Google Authenticator only, so my Mailgun account is really very secure.

However, for the best of reasons, you've implemented the CAPTCHA-I'm-not-a-Robot step where one has to recognize cars, mountains, traffic lights etc... BEFORE the 2-step. It's an annoying extra step that no other site requires for folks with 2FA enabled.

Can you please get rid of it for those of us who've already done the secure thing and switched on 2-step please?

Happy Holidays...

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.

We were excited to discover the multi-user capability and are even more excited for the possibility of restricting access based on role and domain.

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.

Log clicks so that it is viewable / searchable in the stats. An email might have different URLs and it would be useful to see what URL the user clicks on.

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.