Recurly does not have any plans to support DMARC, but you can work around this by doing the following:
- Creates a subdomain on your existing domain that will be used specifically for Recurly emails, such as
billing@accounts.somename.com
. This email would be included in the From email setting of the email templates. - Within the DNS configuration of your new subdomain, create a DMARC policy record that includes the attribute
p=none
. That policy will neither set a Quarantine or Reject policy action in the email header and the email would be routed to the end-user recipient's email server. - The end-user would then need to set their email account spam filter to permit emails from
billing@accounts.somename.com
. - Once the email arrives at the end-user's email server, their Spam filtering configuration will permit the email (from sender:
billing@accounts.somename.com
), to ultimately be delivered successfully into the end-user's inbox.
NOTE: Do not use recurly in the subdomain of the contact emails under Configuration - Site Settings - Advanced Settings - Email Settings. (For example, billing@recurly.mydomain.com is not acceptable, but billing@accounts.mydomain.com is.)