Is DKIM configuration sufficient for Google Workspace and O365 email authentication?
Summary
What email marketers say6Marketer opinions
Email marketer from Mailjet shares that DKIM and SPF are two essential email authentication methods and the two should be used in conjunction. They add digital signatures to emails, which recipients can then verify, and prevent malicious actors from sending emails as someone else.
Email marketer from StackExchange answers that for O365, it’s crucial to enable DKIM and ensure it aligns with your domain. Microsoft’s default DKIM setup might use a Microsoft domain, which can cause issues with DMARC alignment. Custom DKIM configuration is highly recommended.
Email marketer from MXToolbox explains that while Google Workspace provides a default DKIM signature, creating a custom DKIM record specific to your domain is important. This helps to improve deliverability and ensures that your emails are properly authenticated.
Email marketer from SendGrid Blog explains that DKIM is a critical component of email authentication. It helps to prove that an email was sent and authorized by the owner of the domain. Properly configured DKIM improves email deliverability and sender reputation.
Email marketer from AuthSMTP explains that DKIM is very important for a high deliverability rate and is highly recommended for all customers and domains. It also highlights that some providers mark all messages as spam without correct configuration.
Email marketer from Reddit shares that they had issues with Google Workspace until they properly configured DKIM. They recommend generating a DKIM record specifically for Google Workspace and adding it to the DNS records, even if other DKIM records are already in place.
What the experts say5Expert opinions
Expert from Word to the Wise explains that while DKIM is important, it's DMARC that tells the receiving mail server what to do with messages that fail authentication checks. It's a crucial policy layer on top of DKIM and SPF.
Expert from Email Geeks explains that for non bulk mail any DKIM is sufficient, but alignment is a good idea.
Expert from SpamResource shares that DKIM is one of the pillars of modern email authentication along with SPF and DMARC. They are complementary technologies and not just one should be used, they should all be used together.
Expert from Email Geeks shares that if sending any bulk mail then all mail needs to align.
Expert from Email Geeks shares they are dealing with a similar situation on O365, where DKIM is configured for Constant Contact but not O365, resulting in a generic Microsoft DKIM signature and uncertainty about its adequacy for an SMB.
What the documentation says4Technical articles
Documentation from Microsoft Support details that to configure DKIM for O365, you need to use PowerShell to create DKIM signing keys, publish them to DNS, and then enable DKIM signing. It emphasizes the importance of using two DKIM keys for redundancy and rotation purposes.
Documentation from RFC explains that DKIM defines a domain-level authentication framework for email using digital signatures. DKIM permits signing email senders to associate a domain name with an email message, thereby attesting to its authenticity.
Documentation from dmarcian explains that while DKIM is essential for email authentication, it's most effective when combined with SPF and DMARC. DKIM alone might not be sufficient to fully protect your domain from spoofing and phishing attacks.
Documentation from Google Workspace Admin Help explains that DKIM setup involves generating a DKIM key in the Google Workspace admin console, adding the DKIM record to your domain's DNS settings, and then enabling DKIM signing for your domain. This helps verify that messages sent from your domain are authenticated.