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.

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.

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.

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.

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.

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.

Where is the download Log feature located??

I really like the new UI. One request!! Could you please return the count of the number of results returned by the search filter. I entered a search parameter to find out how many emails were sent with that pattern. I see the results, but I need to know how many results are returned. I really need to know the count so that we can increase our user-base. Thanks!!

The new control panel doesn't allow for the ability to set a password, which means if the password is accidentally reset, we can't go back and edit it and we might have a number of applications using the previous password.

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.

Option to have multiple API keys, for example: client 1 has the API key exposed, we now have to roll this key, and update all clients using it.

Whereas, if we had multiple keys, we'd only need to roll and update that one client using the key.