DMARC failures when sending emails from Apple Mail, using a Gmail account with a non-Gmail domain, are often due to authentication mismatches and misconfigurations. Experts, marketers, and documentation sources agree that properly setting up SPF and DKIM records for your domain is crucial. A key problem is when Gmail rewrites the message or when Apple Mail uses the personal Gmail account settings instead of the Google Workspace account settings for the domain. The 'From' address must align with the authenticated sending domain, or the email infrastructure used must be authorized by the domain's owners. Additionally, understanding DMARC basics, configuring Gmail to send with a custom 'From' address, and ensuring Apple Mail uses the correct outgoing SMTP server are vital steps to resolve this issue and prevent email spoofing.
11 marketer opinions
When sending emails from Apple Mail using a Gmail account with a 'From' address of a non-Gmail domain, DMARC failures often occur due to authentication mismatches. Several solutions address this issue: ensuring correct SMTP server and credential configuration within Apple Mail; properly setting up SPF and DKIM records for the domain in Google Workspace; matching the 'From' address with the Gmail account or authorized domain; and utilizing the domain's mail server directly instead of Gmail's SMTP relay. Correctly configuring 'Send mail as' settings in Gmail/Google Workspace and understanding DMARC basics are also critical.
Marketer view
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.
7 May 2025 - SparkPost
Marketer view
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.
18 Feb 2024 - Mailhardener
7 expert opinions
DMARC failures when using Apple Mail to send from a Gmail account with a non-Gmail domain often stem from misconfigurations and authentication issues. Sending mail from Gmail with a different 'From' address can trigger DMARC failures because Gmail might rewrite the message, causing authentication discrepancies. A key issue is the need to use mail infrastructure owned or approved by the domain in the 'From' address. Apple Mail, being a mail client, requires a properly configured outbound server to sign with the correct DKIM. The Google Workspace account associated with the domain may not be set up to sign with DKIM, and Apple Mail might be configured to use a personal Gmail account instead of the Workspace account. Ensuring SPF and DKIM records are correctly configured and aligning the 'From' address with a domain authorized to send email through Gmail or using your own domain's SMTP server are vital steps for resolving this.
Expert view
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.
15 Mar 2023 - Email Geeks
Expert view
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.
8 Apr 2025 - Email Geeks
5 technical articles
Documentation regarding DMARC failure when using Apple Mail and Gmail with a non-Gmail domain highlights several key points: Adding Google's SPF record to your domain is crucial to authorize Google to send emails on your behalf and prevent them from being marked as spam. DMARC, an email authentication protocol, enables domain owners to specify how email receivers should handle messages failing authentication checks (SPF and DKIM), combating spoofing and phishing. Apple Support details how to change outgoing mail server (SMTP) settings in Mail on Mac, emphasizing the need for the correct server from your email provider. DMARC, as per RFC 7489, builds upon SPF and DKIM to give domain owners tools against unauthorized email use. Google Workspace Admin Help provides steps to configure Gmail for sending emails with a custom 'From' address, requiring verification and permission to send on behalf of the domain.
Technical article
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.
18 Oct 2024 - Apple Support
Technical article
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.
29 Jul 2024 - Google Workspace Admin Help
Are SPF, DKIM, and DMARC records necessary for transactional email servers not used for marketing?
Do Gmail reply-to domains need to match the from domain?
Do SPF and DKIM records need to be aligned for all email service providers?
How can I implement a strict DMARC policy without blocking Google Workspace emails?
How can I improve SPF alignment and email deliverability when using Hubspot?
How can I resolve DMARC verification failures when using a subdomain for email sending?
How do I fix an SPF fail when using Hover and Netlify?
How do I fix DKIM alignment errors and configure DKIM signing for a custom domain in Microsoft 365 and is include:spf.mtasv.net required for mailchimp?
How do I fix DMARC issues with Mailchimp and Woodpecker while using O365?
How do I troubleshoot DMARC failures and potential DKIM replay attacks affecting email deliverability?
What DMARC settings should I use and what are the implications of using p=reject?