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. Flex plan needs some way to use inbound routes feature

    With the introduction of the the Flex plan and the elimination of the free plan the "Inbound Routing" feature is no longer available for the entry level plan.

    This broke a major use case for Mailgun as routes are an essential feature even for low mail volume accounts.

    $35 to acquire mail routing is just infeasible when you only use 200 e-mails per month.

    Mailgun needs to somehow allow Flex plan users to either have a pay-per-use for routing or make it available outright. Otherwise you are saying you do not really need these low volume customers.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  2. Free Chat Support for Initial Setup Only

    I understand that Mailgun should have premium plans and that those plans should have premium services. However, I believe when it comes to getting Mailgun to work for the first time, chat and phone services should be available. After the Mailgun is being used, because it works, then those premium services should no longer be available. I just don't think clients should have issues trying to setup their CNAME, TEXT, MX, etc. and then have no recourse to help them use the actual product. Mailgun should encourage the setup, not discourage it.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →
  3. Setup was missing a step

    Your instructions had me create 2 DNS records: TXT and CNAME. It would not work until I added a 3rd: had to have an "A" record for the "mg" subdomain. Cost me several hours of testing and log reading to figure that out.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add unsubscribe footers to emails sent via "everyone" / "members" mailing list

    Currently, if you set up a mailing list, add people to it and select the access level to "everyone" or "members" you have a good old fashioned email discussion list where people use their regular email clients to access (ie we are not talking about programmatic access here).

    But - even when you enable "unsubscribes" in the mailgun admin - unsubscribe links are NOT appended to each email received via the list.

    After a lengthy discussion with support they tell me this is as the system is designed and the footer only gets added if people send via Mailgun's SMTP.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Mailing Lists  ·  Flag idea as inappropriate…  ·  Admin →
  5. Seemed ok at first, but many emails not delivered to recipients without any issue notification.

    Many recipients failed to receive my email and no issues were reported. Lack the experience or subject matter expertise to track-down the issue(s).

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  8. Monetise small improvements

    Hi there. I've been using your great free service for the last 6 months. I run a very small charity site for alumni of Save the Children. Don't worry - I'm not asking for a freebie!
    It seems to me there is a large gap between your free service and your lowest cost billable service - which my charity can't afford. I wonder if you could make more money and offer customers a better service with low cost annual subscriptions for specific small features. Here's an example. The limit of 1,000 emails a day for my site is fine. The…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Mailing Lists  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Domains  ·  Flag idea as inappropriate…  ·  Admin →
  10. Routes Pricing

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

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  11. Route support unsecure HTTP but when HTTPS is used, A Grade cert is required

    You can use HTTP for a route to post meaning it supports unsecured communication but when you switch to HTTPS, it enforces A Grade HTTPs certs.

    We should be able to use self-issued or lower grade certs. Similar to curl -k, mailgun route should support "skip cert validation".

    This is especially important for our QA, Stage type environments where buying highest grade cert financially does not make any sense

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow query string parameters on Route URIs

    Currently, if you put any query string parameters onto a route URI (such as https://mydomain.ext/path?live) the route will not work and, as far as I can tell, it won't show any error messages or warnings.

    I propose that query string parameters are allowed, or at least ignored, and this added to the documentation and/or as a warning when entering them in the Routes page.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  13. Show API errors in MG logs

    An example would be seeing this response in your logs:

    {"message":"'to' parameter is not a valid address. please check documentation"}

    I think this is important when you send batch requests because then things aren't always as clear.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Logs  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support default callback webhooks for all domains in my account

    When I create a new sending domain, I need to configure the webhooks again. These are the same URLs for every domain, so it would be easier if I could set this for my account.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

    10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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/effectivetldnames.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…
    17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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.

    10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

General Feedback

Categories

Feedback and Knowledge Base