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!
247 results found
-
User variables fallback / default values
When using user variables, e.g. %recipient.name%, it would be useful to implement a fallback value for when that variable is not present. For example:
Hello %recipient.name|Customer%
So, for the above the output would be either:
Hello Jane
or, where the name is not set for the user
Hello Customer
8 votes -
Stats for multiple domains
We run a lot of domains (for inbound forwarding) and want to gather daily stats. The only way to do this is to make multiple API calls , 900+ each time. Can we get stats for multiple/all domains at once?
9 votes -
Allow rotation of DKIM keys
I would like the ability to rotate the DKIM key used by mailgun for my domain on a periodic basis. The only option I was given by mailgun support is to delete my domain and start over. Rotating the key is important to mitigate the effects when keys are compromised.
14 votesHi all,
Apologies for the lack of updates here, this feature is currently in development and is slated for a March 2023 release.
-
Please support DMARC on Mailgun and make it easy to deploy
-Please support DMARC on mailgun, and make it easy to deploy.
- Generate useful TXT entries (just like you already do for SPF and DKIM)
- Handle the DMARC reports
- Present DMARC reports in your control panel after decoding the ZIPed XML files the providers send.
- Convert DMARC failures (and successes?) into web hooks, events and log entries.131 votes -
Provide option to send Non-Delivery Reports to the original Sender
Mailgun bounce processing works great when a single sender is sending email to a broad audience. It does not work well when there are many original senders each with their own list of contacts.
Scenario:
- Company with 10 to 1000 employees.
- Company switches from a traditional in-house mail solution to Mailgun for all outgoing email.
- John, a typical employee in the organization, sends email to a customer, but spells the address wrong.Traditional in-house system behaviour:
- John would get a Non-Delivery Report letting him know of his mistake. John would fix his mistake, and re-send the…70 votes -
Alert and Notify based on Sending Metrics and Usage
There are some delivery issues which usually warrant manual inspection and care by the administrative users. I feel that continuing to send emails to addresses that have ended up in the Bounces list would at least be one of them.
It would be convenient if the user could select certain common delivery issues like this and get a notification about them emailed to a specified email address. This email address could then be a mailing list for administrative personel who could look in to the error and see it they should act upon it.
It is possible to implement this…
33 votesWe are currently in concept for a alert and notification feature to allow end user to configure alerts based on any number of sending metrics (e.g. hard bounce rate), notification channel (e.g. email) and filter by (e.g. specific sending domain, recipient domain, etc.).
Additionally notification may cover usage monitoring (e.g. send me an alert when I have reached 90% of my sending limit for the month).
-
Shorten Tracking URLs
The current URLs used for tracking link clicks are quite long. Offering a way to shorten them via Bit.ly or perhaps an custom shortened URL would be helpful.
13 votes
- Don't see your idea?