Custom email verification does not allow trailing period in host name

In the custom email domain verification, we are required to input our domain name as the host name in multiple TXT and MX records. The instructions specifically state to add trailing periods. Namecheap doesn't allow this so I ommitted but after 12 hours, verification is still failing. Anybody had any success?

Posted on Aug 26, 2021 6:19 PM

Similar questions

Custom email - Replace sig1.dkim.EXAMPLE.COM.at.icloudmailadmin.com. I honestly think people should have made it clear that you have to replace sig1.dkim.EXAMPLE.COM.at.icloudmailadmin.com. with your actual own domain name. It's mentioned absolutely nowhere in the instructions and if you simply copy-paste their stuff from the instructions, the verification will fail.
2121 2
Cannot verify email address I want to add to my custom domain: the verification link does nothing. Now what? During my custom domain creation, one step is to declare every existing email addresses before modifying the DNS. During this step, verification links are send to those addresses in order to verify that they are valid and everyone knows about the migration. So far, so good. I've validated couple of addresses but the last one cannot be verified. I do have the verification email and the verification link. But when I clic the link, it opens icloud.com and... does nothing. I'm supposed to get a notification popup in the page that says the email address has been successfully verified. But I don't have that message and my migration is now stuck. Does anyone has experience that kind of symptoms?
4369 8
Verification process to send mail fails I have a family member that can't send email. The verification process always fails. The username should be simply their first name but somewhere Mail.app keeps forcing it to be the first name plus the domain name. So bob becomes *** which isn't the username an thus fails. Since Apple added the automatically manage my mail settings check box. This has been a problem. That button only assumes emails are fully qualified such as *** During initial configuration it is critically important to put the username as the last entry. If this isn't done then Mail.app replaces bob with ***. I have learned to always input the username last. If this isn't done the rest of the gui will display the correct username "bob" but this isn't what one will see in the mail server log file. All login attempts will use *** instead of just bob. The entire account will need to be deleted and re-set up. This process has worked for at least 5 plus years. Suddenly I have a user that no matter what I do the gui can't seem to convinced to use just the username. If I use the connection doctor to confirm my settings everything passes the tests. If I try to send mail authentication fails. Connection doctor doesn't display the username during its tests so I'm not sure it is used to verify accounts. I think it must be wrong inside the accounts.sqlite file... Thanks, Ben [Edited by Moderator]
531 5

2 replies

Aug 26, 2021 9:52 PM in response to Justin Choy

Can confirm that @ is required for Host name on DreamHost DNS setup as well as they also do not allow trailing " . "

Justin Choy Author

Level 1

11 points

Aug 26, 2021 9:02 PM in response to Justin Choy

Solved it myself. use an @ instead

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Custom email verification does not allow trailing period in host name