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. API: possibility to filter events based on our user-variables values

    Currently, in the API, there is no way to filter the Events via our user-variables. They get return in the result but still they aren't available on the Filter Field list described on the documentation.

    It could be really cool to be able to do so!

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  2. Expand the stripped-text feature to other languages, e.g. german

    I'm happy to help and I'm glad you open sourced this library, but please let pull requests in and ship it to production :)

    https://github.com/mailgun/talon/pull/23

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  3. make event filtering case insensitive

    To clarify a bit: say we have a route matching "foo-bar@domain.com" with a store action. Mails coming in for FOO-BAR@domain.com and foo-bar@domain.com will all get stored correctly.

    If we then query the event API for incoming mails for "foo-bar@domain.com" we will not see the mail for "FOO-BAR@domain.com". It seems that the event filtering _is case sensitive_. So we need a query for each possible capitalization in order to see all possible incoming messages.

    (We tried using regular expressions with a flag to make it case insensitive, but it seems that regular expressions are not…

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 →
  5. 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 →
  6. Provide dashboard access email validation logs

    Having the ability to view or download a date range of the email validation logs would in debugging and identifying abuse of the service. Currently I have to request from your support team every time I need them and the logs entries are not formatted with date/time stamps.

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  7. role-based multi-user access restricted by domain

    We were excited to discover the multi-user capability and are even more excited for the possibility of restricting access based on role and domain.

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow Mailgun account email to send emails to mailing lists from Outlook

    Allow Mailgun account email to send emails to mailing lists from Outlook without having to change the outgoing servers. This would be a step between needing to be authenticated (Read Only) and Allowing people in the mailing lists to post things.

    This way the owner of the mailgun account can send emails from Outlook to their mailing lists, but no one else would be able to do this.

    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  ·  External Integrations  ·  Flag idea as inappropriate…  ·  Admin →
  9. Log clicks on a per link/URL basis

    Log clicks so that it is viewable / searchable in the stats. An email might have different URLs and it would be useful to see what URL the user clicks on.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  10. Expose Sending IP Address(es) assigned to domain in API (and website interface)

    Currently there is no convenient way to get a list for each of your domains what sending IP address(es) are assigned to them, the only way is using the website drill down into each individual domain's details.

    Exposing the IP Address(es) of each domain in the /domains API endpoint seems like a good solution.

    Additionally being able in the website to enter a sending IP address on the domains listing page and it would show all the domains with that sending IP address assigned.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  11. Error, fail, bounce and reply mails back to sender (application)

    Bounce mails dont came back to senders e-mail account, tracking is impossible without API. Routed e-mails need reply information, feature will make Mailgun perfect.

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

    We’ll send you updates on this idea

    2 comments  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  12. Decrease retry interval for Mailgun server errors

    When an email is not sent due to a Mailgun server error (e.g. 499 MX server resolution error), the retry should be much shorter than 10 minutes. Errors that are very likely transient (such as DNS resolution of a Gmail server), should be retried immediately and any error not resulting from a rate-limit should use a geometrically increasing retry interval, rather than the 10-10-15-30... interval progression.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  13. Do not send duplicate email to same recipient in different list

    Recipient in different list would receive only one copy of message, this is a basic ESP feature that everyone supports. But currently if a address is on more than one list than recipient will receive messages that are sent to each list, the only way to avoid this is to remove the email from other list.

    Please add a workaround for this basic ESP feature.

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  14. Set up a way to archive outgoing emails.

    We send a lot of emails that are custom to the individual and would like a simple way to save them. Our email generators are on 20 or so amazon instances and we spin up and shut them down as needed. So we have 3 options: save the file and hope to dl before the box dies, send bcc to a stable box, or post to a webhook on a stable box.

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

    We’ll send you updates on this idea

    2 comments  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  15. Specify Outbound IP on Submit

    Would be great to define the outbound IP address (of those in my pool), for which emails will deliver, upon submitting to the API.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  16. Auto-detection feature for affected IP-addresses

    A problem with sending email with Mailgun is: many Mailgun users are using the same IP-address. When another user is sending spam, all emails from that IP-address to Hotmail/Live addresses are blocked, until Mailgun has assegned a new IP-address after a couple of hours (when I create a ticket).

    My idea: an automatic affected IP-address detection. When Microsoft returns an error "bad IP reputation", then automatically assign a new IP address and resend the failed emails.

    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  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  17. Please Turn of CAPTCHA-I'm-not-a-Robot for Those with 2FA

    Hi Guys:

    I have 2-factor switched on with you... super-hi secure. I don't even allow the texting version - Google Authenticator only, so my Mailgun account is really very secure.

    However, for the best of reasons, you've implemented the CAPTCHA-I'm-not-a-Robot step where one has to recognize cars, mountains, traffic lights etc... BEFORE the 2-step. It's an annoying extra step that no other site requires for folks with 2FA enabled.

    Can you please get rid of it for those of us who've already done the secure thing and switched on 2-step please?

    Happy Holidays...

    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 →
  18. SIngle SMTP Sign-In for multiple domains

    We run a platform that sends mail from 50+ different domains. With a former provider, we had a one-stop SMTP authorization and a per-domain signature configuration (DKIM, SPF, etc.). Now, we need to code around this and figure out what credentials to use for which sending domain. I know it is still possible to send on behalf of another domain, but then outgoing e-mails won't be properly signed with DKIM.

    The same goes for the reporting, as I gather from other user's comments. A single point of entry to download information for all domains would be more practical than build…

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

Feedback and Knowledge Base