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!
12 results found
-
More Verbose Error When Creating Route
Customer had failures when trying to create a route, and the only message in the failure was "Failed to create route". They would like more verbose error messages that would help them identify the issue.
3 votes -
1 vote
-
Submit mailgun.com for HSTS preloading
Please submit mailgun.com for HSTS preloading to force users to use HTTPS when they visit mailgun.com.
https://hstspreload.org/?domain=mailgun.com1 vote -
Encryption for the feedback site
http://feedback.mailgun.com should be encrypted. Before long, it will be painful, if even possible, to visit the site with most browsers. Encryption can be added for free with Let's Encrypt. https://letsencrypt.org/
We have credentials crossing the Internet in plain text until this is done. Unfortunately, some people use the same passwords on multiple sites.
Kind regards,
Ted2 votesThanks for the feedback here. We’ve enabled and enforced https on feedback.mailgun.com.
-
When sending email to web hook (receiving) send also the attempt numbr
When receiving emails, we sometimes return temporary error. Mailgun then waits and later tries again, 8 times. If we knew the attempt number, we could better handle the fails - for example if this was the last attempt (we could alert the admin this email was "lost" ) vs the first (just log it).
67 votesHi there,
Thanks for submitting and supporting this feature request!
We upgraded our Webhooks to report additional data. This includes timestamps that will match events that occur to Webhooks in the delivery process.
Unfortunately, we will not have a feature that shows exactly what number of attempts are remaining— especially since that is not the only data we’re tracking. It makes sense for all events to be marked with a timestamp, therefore you can utilize the timestamps to determine how many retries had been attempted. Additionally, we offer a couple quick reads on how our updated Webhooks work:
https://help.mailgun.com/hc/en-us/articles/202236504-How-do-webhooks-work-
https://www.mailgun.com/blog/same-api-new-tricks-get-event-notifications-just-in-time-with-webhooksThanks again for your patience and understanding as we work to improve our product!
-The MG Team
-
Include the Tag property in all webhook events
The Tag property is currently missing in Dropped and Delivered webhooks, which really does not make sense. Yes, as I learned, it is still in the headers JSON, but why would you offer such a handy thing like tagging and then omit it from just two of all the webhook event types, forcing programmers to handle the same data from different events differently. Why are these two an exception!? I don't see any difference. I'm handling drops and need to know what specific handling I need to apply to it depending on what was the purpose of the email, designated…
3 votesHowdy,
Thanks for your suggestion!
This was fixed in our recent release of Webhooks 2.0: https://documentation.mailgun.com/en/latest/api-webhooks.html. Please feel free to switch over to the new version!
-
API: possibility to assign domains to any of my dedicated IPs via API
Every time I want to assign a domain to specific IP addresses, I have to create a support ticket and then wait while Mailgun's support moves a domain to particular IP addresses. This is frustrating. It would be better to have a control over API + via Mailgun's UI.
13 votesThis feature was completed and released in October of 2017. Documentation for Mailgun’s IP API can be found here: https://documentation.mailgun.com/en/latest/api-ips.html
-
Fix email tracking with SSL websites
Using email tracking with SSL website prevents user to perform the action with Google Chrome.
If you use SSL with HSTS, it triggers big warning in Chrome when the user click on the link http://cl.ly/image/0A373O2r3539Email tracking in mailgun is performed by replacing links in email by a custom subdomain setup in the admin panel, ie email.domain.com which as to be configured as a CNAME for mailgun.org.
Chrome will try to access httpS://email.domain.com which will fail because the underlying server is mailgun.org and not domain.com's server.
Proposed Solution:
Instead of pointing email.domain.com => mailgun.org, configure your server for https://email.domain.com and…150 votesHi all,
I’m happy to announce that we’ve released this feature to production.
For the time being, this is only available on our Scale and Enterprise plans, however, this is only during the initial launch as we are monitoring performance during initial adoption. We have plans to expand this to all of our current plans in the near future.
Please check out our blog post for more information: https://www.mailgun.com/blog/https-innovation-and-optimization
Also check out our Help Article that outlines setup: https://help.mailgun.com/hc/en-us/articles/360011566033-How-to-Enable-HTTPS-Tracking-Links
-
Notify webhook while a temporary failure occures
As we know, at this time Mailgun webhook will only notify in the case of the Event permanently dropping, it will not notify on temporary failures.
Now the situation is we collect the log data from webhook and use these metrics data to generate dashboard in our own system. but we find the metrics data is different from what we use mailgun Events api to check out. because we can't get some temporary failures through webhook. so we want Mailgun can notify webhook while a temporary failure occures?Ticket number: #150129
16 votesHowdy all,
Thanks for your support on this suggestion! This is now available through our Webhooks 2.0 API: https://documentation.mailgun.com/en/latest/api-webhooks.html. You can create a webhook specifically for temporary_fail through either the API or the Mailgun Dashboard.
The Webhooks 2.0 API also closely follows our Events API, which is much less confusing.
-
Webhooks payload in JSON instead of multipart
It'd be nice to have the payload of webhooks POSTs to be encoded in JSON instead of multipart or form encoding.
14 votesHowdy all,
Thanks for your feedback and support! With the release of our Webhooks 2.0, the payload is now in JSON, and they follow our Event API schema. I’ve tested them out with Keen.io, and it does indeed work. Feel free to check out our webhooks documentation here: https://documentation.mailgun.com/en/latest/api-webhooks.html
-
Specify reply-to for everyone mailing list
I would like to be able to specify a reply-to address when a mailing list is set to everyone. Currently it is overwritten to the mailing list address.
56 votesHey all,
This has been released to production in our dashboard! If you click on a mailing list, you’ll see a new “Reply Preference” section under “Details”. Please let me know if you encounter any issues.
-
Allow multiple webhook urls per domain
It would be useful to publish events (opens, clicks, bounces, etc.) to more than one endpoint from Mailgun. Currently, it is only possible to have one webhook url set per domain. This is useful for catching events in your application, but it gets tricky if you work with 3rd party email services in conjunction with Mailgun. For instance, we are currently working with a 3rd party email templating solution called SendWithUs that nicely captures events for reporting. We currently have to make a choice, however, whether to have the webhook URL set to this 3rd party endpoint or our own…
28 votesWith the latest webhooks release you can now provide up to 3 webhook urls per event. Please see the documentation here (https://documentation.mailgun.com/en/latest/api-webhooks.html) for more information.
- Don't see your idea?