Verification emails through SendGrid don't send. Test emails work however

I experiencing this issue “Is there an issue sending out email verification notices?
My SendGrid domain is verified and works for test emails sent via both Email Template and Email Provider. However when used in practice for sending a verification code, I’m seeing this error coming from the logs.

  "date": "2020-10-02T20:14:09.745Z",
  "type": "fn",
  "description": "To: <my email>",
  "connection": "email",
  "connection_id": "",
  "client_id": "<client_id>",
  "details": {
    "email_type": "verification_code",
    "to": "<my email>",
    "error": "The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved. Visit to see the Sender Identity requirements"
  "log_id": "90020201002201414993000125272909083283969104061256433682",
  "_id": "90020201002201414993000125272909083283969104061256433682",
  "isMobile": false,
  "user_agent": "Other 0.0.0 / Other 0.0.0"

It seems to be an Auth0 bug, given that our verification works end-to-end in test emails – why would Auth0 not use same sender for verification emails? The “from” email looks correct in all circumstances in the logs, and is the same “from” email I use in tests.

Hi @seansy,

Welcome to the Community. I don’t have an immediate answer for you. Can you confirm that you have completed domain ownership verification under Settings -> Sender Authentication in your Sendgrid environment?

Thanks for helping out @markd. I can confirm that the domain is verified.

We’re sending emails from hello@(ourdomain), and we have verified that domain and that email address on sendgrid. Wouldn’t the test emails fail if we weren’t domain verified?


So after much hacking with the settings, I figured it out. Someone else on this app had setup passwordless auth originally, and I didn’t realize these items were clickable in the auth0 management:

Clicking into passwordless email, I saw something like this:

Screen Shot 2020-10-05 at 11.56.59 AM

I updated to my verified domain as sender, and issue is now fixed:

Screen Shot 2020-10-05 at 11.57.02 AM