Last month a client emailed us from their @icloud.com address asking why our welcome emails kept landing in junk. Same email, same authentication, same content — Gmail put it in inbox, Outlook put it in inbox, Apple Mail threw it straight into junk. Every. Single. Time.

Frustrating? Yeah. We spent two hours on it before figuring out the problem was something embarrassingly basic (more on that in Step 2).

That's the thing about Apple's filtering. It doesn't behave like the others.

We're the JustEmails team, built by Velocity Digital Labs. Most deliverability guides focus on Gmail and Outlook — but Apple devices account for roughly 50-60% of email opens on mobile. If your emails hit junk on iPhone, you're losing a lot of eyeballs.

This is the Apple-specific troubleshooter. Just Apple Mail, iCloud, and iOS.

How Apple's Junk Filtering Actually Works

Apple's approach is a hybrid — part local machine learning, part iCloud-based filtering, part user behavior modeling. Here's what that means practically:

Local learning. Apple Mail on macOS and iOS learns from your actions on that specific device. Mark your email as junk once, the local model remembers. This is per-user, per-device — not a global reputation system.

iCloud filtering. For @icloud.com, @me.com, and @mac.com addresses, Apple runs server-side filtering before mail reaches the device. This layer checks authentication, content patterns, and sender IP reputation. Apple publishes almost nothing about how it weights signals. There's no iCloud Postmaster Tools equivalent.

Mail Privacy Protection. iOS 15+ and macOS 12+. Apple pre-fetches email content (including tracking pixels) through proxy servers. Doesn't affect junk filtering directly, but inflates your open rates. More on this in Step 5.

No engagement feedback loop. Gmail uses aggregate engagement data across all Gmail users to inform sender reputation. Apple doesn't share engagement data across users the same way. Black box. Good luck.

The upshot: fixing Apple deliverability isn't the same as fixing Gmail deliverability.

Step 1: Check Authentication First (Always)

Before anything else — verify SPF, DKIM, and DMARC are passing. This is the floor for every email provider, Apple included.

Send a test email to an @icloud.com address you control. Open it on a Mac, go to View > Message > All Headers. Look for Authentication-Results:

Authentication-Results: mx.icloud.com;
    dkim=pass header.d=yourdomain.com;
    spf=pass smtp.mailfrom=yourdomain.com;
    dmarc=pass policy.dmarc=reject header.from=yourdomain.com

If any of those show fail, softfail, or none, you've found your problem. Go fix your DNS records. Our DMARC ramping guide covers the full process, and our custom domain email setup guide walks through SPF, DKIM, and DMARC from scratch.

Common failures we see:

DKIM not configured for transactional senders. You set up DKIM on Google Workspace but forgot to configure it on SendGrid or Postmark. Each sending service needs its own DKIM signing.
SPF lookup limit exceeded. SPF allows 10 DNS lookups. If you include too many services, the record fails silently. Use dig +short TXT yourdomain.com and count the includes — nested includes count too. We cover SPF flattening techniques if you're hitting this limit.
Subdomain vs root domain mismatch. Sending from mail.yourdomain.com but DMARC is only on the root? Alignment fails. Use sp=reject in your DMARC record to cover subdomains.

If authentication is passing and you're still hitting junk, keep reading.

Step 2: List-Unsubscribe Headers (Non-Negotiable for Bulk Mail)

Apple's filter treats bulk senders differently than transactional senders. And the primary signal it uses to tell them apart? The List-Unsubscribe header.

For any marketing email, newsletter, or promotional message, you need this header:

List-Unsubscribe: <mailto:unsubscribe@yourdomain.com>, <https://yourdomain.com/unsubscribe?id=abc123>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

The List-Unsubscribe-Post header enables one-click unsubscribe without the user having to visit a webpage or send an email. Gmail, Yahoo, and Apple all support it. As of June 2024, Gmail actually requires it for bulk senders (5,000+ daily sends to Gmail). See our complete List-Unsubscribe header guide for implementation details.

