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.

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.

We send a lot of emails that are custom to the individual and would like a simple way to save them. Our email generators are on 20 or so amazon instances and we spin up and shut them down as needed. So we have 3 options: save the file and hope to dl before the box dies, send bcc to a stable box, or post to a webhook on a stable box.

I didn't mind so much that you removed the free tier even though that's why I tried and have used mailgun over past years. Flex plan removing the pay as you go validation service is a dealbreaker for me though and now has me exploring Sendgrid, Amazon SES and on-premise solutions for replacing this feature.

Let me click on the bounces to drill in and see which domains are bouncing my emails. As it is, if an email isn't received by a recipient who expected it, there's no way for me to do anything but see something was dropped.

I would like to export data from the "Logs" screen.

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

No way to delete domain that isn't verified

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

The new design looks nice but not mobile friendly. I had difficulty navigating around while on my iPhone XS.

The reason I had to use mobile was to check the logs to see if an email was sent out or not.

I want to be able to set my profile picture when sending via MG thru Gmail.

in your routing, I wonder if you might be able to implement SRS on the forward() function? Perhaps forward("someone@example.com", "SRS") or some such? (Forwarded mails fail SPF at the destination without SRS).

Log clicks so that it is viewable / searchable in the stats. An email might have different URLs and it would be useful to see what URL the user clicks on.

If I attempt to send 100 emails to users at a single host and am rate-limited by the recipient's e-mail host, the mailgun system attempts to resend those e-mails after 10 minutes. The result is that the same 100 emails all retry at the exact same time and nearly all of them bounce again. Subsequent retries with longer delays will continue to bounce as they all attempt at once.

If retries were randomized between 5-15 minutes, deliverability in this scenario would be substantially improved with minor development effort.

Currently there is no convenient way to get a list for each of your domains what sending IP address(es) are assigned to them, the only way is using the website drill down into each individual domain's details.

Exposing the IP Address(es) of each domain in the /domains API endpoint seems like a good solution.

Additionally being able in the website to enter a sending IP address on the domains listing page and it would show all the domains with that sending IP address assigned.