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. Add regex capabilities to search boxes in the website

    Especially:
    - mailing list recipients
    - logs

    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  ·  External Integrations  ·  Flag idea as inappropriate…  ·  Admin →
  2. View in browser like mailchimp

    There should be a feature emails to contain the "view in browser" feature.

    27 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 →
  3. Notify account holder when reaching max routes limit

    The maximum limit for routes is 5,000. Currently Mailgun does not notify you when you're close to the limit. This is especially risky if you create lots of routes programmatically via the Routes API.

    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 →
  4. The failed reason value passed to webhook and classfied in Mailgun event log are different

    I find the failed reason value passed to webhook and classfied in Mailgun event log are different.
    e.g. we just can get the reason value like "hardfail" or "old" from webhook, but we use Event api can get "bounce", "suppress-bounce", "old", "suppress-Complaint", .... these many reasons. so we want Mailgun can make the reason values are consistent in both ends.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Forwarding of auto-responses sent to the return-path

    Delayed bounce messages sent to the return path are correctly processed by Mailgun (if the MX records are set).

    But other kind of messages sent the return path address, like vacation or out of office auto-responses are simply ignored and dropped.

    It would be great to be notified when an auto-response is sent to the return path address, by forwarding and/or using a webhook.

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

    We’ll send you updates on this idea

    4 comments  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide an option to not re-sign emails when forwarding

    Currently, Mailgun re-signs emails using DKIM and modifies mail headers when forwarding incoming mail. This causes Gmail, and possibly other spam filters, to give the email more trust than it should have. Could an option be provided to forward the existing envelope, without re-signing?

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add the ability to set a daily or hourly cap on outgoing messages

    This would be a useful safety feature in the event that something goes wrong in user code that is pushing messages thru mailgun.

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add the event's timestamp in addition to the webhook timestamp

    The time of the event is important to us and if the event time is only available from the Event API, then we will have to make additional calls to the Event API for EVERY single notification(delivered, failed, open, click etc), which may add significant load to our (and probably yours) server and network.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow sending text/calendar as a multipart/alternative format so Outlook can accept my invites

    We've been sending ics files as attachments, but the only way that Outlook will recognize them as calendar events is if you send it as a multipart/alternative. The Mailgun API only supports text or html, which means I have to build a MIME email to send it.

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

    We’ll send you updates on this idea

    0 comments  ·  Internal Integrations  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add segmenting options to the list sending API to make it easier to send to a portion of the list

    Add some options to segment list sending, or create temporary lists based on number of list members.

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add a throttling to allow for list sending to be sent over longer time period

    When sending out to a large list, a user may sometimes wish to throttle the sends over a time period to avoid having too many responses or heavy web traffic all hitting at once.

    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 →
  12. 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 →
  13. HTML mailing list variables

    Have the ability to put HTML into the mailing list template variables.

    e.g.

    {

    html : "<strong>bold text</strong>"
    

    }

    <html>
    <body>
    %recipient.html%
    </body>
    </html>

    Gets transformed into:

    <html>
    <body>
    <strong>bold text</strong>
    </body>
    </html>

    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  ·  Flag idea as inappropriate…  ·  Admin →
  14. Provide option to send Non-Delivery Reports to the original Sender

    Mailgun bounce processing works great when a single sender is sending email to a broad audience. It does not work well when there are many original senders each with their own list of contacts.

    Scenario:
    - Company with 10 to 1000 employees.
    - Company switches from a traditional in-house mail solution to Mailgun for all outgoing email.
    - John, a typical employee in the organization, sends email to a customer, but spells the address wrong.

    Traditional in-house system behaviour:
    - John would get a Non-Delivery Report letting him know of his mistake. John would fix his mistake, and re-send the…

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

    We’ll send you updates on this idea

    8 comments  ·  Feature Enhancements  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add "block" as a third option in spam_action with the Domains API.

    Add "block" as a third option in spam_action with the Domains API.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow system-enforced BCC by domain

    Provide a mechanism to BCC or forward a copy of every message to a mail archival service (smtp address). This might be applied as a ROUTE rule or a separate facility.

    10 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. 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 →
  18. Automatic conversion of HTML to text for outgoing messages

    If no text portion of an email is submitted, automatically make one from the html portion. This should help with deliverability. The parse incoming seems to do this now according to the documentation so you may already have routines to do this.

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

    We’ll send you updates on this idea

    1 comment  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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!

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  20. Force delivery address to aid development (per-domain)

    When developing, I want to capture all emails - and have peace of mind that no one can possibly be spammed.

    Some web frameworks allow you to force the delivery address for emails sent in dev mode; this is very useful (particularly when debugging problems on a live dataset) to ensure no one is spammed.

    However to be really confident we need to do it server-wide. it's possible to do this via exim/postfix, but our devs aren't exim/postfix gurus and we've found it error prone (even with templates/docs)

    Being able to plug in a Mailgun domain's SMTP details and know…

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

Feedback and Knowledge Base