Along with delete domain at bottom of domain page, add a pause/disable domain, so all mail for all credentials can be paused if problem occurs + resumed when problem is cleared.

Today it is already possible for Mailgun clients to get deep linking working.

e.g.: Set up Cloudfront "in front of" Mailgun, proxying everything to malign, except the requests for association files.

This comes at one big downside. The IP resolution is now based on what ever AWS instance handled the request, not the client IP.
It should be easy to use the Client IP as given by the proxy.

For extra security, Mailgun could require the proxy to add a special header, to be sue the info is indeed coming from a trusted source.

Being forced to install composer seems a bit unnecessary. I would love not needing the overhead of composer.

The new capability to show a rendering of the message on the dashboard is fantastic, but would be nice if we could request this via the API for display on our side.

I am missing the option to export a log-list from the Mailgun Control Panel.
I suggest you create a table view that show this data, like an Excel table, showing columns like; email address, error code, error-message.

Dear Mailgun,

Firstly, I'm all for protecting IP reputation and clean mailing lists. However, we accidentally uploaded our whole list today, not the filtered one based on use of Bounce/Unsubscribe APIs. We quickly hit a bounce limit, especially as the older records are a lot dirtier.

We completely understand a block of the domain and the halt of the distribution and any further messages, but blocking clickable links in successfully received messages is really embarrassing, particularly on behalf of a client. Ironically, recipients cannot unsubscribe either.

Keep up the good work :)

Can you please add search count of emails also on LOG page along with the date?

Count is a very important stat required on day to day basis, request you to please add that feature ASAP

Thanks

It is already possible to set a global account message limit which applies across all domains. However, it would be nice to get more control and be able to set a specific message limit for each individual domain.

I wonder if this kind of error occurs, do you have any retry principle?

Allow adding address such as the following to suppress lists so that known bad domains can be preemptively blocked.

test*@baddomain.com
*@extrabaddomain.com

It's a common scenario when you want to send an email and have a list of recipients which for business purpose needs to be in BCC.

Currently the error which comes from the MailGun Api is "'Bad Request - 'to' parameter is missing' error."

Here are some StackOverflow threads about this
* http://stackoverflow.com/questions/28503099/how-to-send-mail-only-to-bcc-with-mailgun-php-api
* http://stackoverflow.com/questions/34400386/do-i-have-to-specify-a-to-recipient

Please add support for International Domain Names.

The current limit of 1000 mailing lists/account is insufficient.
Increase it to at least 10,000.

As a marketing tool we're sending email on behalf of numerous clients and their domains. Some of those clients are either using Mailgun directly or through another marketing service.

This causes problems when they attempt to validate their DKIM and SPF records, as we can't add their domain to our account.

Adding a sub-domain instead is a work-around at best and transferring the domain to our account is impossible most times, so being able to share domains across Mailgun accounts would fix this nicely.

It would be nice to see which domains are using X IP address. https://mailgun.com/app/domains

Webhook for Disabled Domains

The new hook would let us view a list of domain that have been disabled by our outbound spam filter in the last 30 days.

Our email routing logic can't be described with existing Routes rules.
It would be nice if a forward("http://...") webhook could respond with an optional list of actions to execute such as store() and forward("...@example.com")