Apple’s postmaster page for iCloud Mail became a list of requirements in February 2025: bulk mail to icloud.com, me.com and mac.com must use SPF and DKIM, publish DMARC, come from IPs with reverse DNS and offer an unsubscribe that works at once — or be rejected. Apple does not say how much mail counts as bulk.
| Applies to | Bulk mail to icloud.com, me.com and mac.com |
| Bulk sender | Not defined; Apple publishes no threshold |
| Authentication | SPF and DKIM, and a published DMARC policy |
| If not met | The email is rejected |
| Postmaster tool | None; contact icloudadmin@apple.com |
Check your domain against Apple iCloud Mail’s rules
Enter the domain in your From address. What its DNS shows is tested here; for the rest, send one message to our email test.
What bulk senders need
Apple says all of these must be met to send bulk email to iCloud Mail, and that email which does not meet them will be rejected. It does not define bulk.
- Both SPF and DKIM.
- A DMARC policy published for the sending domain — Apple sets no minimum policy. iCloud checks SPF and DKIM on all mail it receives and honours the sender’s DMARC policy.
- ARC headers added to mail you forward.
- Reverse DNS that identifies your sending IPs with your domain.
- Compliance with RFC 5321 and RFC 5322.
- Consistent sending IPs, domains and From name and address — with marketing and transactional mail kept apart.
- Mail only to recipients who explicitly subscribed: no purchased, rented or appended lists.
- An unsubscribe link that takes effect immediately, and addresses on your unsubscribe or suppression list never re-activated.
- Temporary and permanent SMTP errors acted on, with a bounce-handling policy, and inactive subscribers removed periodically.
What happens to mail that does not comply
Bulk mail that does not meet the requirements is rejected. Apple says a rejection explains why, and most include a URL with more detail. It publishes no list of its own SMTP codes, runs no feedback loop and keeps no allowlist: delivery rests on the reputation of your IPs and domains, content checks and what users report.
Apple iCloud Mail’s tools for senders
- Postmaster information for iCloud Mail — Apple’s requirements, and what to send to icloudadmin@apple.com if you are blocked
- Private email relay — for apps using Sign in with Apple: register every domain and address that sends to privaterelay.appleid.com
Recommended, not required
- The M3AAWG Sender Best Practices.
- Suppressing disengaged subscribers and removing addresses that bounce consistently.
- Both SPF and DKIM for Sign in with Apple relay mail, where one of them is the minimum.
Common mistakes
- Mail to Sign in with Apple relay addresses from a domain or address not registered in your Apple developer account: it bounces.
- Relay mail whose DKIM d= does not exactly match the From domain, or whose envelope sender is not the registered domain — the relay wants an exact match, not a relaxed one.
- Forwarding without ARC, now a requirement at Apple.
Setting up the records? The exact SPF include and DKIM records for each service are in our email setup guides, and what each part of a record does is in SPF, DKIM and DMARC explained.
Questions
How do I contact Apple about blocked mail?
Email icloudadmin@apple.com with your company name, your domain, the affected IPs, the SMTP errors you received and when the problem started.
Does iCloud Mail require DMARC p=reject?
No. Apple asks for a published DMARC policy and sets no minimum; iCloud then applies whatever policy you publish.
Sources
Checked against Apple iCloud Mail’s own documentation on 25 September 2026:
- Postmaster information for iCloud Mail — support.apple.com
- Configure private email relay service — developer.apple.com