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!
111 results found
-
Support UTM Parameters and Google Analytics Integration
Support UTM Parameters and Google Analytics Integration.
Other competitors offer this or integration with solutions.
3 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 -
Resend Failed Webhook Data After Retry Schedule Expires.
Resend Failed Webhook Data After Retry Schedule Expires.
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 -
View exact email that is sent out when using templates and variables.
The customer would like to have the ability to download the exact email sent to their customers when using templates and variables.
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 -
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 -
Simplifying SPF Value for Domain Verification
Currently used SPF setting "include:mailgun.org" consumes 5 DNS lookups, which is 50% of the allowed 10 lookups defined in RFC7208.
Puting this in one entry, which consumes only 1 DNS lookup would be very great.Many greetings!
Stefan2 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 -
Add a small Sender Domains Amout to Basic Plan.
Hi Mailgun, 1 Sender Domains in Basic Plan vs. 1K in bigger plans?... makes no sense. I personally for example need 5 Sender Domains and NEVER i will subscribe 50K plan by sending 500 Emails a month. So Basic Plan is no opinion... und free trail is redundant. Why there is such a big barrier in front of Basic Plan usage? With 10 Senderdomains you will get the most small sized businesses.
2 votes -
Suppress entire recipient domain
Have the ability to suppress all sends to specific inbox provider/domain.
2 votes -
Suspend/unsuspend SMTP Creds
I would love to see the ability to suspend/unsuspend SMTP Credentials.
Occasionally customers don't pay and I'd like to suspend their creds...but my only option at the moment is to delete their creds or reset their password. Both of those options require us to spend time settings things back up in various different systems.
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 -
Track responses to messages sent from Mailgun
looking to add the option to be able to track whether or not an email has been responded to via webhook
2 votes
- Don't see your idea?