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!
249 results found
-
"not" operator for mailgun routes
It would be helpful at times to have a "not" operator to go with the mailgun routes. I run across this at times when trying to keep unwanted email traffic off my server. Say I am matching recipients in my routes. For a simple ruleset I can just match the recipients I want, and never see those emails that don't match. For more complicated rulesets I may want to throw out some or all of the addresses I don't want, and then further process the remaining addresses to route them. The ones I don't want are usually most easily defined…
1 vote -
Test with uBlock origins
Unable to login to Mailgun if uBlock origins is enabled. It is necessary to disable for Mailgun domain otherwise exceptions are thrown on in Chrome console and loading icon displayed.,
1 vote -
Ability to Search for Email Templates
It would be great if I could use a search to find template. Right now I am forced to use pagination to find the right template.
1 vote -
Allow setting the open, click, and unsubscribe settings when creating a domain
Currently when creating a new domain via the API, we have to set the open, click, and unsubscribe tracking settings via individual PUTs. Instead, we should be able to create and configure a domain in a single call - that way we don't have to worry about a domain being partially setup.
1 vote -
Allow specifying the DKIM selector during domain creation via the API.
Currently when creating a new domain via your API, you have to post a second request to set the DKIM selector. I think it would make more sense to allow us to specify the DKIM selector (along with anything else) in a single request - that way we don't have to worry about the possibility of a domain being partially setup (e.g. the create domain being successful but setting the DKIM name as unsuccessful).
1 vote -
Provide receiving API keys specific to domains
This would enable finer grained control for development teams that have multiple environments or applications using the same account.
For example, credentials to receive from development / receiving domains would be different than the ones needed to receive from the production domain.
1 vote -
API Changelog
Currently Mailgun does not have any sort of changelog for our API / Infrastructure. This would be helpful as some customers would benefit from knowing when and if things may have been changed
1 vote -
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 -
Mailing List Members, sorting possibilities
Sorting the list of mailing list members by email and/or by name
2 votes -
5 votes
-
Fix DNS records print page
oh my god. Fix the print DNS records button already. The redesign has made it all even WORSE. now the print even includes the sidebar!
1 vote -
Fix Logs (It's completely broken)
Whatever you've done to change the logs report has completely broken it. The pagination breaks the search, sometimes the pagination just doesn't appear, the time filter randomly changes your time range.
1 vote -
ability to assign IP alongside assigned IP pool
Hello.
Here is a use-case. example.com is assigned with some IP pool. I need to add additional IP to this domain without adding it to the IP pool.
Currently, it's not possible. Please, make it possible.thanks.
2 votes -
Email template parameter
For email template parameter. Mailgun has 2 types of parameter one is {{paramname}} and the other is %recipient.paramname%. this design force email template to choose which parameter type should be provided when calling via api. My suggestion is use one {{param_name}} and then if the api client send both global parameter and recipient parameter. when apply you should apply by merge the later with the former.
2 votes -
Include Mailing List Member Variables in Webhook Payload
It would be very very helpful if the variables that we included in mailing list members were included in the webhook payloads. Your documentation makes it sound like they might, and a Mailgun staff person I am working with similarly expected them to. But they do not. This makes it very hard for us to connect webhook payloads (think clicks and opens) with rows in our database after a user changes their email address (so we cannot look them up via the recipient email)
1 vote -
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 -
Visual Builder to HTML
convert from visual builder to HTML view
5 votes -
Sending DNS record instructions via email with one click.
I should be able to send someone the DNS records via email so they can connec it to their hosting.
1 vote -
Filter Logs by sending IP address
Please, add option to filter events by "sending-ip". It can help find/monitor problems with warm-up phase of dedicated IP.
1 vote -
Don't like new dashboard
I don't like the new dashboard graph. I want to see month to date, not a rolling month. Also, when I change the dates for month to date, the totals don't recalculate, so I can't see how many emails have gone out month to date.
1 vote
- Don't see your idea?