We want to ensure that our email traffic is sent securely. There is the option to enforce TLS from Mailgun but not for our connection to mailgun. It would be good to have option to secure email traffic from our applications to Mailgun either by blocking port 25 or enforcing TLS.

Your "breakdown by count" line chart is bugged. See screenshot here: https://app.userback.io/viewer/1/8/1740464uUfTsgkD/

https://help.mailgun.com/hc/en-us/articles/203637190-How-Do-I-Add-or-Delete-a-Domain-
the 'button that allows you to delete the domain from the account' is missing.
How does one delete a domain from an account??

I think the databoard &billing has error , we didn't send so much emails every day from 20th Apr. but your data-board show we sent 4-5K each day. actually we only send 1.5-2K each day!

There is no make a payment button to try to pay when our account is suspended. It's not too hard to put a button.

When rotating API keys, always use the key the client used to authenticate to Mailgun in signing webhooks. The issue is that when a new key gets generated usually we cannot update it everywhere immediately so we use the old key for a period of time, but Mailgun starts signing webhook calls immediately with the new API key resulting in invalid signatures and loss of data on our side.

Hi,
I have a question when using 'Analytics' tab.
I sent a lot of mails in 4/26. In Analytics tab I selected date '4/26', but the result said 'No tags were found with the filters you've selected.'
How could I solve this problem?

Thank you.

I would like to be able to search for an email address that might exist in any domain we have, not just the one selected in the dropdown. Some kind of search all option.

For crying out loud, MAKE A MOBILE-FRIENDLY WEBSITE.

HI there on my newsletter pre-check I get this for the Mailgun server IP:

Your IP 143.55.232.11 is blocked on 4 lists:

s5h.net: See http://s5h.net/rbl
dnsbl-1.uceprotect.net: IP 143.55.232.11 is UCEPROTECT-Level 1 listed. See http://www.uceprotect.net/rblcheck.php?ipr=143.55.232.11
dnsbl-2.uceprotect.net: Net 143.55.232.0/24 is UCEPROTECT-Level2 listed because 33 impacts are seen from MAILGUN-, US/AS396479 there. See: http://www.uceprotect.net/rblcheck.php?ipr=143.55.232.11
Sorbs.net: Spam Received See: http://www.sorbs.net/lookup.shtml?143.55.232.11

The Logs interface is really clunky. The filters are not very intuitive and the search function is not very good. Also, the logs only show a few particular examples rather than a comprehensive list. There's no way to know many failures from a certain domain, for example. It doesn't display pages or anything.

On the Logs page, all date-times are shown in PST8PDT as indicated, but on hover-over, a date is shown in UTC.

Allow other domain-based operations such as retrieving events for domain sending keys. It's nice to be able to have sandboxed API keys per domain for sending but it would be more powerful if it also allowed doing things like querying events for that domain, that way you could have one account with development/QA/production domains each with their own keys restricted to those domains.

Currently you can update the tracking protocol (http/https) via the Mailgun dashboard, and via the Maligun API. There is however, no support in the PHP SDK (https://github.com/mailgun/mailgun-php) as far as I am aware.

Is there any reason this can't be included?

Attempting to create an already existing domain via API does not return verbose error responses:

{
"message": "Domain not found"
}

Creating an already existing domain via the client portal returns an error message that is a lot more informative:

Failed to create domain. Domain already exists in registry. Domain Name: domain.tld.

Parity between the two would be good.

I upgraded my account to foundation, why do I keep getting "you're sending to fast" emails???

Im being billed but not yet using? Theres no answers on the Q&A and it's not letting me start a ticket

Increase the number of recipients allowed in a single API or SMTP request.

Currently we have to manage our own throttling of email recipients to cope with sending limit of 1000 recipients per API or SMTP request. Will be good if Mailgun can handle the throttling on their backend and adjust the sending limitations.

There was an error loading data.