Open Bug 938012 Opened 12 years ago Updated 3 years ago

Gmail 2 step verification smtp password not stored automatically during autoconfig

Categories

(Thunderbird :: Account Manager, defect)

24 Branch
x86_64
Windows 8.1
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: janot2007, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release) Build ID: 20131025151332 Steps to reproduce: 1. Set new app password in google account security settings 2. Reopen Thunderbird to be asked for new password on mail check 3. Input new password and check your emails successfully 4. Close google account security settings and clear your clipboard (or forget that 16 symbols autogenerated password =O) 5. Try to send email and Thunderbird will ask you for same password for SMTP which you can't restore because of step #4 Actual results: Thunderbird asks for same password twice: 1) on receiving 2) on sending Expected results: Thunderbird must set up password for SMTP on step #3 automatically
John, can you assist?
Flags: needinfo?(johngalt2600)
You can get this password out of Thunderbird to reuse it: go to Preferences -> Security -> Passwords -> Saved Passwords, and find the row for your Gmail IMAP account. Then right-click it and select "Copy Password". It's not the world's easiest way to do this, but at least it's possible...
Flags: needinfo?(johngalt2600)
Chris, does this issue still exist?
Component: Untriaged → Account Manager
Flags: needinfo?(chris.ramsden)
Summary: Gmail 2 step verification smtp password not stored automatically → Gmail 2 step verification smtp password not stored automatically during autoconfig
Flags: needinfo?(chris.ramsden)

My work around was to quit 2-step verification in Gmail security settings. Not really what I wanted...
FYI Win10 Thunderbird IMAP server settings - Connection security: SSL/TLS, Authentication method: OAuth2.
Has SMTP really been failing since Windows 8?! It's labelled oddly: Priority: Not set Severity: normal

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.