SMTP fails quietly when attempting to use MailerSend SMTP
wasp version 0.16.3 on WSL
Checked terminal and console logs nothing, made sure to set .env properly and main.wasp
5 Replies
Hi @ralph. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources do not contain specific information about issues with MailerSend SMTP and Wasp's email functionality, especially regarding failures that occur quietly (without logs or errors) when using SMTP providers. The documentation does mention that for SMTP providers, you need to set the appropriate environment variables in your
.env.server file (SMTP_HOST, SMTP_USERNAME, SMTP_PASSWORD, SMTP_PORT) and configure your main.wasp file accordingly, but it does not provide troubleshooting steps for silent failures or mention MailerSend specifically.
If you have already set up your .env.server and main.wasp as described, and you are not seeing any errors or logs, there may be a lack of error reporting in the current Wasp SMTP integration. You might want to check that your project is located on the Linux file system (not the Windows file system) when using WSL, as file system issues can cause unexpected behavior, including problems with file watching and possibly with environment variable loading or process execution. This is a known issue with WSL2 and is documented as a common pitfall for Wasp development on Windows with WSLDocs: Quick Start - Installation.
If everything seems correct and the issue persists, I recommend reaching out on the Wasp Discord for more targeted troubleshooting, as this may be a bug or a limitation in the current version of Wasp's SMTP handling.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ralph, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@kapa.ai Is wasp SMTP configured to use TLS by default?
Let me check the knowledge base for you again. One moment! :books:
----------------------
I'm sorry, but the knowledge sources do not explicitly state whether Wasp's SMTP provider is configured to use TLS by default. The documentation only specifies that you need to provide
SMTP_HOST, SMTP_USERNAME, SMTP_PASSWORD, and SMTP_PORT in your .env.server file, but it does not mention TLS settings or defaults for secure connections Docs: Advanced Email - Providers.
If you need to ensure TLS is used, you may need to consult the Wasp community or check the generated server code for more details.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ralph, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Nevermind, fixed. It was due to me attempting to sign up with an already signed up account, which I feel like should have yelled at me during sign-up 😦
The lack of a warning message is an intentional security feature to prevent leaking active email addresses to malicious users: https://wasp.sh/docs/auth/email
Overview | Wasp
Wasp supports e-mail authentication out of the box, along with email verification and "forgot your password?" flows. It provides you with the server-side implementation and email templates for all of these flows.