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!
57 results found
-
Allow for dynamic domain URLS when forwarding Email Routes
for receiving emails, I want to create a catchall route that can route to a specific client site based on email address, like so:
match_recipient("(?P<user>.?)@(?P<domain>.).mysite.com")
and then in "forward" put:
https://\g<domain>.mysite.net/api/emailrecieving
This would give us infinitely less routes to maintain.
3 votes -
UI tooltip to advise that verified records are from initial domain verificatoin.
Display tooltip in the UI showing that verified DNS records are going to be based on the records present in the DNS at the time the domain was verified.
2 votes -
2 votes
-
Add Plan Based Message Limit Notifications without needing to add a custom message limit
This suggestion is to proactively alert users when certain sending limit checkpoints are reached in order to prevent unexpected overages.
2 votes -
Provide audit logs for suppressions on the mailgun UI or API endpoint
For martechs and major corporations that are using Mailgun. There will be multiple teams handling the email solutions. Hence, having an audit logs for suppression lists, will allow corporations to see who and what and when was the data entry removed or added.
2 votes -
Pagination is incomplete
Please add the number of records being shown on the pagination. Currently, there is no way to see how many rows are in a table.
2 votes -
Testmode per domain instead of via parameters
At the moment you can test with setting the 'X-Mailgun-Drop-Message' or the o:testmode
This is working fine but i think it is still kind of 'tricky'
We used other tools than mailgun before and there was it a option to set a complete domain in testmode.
So this will always prevent you from sending emails when not intended2 votes -
Visual Builder Updates
The visual builder is great for general design, but is missing a couple of features I think would be great for transactional emails. First would be a way to create a "component" with multiple basic design elements. A component would be a group of titles, text, image, or other elements. The component can then be dropped multiple times and have its own variable references. The second is table support. Pulling from variables, it would allow for the building of tables on a referenced variable (that contains array of variables.)
These are things that can be done via handlebars and HTML…
2 votes -
Subaccount performance categorization
it would be very helpful to see if our accounts are also categorized into performance groups, such as high performance, medium, low
2 votes -
Prevent sub-domains from being added to a Mailgun account if the root domain is already added to an account.
Prevent sub-domains from being added to a Mailgun account if the root domain is already added to an account.
2 votes -
Delete Tags in Bulk
Presently, via the UI, users are only able to delete tags 20 at a time. Currently, lacks the ability to delete all tags at once.
2 votes -
Add Proofpoint RBL list to blocklist monitoring
Recently proofpoint blocked mailgun IP ranges and our dedicated IPs were part of this range hence all of our clients using proofpoint were blocking emails from our dedicated IPs. This issue was identified only after our clients started complaining after 2 days when they did not receive any emails for 2 days and missed lot of important ones. This is not good since our client had to inform us about this even though their email provider blocked our IPs but there should be some way for us to identify such issue. We do have blocklist monitoring enable on our account…
2 votes -
A more in-depth permissions / roles system with the API
We need a more in-depth permissions management system with the API. Right now, only the admin role can create SMTP credentials. We are not comfortable having an admin API key floating around, that if someone malicious is putting his hand on it, he could be able to delete every existing SMTP keys / users. A permissions system instead of roles could be a great idea. If it's too complicated, you can create a new role for adding SMTP credentials only. Or maybe simply add the permission to create keys, but not delete, to the developers role.
2 votes -
Deactivating users instead of deleting them
When attempting to revoke access to past employee's account, I was expecting the ability to deactivate an account, especially since the user listing also mentions user status.
Deactivating is generally a better practice since it retains user information and history for auditing purposes. It would also allow temporary suspending access without having to recreate the user.
2 votes -
Suppress entire recipient domain
Have the ability to suppress all sends to specific inbox provider/domain.
2 votes -
Modify Retry Schedule
It would be nice if we could modify the current retry schedule to be lower then 8 hours.
2 votes -
Specify what tag or tags a recipient wants to unsubscribe to when email has more than one tag.
Specify what tags a recipient wants to unsubscribe from when more than one tag is applied to an email.
2 votes -
Add template name as a query parameter in the API.
Add template name as a query parameter for getting templates based on their name through the API.
2 votes -
Scheduled Report Email To Have Report In Body Of Email
Customer would like to have the scheduled report email contain the actual report in the body of the message as opposed to having to download a file.
2 votes -
Make tracking domains reachable via IPv6
Currently tracking domains are only reachable via IPv4 addresses
2 votes
- Don't see your idea?