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!
242 results found
-
Log Retention Period Longer Than 30 Days
Currently our log retention period has a maximum of 30 days. Having a longer message retention is something that many customers would benefit from
6 votes -
Transfer domain between Accounts
Ability to transfer domains while retaining historical data and settings.
3 votes -
user permissions to individual domains
Currently, there is no way to allow developers access to test data only. I don't want to give them access to production data unless I absolutely have to. It's full of sensitive data. So the only "solution" is to set up the whole Mailchimp service 2x, to have everything duplicated.
Please come fix this. Just extend user permissions so that one can select a checkboxlist of domains they can access across the entire dashboard, api.
Take Cloudflare as an example for inspiration.
1 vote -
1 vote
-
1 vote
-
Specific error message when creating too many routes
Add a more specific error message when you create too many routes for your current plan (i.e. flex plan maximum is maximum of 5 routes). Otherwise, you are using trial-and-error for many hours to find the issue (because the current error message is: Couldn't create the route)
1 vote -
Webhook security
Webhook security
I am concerned about the security risks involved in using your service. I would appreciate it if you could consider implementing some of the following suggestions:
- Use a more specific user agent than "go-http-client" to identify your requests.
- Provide a list of verified IP addresses that you use to send webhooks, so that I can restrict access to my server with a firewall.
- Use a dedicated IP address or a domain name to send webhooks, instead of a shared one.
- Then you might even verify yourself to cloudflare (to be recognized as known bot)
These measures would greatly…
4 votes -
Unique user-agent name for webhook requests
Ability to change the user-client name for webhook POSTs. For instance, "Mailgun Webhook API" or something similar.
1 vote -
Confusion Around Error "Destination must be publicly accessible" When Adding Route
When adding a URL for a route, if the URL is not publicly accessible we will return an error of "Failed to create route". When looking in the dev console, only then do we see that the error is related to the URL not being publicly accessible. This can be confusing to users as they are not given the error directly
3 votes -
Make a whole domain authorized for receiving emails send through sandbox domain
Instead of specifying individual authorized recipients, the user can provide a domain so any email that belong to that domain should be authorized to receive emails from sandbox domains.
1 vote -
Outbound routing
For developers, creating a application, it would be nice to route outbound messages to another email address. This is often needed in test situations, when you want to test your application and check if you receive emails. This mechanism would help to ensure no test mails will send to real user. In my case the outbound rule would be: All emails will send to selected email addresses.
2 votes -
5 votes
-
Please bring back short usernames -- why minimum character requirement?
In the past we could have short usernames, but could not manually set passwords (causing issues with printers etc). Now we can manually set passwords (huzzah!), but now usernames are required to be 5 characters long. Why is this?
I use initialisms or initials, so I have a bunch of old legacy two-letter usernames, but can not create new accounts with two letters. This inconsistency is causing issues with code that relies on standard naming conventions, and I am having to hard code around the issue, which is a terrible thing to do.
3 votes -
Retention Parameter in API
We're using the API to add a domain
https://documentation.mailgun.com/en/latest/api-domains.html#domainsIt doesn't give us the option to set a retention period. We require that all our domains are added with a 0/zero retention
2 votes -
Sender and Recipient Address Field From Forwarded Email
Currently, when you retrieve a stored message from a forwarded mail, both sender and recipient fields are filled with the same domain address. It would be nice, it there was an easier way to obtain both address. Right now, you would have to extract the addresses from the body_plain string.
1 vote -
Reporting page
I would like the reporting page to allow any recipient domain, not just known ESPs.
1 vote -
limit a user's access to domains
We need to be able to limit users' access to domains based on their access level. Only some users are privy to all information that goes through a domain under a Mailgun account. A more comprehensive ACL system is needed to eliminate the need for multiple accounts to limit people's access to data.
1 vote -
Have the ability to turn off SMTP sending for the domain if only API is being used.
If we are not utilizing SMTP but only API we want the ability to turn off SMTP so that the server settings can't be used.
3 votes -
Capturing new idea for customer
I would like to Mailgun platform to support this feature
1 vote -
New Idea on Behalf of Customer
this is a description of a feature request I am posting on behalf of a customer
1 vote
- Don't see your idea?