General Feedback

What do you think of our email service? This is the spot for good, bad, or neutral feedback about our main product.
You can also leave feedback on specific features like Inbound Routing, Message Event Logs, or Email Analytics.
If you have feedback that you believe requires an immediate response, don’t post here. Submit a support ticket or email help@mailgun.com. Feel free to interact with other users if you agree, disagree, or found a solution to their feedback.

Please be courteous of others and upvote if you believe strongly enough in an idea!

  1. implement a test api key

    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.

    54 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Prevent duplicate emails to same recipient

    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.

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Add an md5 hash to the attachment object in the API

    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

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Let me pay extra to get > 30 days log retention

    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

    28 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Logs  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Get stats by SMTP credentials

    Hello,

    I think it would be interesting (from a stats perspective) if you can provide another API endpoint to get the current stats by domain and credentials.

    An example:

    Imagine the domain.com has 3 SMTP login:
    - postmaster@domain.com
    - newsletter@domain.com
    - autoresponse@domain.com

    Now we can get stats from domain.com (so we can get the domain has sent 300 messages), but we don't know if we have sent these messages using the autoresponse@domain.com account or using newsletter@domain.com or any other account that we can create.

    If you can consider this new feature I think will be nice from a Stats and…

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SMTP  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Enable MailGun Api to send email with multiple BCC email addresses only.

    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

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  6 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Revert recent change regarding 400 Bad Request on non-working email addresses

    Mailgun provides an excellent service. However, a recent change was made to the API: 400 Bad Request is returned if the address is not valid.

    The validation is a deep check that is not commonly performed (in my experience), including checking the domain for a MX record and effective TLD names (using https://publicsuffix.org/list/effective_tld_names.dat).

    The issue with this is

    1) There are no clear distinction between an invalid API request and invalid content. E.g. you get a 400 bad request if a required parameter is missing and if the email address is invalid

    • Currently the documentation states: "Bad Request -…
    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Unsubscribe page for users (Mailing Lists)

    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.

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Mailing Lists  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow modifying the return-path of routed emails to allow better support of email auto responders.

    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.

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Allow wildcard and full domain suppression

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

    test*@baddomain.com
    *@extrabaddomain.com

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Bulk delete mailing list members via API

    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

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Mailing Lists  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Accept attachments encoded as Base64 strings in the "/messages" API endpoint

    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.

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Give ability to create sandbox for EU region

    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.

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Create a route action to reject incoming emails (ie do not even process them)

    Currently, the stop() action merely stops all subsequent routes. The email that matches the conditions is still processed (and therefore charged). As such, a potential attacker (say a determined competitor) can inflict a huge bill on a mailgun domain by sending a large amount of emails to that domain.

    My suggestion is to have an action that will ignore a sender / sending domain entirely and refuse to accept some emails with the action.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. API Key Permissions/Restrictions to Reduce the Impact of a Leaked Key

    Security Feature:

    It should be possible to restrict the call types that your API key is able to make in order to reduce the impact of a leaked/breached key.

    For example, if my API key is accidentally exposed, an attacker could then go on to exfiltrate data from my account.

    If it were possible to lock down your API key so that it can only make certain call types, the impact of such a breach would be drastically reduced.

    For example, I could lock down my key so that it is only permitted to add/send emails to a particular mailing…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. API : Add an API method to download attachment for inbound emails.

    Right now mailgun SDK provides no method to download attachment given we have the URL. Only method is to download the attachment via language specific libraries like open-uri for ruby and we have to pass parameters for authorization. It would be great if there is a pre-built method to download attachments easily

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Wordpress Plugin Update & Error Reports

    The Mailgun Plugin for WordPress needs to be updated. https://wordpress.org/plugins/mailgun/ I am a fan of MailGun and want to see you all succeed. Currently there is a warning banner on the WordPress plugin repository saying that the plugin has not been tested with the last 3 major releases of WordPress. This plugin currently has over 90,000 installs - I'm sure many are paying customers.

    Also, it would be great to integrate error reporting into the plugin so WordPress is notified when an email fails to send. This way other plugins, such as WP Mail Log, can pick up and report…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. The final failed retry event for a no MX message should have permanent severity.

    When a message is sent to a domain without an MX record (498), mailgun attempts to send the message for up to 8 hours. Each attempt will be recorded as a failed event with severity = "temporary". The reason is set to "generic" for each attempt except the final attempt which is set to "old".

    This final attempt failure event should have severity = "permanent" so you can use the Permanent Failure webhook to observe this dropped message.

    Currently, you must also use the Temporary Failure webhook and inspect the reason property to see if the temporary failure is effectively…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Routes Pricing

    Cleaner pricing verbiage around Routes on the pricing page or FAQ.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Support during opening hours in Europe

    Mailgun needs to provide support in working business hours in Europe. It's crazy that we have to wait until 3pm local time to get in touch with support.

    For two weeks we've been having problems with reputation due to a bad shared IP, and every time we get blocked we have to basically cancel our business for a full day, waiting for Mailgun support to open.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Regions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base