I have experienced that setting the
Reply-To header does degrade deliverability, in two ways:
- MailChannels (a SMTP sending service that we use) will funnel messages with a
Reply-To through their "junk pool" of IP addresses, almost all of which are on some blacklist (usually at least UCEPROTECT1).
FREEMAIL_REPLYTO* rules trigger if
Reply-To contains a freemail address (gmail, yahoo, hotmail, et al) which doesn't match the
From header (which is often true in this use case, since the
From header can't be set arbitrarily because of SPF.
If these guys are suspicious of
Reply-To, perhaps others are too?
Since we depend on these systems, and want good deliverability, we must use these from headers:
(Where the domain
website.com has SPF configured to allow mail sent from the web server and/or SMTP gateway IP addresses.
no-reply is used because the "sender" is Website Visitor, and there is no valid address we can use here – it would be silly to allow replies to go to
This is unfortunate, because the convenience of being able to use email for CRM and easily Reply to the person behind the email is gone. I can't think of a better solution. I have solicited MailChannels to change their policy for sending
Reply-Toemails through junk IP addresses, to no effect.