Admin Panel email test


I have just recently created a docker container running vaultwarden and i am now configuring the admin side of it. I have disabled the create account and I want to set up so i can send invites.
I am trying to set some SMTP settings in the admin panel and am getting the following error after doing a test email (see attached).


Here are my settings

Thank you for the help, it is now working

Hi @prech no still having trouble getting it to work.

I would suggest to enable smtp_debug (restart the container afterwards) and do a test then to see a bit more info.

Not replied in a few months had other things going on…

Where can I access the debug?

It’s in the logs file or container output logs

Something related to the Auth Mechanism:

`[2021-09-22 16:01:56.227][lettre::transport::smtp::client::connection][DEBUG] << at your service, []<CRLF>250-SIZE 35882577<CRLF>250-8BITMIME<CRLF>250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH<CRLF>250-ENHANCEDSTATUSCODES<CRLF>250-PIPELINING<CRLF>250-CHUNKING<CRLF>250 SMTPUTF8<CRLF> 

[2021-09-22 16:01:56.227][lettre::transport::smtp::client::connection][DEBUG] Wrote: AUTH PLAIN AG1haWxhdXRoMjQ2OEBnbWFpbC5jb20AcGVhclAwd2Vy<CRLF> 

[2021-09-22 16:01:56.286][lettre::transport::smtp::client::connection][DEBUG] << 535-5.7.8 Username and Password not accepted. Learn more at<CRLF> 

[2021-09-22 16:01:56.287][lettre::transport::smtp::client::connection][DEBUG] << 535-5.7.8 Username and Password not accepted. Learn more at<CRLF>535 5.7.8 bf28sm1411304edb.45 - gsmtp<CRLF> 

[2021-09-22 16:01:56.287][vaultwarden::mail][ERROR] SMTP 5xx error: lettre::transport::smtp::Error { kind: Permanent(Code { severity: PermanentNegativeCompletion, category: Unspecified3, detail: Five }) }

[2021-09-22 16:01:56.288][response][INFO] POST /admin/test/smtp (test_smtp) => 400 Bad Request

See Error when sending test mail (using gmail) · Discussion #1360 · dani-garcia/vaultwarden · GitHub

Ah great thank you. I guess theres no way to encrypt the email password?

Well, we would still need to decrypt it during login, so it would be a bit difficult, and still able to reverse of course.

You could use docker secrets, but that would still load it into the env/memory and visible via the admin.