I have several distinct domains and/or several subdomains that send mail from the same Exchange environment. I'd like to use mailgun as the outgoing smarthost for this system, but mailgun seems to require unique SMTP AUTH credentials for each of the unique primary domains, which means that many outbound emails will not be deliverable through this smarthost since the outgoing server doesn't support unique SMTP AUTH creds for each outgoing domain...

We have the need for an admin user role who is not the account owner to not be able to access billing information

So, it would be very helpful if we have a possibility to use Handlebars custom helpers feature in templates, because of existing built-in Handlebars helpers can not cover all the cases for rendering hard structured data

Would be good to see code of previous tests in Inbox placement

It would be nice that when you create a template, users don't get redirected to the all the TEMPLATES screen. Instead once the template is created we can update the template by loading the /edit/{template_alias} url into the website (so that it works the same way as when you edit a template)

Allow us to edit a web hook instead of delete then insert a web hook.

I like the forced random very long SMTP password, however limiting it to hex values (0-9 and a-f) severely limits it's usefulness when used as an encryption routine because an attacker can limit their search in a brute force method with that knowledge.

For full cryptographic coverage the random passwords should utilize more of the available character set.

I would like to have the ability to recall emails sent trough mailgun.
Sometimes you send a email by accident.
If the same thing happens in Outlook you are able to recall the email.
This is very important when you send out invoices etc.

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.

Allow graphs when filtering by terms other than event status. Example would be if I wanted to see how many times a certain email address had a permanent fail, allow the chart to display in logs along with entries.

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.

Enable that links are not rewritten when using click/open tracking and maintain the original link from the html template sent.

The "Add Filter" popup window the "Logs" form seems to be missing "Failed" as a possible event in the dropdown filter choice. I see "Failed" for one item on the first page of my log, but there seems to be no way to tell the filter to show me just items with event = "Failed". I can select "Rejected" from dropdown, but that returns zero records from the log.

Please implement an alert feature, so that I can see if an exceptional number of emails are being sen, as this indicates something is wrong, but I doesn't stop authentic emails going out.

Being able to track opens and clicks and consume that data via the Analytics dashboard is awesome. However, most emails that we send out contain multiple links - e.g. for account activation, homepage, featured blog post, social links, etc.

I would like to be able to have analytics on a per-link basis. Mailchimp allows this, see https://i.imgur.com/2iIocrv.png.

It would be useful to be able to search for mailing lists by just part of the email rather than the full email only.

Is it possible under sending > overview to change the opens reporting to a percentage rather than just a gross number of opens? To me, it's more meaningful to see the % of people who opened compared to the send size than just see the gross number.

Currently it is the whole queue for a domain that can be deleted. This could affect other users of an application who do not wish to cancel their queue(s). I'm suggesting an endpoint to delete individual queues. So when an email is sent as a batch an ID is returned which could be used to cancel a batch email. This would make it easier for both the developers and the users of the developed application.

When a webhook call fails for any reason, we have to wait until it retries to see if our server changes are working or not.

If we could manually trigger a retry for a webhook, then debugging would be way simpler for us.

In spanish pleace