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!
139 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
-
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 -
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 -
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 -
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 -
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 -
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 -
2 votes
-
Ideas for improving Api / Quicklook / overall experience
Hi, I have a few ideas for improvement. For batch sending emails via API, please add a safe mode, where the request is rejected, if not every recipient address has a matching entry in recipient-variables. I just happened to send out a bunch of emails that would only show the %recipient.name% placeholder, because of an unintended whitespace in the "name " field of the recipient-variables. This is a very sad experience and could easily be prevent with better tooling.
But even better: Just take the recipient name from the recipient email address: -F to='Recipient Name recipient@email.com' Why do I…
2 votes -
mailing list by domain
Mailing Lists displayed by domain
1 vote -
More than 3 URLs per Webhook event
Customer would like the ability to have more than 3 URLs per event type for webhooks
2 votes -
Rename templates
Allow us to rename templates
7 votes -
Delete disabled domain
be able to delete a disabled domain.
2 votes
- Don't see your idea?