Apple Private Email Relay

Understanding Apple Private Email Relay restrictions and verification limitations.

View as Markdown

This article explains how Emailable handles specific restricted email types, such as Apple’s Private Relay and FCC-listed wireless domains. These addresses are categorized as Undeliverable due to privacy protocols and federal regulations.

Apple’s Private Email Relay allows users to mask their real email address using a "Hide My Email" alias (e.g., kwuvmn2aoi@privaterelay.appleid.com).

Why These Are Marked Undeliverable

Emailable returns an Undeliverable State for these addresses because Apple only allows delivery if the sender’s domain is explicitly authorized within the developer's Apple Developer Account.

Since Emailable cannot authenticate as your authorized domain during verification, Apple rejects the SMTP handshake.

Usage and Best Practices

  • Authorized Collection: If you collected these emails through an app you own and control, do not verify them with Emailable. You are already authorized to send to them via your registered domains.
  • Third-Party Sources: If you did not collect these emails through your own authenticated app, you should not attempt to send to them. Apple will reject any unauthorized traffic.
  • Identification: These addresses typically end in @privaterelay.appleid.com or @icloud.com.
  • Routing: Emails are routed to the user’s primary Apple ID email. The address remains consistent for a user across all apps from a single development team, but changes across different developers.

Summary Table

Email Type Classification Reason Recommendation
Apple Private Relay Undeliverable Requires domain authorization Skip verification if collected via your own app.

For further technical details on how these classifications affect your deliverability reports, please contact our support team.

Was this page helpful?

Thank you for helping improve our documentation.

Related articles