Will SPF and DKIM on a subdomain but delivering emails through a main domain cause an issue?
Summary
What email marketers say7Marketer opinions
Email marketer from GlockApps shares that your IP address and sending domain are two of the most important factors that impact your email deliverability. Make sure that you maintain a good reputation with both of them.
Email marketer from Mailjet shares that using a subdomain for sending emails is a common practice, and SPF and DKIM should be properly configured for that subdomain. They emphasize that while the From: domain might be the main domain, the SPF and DKIM authentication should align with the sending subdomain to ensure deliverability and avoid spam filters.
Email marketer from SparkPost explains that as long as your SPF and DKIM records are properly configured for the sending domain (the subdomain in this case), it should not cause issues. They recommend ensuring that the subdomain is properly set up and monitored for reputation.
Email marketer from Reddit shares that using subdomains for different types of email (e.g., marketing, transactional) is a common and recommended practice. They advise that you must set up SPF and DKIM records correctly for each subdomain used to send email to ensure proper authentication and deliverability.
Email marketer from SendGrid answers that the first step to ensuring email gets delivered correctly is to set up email authentication. Setting up authentication ensures recipients recognize that you are who you say you are, and that your messages are safe.
Email marketer from Email on Acid emphasizes that while using subdomains for email sending is acceptable, it's crucial to monitor the reputation of each subdomain. Poor sending practices on a subdomain can negatively impact deliverability.
Email marketer from StackExchange shares that using subdomains is not inherently problematic as long as the correct SPF and DKIM records are published and properly configured for the subdomain.
What the experts say3Expert opinions
Expert from Word to the Wise explains that Email Authentication can be difficult to set up but is essential for good delivery rates. Email Authentication helps receiving domains verify that your mail really came from you and that it wasn't spoofed by someone else.
Expert from Email Geeks explains that neither SPF nor DKIM authenticate the From header, and it's not unusual for the domains they do authenticate to be different from the one in the From header. The return path uses the mg. hostname, which is what you'd expect the SPF to authenticate. The d= in DKIM is aligned with the domain in the From. It's the ideal you aim for and will not cause any issues.
Expert from Spam Resource explains that SPF and DKIM should be correctly aligned, especially when sending from subdomains. It responds that using a subdomain for sending is fine, but the authentication must be set up correctly for that subdomain to pass checks and avoid deliverability problems.
What the documentation says5Technical articles
Documentation from DMARC.org explains DMARC (Domain-based Message Authentication, Reporting & Conformance) relies on the proper alignment of SPF and DKIM. It's crucial to ensure SPF and DKIM align with the domain in the From: header to pass DMARC checks.
Documentation from DKIM specifies that DKIM authenticates the message by adding a digital signature to the email header. The 'd=' tag in the DKIM signature indicates the domain responsible for signing the message. As long as the DKIM signature verifies against the domain specified in the 'd=' tag, it should pass authentication, even if the 'From:' header uses a different domain.
Documentation from Google explains that you can delegate SPF records for subdomains, which is useful if you want to send email from a subdomain. Make sure your SPF record includes the sending sources for the subdomain. It also highlights the importance of correctly configuring SPF to avoid deliverability issues.
Documentation from Microsoft explains how SPF records work and specifies that the domain used in the MAIL FROM address is authenticated using SPF. When sending emails from a subdomain, the SPF record must be published for that subdomain to authenticate the sending server.
Documentation from RFC Editor specifies that SPF authenticates the 'MAIL FROM' address (return-path), and it doesn't directly authenticate the 'From:' header. Therefore, as long as the SPF record for the domain used in the 'MAIL FROM' address is correctly set up, it will pass authentication, even if the 'From:' header uses a different domain.