Email OTP not delivered

Embedded Wallets (Web3Auth)
2

Hi Aby — thanks for the clear report and for flagging this for Avici users. I’ve pulled the important details so the support team can act quickly and to help us troubleshoot:

Summary (from your message)

  • SDK: MetaMask Embedded Wallets (Web3Auth)
  • Web3Auth Flutter SDK: web3auth_flutter: ^6.3.0
  • Platform: Flutter
  • Issue: Passwordless Email login — OTP emails not being delivered to many users
  • You prefer to share sensitive details (emails/timestamps) via DM — understood.

What I’ll need from you (so we can escalate / investigate)

  • Code snippets: your Web3Auth initialization and the email/passwordless login call (loginSnippet + initialization). Please paste the minimal relevant code (no secrets).
  • Device/console logs: Flutter/device console logs showing the network request/response when the OTP request is made. If you can’t paste logs publicly, please DM or open a private support ticket. We need the HTTP response body/status if available.
  • Network traces / screenshots: a screenshot of the network request to the Web3Auth endpoint (or your backend) and the response (or a HAR) if available.
  • Examples and timestamps (private): 2–3 example email addresses + exact timestamps when the OTP was requested and whether any bounce/spam notices were received.
  • Clarify if you’re using Web3Auth’s hosted email/OTP service or a custom SMTP/email provider configured for Web3Auth (enterprise/customizer).
  • Are the failures limited to certain email domains (Gmail, Yahoo, corporate domains), regions, or ISPs? Any pattern helps.

Quick troubleshooting steps you can try now

  • Ask affected users to check Spam/Junk and email filtering rules; sometimes OTPs are delayed or filtered.
  • Confirm you’re using the correct clientId / network configuration in the Flutter init and that the SDK is up-to-date (6.3.0 noted). If possible, try reproducing with another test account.
  • Capture the network request/response from the client (or server) and check HTTP status codes and any error messages returned by Web3Auth.
  • If using a custom email provider, verify sender domain/SPF/DKIM/DMARC and check the email provider’s logs for bounces or blocks.
  • Check for rate limiting or quota issues (sudden spike in OTP requests can trigger throttling).

Relevant docs

Next steps

  • If you can DM the code snippets, logs, and 2–3 sample emails + timestamps, I’ll escalate this to the support team and ask them to check delivery logs and bounce reasons.
  • If you prefer, open a private support ticket and include the same artifacts.

I’ll hold here and escalate as soon as you share the private logs/snippets. Thank you — we’ll get this sorted for your users.

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. MetaMask Developer Office Hours