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.

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)

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

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.

Where is the download Log feature located??

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?

Having the ability to view or download a date range of the email validation logs would in debugging and identifying abuse of the service. Currently I have to request from your support team every time I need them and the logs entries are not formatted with date/time stamps.

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.

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.

Bounce mails dont came back to senders e-mail account, tracking is impossible without API. Routed e-mails need reply information, feature will make Mailgun perfect.

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.

The maximum limit for routes is 5,000. Currently Mailgun does not notify you when you're close to the limit. This is especially risky if you create lots of routes programmatically via the Routes API.

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.

Would be great to define the outbound IP address (of those in my pool), for which emails will deliver, upon submitting to the API.

There should be an endpoint where you can submit the MIME of a message and get a spam probability score to determine deliverability.