can you look to see if my account is suppressed, the verification email came through for verification at the Community forums though.
I show those as being delivered. Please ensure the following addresses are on the allowlist at your origin mail server: [email protected] and [email protected]
This exact same thing is happening to me. Several attempts to have email verified are not going through. The verification email for this forum hit in about 10 seconds. Is there an alternate method for verification?
I don’t show any bounced emails @mark.simmons, can you try again from incognito mode and/or a mobile device?
No luck. I tried using a typcal Chrome browser, Chrome in incognito mode, and Safari from my phone. No verification email has been received.
Checked SPAM folder.
Logged into Office 365 Admin to check from the Exchange server. Nothing has been received at the mail server.
Are you able to create an account ticket here,
https://dash.cloudflare.com/?to=/:account/support
If so, please share the ticket number here. Sorry for the issue you’re encountering. If not, lmk and we’ll figure out another option.
No luck. The form requires an account upgrade. I do know a few Cloudflare SEs. I’ll check with them offline.
I will create one on your behalf, you’ll receive a copy of it, sorry for the issues.
I created ticket 2862328 and you will have received a copy of it. I am cc’d on the ticket and will track progress and flag this for my colleagues.
Thanks Tim. It is a little funny though…a virtual “circular firing squad”.
A ticket is opened to correct an email verification issue, but that email address must be verified before I may edit the details.
I have an update for anyone following the issue. It tuns out the email verification message was flagged as SPAM by Microsoft Defender 365 at the Office 365 Exchange Server while using the default anti-spam ruleset. Anyone experiencing the issue will have to login to Exchange Online as the Exchange (or domain) admin, find the email in quarantine, and release it.
Thanks for coming back to share your findings, @mark.simmons. Hopefully your follow up here will help someone else in the future.