There is a way to create multiple logins for the same Mailgun account but we can't reuse an existing account. The error message is:

Error: Unable to invite user. User already exists

We need a way to manage multiple accounts under the same email, not having this is a total nightmare :\ We have this in Stripe, Twilio, SendGrid, Mailchimp, etc ...

There is no way I will ask my clients to forward me the "passcode" everytime I need to login on my client's account.

SMTP credentials passwords are not visible. The only way to access a password is to reset it. This is really not great!

A problem with sending email with Mailgun is: many Mailgun users are using the same IP-address. When another user is sending spam, all emails from that IP-address to Hotmail/Live addresses are blocked, until Mailgun has assegned a new IP-address after a couple of hours (when I create a ticket).

My idea: an automatic affected IP-address detection. When Microsoft returns an error "bad IP reputation", then automatically assign a new IP address and resend the failed emails.

request pagination urls with https instead of http, for example: https://api.mailgun.net/v2/<domain>/tags?page=next&tag=<tag>&limit=1000,
Currently GET /<domain>/tags pagination urls with http instead of https.
["first"]=> string(76) "http://api.mailgun.net/v2/<domain>/tags?page=first&tag=&limit=1000"
["last"]=> string(75) "http://api.mailgun.net/v2/<domain>/tags?page=last&tag=&limit=1000"
["next"]=> string(88) "http://api.mailgun.net/v2/<domain>/tags?page=next&tag=<tag>&limit=1000"
["previous"]=> string(99) "http://api.mailgun.net/v2/<domain>/tags?page=prev&tag=<tag>&limit=1000"
and calling on http://api.mailgun.net/v2/<domain>/tags?page=next&tag=<tag>&limit=1000
returns NULL

thank you

For Stats regarding specific Tags, need to use the `/<domain>/tag/<tag_name>/stats` endpoint.
Reference: https://documentation.mailgun.com/en/latest/api-tags.html#tags

Will it be possible to request for an endpoint that returns Stats for all Tags instead of just specific Tag please?

In incoming mails all the files - embedded or attached - come in one big bunch.
It's also impossible to re-build the HTML, because the identifiers aren't there.

If there was an extra array passed on with the request, containing file names with their original identifiers, this would become possible.

Support SAML SSO as well as oAuth or OpenID

Please add a totals row to the Engagement table. Ideally, you'd also show the total %'s of unique opens and clicks.

Please make a better WYWIWYG email editor. Have a look at your competitors, like SendInBlue. There system is excellent. See attached image of their email editor. By comparison editing templates in MailGun is like living in a dark cave with no electricity.

Can we have options or features to allow the change of email attachment size accordingly.

For now, its limits to 25, but we look forward that we can adjust it accordingly to our policy but ensure within acceptable global standard such as 50MB.

Folder structure for handling large quantities of templates. We have MANY templates that fall into different categories, and it would be helpful to have a folder structure to simplify navigation and identification of templates when applying updates...rather than scrolling through a long list.

Add a feature to export the logs summary or log detail in a text, csv or xls file by clicking an export button

Hello guys,

I think we need a new features when we take the tags statistics, now we can set multiple tags for a message but we take the statistics only for one.

We need to can take statistics for 2 or 3 tags concatenated per message because, for example if I want to see how many clicked have a user for a specific marketing message I can't do this.

I can do a difference between stats, because I used the specific marketing email for many users and I used the specific user tag for multiple marketing tags.

Pageload takes about 30 seconds on a gigabit connection.

It'd be pretty great if it was at acceptable levels

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.

Recently you introduced invitation of new users and assigning them roles.
In addition to "roles" i would like to see that these invitations/roles can also be limited to specific domains.

The pagination UX should be much clearer. I have no idea how many total results there are, or what page I'm on. And the "next page" links should be disabled when on the last page.

Please provide a separate API key for sandbox and real domains, or API key per domain.
I do not want to use my api key on dev environments.

Hi, I couldn't figure out how to delete a domain in 'pending DNS verification' state so I deleted it using classic UI.

Maikel