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!
3 results found
-
Add support for idempotent requests to the API
Add Idempotency-Key to request ala Stripe's API. https://stripe.com/docs/api?lang=curl#idempotent_requests
36 votes -
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 -
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).
- Don't see your idea?