Hi,
We use Mailchimp transactional (v1.1.2) on several Drupal instances, to send transactional emails via a common mailchimp account. Each instance has its own sending-domain, which are all setup in the mailchimp account settings.
Unfortunately, DMARC verification sometimes fails because the "return path" in our emails does not match the sending domain (for the record, this value is by default set to "mandrilapp.com").
If we could define a custom "return-path" value in the Mailchimp-Transactional setup of each Drupal instance, and this parameter would be sent over by the module every time it sends something to the transactional API, this would solve our problem.
This is explained here :
https://mailchimp.com/developer/transactional/docs/authentication-delive...
In this specific part :
"You can also change the domain on a per-message basis using the return_path_domain parameter (API) or the X-MC-ReturnPathDomain header (SMTP)."
Do you think this is something that could be added as a new field in the extension setup ?
Feel free to let me know if you need more detail.
Regards,
LP
Active
1.1
Code
I did this on the mandrillapp.com side.
Go to Settings and add a subdomain on the "Tracking & Return Path domain" page
First you have to add a CNAME in your domain, so:
webforms.domain.com CNAME mandrillapp.com
Then test it.
Then go to Outbound - Rules - Add Rule
Fill in a rule name - set to sender's email - matches - webforms.domain.com
then do this: set return-path domain to webforms.domain.com