Skip to content

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

23 results found

  1. webauthn/yubikey support

    Please consider adding support for webauthn/yubikey as a 2FA method for admin accounts. It's superior to TOTP, since it's phishing resistant & hardware tokens cannot be stolen without physical access. Also, it is more convenient to use. (When implementing this please be sure to allow users to enroll multiple security keys when enabling webauthn 2FA)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  2. analytics export

    When viewing delivery failures for a particular tag (in the Analytics window), I would like the ability to actually view/Export the logs of those failures.

    Either adding a button that takes you to the logs page with the appropriate filters and then adding an export button there. OR just supplying an export button on the tag analytics page would be good. Preferably the former as that give the most flexibility.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. provide own SSL certificate for HTTPS tracking domain

    Can you please provide an option for users to provide their own SSL certificate for the HTTPS tracking domain. Currently you only support your own Let's Encrypt cert.

    Using their own SSL certificate (from a preferred supplier) is a requirement from one of our enterprise customers.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. Integration with ERP Systems for Streamlined Communication and Automation

    Hi Mailgun team,

    I’d like to suggest adding integration support for popular ERP systems like SAP, Oracle, and Microsoft Dynamics. By enabling direct communication between Mailgun and ERP platforms, businesses could automate transactional emails (such as order confirmations, invoices, and shipment updates) directly from their ERP systems. This would streamline communication processes, reduce manual errors, and centralize email management. Additionally, the integration could enhance data accuracy and provide deeper insights through combined reporting and analytics. A simple API or plug-and-play connectors could make this integration accessible to a wide range of users.

    Recommended ERP: https://www.impactfirst.co/id/erp/software-erp

    Looking forward to hearing your…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New Idea  ·  Admin →
  5. Whitelist / Allowlist per domain

    Disable IP Allowlist feature selectively only for a specific "sending domain".

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. Ability to Search Log Data By Keyword / Phrases

    The new log layout does not allow for keyword / phrase search for email content. Similar to the way that the Subject can be searched for keywords there should be an option to search all log message content for keywords.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    It is computationally "expensive" and non-performant to search non-indexed fields. With that said we are planning a refresh to the Logs UI which would allow for easier filtering based on our tagging, among others. It might be best to start tagging your messages with keywords for better parsing.

  7. Template sending to route

    Hi, I would like to store template in your system so every user can edit them as they please but I would also like to receive that email on my server with route.

    I want to send template to my client and also store that email in our system to show our user that we send them automatic email, so I added our email address as BCC and expected to get rendered template from you but that didnt happend. I can store template on our side but then we cant use your template builder and any change requires code change.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  8. IP whitelist from SPF record

    IP whitelists for big providers a kept in DNS SPF records.
    In case of big providers they are really long lists of CIDR, and it would be best if Mailgun could automate their lookup and update.

    Example:

    1. Instead of CIDR, use SPF: google.com. To do that we need to perform multiple DNS lookups, since any SPF record may contain "include: $DNS_DOMAIN".
    $ host -t TXT _spf.google.com
    _spf.google.com descriptive text "v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com ~all"
    
    $ host -t TXT _netblocks2.google.com
    _netblocks2.google.com descriptive text "v=spf1 ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 ip6:2607:f8b0:4000::/36 ip6:2800:3f0:4000::/36 ip6:2a00:1450:4000::/36 ip6:2c0f:fb50:4000::/36 ~all"
    
    

    The same for all other _netblocksX.google.com

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    declined  ·  0 comments  ·  Dev Suggestion  ·  Admin →
  9. API access to Authorize Recipients

    Look to include the ability to use the API to add authorize recipients

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  10. Restrict Sending to Recipients

    Feature to restrict outbound sending to select recipient domains

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  11. Inbound Webhooks

    Customer would like to request that we have webhooks for inbound failed emails.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. EU Sandbox domain

    Sandbox domain for the EU region

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New Idea  ·  Admin →
  13. IPv6 support

    We are running out of IPv4 addresses, and while the world is (slowly) working on supporting IPv6 (which is also an internet standard since 2017) Mailgun remains behind.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. Include "originating-ip" within accepted webhook payloads

    Include "originating-ip" within accepted webhook payloads

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thank you for your feedback. Our API response includes a message.id to specifically tracked which client side IP sent the request. Our webhook payloads include that message.id for later parsing/analysis. Adding niche fields to payloads can impact processing time.

  15. add timezone to logs

    Please display the time zone alongside the timestamp in the logs section.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  16. Allow other per-domain API calls for domain sending keys

    Allow other domain-based operations such as retrieving events for domain sending keys. It's nice to be able to have sandboxed API keys per domain for sending but it would be more powerful if it also allowed doing things like querying events for that domain, that way you could have one account with development/QA/production domains each with their own keys restricted to those domains.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    We have expanded API keys to allow for multiple API keys on account with RBAC restrictions:


    https://documentation.mailgun.com/docs/mailgun/user-manual/mg_security/


    And now allowed for CRUD to be available via public API:


    https://documentation.mailgun.com/docs/mailgun/api-reference/openapi-final/tag/Keys/


    No current plan to expand on domain scoped keys beyond sending.

  17. where to find the smtp password in new ui?

    where to find the smtp password in new ui?

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks for the feedback here. We removed the ability to view SMTP passwords in our new app, which was in preparation for hashing SMTP passwords on our platform. Once move to hashed passwords (coming soon), we will no longer be able to retrieve them at all. These changes are being made in order to meet security best practices to avoid any possibility of leaking customer’s credentials should we ever encounter a compromise. This is an instance where we’ve decided to make the sacrifice of usability for the sake of security. All this to say that we will not be re-instating the ability to view SMTP passwords.

    We’d recommend using a password manager such as LastPass to help with password management across apps/sites.

  18. Give us back our passwords....

    Hey kids, I know this horse is dead and I've been beating it pretty hard today but taking away the plain text password field for the domains and then making us learn the API to retrieve the password is a little...idiotic. I really have other, more pressing things to address today than fighting with your tech support to retrieve a password I used to be able to look up by logging in...

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks for the feedback here. The changes we made were in preparation for hashing SMTP passwords on our platform, which means we will no longer be able to retrieve them at all. These changes are being made in order to meet security best practices to avoid any possibility of leaking customer’s credentials should we ever encounter a compromise. This is an instance where we’ve decided to make the sacrifice of usability for the sake of security. All this to say that we will not be re-instating the ability to view SMTP passwords.

  19. Track open events also if images are blocking

    Part of my recipients are blocking images by purpose, it's a principle.
    They won't change it.
    As a result, the open event is not fired for those recipients.
    I expect Mailgun to enable me track ALL OPEN EVENTS, regardless to the recipients settings.
    Thanks!!!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  20. 20 and 40 USD plan

    I would like to pay, but not 79 USD. What about 20 or 40 USD. Computers can do anything, when humans tell them to ..
    regards satisfied from Denmark

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Billing  ·  Admin →
    declined  ·  suzzell responded

    Hey there,

    Thanks for adding your suggestion to UserVoice! Although your suggestions are always valuable, unfortunately we will have to decline this one.

    We strive to keep our prices at market rate for the specific services we offer. We also offer a free plan that gives you 10,000 emails and 100 email validations for free each month. The $79 plan that you mentioned pays for 100,000 emails, 1000 emails validations, and a dedicated IP monthly.

    If you don’t plan on sending that much, please take advantage of our Concept pay-as-you-go plan which is free until you surpass 10,000 emails and/or 100 email validations each month. Please contact our support team via support ticket if you need any further clarification.

    Thanks again for your support and feedback!

← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base