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
-
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 -
Capturing new idea for customer
I would like to Mailgun platform to support this feature
1 vote -
New Idea
I would like to see this feature implemented in Mailgun
3 votes -
New Idea on Behalf of Customer
this is a description of a feature request I am posting on behalf of a customer
1 vote -
API for returning user/admin info - Mailgun UI
Would love an API for returning information about the management users for the Mailgun account.
I'd like to be able to query to get a list of "what employees have mailgun accounts? what role (admin etc) they are assigned to? is 2FA is configured?"
Would like to have the capability to get those details programmatically from Mailgun on a recurring basis.
Having this via the API would be extremely beneficial.
1 vote -
Configuration options for .ics files when using a mailgun template (support for Outlook)
Outlook cannot automatically read the default way Mailgun attaches .ics attachments to emails. (Gmail can, but sadly, outlook can't).
We would like to (a) send an email with a mailgun template with (b) a .ics file attached that (c) gets added correctly to a recipient's calendar.
Using the normal
messagesendpoint of the API with a template, we can get (a) and (b), but not (c). If we construct our own MIME message, we can get (b) and (c), but not (a).Technical details:
Mailgun attaches .ics invites in the following way:
…Example from mailgun (using a template): --1635db27c5b9dd89a16962b725b259cd7c88d10b65664ba25a3bda4e481a Content-Type:1 vote -
1 vote
-
mailing list by domain
Mailing Lists displayed by domain
1 vote -
Allow plus addressing (subaddressing) recipients with the sandbox domain
I kindly request that you consider implementing support for parameterized email addresses within the Mailgun sandbox. This enhancement would greatly improve the testing experience and allow for more comprehensive email testing scenarios.
3 votes -
Show date in correct format
Dates appear in the stupid yankie format which is really confusing if you're not from the US. Profile setting are set to use ISO dates.
Shame you give the UK date format as an option - %d/%m/%y1 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 -
Transfer domain between Accounts
Ability to transfer domains while retaining historical data and settings.
3 votes -
1 vote
-
Set a default DKIM selector for the account
Every sender domain you add currently gets a random DKIM selector such as email.dmarc, mta.dmarc or web._dmarc for example. However, it would be easier to have it so that you can set a default on account level for every new sender domain so it is always the same by default. Offcource you then can change it if needed.
1 vote -
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 -
1 vote
-
Allow Subject Field to be Removed from SAML Request
Currently our SAML response includes the automatically includes the Subject field. This is a pain point for customers wit SAML providers, such as Duo, who do not support this field.
1 vote -
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
- Don't see your idea?