The delivered rate in the beta stats is incorrect. Also, list the domain selected in the filter at the top of the beta stats page. Only way to know what domain I'm looking at is by going back to the filter..

I have emails I need in 15 languages. So if I use the conditions, it will give a huge template with 15 conditions for every word or paragraph. It could be nice to have a way to separate the wanted language from the code (a form, a json, whatever). Thanks!

There can only be one SPF records for any domain, and it's quite common to have multiple includes in one record. The domain verification for the SPF record should be savvy enough to parse the record for the v=spf1, linclude:mailgun.org, and ~all elements seperately so it can verify an SPF record with multiple includes.

Hey, it'd be great if I could change the test data so that I can better preview my email templates. E.g., I'm linking to images. Since I can't change the test data, I have to trigger the emails every time I want to check my css on images...

Could you make an callback-url per domain or an API key pair per domain?

We can create Sending API keys per domain, But in order to notify our clients (different custommade applications) we would like to implement the general API to receive the failure and suppressed events. So our client know that the mailbox is invalid or that they didn't received there messages.

Please make the System remember my last used Domain... i always have to pick it, though i use only one ... and always that one :-)

Give at-least two api key place of one , so api key rotation can happen if the key is used in multiple microservices , so easy rollout can happen, With one key rotation of key cause break in every mcroservices at once

When an e-mail is sent with the "Require TLS" flag, and TLS is not configured on the recipient's server, Mailgun will continuously make retries and eventually respond with error "602 Too old".

This could be improved by sending a "failed to start TLS" response when encountering this (only once, not on every retry).

The Node.js documentation is a bit confusing. You provide me a API base URL in sandbox but it took some time to realize that I need to get only the DOMAIN of that URL. I got that from other languages. Maybe a revision would be nice since it's a bit different from https://github.com/mailgun/mailgun-js.
Thanks.

In the documentation it states the template version with the initial tag is used if its not specified as a parameter. If so then what does set active do? No where in the documentation does it clearly explain this.

Please do not provide dates in mm-dd-yy format. It is very confusing. Please use yyyy-mm-dd

Dropped as 'Other' reason is not enough to do anything.

Fix the VAT setting: when you enter a number, it appears to be successful, but the settings screen isn't updated.

I rarely use SMTP, mostly I just use the API keys. Last month the SMTP password was Brute Force and stolen, the attacker send over 100k emails from my domain which I had to pay for. I would like some ways to help prevent that in the future.

The "test Webhook" feature needs better documentation. The parameters that are sent to the webhook in the test are a complete different structure than what will actually be passed to the webhook when it is used. That is not at all clear in the documentation.

Provide meaningful delivery status description rather than "Too old"

I'm monitoring webhooks for "permanent" failures and forwarding the "delivery-status" message/description (why are those not unified into a single field??) to my end users. Instead of merely reporting "Too old", please insert the error message from the previous "temporary" failure, so that it becomes clear what the real issue is.

It looks like there is going to be wide deployment of potentially two different mechanisms to prevent suppression of TLS usage.

While it would be nice if the email community could agree on a single standard, it looks like there are two standards which will be supported by a significant % of mailboxes: MTA-STS & DANE.

https://workspaceupdates.googleblog.com/2019/04/gmail-making-email-more-secure-with-mta-sts.html

Please consider supporting these standards to enforce use of secured connections to supporting mailboxes.

https://www.zdnet.com/article/microsoft-to-add-dane-and-dnssec-support-to-exchange-online-servers/

https://techcommunity.microsoft.com/t5/exchange-team-blog/support-of-dane-and-dnssec-in-office-365-exchange-online/ba-p/1275494