What are the considerations for using different domains for From, DKIM, and SPF?

Email marketer from SparkPost explains that it's important to authenticate each sending domain (or subdomain) properly with SPF, DKIM, and DMARC. Using different subdomains allows for better tracking and management of reputation for different types of email traffic.

Email marketer from an Email Marketing Forum describes that if you are seeing deliverability issues when using different domains for sending, ensure all DNS records (SPF, DKIM, DMARC) are correctly configured for *each* sending domain. Incorrect DNS configuration is a common cause of deliverability problems.

Email marketer from Email Marketing Blog shares that using a consistent 'From' domain can improve brand recognition and trust. If you use radically different domains for different email types, customers may become suspicious and less likely to engage.

Email marketer from Reddit discusses the impact of sender reputation. They describe that if you are sending from a different domain or subdomain, it's essential to build a good sender reputation for that new domain. They recommend warming up the IP and domain by gradually increasing the volume of emails sent.

Email Marketer from ExpertSender explains that by using different domains for From, DKIM and SPF you will need to ensure your email security is setup correctly. If not, then this can lead to a much higher chance of spam.

Marketer from Email Geeks explains that the DKIM signing domain is in relaxed alignment with the From domain, and that's what matters.

Marketer from Email Geeks explains that DMARC will only be involved if the From domain has a DMARC policy other than p=none.

Email Marketer from Mailgun shares that using different subdomains for transactional and marketing emails helps segment reputation. For example, use 'transactional.example.com' for transactional emails and 'marketing.example.com' for marketing emails. This isolates any reputation damage from marketing campaigns, preventing it from impacting critical transactional emails.

Email Marketer from MailerQ shares that in order to use different domains you'll need to ensure that your DMARC setup for your domain and subdomains are correct. By ensuring that DMARC is setup correctly you should be able to use different From addresses without issue.

Email Marketer from SendGrid shares that when using a shared IP, it's even more important to separate sending streams using subdomains. If one user on the shared IP sends spam, it can impact the deliverability of all users on that IP. Using a dedicated IP and properly authenticated domain mitigates this risk.

Marketer from Email Geeks explains that DMARC only works on the From domain.

Expert from Word to the Wise explains the necessity of maintaining current and correct SPF records. She describes that ensuring your SPF record accurately lists all authorized sending sources is critical, especially when dealing with multiple domains. Outdated or incomplete SPF records can lead to legitimate email being flagged as spam.

Expert from Spam Resource explains that using different domains for sending email can isolate reputation. If one domain has a poor reputation due to spam complaints or blacklisting, it won't necessarily affect the reputation of other domains you use. It's essentially creating separate identities for different sending purposes.

Expert from Email Geeks shares that the selector can differentiate the DKIM, and you don't need a subdomain for that.

Expert from Email Geeks suggests reading the reports and validating the configuration is working as expected.

Documentation from Google explains that domain alignment checks if the domain in the email's 'From' address matches the domain that authenticated the email. For SPF, the 'Return-Path' domain must match the 'From' domain. For DKIM, the 'd=' domain in the DKIM signature must match the 'From' domain.

Documentation from AuthSMTP explains that if the SPF record results in a 'hard fail' ('-all'), the email is very likely to be rejected by the recipient's mail server. Ensure your SPF records are configured to handle mail sent from different domains appropriately, likely using '~all' instead.

Documentation from RFC states that excessive SPF record lookups can cause issues. If you're using many different domains with SPF, this can lead to exceeding the DNS lookup limits, causing SPF to fail and emails to be rejected.

Documentation from Microsoft explains that for SPF, it's crucial that the domain used in the 'MAIL FROM' address (also known as the envelope sender address) matches the domain authorized to send emails on behalf of that domain. If the SPF check fails, it can lead to deliverability issues.

Documentation from DMARC.org explains that for DMARC to pass, either SPF or DKIM must align. SPF alignment requires the 'MAIL FROM' domain to match the 'From' header domain (strict alignment) or a subdomain of it (relaxed alignment). DKIM alignment requires the 'd' tag domain to match the 'From' header domain (strict) or a subdomain (relaxed).