If you're using a marketing platform — Mailchimp, ConvertKit, Beehiiv, whatever — they usually add this automatically. Check your email headers to confirm.

If you're sending marketing mail through your own SMTP (via JustEmails' transactional API or any other relay), you need to add the header yourself:

# Python example using JustEmails API
headers = {
    "List-Unsubscribe": "<mailto:unsub@yourdomain.com>, <https://yourdomain.com/unsub?id=123>",
    "List-Unsubscribe-Post": "List-Unsubscribe=One-Click"
}

Don't add list-unsubscribe to transactional email. Password resets, receipts, shipping notifications — these shouldn't have it. Apple's filter expects transactional mail to look like transactional mail. Mixing signals confuses the classifier.

Step 3: iCloud IP and Domain Reputation

Apple doesn't publish a Postmaster Tools dashboard like Google does. There's no way to look up your iCloud sender reputation directly.

I'll be honest: this drives me nuts. Google gives you data. Apple gives you silence.

What you can do:

Check if your sending IP is on a blocklist. Use MXToolbox's Blacklist Check or multirbl.valli.org. If your sending IP is listed on Spamhaus, Barracuda, or other major lists, iCloud will likely reject or junk your mail.

Use a clean sending IP. Shared IP pools mean bad actors can drag your reputation down. Dedicated IPs cost more (SendGrid charges $90/month, Postmark $50/month) but give you full control.

Warm up new IPs slowly. Sending 10,000 emails on day one from a brand-new IP is a red flag. Start with a few hundred, ramp up over 2-4 weeks. We've made this mistake. It took six weeks to recover.

Monitor feedback loops... where available. Apple doesn't offer a feedback loop. But if you're on Postmark or Mailgun, watch their bounce and complaint dashboards for spikes on @icloud.com addresses specifically. We wrote a detailed guide on handling bounce and complaint webhooks to protect your sender reputation.

Step 4: Content Factors That Trip Apple's Filter

Every spam filter does content analysis. Apple's is less documented than Gmail's, but through testing we've found patterns that consistently cause problems.

Heavy image-to-text ratio. Emails that are mostly images with minimal text look spammy. Keep your image-to-text ratio under 40-60% images.

URL shorteners. bit.ly, t.co, tinyurl — heavily abused by spammers. Apple's filter flags them. Use your own domain for tracking links.

Attachments on first contact. Sending a PDF to someone who's never emailed you before? Spam signal. Establish a reply thread first or use a file-sharing link.

Excessive formatting. Multiple font colors, giant text sizes, dozens of links. Real humans don't write emails that look like flyers.

Misleading subject lines. "Re:" or "Fwd:" on an email that isn't a reply or forward. "Urgent" on routine mail. Apple's filter is trained on patterns spammers overuse.

No physical address in footer. CAN-SPAM requires a physical address. Apple uses its presence as a legitimacy signal.

Strong opinion: the best deliverability trick is writing emails that humans actually want to read. I know that sounds annoyingly obvious. But half the "deliverability problems" we debug turn out to be content problems. People just... don't want the email. If your content is valuable and requested, everything else is table stakes. If it's unwanted, no amount of technical optimization saves you.

Step 5: Understand Mail Privacy Protection (and Its Limits)

Mail Privacy Protection (iOS 15+, macOS 12+) pre-fetches all remote content through Apple's proxy servers — including tracking pixels — regardless of whether the user opens the email. Your open tracking fires even when the user never looks at the email.

What this means for deliverability diagnosis:

You can't trust open rates on Apple devices. Period. A 70% open rate on iOS might really be 30% actual opens plus 40% phantom opens from Apple's pre-fetcher. We learned this the hard way when a client's "amazing" Apple engagement turned out to be mostly robots.

But MPP doesn't affect junk filtering. Pre-fetching happens after the email is already in inbox or junk. If emails are landing in junk, MPP isn't the cause.

