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!
15 results found
-
2 votes
-
Edit template subject in UI
I can only set the subject once upon creation, and then I cannot edit it? This seems like an obvious problem
3 votes -
Webhooks - Change user agent to something that identifies Mailgun
Change the user agent for webhooks from Go-http-client to something more specific.
Our system gets lots of requests from user agents identified as Go-http-client and we want to block them as the vast majority are from Bots2 votes -
DKIM validator should be able to validate DKIM records that are split.
Currently DKIM validator does not support validating DKIM keys that are split into two records. This can happen when the DNS provider has a limit of 255 chars per record and 2048bit key is required to be used. Currently I can see that the validator is able to pick up the split record but add a line break between the records and thus it does not match. This should be handled better.
1 vote -
Domain Queue overview
At the moment, one can clear the domain queue. in doing so, it would be nice to see what is actually queued on the domain e.g. emails in the retry window, scheduled sends, etc. Right now it is a black box.
1 vote -
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
4 votes -
Tracking CNAME via API
Return via API the Tracking CNAME when requesting tracking status for a domain.
1 vote -
Custom headers for bulk email
I am writing to request a new feature that would enhance the functionality of Mailgun's Bulk Sending API. Currently, while Bulk Sending allows for efficient email delivery to multiple recipients, it lacks the ability to set custom headers for each recipient individually.
Here's the scenario I'm facing:
- I want to send a bulk email campaign to a list of customers.
- While the email content might be similar, I need to include different custom headers for each recipient (e.g., X-Customer-ID, X-Campaign-ID).
Proposed Feature:
I would like to propose the addition of a mechanism to incorporate custom headers for each recipient within…
1 vote -
Cancel shedule email
Currently we are stuck in situtation where we are scheduled the future email but we can not cancel the the scheduled email.
Ex: We have scheduled 5000 emails which are sent after 2 days. I want to cancel only 5 emails out of 5000 but this simple functionality does not exist by REST API.
Suppricing for any user that I can schedule the email but I can't cancel the specific scheduled email.
Can we have this functionality, please?
2 votes -
Copy/Paste MIME
Looking to have the mime logs in a textbox so it could be copied to clipboard
1 vote -
Date range for Google Postmaster Tools
The integration w G Postmaster Tools is nice to have, though limited in usefulness by viewing a single day at a time. If I log into Postmaster Tools itself there are graphs showing historical values for months, which is much more revealing of things that happen once in a while.
Offering a date-range feature with graphs and warnings would be helpful. Thanks for considering.
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 -
Add Pretext in Visual Builder
Add a option to add pretext in the visual builder
1 vote -
Search should not happen while I'm still typing
On this page, the search is way too over-eager.
I can't even finish typing before it starts searching, which means it performs useless partially-typed searches.
Please let me hit Enter to search instead.
https://app.mailgun.com/app/receiving/routes2 votes -
Provide meaningful delivery status description rather than "Too old"
Provide meaningful delivery status description rather than "Too old"
I'm monitoring webhooks for "permanent" failures and forwarding the "delivery-status" message/description (why are those not unified into a single field??) to my end users. Instead of merely reporting "Too old", please insert the error message from the previous "temporary" failure, so that it becomes clear what the real issue is.
29 votes
- Don't see your idea?