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
-
Configuration to Send or Restrict emails from specific SMTP User
The requirement to send emails to only specific domains under the particular SMTP user.
For example, an application using Mailgun configuration will trigger emails to @gmail.com, @yahoo.com, @hotmail.com, etc., domains.
But Mailgun needs to allow send emails only to @gmail.com and restrict sending emails to other domains.Mailgun should have a feature to configure domains for both restricting and allowing for sending emails under a particular SMTP User.
4 votes -
User Permissions
Would like the ability to have users only access certain domains. Example if I had 5 domains on the account I would like to have user x only able to see domain A and not b-e.
4 votes -
Use Recipient Variable without batch sending
Could Mailgun provide some option to explicitly disable Batch Sending, or not batch send if the only Recipient Variables being used are related to one-click unsubscribe headers?
3 votes -
Sort domains list by default
The domains list should be sorted in some meaningful way. At least sort it by domain name alphabetical. Or even better give us the option to sort by other columns like delivered or accepted
3 votes -
New Idea
I would like to see this feature implemented in Mailgun
3 votes -
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 -
Transfer domain between Accounts
Ability to transfer domains while retaining historical data and settings.
3 votes -
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 -
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 -
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 -
Create Sending API Keys via API
Currently sending API keys can only be created through our control panel. Some customers would like to be able to create these sending keys programmatically via our API.
3 votes -
Throttle mailing list sending for Comcast and other ESPs
hey Mailgun,
We have been told by Comcast to throttle our sending to Comcast addresses. They want us to send in batches.
Here's the thing: we are using your mailing lists feature! YOU, not US, are in control of how quickly those emails go out. Can you please dial in throttling/batch sending for mailing lists for Comcast and any other ESPs that require it? Our understanding is that this is a general Comcast policy and not specific to us.
As it is, we are left to resort to contorting your platform to do what we want it to do, increasing…
3 votes -
3 votes
-
API access audit logs
API Access Audit Logs
Please provide audit logging for any and all API calls. Results should include
- Date/time
- Source IP
- API called
- Account used
- Query header
- Authentication Success/Failure3 votes -
Exclude bots activity from tagged analytics
Exclude bots activity from sending analytics (for tagged emails)
3 votes -
Allow Route Filter on Email Body
Currently our routes only support filtering for the message header, and not the body. Being able to filter by specific body content would be helpful.
3 votes -
Custom Variables in visual builder
Feature request:
Add the custom variables in the visual template editor in the coding examples, like in the old HTML editor.
It is very hard to keep track of inserted variables now, as you have to visually scan for {{variable}} in the editor.The current visual editor only shows:
-F h:X-Mailgun-Variables='{"test": "test"}'3 votes -
Support for .eml file as attachments
If a user sends using the "forward as attachment option" to a route, the attachments within the forwarded message are not read by the inbound processor because they are nested within the .eml files.
3 votes -
Allow link tracking on URLs longer than 1000 characters
Please add support for click tracking on URLs longer than 1000 characters. As far as I can see this limitation on link-rewriting is not documented. Our SSO solution generates links in the 1000 - 1300 char range that contain a base64 encoded JWT. All browsers support at least 2048 characters so it would be obvious to allow as least as many characters for the rewrites.
/David
3 votes -
Implement mobile version of UI
Please make your web page more mobile friendly. It's impossible to navigate currently. Really small changes would go a long way if you can't commit to a fully mobile integration. The functionality of your product is great, but attention to these kinds of details on the frontend needs improvement.
3 votes
- Don't see your idea?