Note: This is purely an iCloud services issue, it has nothing to do with iOS or macOS.
Summary:
If a DKIM signed message is forwarded through iCloud, the DKIM signature no longer matches, breaking DMARC authentication.
Back in 2017 I opened issue 35953200, which was about messages being forwarded through iCloud mail breaking the DMARC authentication. The problem was fixed sometime in 2018, but now I'm seeing the same problem again (albeit possibly for different reasons).
I'm seeing the current problem in messages as early as February 3rd.
Steps to Reproduce:
Set iCloud to forward messages to another mail provider, preferably one that does strong SPF/DKIM/DMARC authentication: iCloud.com > Mail > Preferences > Forwarding > Forward my mail to: (external email address)
Receive an email to your iCloud (or mac.com, or me.com) email address, sent from a sender that signs the message with DKIM and has DMARC rules established.
NOTE: Many emails from Apple are an example of emails that fulfill step #2: almost every email from Apple has a DMARC failure when forwarded through iCloud. This does not, however, mean that only Apple emails are affected.
Expected Results:
Emails that are forwarded by iCloud should still pass DKIM and DMARC authentication.
Actual Results:
Emails that are forwarded by iCloud do NOT pass DMARC authentication
Attached case:
An especially good example is marketing emails from Apple, because Apple sends the SAME email to two of my addresses: directly to , and the 2nd one to .
I have iCloud set to forward emails sent to to . Therefore, we can compare the emails to see exactly what changes resulted from being forwarded through iCloud. Attached are two such email pairs.
The emails that are sent directly to has an insideapple.apple.com DKIM signature. When FastMail checked the authentication, it passes DKIM and DMARC.
On the messages that are forwarded through iCloud (sent to <iCloud address., forwarded to ), the message fails DKIM because the message or body has been altered:
Authentication-Results: mx4.messagingengine.com;
arc=none (no signatures found);
dkim=fail (message has been altered, 2048-bit rsa key sha256)
Comparison of the message shows that that the message is in fact altered by iCloud.
Impact:
Since failing DMARC indicates the message is forged, it gets a very high probability of Spam score. The result is that many messages that are routed through iCloud.com are considered to be SPAM. Ironically it is the messages that are sent from the most security conscious senders (banks, major companies, etc.) are the ones that are almost always considered (falsely) to be SPAM, because those are the senders that publish DMARC rules in their DNS records.
Comparison to other mail systems:
From what I've seen, ONLY iCloud.com is breaking DMARC on forwarding email. Gmail for example is fine.
Description
Note: This is purely an iCloud services issue, it has nothing to do with iOS or macOS.
Summary: If a DKIM signed message is forwarded through iCloud, the DKIM signature no longer matches, breaking DMARC authentication.
Back in 2017 I opened issue 35953200, which was about messages being forwarded through iCloud mail breaking the DMARC authentication. The problem was fixed sometime in 2018, but now I'm seeing the same problem again (albeit possibly for different reasons).
I'm seeing the current problem in messages as early as February 3rd.
Steps to Reproduce:
Set iCloud to forward messages to another mail provider, preferably one that does strong SPF/DKIM/DMARC authentication: iCloud.com > Mail > Preferences > Forwarding > Forward my mail to: (external email address)
Receive an email to your iCloud (or mac.com, or me.com) email address, sent from a sender that signs the message with DKIM and has DMARC rules established.
NOTE: Many emails from Apple are an example of emails that fulfill step #2: almost every email from Apple has a DMARC failure when forwarded through iCloud. This does not, however, mean that only Apple emails are affected.
Expected Results: Emails that are forwarded by iCloud should still pass DKIM and DMARC authentication.
Actual Results: Emails that are forwarded by iCloud do NOT pass DMARC authentication
Attached case: An especially good example is marketing emails from Apple, because Apple sends the SAME email to two of my addresses: directly to, and the 2nd one to .
I have iCloud set to forward emails sent to to . Therefore, we can compare the emails to see exactly what changes resulted from being forwarded through iCloud. Attached are two such email pairs.
The emails that are sent directly to has an insideapple.apple.com DKIM signature. When FastMail checked the authentication, it passes DKIM and DMARC.
On the messages that are forwarded through iCloud (sent to <iCloud address., forwarded to), the message fails DKIM because the message or body has been altered:
Authentication-Results: mx4.messagingengine.com; arc=none (no signatures found); dkim=fail (message has been altered, 2048-bit rsa key sha256)
Comparison of the message shows that that the message is in fact altered by iCloud.
Impact: Since failing DMARC indicates the message is forged, it gets a very high probability of Spam score. The result is that many messages that are routed through iCloud.com are considered to be SPAM. Ironically it is the messages that are sent from the most security conscious senders (banks, major companies, etc.) are the ones that are almost always considered (falsely) to be SPAM, because those are the senders that publish DMARC rules in their DNS records.
Comparison to other mail systems: From what I've seen, ONLY iCloud.com is breaking DMARC on forwarding email. Gmail for example is fine.
- Product Version: Created: 2019-04-14T21:10:35.948506 Originated: 2019-04-14T00:00:00 Open Radar Link: http://www.openradar.me/49888068