How is verified domain used?

From reading blogs and docs, it sounds like the domain we verify in the developer portal is used to whitelist domains that can send to a relay email address of a SiwA user who has chosen to hide their real email.


Is this the only purpose of the domain? Does it have to match exactly, i.e. if our website is www.foo.com but our emails come from @foo.com, is it required to add the verification file to https://foo.com/.well-known/ (no www)?

no really, can we get some official guidance on this please?

Accepted Answer

On Jul 9, 2019, tsombrero wrote:


> Is this the only purpose of the domain? Does it have to match exactly, i.e. if our website is www.foo.com but our emails come from @foo.com, is it required to add the verification file to https://foo.com/.well-known/ (no www)?


In order to send email messages through the relay service to the users’ personal inboxes, you will need to register your outbound email domains. All registered domains must create Sender Policy Framework (SPF) DNS TXT records in order to transit Apple’s private mail relay.


If you’re enrolled as an individual, you can register up to 32 email sources. If you’re enrolled as an organization, you can register up to 100 email sources. You do not need to upload a file on your server to complete the registration process for domains and subdomains.


For additional information about configuring the private email relay service, please see here.

How is verified domain used?
 
 
Q