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!

What features do you want to see added to Mailgun?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. support international domain names (idn) in routes!

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

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

    Add "batch resend" feature for failed messages within a time range.

    Why this is an important feature:

    If you've used a shared IP and use the mailgun API to send customer receipts, order confirmations etc, and the IP has been flagged for spam or blocked, you then purchase a dedicated IP, and now you need to resend the failed messages, today you have to do this manually, and if you have several hundred or thousands of messages, this is a extremely big waste of time.

    6 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 →
  3. Do not silently drop nameless attachments over HTTP API

    We're currently switching our email sending from SMTP to the HTTP API and noticed that some attachments were being silently dropped.
    The main problem seems to be twofold:
    1) the HTTP API requires non-ASCII filenames to be encoded using the "newish" RFC 7578 and simply ignores filenames encoded using the older RFC 2231.
    2) attachments sent without filenames (or whose filenames were ignored because of #1) are simply dropped without warning, causing broken content to be sent.

    Some more technical info can be found in this github issue: https://github.com/anymail/django-anymail/issues/125 (including examples of how to replicate)

    Ideally, we'd expect mailgun to…

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 →
  5. Redirect and secure

    Please redirect http://mailgun.org to https://mailgun.org
    Also, implement missing headers on mailgun.org: Strict-Transport-Security; Content-Security-Policy; X-Frame-Options; X-XSS-Protection; X-Content-Type-Options; Referrer-Policy

    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 →
  6. Enable forwarding all outgoing mail to a monitoting account

    We need to monitor our employees mail activity. We have their consent and we don't mind the way they are noticed and reminded that they are being monitored (even a systematic mail reply).
    We really need a way to easily configure a route for forwarding all the outgoing mail at certain accounts. We can not achieve it with other mail tools, unfortunately.

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  7. The ability to forward out of office replies

    Currently you are able to differentiate between the delayed bounces and the out-of-office replies, but there is no way to forward the out of office replies. Your system will automatically drop them due to lack of sender header. We need to receive out of office replies, they are essential emails for our customers.

    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 →
  8. Option to disable logs for specific domain

    This use case involves adding a private domain (its my family na.me). I would love to use mailgun for simple forwarding of first@na.me for various family members without the ability to snoop their messages.

    If there were an option to at least disable content logging for this specific domain, I would happily use mailgung for that purpose.

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  9. Edit Pending Email Queue (GUI and API)

    When an email is submitted with a delayed delivery date (ie using the o:deliverytime' feature.) We have no control over that email after it is submitted.

    However, sometimes there is a need to delete an email message that is in the queue but which delivery has not been attempted yet as the delivery time has not been reached.

    Therefore my suggestion is adding a method that allows us to delete messages from the queue indvidually, or with search criteria. It would be desirable for me if this was an API call.

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

    We’ll send you updates on this idea

    2 comments  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  10. 2048 DKIM

    Support 2048-bit DKIM keys

    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. Testing/Staging functionality

    It would be great to be able to send mail to a sandbox, but not have it sent out. Since, when testing an applications, emails come from a database or are retrieved dynamically, this would enable us to test email functionality from an application without having to create dummy emails.

    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 →
  12. Add settings for "Not delivering to previously bounced address" error

    A few days ago one of our users got into suppression list because Google (for some unknown reason) hard bounced his CORRECT email. We have doublechecked it and it works alright. Each time Mailgun received hard bounce, it adds the bounced email into suppression list. But sometimes innocent users are getting there too.

    So, please add a feature/setting "Hard bounce attempts required to move email into the suppression list", with increasing cooldown, starting from 600 seconds, or something similar. So if it's a wrong email, it will be hardbounced three times and suppressed; it is a result of some bug…

    30 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 →
  13. 24 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 →
  14. Extract the original sender of a forwarded email

    How can I get the address of the original sender, when an email has been forwarded to Mailgun?

    The chain of events looks like this:

    originalSender sends message to someUser
    someUser forwards message to Mailgun
    Mailgun POSTs a parsed message to my server
    Put in another way:

    orignalSender (send)-> someUser (forward)-> mailgun (POST)-> myserver

    The best I could get is doing a regex on the "body-plain" property.
    The problem is that email clients do send this differently. Here are two examples.

    Forwarding from GMail (I added the ...):

    body-plain: "---------- Forwarded message ----------\r\nFrom: Kalle Kalleson <kalle.kalleson@mail.com>\r\nDate: 2014-02-13\r\n ..." …

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

    We’ll send you updates on this idea

    2 comments  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  15. Have api keys specific to domains.

    This would enable finer grained control for development teams that have multiple environments.

    For example, credentials to send from development / sending domains would be different than the ones needed to send from the production domain.

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

    We’ll send you updates on this idea

    21 comments  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support developers - let them view emails sent via your servers (in dev mode)

    It'd be oh-so-useful to use MailGun like http://mailcatcher.me/, http://papercut.codeplex.com/ or http://mailtrap.io/ when developing software - you've got most of the infrastructure in-place already!

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

    We’ll send you updates on this idea

    3 comments  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  17. Template Variable Logic

    Allow logic to be included in templates to make decisions based on template variable data.

    Example:
    {% if %recipient.name% %}
    Hi, %recipient.name%!
    {% else %}
    Hi!
    {% endif %}

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

    We’ll send you updates on this idea

    3 comments  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  18. Provide a periodic (weekly) email update with latest deliverability numbers.

    When my deliverability swings up or down I often don't see it until days or weeks later. A weekly email with my recent statistics would allow me to track it more easily (and give you the ability to upsell static IP's)

    5 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 →
  19. Support the + alias for non-gmail domains

    Currently, the mailbox_validation comes back as false for emails with the + alias trick (joe+alias@example.com) even if the domain is hosted by G-Suite

    Support tells me this is a gmail only feature but that's not true, it works at least for hotmail.com and outlook.com emails too.

    Why can't you just check the MX records to verify if the MX domain is one that supports the + alias trick?

    5 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 →
  20. a feature to suppress using a wildcard or entire domain as this was the method used on a spam mail attack on my site recently. The spam bo.

    The spam bot will create an account, add an item to their wishlist, and then choose to share the Wishlist. As there isn't any limit on the number of email addresses the customer can enter, they are adding in thousands. The bot will then enter a spam message in the message field and then send them out via the website, essentially using it a spam mail service. We suggest a feature to suppress the use of a wildcard or entire domain be available to stop this recurring.

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

Feedback and Knowledge Base