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. Add option to temporarily pause/disable domain, so it can be reactivated later

    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.

    11 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 →
  2. 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…

    5 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 →
  3. Provide deep linking support (universal links) by client proxy

    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.

    2 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 →
  4. Setup a Mailgun install without composer required.

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

    9 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  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Retrieve Rendered Message via API

    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.

    5 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 →
  6. View the log file as a table I can copy to Excel

    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.

    19 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  ·  Logs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow DNS if Domain becomes Disabled

    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 :)

    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  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →
  8. Provide a search count on Log page

    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

    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  ·  Logs  ·  Flag idea as inappropriate…  ·  Admin →
  9. Implement a configurable per-domain message limit

    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.

    7 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  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →
  10. unable to establish a TLS connection

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

    2 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 →
  11. 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

    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

    2 comments  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    5 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support IDN domains; Domains with Unicode characters

    Please add support for International Domain Names.

    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

    4 comments  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →
  15. Increase limit of number of mailing lists that can be created.

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

    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  ·  Mailing Lists  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow the same domain across multiple accounts

    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.

    9 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 →
  17. Search domains by IP address

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

    8 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 →
  18. Webhook

    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.

    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  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  19. Routes: allow forward() webhook to choose routing action

    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")

    7 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  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  20. Inbound verification of DKIM signature

    From what I understand based on responses to another support ticket, incoming messages that are processed via mailgun routes are not validated using DKIM. This would seem to pose a security hole. Consider the following scenario:

    • A malicious sender creates a message and signs it using DKIM (but the signature is bad because the sender does not have the private DKIM key.)
    • This message is received by mailgun for processing via routes. ** The DKIM signature is not verified by mailgun (according to what I have been told by mailgun support.)
    • Mailgun may add new headers to the message and…
    2 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 →
  • Don't see your idea?

General Feedback

Categories

Feedback and Knowledge Base