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

    6 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 →
  3. Add bounce and complaint route actions

    https://documentation.mailgun.com/api-routes.html#actions

    It could be usefull for testing/debuging bounces or complaints.

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

    We’ll send you updates on this idea

    3 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  4. Create a route to filter by sender

    I suggest you add the ability to create routes that can filter by sender, for example:


    1. a@b.com sends an e-mail to @support.alerts.jp, the e-mail gets action 1


    2. b@b.com sends an e-mail to @support.alerts.jp, the e-mail gets action 2


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

    We’ll send you updates on this idea

    1 comment  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  6. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Routes  ·  Flag idea as inappropriate…  ·  Admin →
  7. Increase max route limit

    The current limit is 5,000 routes and is a hard set limit that cannot be changed. It's an account based limit, rather than domain based, so you're likely to reach this limit quicker if you use multiple domains.

    It would be useful if you could increase this limit.

    5 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 →
  8. 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 →
  9. 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 →
  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 →
  • Don't see your idea?

General Feedback

Categories

Feedback and Knowledge Base