This is a problem related to Outlook. The bug is reported and the engineers are working on it. In the meantime, as a workaround, please use a different email client (maybe a webmail version of your inbox) to read the email.

I don't use Outlook. No verification email at all.

I use Outlook, but I checked via Gmail.com too, and tried another email address that isn't hooked into my Outlook.

I just become verification email.

I have this problem as well. I never receive the email verification. I've been waiting for hours. I'm not using Outlook.

I managed to reset the sync password. I got that mail, but whenever I log in with the new password it just tells me that I need to verify my email.

Nothing to do with Outlook. I'm running my own mail domain with postfix. Whenever I "resend verification email", It appears I get messages in the server log like:

Aug 5 12:50:53 sideshowbob postfix/smtpd[3973]: connect from a27-125.smtp-out.us-west-2.amazonses.com[54.240.27.125] Aug 5 12:50:53 sideshowbob postfix/smtpd[3973]: B39F843F7E: client=a27-125.smtp-out.us-west-2.amazonses.com[54.240.27.125] Aug 5 12:52:57 sideshowbob postfix/smtpd[4350]: timeout after DATA (0 bytes) from a27-85.smtp-out.us-west-2.amazonses.com[54.240.27.85] Aug 5 12:52:57 sideshowbob postfix/smtpd[4350]: disconnect from a27-85.smtp-out.us-west-2.amazonses.com[54.240.27.85]

Looks like something is connecting and disconnecting without sending anything. There appear to be a number of subsequent retries with the same messages.

Just noticed the second two messages are from a different pid. The disconnect messages for the same pid come after five minutes. Overlap may be because I've tride several times to resend

Finally got around to solving this problem. I discovered that some other email servers were failing to connect to mine and this was due to some intermediate router having a lower MTU and the origing server presumably failing to correctly perform path MTU discovery. The tracepath utility allowed me to determine that the lowest MTU between the amazon servers used for firefox sync and my email server was 1492, configuring the MTU on the network interface of my mail server solved the problem.

What isn't clear is where the MTU path discovery fails - is that an issue with the amazon servers?

Same issue here. Whitmad is right. I was unable to register by using two differents domains emails : laposte.net and free.fr I have had to create my own smtp server with my domain to be able to receive the confirmation email. Same thing to register my account on this support. Mozilla, please check your network setup !