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!
14 results found
-
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 votenot a priority
-
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 voteThe new Tags experience offers quick links to both reporting and logs that allow for export of the data related to your tag.
-
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.
-
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 -
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 -
Inbound Webhooks
Customer would like to request that we have webhooks for inbound failed emails.
1 vote -
Include "originating-ip" within accepted webhook payloads
Include "originating-ip" within accepted webhook payloads
1 voteThank 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.
-
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.
- Don't see your idea?