When logging into the game via Web3Auth using email authentication, the OTP (one-time password) emails are not appearing in the inbox. Instead, they are being directed to the Spam folder.
This causes confusion and delays in the login process, as players often assume they haven’t received the OTP.
Steps to Reproduce:
Launch the game and tap Continue with Email.
Enter a valid email address and tap Continue.
Wait for the OTP email from Web3Auth.
Check inbox → no OTP email received.
Check Spam folder → OTP email is present there.
Expected Behavior:
OTP emails from Web3Auth should be delivered directly to the Inbox, not the Spam folder.
Actual Behavior:
OTP emails are automatically routed to the Spam folder in most cases.
Thank you for sharing the details, Arun! I understand that you’re experiencing an issue where OTP emails sent via Web3Auth’s email passwordless login are landing in users’ spam folders instead of their inboxes. This can indeed cause confusion and hinder the login experience.
Here’s a summary of your issue for the support team:
Issue Summary:
Problem: OTP emails from Web3Auth (email passwordless login) are going to users’ spam folders.
Expected Behavior: OTP emails should be delivered directly to the inbox.
Actual Behavior: OTP emails are consistently routed to the spam folder.
Integration Context:
SDK Used: Web3Auth Modal SDK (React, but could be applicable to other frontend SDKs as well)
Authentication Method: Email passwordless login (OTP via email)
Platform: Web (React app, possibly others)
Steps to Reproduce:
User selects “Continue with Email” in the app.
Enters a valid email address.
Waits for OTP email.
Email does not appear in inbox, but is found in spam.
Additional Information Needed (if possible):
Can you share a sample of the email headers from one of the OTP emails that landed in spam? This can help the support team identify if there’s a deliverability or domain reputation issue.
Are you using any custom whitelabeling or have you configured a custom email sender domain via Web3Auth Dashboard? (This affects how emails are sent and their likelihood of being marked as spam.)
Is this happening across all email providers (Gmail, Outlook, Yahoo, etc.) or specific ones?
Next Steps & Suggestions
For Users: As a temporary workaround, please advise users to check their spam/junk folders and mark OTP emails as “Not Spam” to help train their inbox.
For Developers: If you are using a custom whitelabel or sender domain, ensure that your domain’s SPF, DKIM, and DMARC records are properly set up. Web3Auth Whitelabel Docs may be helpful.
For Support: This may require checking the email service configuration on the backend or reviewing sender reputation.
Let us know if you can provide an email header sample or if you have any custom email configuration in place. This will help the support team investigate and resolve the issue more efficiently.
Thank you for bringing this to our attention!
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support 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. Web3Auth Developer Office Hours
