General Feedback
What do you think of our email service? This is the spot for good, bad, or neutral feedback about our main product.
You can also leave feedback on specific features like Inbound Routing, Message Event Logs, or Email Analytics.
If you have feedback that you believe requires an immediate response, don’t post here. Submit a support ticket or email help@mailgun.com. Feel free to interact with other users if you agree, disagree, or found a solution to their feedback.
Please be courteous of others and upvote if you believe strongly enough in an idea!
-
4 votes
-
Email me when one of my domains falls out of verification
If something happens to my DNS records and the domain gets un-verified, I need to know about it. Because of the 300 daily messages allowed on unverified domains, I have time to fix the problem before being cut off completely, but only if I KNOW about it!
Maybe this isn't common, but it's happened to me more than once now. Sometimes it's an issue with my DNS provider. Sometimes an included SPF record changes, causing the "too many DNS lookups" error.
I get an email if you automatically verify one of my domains, so why not also one when you…
17 votes -
allow cancelling an email via API
I'd like to be able to cancel a pending email via the API. eg If we don't get a 'delivered' or 'bounced' webhook within 10 minutes, it probably means that the email was delayed in some way (throttled by receipient or some other soft bounce) and at that point we'd like to cancel the sending of that email so that we can resend through other methods without the recipient later getting a duplicate message once the message finally goes through with you.
I'd suggest the MessageId as the key for use for cancelling since it is returned from the sending…6 votes -
Bulk delete mailing list members via API
Currently the API allows POSTing a CSV list of users to be added to a mailing list.
I would like to POST a list of users in CSV who should be deleted from a mailing list
16 votes -
Increase max route limit
The current limit is 5,000 routes and is a hard set limit that cannot be changed. It's an account based limit, rather than domain based, so you're likely to reach this limit quicker if you use multiple domains.
It would be useful if you could increase this limit.
6 votes -
Create a better way to determine campaign engagement
I really like the campaign feature. When I am trying to see if I have improved engagement with a campaign though, it I don't think it is possible with the current UI.
For example, lets say that I change the copy in a campaigns only email. I want to see if that increases the click and open percentages. I can see that Unique Click number goes up, but it could just be because I sent more emails in the latest month. It is not expressed as a %.
It would be good to see if the percentage has gone up…
7 votes -
4 votes
-
DNS records information sent via email
When we add a domain we are presented with the 5 DNS records that are to be added.
The dns records are presented nicely in the DNS success page. However, if you are not the one that will be entering the DNS record into the provider, then the manual copying of each the DNS records into an email is an error-prone hassle.In most situations, we have to send the DNS records via email to someone else who will enter them. This means copy and paste of those 5 records. It may not seem like much, but it takes awhile…
9 votes -
Unsubscribe page for users (Mailing Lists)
Make a template editing unsubscribe page (use this template in the mailing lists). Suggest using the editing unsubscribe page for use in various languages (e.g. Russian, French, German, etc.), similar to the design of the main site, and more.
21 votes -
Search Bounces by domain name
Would like the option to search all bounces by domain name. We have had issues with a couple of our member firms where most emails in their companies bounced back and they have whitelisted us, but we have to remove them from the bounce list to be able to resend the emails when this happens. We have to individually search by each email address with the way it is currently setup and would rather search for everyone on that domain.
21 votes -
SMTP batch sending without using mailing lists
It should be possible to do batch sending without messing with low-level MIME or having to use mailing lists - it would be very convenient if it were possible to do batch sending through SMTP and simply supply the recipient (JSON) variables through a header field such as the current 'X-Mailgun-Variables'.
6 votes -
Mailing List Recipient Search
The search feature WITHIN a mailing list only seems to search on full fields. Would be nice to type "RO..." and get roy, ******, ronaldo, etc. in the search.
26 votes -
Filter Stats by Multiple Tags
At the stats API, it would be helpful to be able to filter statistics by multiple tags.
9 votes -
Show API errors in MG logs
An example would be seeing this response in your logs:
{"message":"'to' parameter is not a valid address. please check documentation"}
I think this is important when you send batch requests because then things aren't always as clear.
2 votes -
Provide a search count on Log page
Can you please add search count of emails also on LOG page along with the date?
Count is a very important stat required on day to day basis, request you to please add that feature ASAP
Thanks
6 votes -
Provide deep linking support (universal links) by client proxy
Today it is already possible for Mailgun clients to get deep linking working.
e.g.: Set up Cloudfront "in front of" Mailgun, proxying everything to malign, except the requests for association files.
This comes at one big downside. The IP resolution is now based on what ever AWS instance handled the request, not the client IP.
It should be easy to use the Client IP as given by the proxy.For extra security, Mailgun could require the proxy to add a special header, to be sue the info is indeed coming from a trusted source.
2 votes -
Allow DNS if Domain becomes Disabled
Dear Mailgun,
Firstly, I'm all for protecting IP reputation and clean mailing lists. However, we accidentally uploaded our whole list today, not the filtered one based on use of Bounce/Unsubscribe APIs. We quickly hit a bounce limit, especially as the older records are a lot dirtier.
We completely understand a block of the domain and the halt of the distribution and any further messages, but blocking clickable links in successfully received messages is really embarrassing, particularly on behalf of a client. Ironically, recipients cannot unsubscribe either.
Keep up the good work :)
4 votes -
Implement a configurable per-domain message limit
It is already possible to set a global account message limit which applies across all domains. However, it would be nice to get more control and be able to set a specific message limit for each individual domain.
7 votes -
unable to establish a TLS connection
I wonder if this kind of error occurs, do you have any retry principle?
2 votes -
3 votes
- Don't see your idea?