For accurate Apple engagement data, use click rates, reply rates, or conversion rates instead of opens. If your click rate on Apple devices is significantly lower than Gmail/Outlook, that might indicate junk folder placement even if open rates look fine.

Step 6: User-Side Fixes (When You're the Recipient)

Sometimes the problem isn't the sender — it's the recipient's device settings. If someone tells you your emails keep landing in their Apple Mail junk, here's what they can do:

On macOS: Find the email in Junk, right-click > Move to Inbox, then add the sender to Contacts. Apple Mail trusts contacts.

On iOS: Open Mail, go to Junk folder, move the email to Inbox, add sender to Contacts. Check Settings > Mail > Blocked Sender Options isn't catching legitimate mail.

For iCloud web: Log into icloud.com/mail, move the email from Junk to Inbox, check gear icon > Rules for errant filters.

The user-side fix doesn't help you at scale. Obviously. But for important one-on-one contacts — your accountant, your lawyer, that client who keeps missing your invoices — walking them through the whitelist process is often the fastest path. Swallow your pride, send the instructions, move on.

A Quick Checklist Before You Panic

Before assuming Apple hates your domain:

SPF, DKIM, DMARC all passing? (Check headers on a test to @icloud.com)
Only one SPF record on your domain?
DKIM configured for every sending service (not just your primary)?
List-Unsubscribe header present on marketing mail?
Sending IP not on any blocklist?
Content doesn't have heavy images, URL shorteners, or spammy formatting?
Not sending attachments to new contacts?
Physical address in footer for marketing mail?

If everything checks out and you're still hitting junk, email support@justemails.app — we'll take a look at your headers and content. We've debugged enough Apple-specific issues that patterns jump out pretty quickly.

For the full DNS and authentication setup from scratch, start with our custom domain email guide. And if you want your brand logo showing next to your emails in Apple Mail and Gmail, check out our BIMI setup guide.

Frequently Asked Questions

Why do my emails go to junk on Apple Mail but not Gmail?

Apple Mail's junk filtering is partly local and partly iCloud-based, and it weighs different signals than Gmail. Gmail heavily uses engagement metrics and sender reputation from billions of users. Apple prioritizes authentication (SPF, DKIM, DMARC), the presence of list-unsubscribe headers for bulk mail, and local user behavior on that specific device. If a recipient has never opened your emails or has marked similar mail as junk before, Apple Mail on their device learns that pattern — even if Gmail users click through every time.

Does Mail Privacy Protection affect my deliverability on Apple devices?

Not directly for junk filtering, but it affects your metrics. Mail Privacy Protection (introduced in iOS 15) pre-fetches all images and caches emails through Apple's proxy servers. This means open tracking pixels fire even when the user doesn't open the email, inflating your open rates on Apple devices. It doesn't cause emails to land in junk — but if you're using open rates to measure Apple deliverability, those numbers are unreliable. Use click rates or reply rates instead.

How do I check if my DKIM is passing on Apple Mail specifically?

Send a test email to an iCloud address (yourname@icloud.com or yourname@me.com). Open it in Apple Mail on macOS, go to View > Message > All Headers. Look for the Authentication-Results header. You'll see spf=pass, dkim=pass, and dmarc=pass (or fail) listed. If any show fail or none, that's your problem. Apple Mail doesn't surface this in iOS, so use macOS or forward the raw message to yourself and inspect the headers there.

Should I add a list-unsubscribe header for transactional emails?

No — list-unsubscribe is specifically for marketing and bulk email, not transactional. Adding it to password resets, receipts, or account notifications can actually confuse filters and potentially train user behavior incorrectly. Apple's filter distinguishes between bulk senders (who should have list-unsubscribe) and transactional senders (who shouldn't). Keep your transactional and marketing mail on separate sending streams, and only add list-unsubscribe to the marketing stream.

Try JustEmails

Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.

Start your 7-day free trial → · How it compares

Fix Emails Going to Junk in Apple Mail and iPhone (2026)