Why your emails land in junk on icloud but not gmail
A friend messaged me last week, a bit frustrated. His sign-in emails were landing in the inbox on Gmail and Proton, but going straight to Junk on iCloud mail! He had already asked the AI about it but kept circling the same three things SPF, DKIM, DMARC and telling him to double-check the records.
We hopped on a Zoom call and walked through every setting together. Before we started clicking around, I gave him the short version of what usually causes this, because the technical stamps are only part of the story, most of the time the difference comes down to a few basic rules.
First of all the mail services look at:
- whether your domain is allowed to send (SPF),
- whether the message carries a valid signature (DKIM),
- and what you told them to do if those checks fail (DMARC).
When those line up, the mail looks legitimate but plenty of services will still put it in Junk if something else as below feels off, especially stricter ones like iCloud.
- Shared infrastructure makes it messier. A lot of email tools run on the same IPs, so one noisy sender can drag the reputation down for everyone else.
- High bounce rates, links to blocked domains, or cold-emailing old lists start the slide.
- Dropping open rates as the mail is being delivered, but more of it is landing in Junk/Spam (or people are simply ignoring it). This is a softer, later signal. By the time your service might warn you and you notice opens falling, but the big inbox providers have already noticed and the filters decided your mail looks less trustworthy.
High bounce rates means the mail is failing to deliver at all (bad or dead addresses). When you send to an address that doesn’t work, the receiving server sends back a
bouncea automatic failure notice. This is a hard, technical signal that inbox providers see immediately. It directly damages your reputation. A few bounces are normal. A high rate (often anything consistently above 2–5%, and especially 8% or more) is a red flag.
Some tools treat guarding against that as the main job. They will pause or reject accounts that keep repeating the same mistakes, because one bad actor eventually hurts the customers who clean their lists and only mail people who asked. You can bring your own mail server and skip those rules, or you can use a managed service that applies them for you. Either way, deliverability is mostly about not sharing your reputation with people who treat email like a free-for-all.
Small habits still matter once the stamps are correct:
- keep the From address stable,
- put price, codes and numbers in the body instead of the subject,
- and clean old addresses before the bounce rate climbs.
Back to his issue, we went through his records on the call. SPF included the right services. DKIM was published and matching. DMARC was present. Everything passed!
The only clear difference from a similar project that landed in the iCloud inbox was the subject line he was putting the numeric sign-in code right in the subject (141290 is your sign-in code) for quick user view!
I asked him to change it to something plain like Your sign-in code, sent a fresh test, and it went to the inbox :) The stamps had been fine the whole time. The subject was the piece iCloud was treating more cautiously, especially on a domain that didn’t yet have much positive history with Apple users.
That is usually how it usually goes, the three records get you most of the way. Shared reputation and a few content choices decide the rest.