Apple’s False “User Not Found” Bounces Put Valid iCloud Addresses on Suppression Lists
Apple returned false "user not found" errors for valid iCloud and Hide My Email addresses on 17 November, and ESPs suppressed real recipients. SparkPost and Bird have cleaned up; Mailgun is still removing them.

Apple's mail servers rejected valid iCloud and Hide My Email (Private Relay) addresses with false "user not found" errors on 17 November 2026. Because those errors look like permanent failures, sending platforms treated them as hard bounces and added real, working recipients to their customers' suppression lists. SparkPost, Bird and Mailgun have confirmed the problem on their status pages and say the cause was on Apple's side.
The bounces arrived in several waves on the same day as Apple's iCloud Mail outage. Apple's System Status page now lists an iCloud Mail performance issue from 08:45 to 13:15 PST (16:45 to 21:15 UTC), marked resolved, with the message "This service may have been slow or unavailable." Apple has not published anything about the bounces themselves on that page.
Key facts
- What happened: false "user not found" bounces for valid iCloud and Private Relay (privaterelay.appleid.com) addresses
- When: 17 November 2026, in several waves starting in the morning (US time)
- Cause: an issue on Apple's side, according to SparkPost, Bird and Mailgun
- Side effect: valid recipients added to suppression lists as hard bounces
- SparkPost and Bird: suppressions removed, incident resolved at about 22:55 UTC on 17 November
- Mailgun: still removing affected addresses from suppression lists at 03:58 UTC on 18 November (status: monitoring)
- Apple System Status: iCloud Mail performance issue from 08:45 to 13:15 PST, resolved
What the sending platforms report
SparkPost opened its incident at 14:45 EST (19:45 UTC). It said that starting that morning, Apple's mail servers had returned "a large number" of "user not found" bounces for iCloud and Hide My Email addresses that are valid, and that "some valid recipient addresses may have been added to your suppression list." At 20:40 UTC it confirmed the cause was on Apple's side, that Apple had returned the errors "in several waves", and that it had started removing the suppressions, a cleanup it expected to take several hours because of the number of addresses involved.
At 22:55 UTC SparkPost closed the incident: the suppressions created by the false bounces had been removed and "the affected addresses can receive email again." It also said it had made a change so that if Apple returns these errors again, the addresses will not be added to suppression lists. Bird, which owns SparkPost, posted the same updates and resolved its incident at 22:54 UTC. Both told customers that no action was needed.
Mailgun reported "erroneous 'user not found' responses" for iCloud and Private Relay addresses at 12:31 PST (20:31 UTC) and said it was removing addresses added to suppression lists during the affected period. Its latest update, at 19:58 PST on 17 November (03:58 UTC on 18 November), says impacted addresses "are in the process of being removed from suppression lists." The incident was still in monitoring status when this article was published.
Why a false "user not found" hurts
"User not found" is the classic permanent failure, usually sent as a 550 5.1.1 user unknown response. Sending platforms are built to stop mailing such an address at once, because repeated sends to non-existent mailboxes damage sender reputation. When a mailbox provider returns that code for addresses that do exist, the safety mechanism works against the sender: the recipient stays suppressed and silently stops getting newsletters, receipts or password resets until someone removes the entry.
Hide My Email addresses add a twist. They are relay addresses on privaterelay.appleid.com that forward to the user's real inbox, so a sender cannot spot them as iCloud users by looking at the domain alone. Lists with many Sign in with Apple sign-ups are the most exposed.
What it means for senders
What changes
Valid iCloud and Hide My Email recipients may sit on your suppression list after Apple returned false "user not found" bounces on 17 November 2026. SparkPost and Bird have removed those suppressions; Mailgun is still removing them.
Who is affected
Anyone who sent to iCloud, me.com, mac.com or privaterelay.appleid.com addresses on 17 November, through an ESP or their own servers. Senders who keep their own suppression list, or who sync bounces from their ESP into a CRM, may still hold the bad entries even after the ESP cleanup.
When
The false bounces came in waves on 17 November 2026. SparkPost and Bird finished their cleanup the same evening (UTC); Mailgun's cleanup was still under way on 18 November.
Action checklist
- Export the hard bounces of 17 November from your ESP and filter on icloud.com, me.com, mac.com and privaterelay.appleid.com.
- Check your own suppression lists in your CRM, data warehouse or self-hosted MTA: an ESP cleanup does not reach copies you synced elsewhere.
- Reactivate only those addresses whose bounce text was "user not found" on that day and that were engaged before; keep other bounce reasons suppressed.
- Resend critical transactional mail such as receipts, account confirmations and password resets that bounced for those recipients.
- Watch your ESP's status page if you use Mailgun, until its incident is closed, then confirm the suppressions are gone.
- Review your bounce rules so a sudden spike of permanent failures from one mailbox provider triggers a review instead of instant suppression.
Sources
- SparkPost Status: Invalid "user not found" bounces from Apple iCloud / Private Relay addresses, 17 November 2026
- Bird Status: Invalid "user not found" bounces from Apple iCloud / Private Relay addresses, 17 November 2026
- Mailgun Status: Erroneous "user not found" responses for Apple iCloud and Private Relay addresses, 17 and 18 November 2026
- Apple System Status, iCloud Mail entry for 17 November 2026
Related on SMTPedia
SMTPedia News follows our editorial standards. Spotted an error? See how we correct it.
Get SMTPedia news first on Google
Add us as a preferred source to see our stories in Top Stories and Discover.
Add as preferred sourceUseful story?
SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.
Buy SMTPedia a coffeeNewsletter