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!
489 results found
-
Document list of error codes, reasons, and event types that may be generated by Events
Currently, there is no documentation detailing the set of error codes and reasons that could appear in an Event. For event types, this appears to be the only available link https://documentation.mailgun.com/en/latest/api-events.html#event-types but has some inconsistencies.
8 votes -
The (subscribed) sender of a mailing list should also receive his own sent mail
The (subscribed) sender of a email (to a mailgun mailing list) will not receive his own email, when he writes to a list. This is a very confusing behaviour for most of the users and it will result in countless misuses: The users will try to send their email over and over again, because they think that their email didn't get through the mail system.
I have never seen and never used a mailing list service that behaved in this way. Googlegroups, Yahoogroups, Domeus, whatever... you always get back your own email. Furthermore, this behaviour is not mentioned in the…5 votes -
Enhance DMARC By Adding the Authenticated Received Chain (ARC) Protocol
Mailgun should enhance their mail engine MTA to use the Authenticated Received Chain (ARC) protocol with all inbound and forwarded messages that go through Mailgun.
There are 2 situations where this will help. When evaluating inbound emails and the DMARC policy of the sending domain is checked and fails or when Mailgun receives an email sent to a mailing list that, in turn, sends the message to all mailing list members.
For both these scenarios, if a DMARC check is done and the original sending party has a policy of quarantine or reject, it is possible for these valid emails…
30 votes -
Use https protocol instead http in tracking url
Now we have troubles with removing our domain from blacklist because of using non-secure protocol in tracking pixel: http:email.ourdomain.com/bla-bla-bla. Your system doesn't provide ability to use https now, but it would be very useful to provide it
12 votes -
role-based multi-user access restricted by domain
We were excited to discover the multi-user capability and are even more excited for the possibility of restricting access based on role and domain.
10 votes -
Visibility of billing history in control panel login role : support
If a user is added with a role of "Support" they can view billing history for the account - this is not something that should be visible outside of the admin or billing role - it's should be hidden
3 votes -
Enable a "Reply to" address that is different than the "From" address in Zapier
Allowing a "Reply to" address that is different from the "From" would GREATLY expand the power of the Zapier integration by allowing users of an application to follow the Truthful Routing clause of the CAN-SPAM while being able to receive replies.
8 votes -
Easy Forward User to User Emails with masked Email Adresses
Some Apps allow User to User communication via Email (example LinkedIn). These App creates virtual Email Addresses to hide the original Email Address, either for the purpose of privacy or for intersecting the communication via store() or forward() routes, either to save the conversation in the system or simply to forward the email to the real address.
Where this works great for Emails without attachments, we could save some expensive roundtrips with emails that have attachments.
In that case all attachments have to be downloaded first to the App Server and then send to mailgun again, although mailgun has these…4 votes -
Billing - updates on reaching different pricing tiers during a billing cylce
We would really like to have some kind of notification (preferably over email) from Mailgun when we hit a particular pricing tier in a billing cycle. So for example, when volume crosses 10K and a new price point kicks in, we get a notification. Similarly a notification when we hit different price tiers in a month (billing cycle)
8 votes -
Add multiple API Keys or Sub API Keys to be used for commercial software distribution.
I have some software nearing completion and it will be distributed to customers on a subscription basis. A few customers would also like the host the software themselves. Maintaining multiple API Keys that link to the one account allows us to control our customer's usage should the subscription expire and prevent us from giving them our API key.
30 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
26 votes -
Allow Mailgun account email to send emails to mailing lists from Outlook
Allow Mailgun account email to send emails to mailing lists from Outlook without having to change the outgoing servers. This would be a step between needing to be authenticated (Read Only) and Allowing people in the mailing lists to post things.
This way the owner of the mailgun account can send emails from Outlook to their mailing lists, but no one else would be able to do this.
8 votes -
Expose the "in reply to" node in your Zapier integration.
The Zapier integration desperately needs the "in reply to" node exposed for logic such as ticketing systems.
12 votes -
allow for a "catch all" webhook
if I have a general webhook script that can handle all types of messages, it would be very convenient if I could set all your webhook messages to go to the same url without having to edit every one separately. Also, it would be great if there could be a single webhook url set for ALL domains as well if needed. So, a single webhook url could be set across all domains and all webhook types.
6 votes -
New Mailing List Access Level List of Permitted Senders
Change the access level of a mailing list not only to be limited to "members", "everyone", and "read-only" to also include an option for allowing a list of addresses for a particular list or domain. Updating the list of permitted Addresses should have a similar API access as editing mailing lists. This allows specific people to send to lists they are not on, but also restricts unwanted senders.
10 votes -
Forward feedback loop emails
Please add the possibility to forward feedback loop emails so that we can use other tools to analyse them in more detail then Mailgun provides...
3 votes -
Support wildcard suppression of email addresses
Hello,
I need to suppress emails that are sent to my automation users.
qa_automation+df1qb6fn293okcevaucv@zzz.com
Basically, anything that is sent to qa_automation+xxxxx@zzz.com, I would like to suppress. Please consider this as an enhancement.
Thanks
7 votes -
Re-send and View rejected mail
Recently because of insufficient balance in credit card, mail gun rejected many transaction mails in my account, and this effected our business badly.
So i request for two features:
Re-send rejected mails (please add code in your docs)
View rejected mail content
http://blog.mailgun.com/how-to-view-your-messages/
It seems currently you store only delivered mail content in your servers, Please add this feature in rejected mail.
So that we can copy the html and send it again.Thank you.
4 votes -
Inbound sending mail server IP address attribute
As part of the inbound mail parse output to have a field that includes the IP address of the sending email server - what is used as part of the TCP handshake. I realize that mailgun may add this as a header in the mime parse, but would be great to have this already extracted as part of the output. This could be used for additional security and spam checks by the developer. Thank you.
2 votes -
Set up email addresses for simulating various outcomes
It would be really useful if I could simulate certain delivery outcomes in mailgun by using some special/reserved email addresses you've implemented.
For example, I'd like to be able to specify something like "bounce@test.mailgun.com" as a recipient, and have mailgun instantly treat the message as a bounce and notify my webhook.
Some of your competitors provide this functionality to their customers, e.g. http://docs.aws.amazon.com/ses/latest/DeveloperGuide/mailbox-simulator.html
12 votes
- Don't see your idea?