How do I fix Apple Mail DMARC failure when sending from Gmail with a non-Gmail domain?

Email marketer from SparkPost details understanding the basics of DMARC is vital to ensure your email is not marked as spam and they recommend ensuring you set this up or configure your settings correctly.

Email marketer from Mailhardener responds that when using Gmail's SMTP relay to send emails with a different From: address, DMARC failures are likely. To resolve this, configure your domain's SPF and DKIM records correctly and ensure that the From: address aligns with the authenticated sending domain.

Email marketer from Reddit answers that the problem is often caused by the user trying to send emails with a 'From' address that doesn't match the Gmail account. The recommended solution involves correctly configuring the 'Send mail as' setting in Gmail or Google Workspace to use the desired domain.

Email marketer from StackOverflow responds to ensure you configure SPF records for all domains you use to send email and that you are using the domain of the account set up in Apple Mail to send emails.

Email marketer from Email Geeks explains to ensure the workspace account is correctly set up in Apple Mail and the correct SMTP server and credentials actually work and if Apple Mail has a problem sending emails via the accounts SMTP server, it asks to use a different server.

Email marketer from Email Geeks shares that the outbound for the account had defaulted to Gmail and to fix it, toggle the drop down to the right outbound account for the email address.

Email marketer from MXToolbox explains that DMARC relies on both SPF and DKIM for authentication. Ensure your SPF record is correctly configured to authorize Gmail to send emails on behalf of your domain.

Email marketer from Litmus answers that ensuring both SPF and DKIM records are properly set up for your domain and also that the domain in the 'From' header matches what you are authenticating with is vital to ensure your emails are not marked as spam.

Email marketer from StackExchange shares that when using Gmail SMTP servers to send emails, if the email isn't correctly authenticated with SPF/DKIM for the domain in the 'From:' address, it's likely to trigger a DMARC failure. One workaround includes configuring Google Workspace to send as the domain or sending directly from the domain's mail server.

Email marketer from EmailOnAcid explains that to resolve DMARC issues, setting up DKIM (DomainKeys Identified Mail) is crucial. DKIM adds a digital signature to your outgoing emails, which verifies that the email was sent and authorized by the owner of the domain and gives clear steps on how to do this.

Email marketer from Super User Forum shares that ensuring both SPF and DKIM records are properly set up for your domain in Google Workspace is essential and failing to do this will most likely result in emails failing the DMARC test.

Expert from Email Geeks shares that Apple Mail is a mail client, not a mail server, and needs an outbound server to send mail and the outbound server isn’t configured to sign with cooalliance.com DKIM.

Expert from Email Geeks shares that one cannot use a cooalliance.com email address unless they are using mail infrastructure owned or approved by the owners of cooalliance.com to send mail.

Expert from Email Geeks explains that it seems like Apple Mail is configured to send it from the user's personal Gmail account, not the Workspace account where the domain is configured and when connecting to Gmail to send from a mail client, Gmail overwrites the mail from with the Gmail user account credentials.

Expert from Spam Resource explains that if you send from a Gmail account (even if you set the 'From:' to a different address), Gmail will likely rewrite the message in a way that can cause DMARC failures. Using your own domain's SMTP server with proper SPF/DKIM setup is crucial to avoid this.

Expert from Email Geeks explains that sending mail from Gmail but using a non-Gmail domain in the From: header will cause DMARC to fail, as DMARC sees it as incorrect.

Expert from Email Geeks explains that the Google Workspace account may not be configured to sign with DKIM and questions if the user is trying to relay out through a Gmail account rather than the Workspace account.

Expert from Word to the Wise suggests that when experiencing DMARC failures while sending from Gmail with a non-Gmail domain, it's essential to ensure that your domain's SPF and DKIM records are correctly configured. It is crucial to align the 'From:' address with a domain authorized to send email through Gmail's servers. Also, verify that Apple Mail is using the correct outgoing SMTP server for your custom domain.

Documentation from Apple Support details the steps to change the outgoing mail server (SMTP) settings in Mail on Mac. It highlights the importance of using the correct server provided by your email service provider for sending mail.

Documentation from Google Workspace Admin Help provides the steps to configure Gmail to send emails using a custom 'From' address. This involves adding the email address and verifying it, ensuring that you have permission to send emails on behalf of the domain.

Documentation from Google Workspace Admin Help explains that to prevent email spoofing, add Google's SPF record to your domain. This authorizes Google to send email on behalf of your domain, helping to prevent messages from being marked as spam.

Documentation from RFC Editor (RFC 7489) explains that DMARC builds on SPF and DKIM technologies to provide email domain owners with a mechanism to reduce the threat of unauthorized use of their email addresses.

Documentation from DMARC.org explains that DMARC (Domain-based Message Authentication, Reporting & Conformance) is an email authentication protocol that allows domain owners to specify how email receivers should handle messages that fail authentication checks (SPF and DKIM). This helps prevent email spoofing and phishing attacks.