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!
12 results found
-
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.
1 vote -
Self Service Account Deletion
let us delete our own accounts.
1 vote -
Cancel queued emails from a particular sender
Similar to the cancel emails for a domain but filtered on emails sent by a sender (From field in the message). for example this would allow cancelling emails from no-reply@company.com but not the ones sent by alerts@company.com
1 vote -
email notification when recipients export is over
It would be great to get a notification when the export we previously launched is over.
The export of a mailing list can take several hours.1 vote -
Sending DNS record instructions via email with one click.
I should be able to send someone the DNS records via email so they can connec it to their hosting.
5 votes -
API access audit logs
API Access Audit Logs
Please provide audit logging for any and all API calls. Results should include
- Date/time
- Source IP
- API called
- Account used
- Query header
- Authentication Success/Failure12 votes -
Allow setting the open, click, and unsubscribe settings when creating a domain
Currently when creating a new domain via the API, we have to set the open, click, and unsubscribe tracking settings via individual PUTs. Instead, we should be able to create and configure a domain in a single call - that way we don't have to worry about a domain being partially setup.
2 votes -
Sort order SMTP login
Hello,
It would be great if SMTP Credentials could be sorted on Login (ascending or descending).
Best regards,
Simon1 vote -
Request for method to programatically pull security event logs
Requesting to have an api endpoint or programmatic way of pulling security event logs (e.g. a org user logs in, if there was a failed login, activity of users etc) so they can be ported over into a SIEM.
2 votes -
Search suppressions list by email domain
PLEASE allow us to search the suppressions list by email domain, not just specific email. Our use of the product means that we often have multiple users from a single domain that we send email to. If something goes wrong with their email server, and they end up suppressed, removing them is a real pain. The customer has to provide us with every possible email that was suppressed, and we have to search them all one by one. I REALLY wish I could just search by domain instead.
18 votes -
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
41 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…
35 votesHello,
As we work through ideation on an alerts feature for Mailgun, I wanted to gauge opinion on the configuration of notification channels. If out of the box, Mailgun allows for configuration of notification channels to include emails addresses, webhooks, and Slack integration where in the flow does it make most sense where the channels are defined.
Our position is that the pattern for notification channels is created on the account level. Such that any all alerts created would use the notification channels previously defined. This would be foundational to a future state is which users could have greater control on how Mailgun communicates emergent issues (e.g. some users would like to receive domain disablement or similar notification posted to webhook rather than email).
So, for "alert and notify based on sending metrics and usage" is there any reason Mailgun needs to have notification channels defined on a per alert…
- Don't see your idea?