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 want to see the contents of mail log

    I want to see the contents of the email log, I find it convenient if viewing the contents of the email was sent
    Thanks you

    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 →
  2. Node/Meteor devs need Ability to assign Recipient Variables for batch sending

    There's currently no direct way to assign recipient variables for batch sending using Node/Meteor. I'm using the sendRaw method, and I can assign other fields like "to" and "subject," of course, but I can't assign "Recipient-Variables."

    I did some googling and found that other devs have the same issue. It can be done with other languages, but it's desperately needed for Node and Meteor.

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  3. Unsubscribe email based on tag

    For url based unsubscribes you can either do: all, mailing list, or tag. With email unsubscribes there is only an option for all. It would be nice to have mailing list and tag based unsubscribes (ex: %tagunsubscribeemail% and %mallinglistunsubscribe_email%).

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  4. View cities in the campaign's geographic coverage

    Most of my emails are sent to users in Sweden. The geographic coverage is not very useful for me since it only shows statistics for countries.

    I would like to see more details here. I would like to see an estimated city for the recipients. I know the data will not be 100% accurate but it is way better than nothing.

    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 →
  5. Ability to "Replay" a POST for a received message through the Route system

    From the Logs, be able to have MailGun reprocess an existing message through a configured route. This would help debug messages that are posted to routes on incoming mail.

    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 →
  6. accept a body-calendar parameter with an ical string when sending mail

    When parsing meeting requests with mailgun, the ical part comes back as a body-calendar property on the JSON. It would be nice to have mailgun accept the same parameter to construct a message containing a meeting invite

    3 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 →
  7. Allow per-message webhooks

    It would be really helpful if there were a way to specify webhooks at the message level as well as the domain level. (Perhaps the message-level webhook, if present, would override the domain-level webhook.)

    I send some emails from one server, and some emails from another. It would be really nice to be able to have the postbacks go to the right place. I can emulate the functionality by querying Mailgun about each message at intervals, but that's awfully inelegant.

    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 →
  8. Enable Gmail Quick Actions!

    it should be easy to support "One-Click Actions" and "Go-to actions" and would be a really nice feature imo.

    https://developers.google.com/gmail/markup/overview#gmail_actions

    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 →
  9. Send Request Signature as an HTTP Header

    Please consider providing the timestamp, token and signature as http headers. Some frameworks such has JAX-RS provide the ability to validate an incoming request via interceptors. This is difficult to do with form data as it is processed later in the request.

    Ideally this would be done similar to Twilio https://www.twilio.com/docs/security

    Maybe an

    X-Mailgun-Timestamp
    X-Mailgun-Token
    X-Mailgun-Signature

    Based on this we could verify the request before actually decoding the form data.

    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  ·  HTML  ·  Flag idea as inappropriate…  ·  Admin →
  10. POST an Email using a Serial to Ethernet Server

    Most Serial to Ethernet server devices use a POST method similar to the following:

    Serial.println ("POST: http://domain.com HTTP/1.0");
    Serial.println ("Host: domainhost");
    Serial.println(Content-Length: xx");
    Serial.println("");
    Serial.println(Content);

    I have used this method to post data to data logging web sites and would like to use the same method for emailing. Thanks.

    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  ·  Dev Suggestion  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add tracking of email delete event (and a webhook)

    Some gateways can track when a customer deletes an email. This is an important indication of the recipient's attitude towards the email received, especially for marketing emails, but also for other types.

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  12. Detect for multiple emails sent to same person by subject line and time rather than message ID

    Right now, Mailgun will send the exact same email to our customers if the message ID is different. Some of our customers have received more than 150 copies of the exact same email, each within seconds of the last, because the message ID# for each is different, even though the subject line and content of the email is identiical. There ought to be a way for Mailgun to notice when it is sending the same email to the same person over and over again.

    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 →
  13. Forward mail to mailgun server for receiving Emails (instead via MX record)

    Hello mailgunners,
    wouldn't it be a nice possibility to receive inbound Emails via forwarding? We mostly cannot point to mailgun mailserver via MX record. But we could configure the Email addresses in question to be forwarded to some-cryptic-mailbox-name-dedicated-to-our-domain@inbound-or-whatever.mailgun.org.
    Greetings from Germany,
    Tobias Jamin

    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  ·  New Idea  ·  Flag idea as inappropriate…  ·  Admin →
  14. Disablement process needs to be improved

    The account disable process as currently defined is somewhat user-hostile. There are a couple small items that would make the actual experience less disruptive and easier for everyone to resolve. First and foremost, disabling the logs page on the impacted domain seems to be counter productive. I was hoping to be able to investigate for malicious behavior via those logs. Disabling the page means that I had to waste the time of the support staff to help root cause the problem (thanks again Raquel!). Secondly, the quick-pass onboarding process doesn't call out that inbound messages can impact the operation of…

    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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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 →
  • Don't see your idea?

Feedback and Knowledge Base