If no text portion of an email is submitted, automatically make one from the html portion. This should help with deliverability. The parse incoming seems to do this now according to the documentation so you may already have routines to do this.

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.

I have some software nearing completion and it will be distributed to customers on a subscription basis. A few customers would also like the host the software themselves. Maintaining multiple API Keys that link to the one account allows us to control our customer's usage should the subscription expire and prevent us from giving them our API key.

It'd be oh-so-useful to use MailGun like http://mailcatcher.me/, http://papercut.codeplex.com/ or http://mailtrap.io/ when developing software - you've got most of the infrastructure in-place already!

Add Idempotency-Key to request ala Stripe's API. https://stripe.com/docs/api?lang=curl#idempotent_requests

There's currently no direct way to assign recipient variables for batch sending using Node/Meteor. I'm using the sendRaw method, and I can assign other fields like "to" and "subject," of course, but I can't assign "Recipient-Variables."

I did some googling and found that other devs have the same issue. It can be done with other languages, but it's desperately needed for Node and Meteor.

Allow logic to be included in templates to make decisions based on template variable data.

Example:
{% if %recipient.name% %}
Hi, %recipient.name%!
{% else %}
Hi!
{% endif %}

I would love the ability to hook up my Mailgun account to a service like Papertrail (https://papertrailapp.com) so I can get access to emails more than 30 days old. We've had half a dozen cases in the last few weeks where we've needed to see if a receipt email was received, but since it was more than 30 days ago, we're out of luck.

Hi there.

When designing HTML emails, having to use inline styles (style="xxxx") instead of CSS classes is a right old pain.

There are tools and libraries that can take a HTML document, and automatically 'inline' the CSS styles. E.g. http://beaker.mailchimp.com/inline-css

It would be AWESOME if there was an option to apply this transformation to a HTML email before it gets sent....

At this time Mailgun does not provide support for sending user specific attachments in batch mailing. Please add the support for that. In case of sending thousands of emails, we have to call the mailgun APIs thousands of times which does not look a valid approach. And we can't send URL of the attachments in the emails because the attachments files are stored temporarily on the server and it's confidential.

Adding this feature will be very helpful.

Thanks a lot.

It would be great to add the ability to disable click tracking only for some specific links in an email.

In know that you can disable click tracking for all links in an email, but I couldn't find anything about doing it only for a specific link.

The Zapier integration desperately needs the "in reply to" node exposed for logic such as ticketing systems.

It would be really useful if I could simulate certain delivery outcomes in mailgun by using some special/reserved email addresses you've implemented.

For example, I'd like to be able to specify something like "bounce@test.mailgun.com" as a recipient, and have mailgun instantly treat the message as a bounce and notify my webhook.

Some of your competitors provide this functionality to their customers, e.g. http://docs.aws.amazon.com/ses/latest/DeveloperGuide/mailbox-simulator.html

Can't find the API settings now!!

Support SAML SSO as well as oAuth or OpenID

Implement U2F/Yubikey support for 2 factor auth.

This will enable people who can't use their phones in the office, but can use hardware tokens, to take advantage of the 2 factor auth you just implemented.

Provide a mechanism to BCC or forward a copy of every message to a mail archival service (smtp address). This might be applied as a ROUTE rule or a separate facility.