Feature Requests

If you’ve got a feature request, you’ve come to the right place! Please relay your request request here, along with any additional details you think might be helpful.

This is not the spot for feedback on current features, only new plausible ideas will be considered. Please be courteous of others and upvote if you believe strongly enough in an idea!

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. I would like to see you add SUPPORT, as no one is replying or getting back to us !

    I would like to see you add SUPPORT, as no one is replying or getting back to us !

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  2. Longer Message Details Retention Periods

    Would like to be able to view the Message Details (MIME, content, etc) for longer than the 72 hour period after the message is sent.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  3. Longer Log Retention

    Log retention periods longer than 30 days

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

    We’ll send you updates on this idea

    1 comment  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  4. Inbox placement stats

    Inbox placement stats from ISPs that are sent every month to high volume users.

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  5. Sanitize and/or parse addresses in headers for incoming email

    Standard email headers such as FROM, CC, TO, SENDER, etc. contain email addresses, groups, or lists of addresses as described in RFC 5322.

    Mailgun currently passes on the (transcoded) data as it is received, including any errors that buggy MUAs or ESPs may send. Moreover, most libraries only do very strict parsing; This forces developers to implement lenient parsing themselves to ensure all incoming email is accepted.

    Mailgun could sanitize these fields in a way that we can really trust the headers and use a strict parser on them. That would be a big plus.

    It would even BETTER if…

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  6. Optional Filters on GET /routes

    It would be nice if there were filtering options on the GET /routes endpoint. Get all routes with priority <|>|= X. Get all routes where expression matches <regex>. Get all routes created since X.

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  7. Filter get tags by multiple filters

    Hello guys,

    I think we need a new features when we take the tags statistics, now we can set multiple tags for a message but we take the statistics only for one.

    We need to can take statistics for 2 or 3 tags concatenated per message because, for example if I want to see how many clicked have a user for a specific marketing message I can't do this.

    I can do a difference between stats, because I used the specific marketing email for many users and I used the specific user tag for multiple marketing tags.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  8. short email address for testing less than 50 characters

    I am testing to subscribe to mailgun connected to an App.
    The limitation in external app is that the email address cannot exceed 50 characters. In Mailgun the sandbox email id is more than 50 characters. So I am not able to go forward with Mailgun with this limitation.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  9. Pls add line numbers to the Logs output.

    The Logs page needs some line numbers on its output. This would to see how many of a particular type of email there are when using the filters.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  10. reply

    Individual replies go to list rather than the person who sent it. The reply-to option needs flexibility to only have single replies go to the person rather than the whole list, in case of sensitive information. This can apparently be done in "Read Only" status, but it should be available with "Members" status as well.

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  11. Enable or Disable retrying of bounced forwards on routes

    However, the fact that failed forwards are retried many times is giving us quite a headache. Generally, a bounce means that there's something wrong on our end that needs to be fixed. Though unlikely, if a forward were to succeed when retried, it may prevent us from discovering and correcting a bug in our systems. In the much more common scenario that the email keeps failing, a single failed forward will generate 5-10(?) error logs. Naturally, both scenarios are highly undesirable.

    As a result, we'd like to suggest adding a parameter to the route config to enable or disable retrying…

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  12. support international domain names (idn) in routes!

    For example, forwarding an address like jan@rüegg.cc is currently not working...

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  13. Be able to Import the same file that was Exported (i.e. support vars in Import file).

    The CSV import file format should accept the CSV file that is created by the Export feature. Presently, the import file cannot have var (JSON) data or any other data except for a name and email address. This would be useful for archiving existing lists and for seeding new lists.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  14. Implement a way to get the string of opening tracking pixel with MailGun (eg API) before sending the email

    Implement a way to get the string of opening tracking pixel with MailGun (eg API) before sending the email, to prevent the body of the message from being modified.

    We sending emails signed with a SMIME certificate, but after activating the opening webhook, it is breaking the signature of the email, because it is inserting this string at the end of the body:

    "<img wi= dth=3D"1px" height=3D"1px" alt=3D"" src=3D"http://email.info.xxxx.com.br/o/= eJwtyzEOwyAMAMDXlA1Egm3wwGOwwSpS0khE6vubobdfryVj39jNqgM3HoU8dREPqs0zFvaa9mw= Ae7eeXhDnx67QznkEvc4gy70rRUuSUCJqBCPgKHsiGsbCgHm4Vds9j297-vB3s7H--Qf_bSVd">= </body></html>"

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add option to do mirror email or cc/bcc of every email. As it's require for transnational email backup purpose.

    Configuring Email mirroring for transnational services i.e. cc / bcc services.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  16. Notification When Email Dropped

    Whenever an email is dropped by mailgun, there should be a notification sent to the account holder email address so they are aware. Otherwise there is no way of knowing if an email has been dropped without logging in to mailgun everyday, and this can lead to customers to be missed.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add option to move tracking pixel to beginning of email

    Our platform allows users to generate emails and send them. Some of them are quite long, and end up being truncated by email clients like Gmail. This results in open events not being tracked for many of the emails, since the tracking pixel is at the bottom and the email was truncated. It would be great to be able to optionally move the tracking pixel to the beginning of the email.

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

    We’ll send you updates on this idea

    1 comment  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  18. Send only the first Open event webhook

    As background to this, I read somewhere somebody saying "it's not really any body else's business when someone opens and reads an email" and also that "the biggest lie in tech is 'we value your privacy'".

    Those are just kind of moral background to this, but there's a technical reason too --- while I could follow the magic road and start building a distributed application using lambda functions (and I get that in theory using those may be a good fit for processing webhooks, all other unknowns simply presumed equal - which of course they can't be), the simplest option…

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  19. Static IP's for webhook calls to enable whitelisting

    Hello!
    Can you please add support for the webhooks to originate from a static list of IP's (via proxy if you have to) so that I can whitelist those IP's for local development environment?

    A similar implementation of this is done by Blitilne --

    http://helpdocs.blitline.com/article/CJ9KuQjMGc-static-i-ps

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  20. Ability to resend emails to a route

    The resend feature in logs doesn't allow for resending to routes. When a email fails to a route you should be able to resend it again, like with the emails, by specifying the route that it should be sent to.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base