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!
20 results found
-
1 vote
-
1 vote
-
include:mailgun.org takes three DNS-lookups for your customers
Your SPF-setup include:mailgun.org takes three DNS-lookups for your customers.
I don't think this is professional enough. Ten DNS-look-ups is their maximum.
See:
https://www.mailhardener.com/tools/spf-validator?domain=mailgun.org1 vote -
Missing Essentials for Template Editor
The visual template editor really needs some attention.
The editor itself works fine, but everything that is not in the editor window itself severely lacks functionality and quality of life.
Especially two points really set us back with trying to use the mailgun templates.When setting up a new templates there are options to set Subject from and reply-to adresses. Unfortunately these values are NOT EDITABLE, instead the support told me I would need to delete and completely re-create my template to change them.
Which leads to point two, duplicating or reusing a template is impossible, there is no way…
2 votes -
The CSFR token has expired
error "The CSFR token has expired"
1 vote -
Fix application and contact forms: no addresses qualify as valid business address
I can't contact you or sign up for your service because your forms reject both my AOL and Gmail business email address - saying they aren't valid business addresses. My AOL business email address has been active for 20 years! I live in the US. What is a qualified email address to you?
1 vote -
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.
2 votes -
Allow user invites during free trial
If a business person makes an account and wants to give access to a tech person, it's needlessly frictionful and probably bad for security that the free trial prevents user invites and encourages sharing login credentials.
1 vote -
Search in Account Security
Implement a way to search for users within the Account Security page, to make removing access or verifying access easier.
1 vote -
1 vote
We are developing multi-currency support in Mailgun for both the Euro and GBP.
-
1 vote
-
Provide More Verbose Response When Attempting to use SAML SSO on non Scale Plans
If a plan was on Scale and used SAML SSO, then downgraded to a lower plan while SAML was enabled, attempting to log into Mailgun via SAML returns a 500 error. This can be confusing to customers who are not aware that SAML SSO is exclusive to Scale plan
1 vote -
Update pricing page to reflect that review is done for dedicated IPs
Update pricing page to reflect that review is done for dedicated IPs
1 vote -
include smtp client's ip address
when sending (smtp) & receiving (Receiving Route) via Mailgun, within the same domain, the smtp client's ip address is not included in the POST parameters.
It would be very helpful if we could captre that ip address3 votes -
Create a route action to reject incoming emails (ie do not even process them)
Currently, the stop() action merely stops all subsequent routes. The email that matches the conditions is still processed (and therefore charged). As such, a potential attacker (say a determined competitor) can inflict a huge bill on a mailgun domain by sending a large amount of emails to that domain.
My suggestion is to have an action that will ignore a sender / sending domain entirely and refuse to accept some emails with the action.
8 votes -
The final failed retry event for a no MX message should have permanent severity.
When a message is sent to a domain without an MX record (498), mailgun attempts to send the message for up to 8 hours. Each attempt will be recorded as a failed event with severity = "temporary". The reason is set to "generic" for each attempt except the final attempt which is set to "old".
This final attempt failure event should have severity = "permanent" so you can use the Permanent Failure webhook to observe this dropped message.
Currently, you must also use the Temporary Failure webhook and inspect the reason property to see if the temporary failure is effectively…
5 votes -
API Key Permissions/Restrictions to Reduce the Impact of a Leaked Key
Security Feature:
It should be possible to restrict the call types that your API key is able to make in order to reduce the impact of a leaked/breached key.
For example, if my API key is accidentally exposed, an attacker could then go on to exfiltrate data from my account.
If it were possible to lock down your API key so that it can only make certain call types, the impact of such a breach would be drastically reduced.
For example, I could lock down my key so that it is only permitted to add/send emails to a particular mailing…
6 votes -
Get stats by SMTP credentials
Hello,
I think it would be interesting (from a stats perspective) if you can provide another API endpoint to get the current stats by domain and credentials.
An example:
Imagine the domain.com has 3 SMTP login:
- postmaster@domain.com
- newsletter@domain.com
- autoresponse@domain.comNow we can get stats from domain.com (so we can get the domain has sent 300 messages), but we don't know if we have sent these messages using the autoresponse@domain.com account or using newsletter@domain.com or any other account that we can create.
If you can consider this new feature I think will be nice from a Stats and…
28 votes -
Accept attachments encoded as Base64 strings in the "/messages" API endpoint
It might be helpful for some users if the "/messages" API endpoint would accept attachments as Base64-encoded strings, with a name and content-type described somehow.
16 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.
27 votes
- Don't see your idea?