I would like to be able to do is simply to let our clients add a CNAME record to the [domain] DKIM record (mx._domainkey.[domain], and then, when sending we could specify the signing domain for the DKIM signature.

For example: to align the domains in the example above, I would just create a CNAME record at mx.domainkey.domain2.tld which point to mx.domainkey.domain1. Then, the DKIM signature would declare the signing domain as d=domain2 instead of d=domain1

The benefits of this are:

1. We don't need to continually create and manage new domains in our account.


2. The domains are aligned by signing the message using the same domain as the From header.

Use case 1: Backup sent emails that were done through SMTP.

The company I work for have a generic SMTP credential per country with multiple people using it, this enables any of them to handle emails if available, the problem is that this requires us to have an script to backup of the messages sent on each computer.

Use case 2: Being able to send a copy of the emails from novice worker using the SMTP crendential to a manager during their training phase.

Outbound routes would be similar to inbound routes where instead of "match_recipient" it would have "match_smtp_credential" or "match_sender".

As a non-technical user (the CEO of a start-up), I do not feel comfortable editing in HTML, which seems to be the only option. I need to be able to:

1. Generate a master list of all of the templates, including name, version tag, etc.




2. Export each template (or, alternatively, do a bulk send to a specified email address) so that I can compare each email in Mailgun to the master version that was approved as part of our overall messaging.

To put it more abstractly, there needs to be a way to easily review / verify / update the messages on Mailgun by the non-technical marketing people who are responsible for messaging, branding, etc. At the moment, there doesn't seem to be a way to do this. This makes it very difficult for marketing people to manage the messaging.

I would like to request that Mailgun offers an inexpensive plan for non-senders.

Specifically, myself and many others love using Mailgun exclusively as a mail routing/forwarding service for their domain(s). Mailgun's implementation of this is brilliant, but unfortunately I cannot justify upgrading to the $35/month plan for this feature only: I send zero emails out per month via Mailgun, which obviously is far less than what Foundation 50k allocates!

May I suggest the following new plan: "Inbound Only". It would be the same as Foundation 50k except:
* Zero outbound emails per month (instead, billed on flex pay-as-you-go model)

I would be happy to pay $30/year for such a service.

Thank you kindly for your consideration!

Provide a way to disable List-Unsubscribe headers for transaction emails. Currently Mailgun adds the List-Unsubscribe header for all emails, including transactional emails like password reset notifications and order confirmation emails. This header is intended for mailing lists, not transactional email. Additionally--we want to handle subscription and unsubscribes in our application not in mailgun.
We discovered this header was recently added when troubleshooting a support request from a user who was not receiving password reset notifications and found he had unsubscribed using a link provided by this recently added header. He did not remember clicking unsubscribe and did not intend to unsubscribe. He is the only user in our account who unsubscribed using this mechanism. Thus, for our sample size of 1, 100% of users who clicked the link provided by this header did so accidentally.