Lorixen.
EN

Emails to Sign in with Apple relay addresses bouncing?

Short answer: When a customer signs up with Sign in with Apple and chooses to hide their email, your app receives a relay address, usually ending in @privaterelay.appleid.com. Apple only forwards mail to that address from senders you have registered in your Apple Developer account, and only if the message passes SPF or DKIM in the exact way Apple checks. If your booking confirmations, receipts or password resets to those customers bounce, the fix is almost always to register every sending domain or address and line up your mail authentication with it.

Why these emails behave differently

Apple's documentation describes the private relay as a service that routes all email between you and the customer. The address it gives you is generated automatically and hides the person's real inbox. A few properties matter for anyone sending mail to it:

  • The address ends in @private.icloud.com, @privaterelay.appleid.com or @icloud.com.
  • It is the same for that customer across every app from your development team, and different for apps from other teams.
  • It stays active whether or not the app is installed, so you can keep emailing the customer later.
  • Apple documents a daily limit on the number of emails per relay address, counting both your messages and the customer's replies.
  • If the customer turns off forwarding for your app, the relay rejects everything you send afterwards.

The key line is this one: to send to these addresses, you must register your outbound email domains or addresses and authenticate the mail. An unregistered sender is not treated like an ordinary unknown sender. Apple's account help says plainly that mail from an unregistered source results in a bounce.

Step 1: list every place your app sends email from

Before touching any settings, write down every From address and sending service your business uses for customers. For a typical small app this is more than people expect:

  • transactional mail from your own backend (order confirmations, password resets)
  • a separate email platform for newsletters or win-back campaigns
  • a helpdesk tool that replies to support tickets
  • a booking or payments platform that sends its own receipts
  • a subdomain such as mail.example.co.uk or bookings.example.co.uk

Each distinct sending domain, or each individual address if you don't control the domain, has to be registered. Apple's own example is useful: registering example.com and sales.example.com does not cover help.example.com. That needs its own entry.

Step 2: register your email sources with Apple

In your Apple Developer account, open Certificates, Identifiers & Profiles, choose Services in the sidebar, and click Configure under Sign in with Apple for Email Communication. In the Email Sources section you can add:

  • Domains and subdomains, as a comma-separated list. No file upload on your server is needed.
  • Individual email addresses, if you send from an address on a domain you don't manage.

After you click Register, the table shows whether each source passed Apple's SPF check. A red result here is your first clue. You need the Account Holder or Admin role to change these settings, so if your developer account is held by an agency or a former freelancer, sort out access first.

Step 3: make SPF or DKIM match what Apple checks

Apple requires every message to the relay to be authenticated with SPF, DKIM or both, and recommends both. The subtle part is which domain is compared with which.

SPF: Apple looks at the envelope sender, also called the Return-Path or bounce address, not the From address your customer sees. That envelope domain must be registered, must pass SPF, and must match the registered domain exactly. Many email services use their own domain for the envelope sender by default, so your SPF record can be perfect and the check can still fail. Set up a custom return-path or bounce domain on your own domain if your provider supports it.

DKIM: If your provider keeps its own envelope domain, sign with DKIM instead. Apple compares the d= value in the DKIM signature with the domain in the visible From address. The signature must verify, must cover the From header, and the two domains must match exactly. A message signed with the provider's shared domain will not pass.

Apple's help page shows SPF records using an include mechanism for common sending services. Follow your own provider's instructions for the exact record.

Step 4: test with a real relay address

Create a test account in your own app using Sign in with Apple with "Hide My Email" selected, then trigger each type of email: welcome, receipt, password reset, a marketing send and a support reply. Check the message headers in the inbox that receives it. Look for SPF and DKIM passes, and confirm the Return-Path and DKIM domains are ones you registered.

Apple also says it periodically emails the Account Holder and team admins when mail from your account could not be delivered through the relay. Make sure those notices go to someone who reads them, not a shared inbox nobody checks.

Step 5: keep your customer records accurate

Delivery is only half the job. Apple can send your server notifications when a customer changes their settings. The documented event types include email-disabled and email-enabled (the customer switched forwarding off or on), consent-revoked (they stopped using their Apple Account with your app) and account-deleted. To receive them you register an endpoint URL that supports TLS 1.2 or later, and you verify the signed payload before acting on it.

Use these events to stop sending to relay addresses that will reject you, because repeated bounces can hurt your sender reputation. If the customer turns forwarding back on, re-enable sending.

It also helps to mark relay addresses in your customer table so your team understands why "jane.smith@gmail.com" can't be found when a customer phones about their booking. Show "Signed in with Apple" on the account screen and support tools, and offer customers a way to add a contact email if they want one.

An illustrative example

A salon booking app in Leeds sends confirmations from bookings.example.co.uk through a transactional email service and newsletters from example.co.uk through a marketing platform. Customers using hidden emails complain they never get reminders. The team finds only example.co.uk registered with Apple, and the transactional service uses its own bounce domain. They register bookings.example.co.uk, add a custom return-path on that subdomain, turn on DKIM signing with their own domain, and test with a hidden-email account. Reminders start arriving, and the admin delivery notices stop.

FAQ

Can I just ask customers for their real email instead?

You can offer an optional contact email field, but don't make hiding the email pointless by forcing it. Many customers chose the relay on purpose.

Do replies from customers reach us?

Yes. Apple routes replies back to the address you sent from, rewriting your address so the customer sees something readable while their own address stays hidden.

Why did emails work for months and then start bouncing?

Common causes are a new sending tool, a new subdomain, or a provider change that altered your return-path or DKIM domain. Any new source needs registering.

Does this affect customers who shared their real email?

No. If the customer chose to share their real address, mail goes straight to that inbox and the relay rules don't apply.

If hidden-email customers aren't receiving your app's messages and you'd like the sending setup checked end to end, send us the domains and tools you send from.

Sources

WhatsAppBook a call