Cannot enter SMTP password
I have smtp.gmail.com set up as my outgoing server (port 465, username = my gmail address, Authentication = OAuth2, connection security = SSL/TLS, also tried STARTTLS with port 587). There doesn't appear to be any way to set the password in the "Outgoing Server (SMTP) Settings", even when I click "Edit". Nor can I add a password to the "Edit/Privacy&Security/Saved Passwords" dialog box (which allows you to see existing passwords or remove them, but not add any).
When I try to send an email, the "Sending Message" dialog box pops up, and after a few seconds a second box pops labeled "Login to account 'smtp.gmai.com' failed". This box has three buttons: "Enter New Password", Cancel and Retry. Clicking on the "Enter New Password" button does not offer me the chance to enter a new password--instead, it immediately takes me back to the "Sending Message" box, which then immediately takes me back to the "Login...failed" box. There is never an opportunity to enter the password!
TBird 140.7.0esr, Thunderbird for Linux Mint. Mint version 22.3.
Sending works ok if I choose a different SMTP server.
Izabrano rješenje
Sometime between this morning and now, the SMTP via gmail started working again. I did not make any changes to the server settings, maybe gmail's SMTP was rejecting my username because of some earlier setting error. Anyway, it works now. Thanks for the info.
Pročitajte ovaj odgovor sa objašnjenjem 👍 0All Replies (2)
Select the account in the left pane of Account Settings, then click Edit SMTP server in the right pane. What is the authentication method shown, and is the User Name (email address) the same as for the selected account?
If the setup is correct, there is one oauth:// entry in Saved Passwords that applies to the incoming and outgoing servers.
Odabrano rješenje
Sometime between this morning and now, the SMTP via gmail started working again. I did not make any changes to the server settings, maybe gmail's SMTP was rejecting my username because of some earlier setting error. Anyway, it works now. Thanks for the info.