RE: Updating Payment Method

Re: Address section
Only 'Billing address (line 1)' is available

This is weird.. it makes you feel like the form is incomplete and updating credit card wont work - which it didn't - took three attempts before my updated credit card would save.

Suggest you do a UX run through.

Add place where users can pay due invoices, have to wait for the customer support is an overkill

This use case involves adding a private domain (its my family na.me). I would love to use mailgun for simple forwarding of first@na.me for various family members without the ability to snoop their messages.

If there were an option to at least disable content logging for this specific domain, I would happily use mailgung for that purpose.

When my deliverability swings up or down I often don't see it until days or weeks later. A weekly email with my recent statistics would allow me to track it more easily (and give you the ability to upsell static IP's)

Currently, the mailbox_validation comes back as false for emails with the + alias trick (joe+alias@example.com) even if the domain is hosted by G-Suite

Support tells me this is a gmail only feature but that's not true, it works at least for hotmail.com and outlook.com emails too.

Why can't you just check the MX records to verify if the MX domain is one that supports the + alias trick?

Currently my app (email.mydomain.com) CNAME is pointed to mailgun.org, but when I have my users' domains point to email.mydomain.com, it does not accept this as a chain CNAME.

It would be nice to validate this so it can be whitelabel.

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.

Enable users to check the login history of their accounts/sub accounts. It's just good security, I imagine you must log this internally, just expose a limited subset of it.

You do this when the access level for a mailing list is set to "read-only" but you do not do this if it is set to "members". You should always send the bounce / non-delivery notification if the sender was not allowed to send to the list.

When an email is not sent due to a Mailgun server error (e.g. 499 MX server resolution error), the retry should be much shorter than 10 minutes. Errors that are very likely transient (such as DNS resolution of a Gmail server), should be retried immediately and any error not resulting from a rate-limit should use a geometrically increasing retry interval, rather than the 10-10-15-30... interval progression.

Would be great if this could be simple but configurable - or if we could opt to have summary reports at the end of a day/week/month of bounces, suppressions etc. Thanks

I'm happy to help and I'm glad you open sourced this library, but please let pull requests in and ship it to production :)

https://github.com/mailgun/talon/pull/23

Recipient in different list would receive only one copy of message, this is a basic ESP feature that everyone supports. But currently if a address is on more than one list than recipient will receive messages that are sent to each list, the only way to avoid this is to remove the email from other list.

Please add a workaround for this basic ESP feature.

Per-domain sending limits

Would like to export delivery logs to a text file without use of programming extract.

No way to delete domain that isn't verified

Hi! Please enable HTTPS on eu.mailgun.org because I can't configure Tracking.