In Mailgun you should be able to use a test api key to experiment with Mailgun's API. No mail should be sent, but webhooks should trigger normally and you should be able to generate synthetic bounces and complaints without impacting your reputation.

This also lets the developer to setup a development environment that is similar to the production environment without the risk of sending any mails by misstake.

We had a bug on our end that sent the same message to the same recipient thousands of times—resulting in thousands of spam reports while we were oblivious until months later.

While there are things we could do on our end to improve quality control and ops, etc., it would be amazing if Mailgun could provide a duplicate detection feature. I'm imagining saving a hash of content for sent messages, and catching any time we repeat the content to any recipient. A repeat could be prevent, or an alert sent, or both.

I would like to save myself from having download an attachment if I already have a matching file stored locally.

Our organisation sends out alot of product brochure that are mostly all identical.

Rather than download this attachment in our application, I would use the copy I have on hand. Saving alot of bandwidth/server load

We would like to pay you guys real money to have the option to extend our log retention...there have been many cases where we need more than 30 days, and we dont want to setup webhook or anything external...your UI is perfectly good!

...you like money right

The search feature WITHIN a mailing list only seems to search on full fields. Would be nice to type "RO..." and get roy, ******, ronaldo, etc. in the search.

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

Make a template editing unsubscribe page (use this template in the mailing lists). Suggest using the editing unsubscribe page for use in various languages ​​(e.g. Russian, French, German, etc.), similar to the design of the main site, and more.

Would like the option to search all bounces by domain name. We have had issues with a couple of our member firms where most emails in their companies bounced back and they have whitelisted us, but we have to remove them from the bounce list to be able to resend the emails when this happens. We have to individually search by each email address with the way it is currently setup and would rather search for everyone on that domain.

Right now if you receive an email that you are forwarding with a route to gmail, Mailgun sets the Return-Path header to a bounce email. This does not play nicely with vacation reponder systems (namely Gmail). Those systems respond to the Return-Path and the auto-response doesn't go to the intended recipient. I'd like the ability to override the modified Return-Path and set it to the from/reply-to email.

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.

currently the bounce API only allows me to retrieve 1000 at a time, so the scripting I implemented on my end is error prone and can require multiple runs. It would also be nice to be able to search bounces by domain rather than by email.

Please add support for International Domain Names.

Currently the API allows POSTing a CSV list of users to be added to a mailing list.

I would like to POST a list of users in CSV who should be deleted from a mailing list

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 might be helpful for some users if the "/messages" API endpoint would accept attachments as Base64-encoded strings, with a name and content-type described somehow.

Otherwise, it's quite hard to test own integration with Mailgun API when you develop a solution for a big number of clients who are required to use EU region.

The search feature should allow for some sort of partial or wildcard search (eg. "@domain.com" or "m@domain.com" or even just on name