Please provide a field for VAT number to be included into invoices.
Thankn you

This would mean that Mailgun has to support us uploading the apple-app-site-association file (and equivalent Android file), Maligun would also have to support https request this way.

Adding an option to let Mailgun rebuild routed messages if they're going to fail on destination.
For example DKIM signed messages sent to Mailgun that are routed will fail.

For monitoring, it would be very useful if shared links like those used by google, dropbox, monitis etc. were available.

These links should contain an obscure, non-guessable identifier such as a GUID.

There is a lot of detail on the Mailgun site to get lost in. Some case study examples would help lessen the learning curve. Some I can think of are:
1. Using Mailgun with a Wordpress Domain host.
2. Using Mailgun with popular Newsletter applications.
3. Setting up multiple Mailgun domains on your DNS host.
etc.

Currently the mail log contains both the events for inbound and outbound email. In some cases I only want to see the outbound mail or the inbound mail. I'd be nice if I can somehow limit the log to either of these.

Under Reporting Section, we have filters based upon domain and Tagging . Please provide the same filters options on Logs Section to provide better filtered out results.

Currently we have to type manually in Search bar of Logs section.

For various privacy/legal reasons it would be good to have servers in non U.S. regions/zones. (Kind of like what AWS does.)

It would be useful to search for terms in specific field explicitly. At the moment searching for an email address will match on From as well as To fields.
Gmail supports search terms of the form "to:name@domain.com" or "from:name@domain.com"

You should log config changes. This will allow problems to be tracked back to the source quicker and aid in fault diagnosis. E.g. we had a problem on 12/01/2017 what config changes did we make? Log what changed from what, to what, log who changed it and when.

Please add the possibility to forward feedback loop emails so that we can use other tools to analyse them in more detail then Mailgun provides...

As part of the inbound mail parse output to have a field that includes the IP address of the sending email server - what is used as part of the TCP handshake. I realize that mailgun may add this as a header in the mime parse, but would be great to have this already extracted as part of the output. This could be used for additional security and spam checks by the developer. Thank you.

Recently because of insufficient balance in credit card, mail gun rejected many transaction mails in my account, and this effected our business badly.

So i request for two features:

1. Re-send rejected mails (please add code in your docs)




2. View rejected mail content

http://blog.mailgun.com/how-to-view-your-messages/

It seems currently you store only delivered mail content in your servers, Please add this feature in rejected mail.
So that we can copy the html and send it again.

Thank you.

Currently searches require an exact match. Partial match would be helpful.

In SMTP you can set envelope recipients that are not listed in the To: header fields (think BCCs here).

We have a need for this to send unique emails to individuals, while having the To: header in their email client appear as if it was to a group that this user is a part of.

Currently, this is not possible via the Mailgun API, but only via SMTP. Since Mailgun recommends using the API, I would love to see this feature included so we can make the leap over to the API instead of using SMTP for these particular emails.

Universal links in iOS 9 make it possible for our links to open directly in our app. Unfortunately redirects break this behavior, so Mailgun's click tracking breaks our universal links.

A simple workaround would be to allow us to set an arbitrary CNAME. I could then point that CNAME at a CloudFront distribution. That way we could serve an apple-app-site-association file and redirect all other requests to mailgun.

We could then intercept the click tracking links in the app, and fetch the click tracking link to record the click and get the redirect target.

The click tracking data currently provided provided appears to roll up click activity in an email to the URL level. For example, if an email contains a text link in body copy and a button image...and both are hyperlinked to the same target URL you cannot distinguish which one of the two links a user used when a click is recorded.

Being able to do this would provide insight to designers, helping them compare layouts for optimized response performance.

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.