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!
17 results found
-
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 voteThere is a process to host a 3rd party cert via CDN - https://help.mailgun.com/hc/en-us/articles/360011566033-HTTPS-Tracking-Links
This would be the only available option in this case.
-
Whitelist / Allowlist per domain
Disable IP Allowlist feature selectively only for a specific "sending domain".
3 votes -
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 votesIt 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.
-
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:
- 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 -
API access to Authorize Recipients
Look to include the ability to use the API to add authorize recipients
1 voteNo need. We have recently released a new Free plan that allows for sending to any recipient via your own custom domain.
-
Restrict Sending to Recipients
Feature to restrict outbound sending to select recipient domains
1 vote -
EU Sandbox domain
Sandbox domain for the EU region
1 voteWe have released a new Free account for our dev audience to allow for testing on their own custom domains and without authorized recipients.
-
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 votesIPv4 still plentiful. You won't see any movement across ESPs until the major players like Yahoo/Google make it some facet of their guidelines.
-
add timezone to logs
Please display the time zone alongside the timestamp in the logs section.
2 votesWe recently released our updated Logs experience (Now found in Reporting).The timestamp visible in logs is taken directly from the timestamp on the event in UTC as indicated in the UI.
-
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 votesWe 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.
-
where to find the smtp password in new ui?
where to find the smtp password in new ui?
9 votesThanks 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.
-
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 voteThanks 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.
-
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 voteThis isn’t currently possible based on the technology used to track opens in an email message.
-
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 Denmark2 votesHey 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!
-
Mailgun Invoicing: breakdown messages by domain
Each month we receive an invoice and on that invoice is the number of messages for each month. We have multiple domains and we need to know the total amount per domain.
Something like:
domain1: 3000 messages
domain2: 6000 messages
domain3: 6000 messages
total: 15000 messagesOur accounting people need this information, so including on the invoice is the best way for them.
You could just have the invoice the way it is today and add a second page that breaks it down by domain.
12 votesThanks for the feedback here. Unfortunately this isn’t something we’ll be able to do. Some clients have 100’s of domains, which would make invoices incredibly long. We also don’t send usage on a domain level to our billing system.
-
Allow text/calendar MIME for .ics attachments sent through REST API
I'd like to send .ics (iCal event) attachments through the REST API. For eMail clients such as GMail or Outlook to recognized those attachments as event invitations they have to be sent with a text/calendar MIME type.
1 voteThis is currently possible and supported by our API.
-
Block invites from Facebook, Twitter, Google+,...
Ability to block invites and invite-reminders from popular social networks like Facebook, Twitter, Google+,... Many users send out invites to join these networks to their whole address book. These emails end up getting parsed and added to our applications.
2 votesThese emails can be blocked using our Routes feature.
- Don't see your idea?