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!
232 results found
-
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
1 vote -
1 vote
-
Some feedback after almost a year of use
Changing the date in the analytics view doesn't update the metric numbers in the tag breakdown.
In the analytics view, three metrics are highlighted at the top: delivered, open, clicks. These should be unique opens and unique clicks. The total number of opens is essentially always irrelevant.
In the engagement view for a specific tag, you can't see the number of delivered emails. The absence of this metric makes the tool difficult to use.
In the reporting section, the line chart displays the open rate but not the unique open rate. This is ineffective because some people open the same…
1 vote -
Add support for UTF-8 characters in domain names
Allow domains with non-ASCII characters, as many mailbox providers are nowadays supporting them. Alternatively, add full support for IDNs, which is currently partially functional (for example, domain validation works, SMTP credentials creation doesn't work).
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…
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 -
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.
2 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 -
api for IP stats
Here Using Domain API, I can track the volume which sent out in last 24 hrs so this helps me to track the sent volume of a particular domain and maintain a separate data related to the domains volume using this API
def getstats():
return requests.get(
"https://api.mailgun.net/v3/YOURDOMAINNAME/stats/total",
auth=("api", "YOURAPI_KEY"),
params={"event": ["accepted", "delivered", "failed"],
"duration": "1m"})Likewise I would like to track the volume of individual IP of last 24hrs for my tracking purpose but unfortunately their is no IP available for this so that is why requesting here to provide an IP related to track…
1 vote -
Multiple Webhook Signing Keys
The HTTP Signing Key for Webhooks is currently limited to a single key per account. Some customers would benefit from having the option to create multiple signing keys.
1 vote -
Delete disabled domain
be able to delete a disabled domain.
1 vote -
2 votes
-
Email Admins when new SMTP or API credentials are created
This is a fraud prevention action. We had multiple SMTP credentials created then fraudulently used. If we got emails whenever they are created we would know they weren't done by us true admins.
2 votes -
update template portion in documentation
It needs to use 't:version': to reference the version. I found this on another website but it would be helpful to have this added to the main docs page
2 votes -
Sent emails threshold reached notifications
Email Notifications when send threshold is met. (i.e. send an email when > 5000 emails are sent in 1 day). Every once in a while we have a bad actor that uses our system to try to send out spam emails in bulk. This causes the sent emails for that day to spike way above normal. Would be nice to have alerts for when this happens so I can investigate right away, rather than just see it happened in the past the next time I log in to Mailgun, which isn't often.
1 vote -
Allow for duplicating templates
Hi,
Please allow duplication of templates, at the template level.
1 vote -
Webhook security
Webhook security
I am concerned about the security risks involved in using your service. I would appreciate it if you could consider implementing some of the following suggestions:
- Use a more specific user agent than "go-http-client" to identify your requests.
- Provide a list of verified IP addresses that you use to send webhooks, so that I can restrict access to my server with a firewall.
- Use a dedicated IP address or a domain name to send webhooks, instead of a shared one.
- Then you might even verify yourself to cloudflare (to be recognized as known bot)
These measures would greatly…
2 votes -
Support for Retina Files in Template Builder
The visual template builder currently does not support retina images, and they are treated the same as any other image. This causes retina images to appear blurry due to the high pixel content of retina images
1 vote
- Don't see your idea?