We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Like many others (#86) I'm struggling, so far without success, to configure SMTP for verification.
I've tried other ways (Resend, Zoho, Gmail) to set up SMTP in pds/pds.env. I'm currently trying with Proton Mail.
pds/pds.env
My Proton plan lets me generate SMTP tokens, so I've done that. Here's my current pds/pds.env:
PDS_EMAIL_SMTP_URL=smtp://[email protected]:<token>@smtp.protonmail.ch:587 [email protected]
No success. I'm not even sure what's happening (or failing to happen) under the hood.
EDIT: I've also tried port 465, with no better success.
The text was updated successfully, but these errors were encountered:
For context, when I curl with my Gmail app password, mail sends correctly:
curl --ssl-reqd \ --url 'smtps://smtp.gmail.com:465' \ --user '[email protected]:<app password>' \ --mail-from '[email protected]' \ --mail-rcpt '[email protected]' \ --upload-file mail.txt
The mail.txt file has some boilerplate.
mail.txt
So it doesn't look like a PDS issue per se. But when I specify those Gmail values in my pds/pds.env, nothing sends:
PDS_EMAIL_SMTP_URL=smtps://[email protected]:<app password>@smtp.gmail.com:465 [email protected]
Sorry, something went wrong.
No branches or pull requests
Like many others (#86) I'm struggling, so far without success, to configure SMTP for verification.
I've tried other ways (Resend, Zoho, Gmail) to set up SMTP in
pds/pds.env
. I'm currently trying with Proton Mail.My Proton plan lets me generate SMTP tokens, so I've done that. Here's my current
pds/pds.env
:No success. I'm not even sure what's happening (or failing to happen) under the hood.
EDIT: I've also tried port 465, with no better success.
The text was updated successfully, but these errors were encountered: