Do not build a suppression rule from Apple's June note alone

Answer Do not build a suppression rule from Apple's June 15, 2026 note alone. That note said new Sign in with Apple addresses and new iCloud+ Hide My Email addresses would be issued on private.icloud.com later in the summer, and that existing addresses would keep forwarding. If the page now points you to a newer note, follow the newer note. A June paragraph is not a kill list.

The note that started this: Sign in with Apple and Hide My Email address changes, Apple Developer, June 15, 2026.

Sellers love a domain rule they can paste into a segment. Apple relay addresses look strange, so they get labeled bots. The June note is about where new addresses would be minted. It is not a finding that the addresses are fake, and it is not permission to throw away a subscriber who used a private relay on purpose.

The page is Apple's developer news from June 15, 2026. Read it as a dated announcement. New Sign in with Apple addresses, the ones that had been coming from privaterelay.appleid.com, and new Hide My Email addresses, the ones that had been coming from icloud.com, were both described as moving to private.icloud.com later that summer. Existing addresses would continue to forward. That is the whole operational sentence for a sender on the day the note went up. You keep accepting the addresses you already have. You get ready for a new suffix. You do not decide, from this paragraph, that one of the old suffixes is junk.

What did Apple announce on June 15, 2026?

The June 15 note said that new Sign in with Apple addresses, which had been on privaterelay.appleid.com, and new iCloud+ Hide My Email addresses, which had been on icloud.com, would be issued on private.icloud.com later that summer. Existing addresses would keep forwarding.

Two products were mentioned, and both were pointed at the same future suffix. A sender who only watches one product name will mis-file the other. Sign in with Apple and Hide My Email are different features that can land in the same inbox as a private address. The person behind either one asked Apple to hide the real mailbox. They may still have opted into the seller's list. The relay is the transport. The opt-in is the question that matters on a solo ad.

The note also tells you the old mail does not die on the day of the announcement. Forwarding continues for existing addresses. A suppression that drops privaterelay.appleid.com because the headline said change will drop people whose mail still works. That is a self-inflicted hole in the list, and it is invisible in a blended open rate until someone asks why the Apple slice vanished.

• Existing relay addresses stay mailable if they opted in.
• A new suffix is a reason to update an allowlist, not a reason to purge.
• The June text is dated. A pointer on the page is part of the text.
• Nobody calls a relay address a bot because the domain looks odd.

Should a sender suppress every Apple relay domain based on that note?

No. The June text is not a list of bad domains. Existing addresses keep forwarding. If the page now points to a newer note, follow that note before you write a suppression rule.

Apple edits news posts when the plan changes. A reader who cached the June wording and built a filter in July is obeying a draft. Open the page. If it says the announcement is outdated and sends you somewhere else, go there before you touch the file. This desk will not pretend a later clarification had already been published on June 15. On August 21 the disciplined move is to read whatever the June URL currently points at, and to obey that, not a memory of the first paragraph.

If you sell solo ads, say in the quote that you do not delete Apple relay domains by a homemade rule. If you buy solo ads, ask whether the seller's file still contains people who joined with a private address. A list that has zero of them may have purged real subscribers. A list that has them is not automatically dirty.

What should a solo ad buyer do with Apple relay addresses on a list?

Ask the seller whether those addresses opted in, and ask them not to delete a domain because a June headline sounded broad. A relay address can be a real subscriber. A made-up rule will cut real people.

The opt-in is the standard you already use for every other domain. Did this person ask this seller for this kind of mail? The relay does not answer that. The form they used answers it. A seller who cannot say should not be guessing with a suppression.

Keep the June note as a dated warning that the suffix was going to change, and as a reminder to follow the page's newer pointer. Best solo ad vendors will not invent a blocklist from a headline. Neither should the quote you pay for.