Bug 1978361 Comment 19 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I've had a little breakthrough methinks. I did this on my own home PC but it's now at TB 141.0 so don't know if that makes any difference. I set up my Mom's @att.net account from scratch this way using the "+ New Account" button

STR (requires the Security Key / Secure Mail Key):

1. Fill in Name and Email address, click Continue.
2. It only finds POP3 as a choice. so on the "Configuration found in Mozilla ISPDB" screen, click Edit Configuration
3. Incoming server settings: Protocol: IMAP, Hostname: imap.mail.att.net, Port: 993, Connection Security: SSL/TLS, Authentication Method: Autodetect, Password, Username: <full @att.net email address>, click Continue
4. Outgoing server settings: Protocol: SMTP, Hostname: smtp.mail.att.net, Port: 465, Connection Security: SSL/TLS, Authentication method: Autodetect,  Password, Username: <full @att.net email address>, click Test, click Continue
5. Now, enter your Security Key / Secure Mail Key and click Continue
6. If presented with the "Thunderbird was unable to find connected services", click Continue
7. Click Finish

This is where it gets a bit murky. The resulting working account's Incoming Server settings show Authentication Method as Normal Password. Same for Outgoing Server SMTP : Authentication Method = Normal Password. Now, if you try to repeat the above STR steps #3 and #4 and use Authentication Method: Normal Password, account creation WILL fail. I tried it twice to make sure I wasn't going insane.

Seems that needing Authentication Method: Autodetect during manual IMAP setup is required. I wonder what would happen for those having the issue to change their existing Authentication Method from OAuth2 to Normal Password? CAVEAT: Back up your profile first! I am not responsible if it busts a working profile.
I've had a little breakthrough methinks. I did this on my own home PC but it's now at TB 141.0 so don't know if that makes any difference. I set up my Mom's @att.net account from scratch this way using the "+ New Account" button

STR (requires the Security Key / Secure Mail Key):

1. Fill in Name and Email address, click Continue.
2. It only finds POP3 as a choice, so on the "Configuration found in Mozilla ISPDB" screen, click Edit Configuration
3. Incoming server settings: Protocol: IMAP, Hostname: imap.mail.att.net, Port: 993, Connection Security: SSL/TLS, Authentication Method: Autodetect, Password, Username: <full @att.net email address>, click Continue
4. Outgoing server settings: Protocol: SMTP, Hostname: smtp.mail.att.net, Port: 465, Connection Security: SSL/TLS, Authentication method: Autodetect,  Password, Username: <full @att.net email address>, click Test, click Continue
5. Now, enter your Security Key / Secure Mail Key and click Continue
6. If presented with the "Thunderbird was unable to find connected services", click Continue
7. Click Finish

This is where it gets a bit murky. The resulting working account's Incoming Server settings show Authentication Method as Normal Password. Same for Outgoing Server SMTP : Authentication Method = Normal Password. Now, if you try to repeat the above STR steps #3 and #4 and use Authentication Method: Normal Password, account creation WILL fail. I tried it twice to make sure I wasn't going insane.

Seems that needing Authentication Method: Autodetect during manual IMAP setup is required. I wonder what would happen for those having the issue to change their existing Authentication Method from OAuth2 to Normal Password? CAVEAT: Back up your profile first! I am not responsible if it busts a working profile.
I've had a little breakthrough methinks. I did this on my own home PC but it's now at TB 141.0 so don't know if that makes any difference. I set up my Mom's @att.net account from scratch this way using the "+ New Account" button

STR (requires the Security Key / Secure Mail Key):

1. Fill in Name and Email address, click Continue.
2. It only finds POP3 as a choice, so on the "Configuration found in Mozilla ISPDB" screen, click Edit Configuration
3. Incoming server settings: Protocol: IMAP, Hostname: imap.mail.att.net, Port: 993, Connection Security: SSL/TLS, Authentication Method: Autodetect Password, Username: <full @att.net email address>, click Continue
4. Outgoing server settings: Protocol: SMTP, Hostname: smtp.mail.att.net, Port: 465, Connection Security: SSL/TLS, Authentication method: Autodetect Password, Username: <full @att.net email address>, click Test, click Continue
5. Now, enter your Security Key / Secure Mail Key and click Continue
6. If presented with the "Thunderbird was unable to find connected services", click Continue
7. Click Finish

This is where it gets a bit murky. The resulting working account's Incoming Server settings show Authentication Method as Normal Password. Same for Outgoing Server SMTP : Authentication Method = Normal Password. Now, if you try to repeat the above STR steps #3 and #4 and use Authentication Method: Normal Password, account creation WILL fail. I tried it twice to make sure I wasn't going insane.

Seems that needing Authentication Method: Autodetect during manual IMAP setup is required. I wonder what would happen for those having the issue to change their existing Authentication Method from OAuth2 to Normal Password? CAVEAT: Back up your profile first! I am not responsible if it busts a working profile.
I've had a little breakthrough methinks. I did this on my own home PC but it's now at TB 141.0 so don't know if that makes any difference. I set up my Mom's @att.net account from scratch this way using the "+ New Account" button

STR (requires the Security Key / Secure Mail Key):

1. Fill in Name and Email address, click Continue.
2. It only finds POP3 as a choice, so on the "Configuration found in Mozilla ISPDB" screen, click Edit Configuration
3. Incoming server settings: Protocol: IMAP, Hostname: imap.mail.att.net, Port: 993, Connection Security: SSL/TLS, Authentication Method: Autodetect Password, Username: <full @att.net email address>, click Continue
4. Outgoing server settings: Protocol: SMTP, Hostname: smtp.mail.att.net, Port: 465, Connection Security: SSL/TLS, Authentication method: Autodetect Password, Username: <full @att.net email address>, click Test, click Continue
5. Now, enter your Security Key / Secure Mail Key and click Continue
6. If presented with the "Thunderbird was unable to find connected services", click Continue
7. Click Finish

This is where it gets a bit murky. The resulting working account's Incoming Server settings show Authentication Method as Normal Password. Same for Outgoing Server SMTP: Authentication Method = Normal Password. Now, if you try to repeat the above STR steps #3 and #4 and use Authentication Method: Normal Password, account creation WILL fail. I tried it twice to make sure I wasn't going insane.

Seems that needing Authentication Method: Autodetect during manual IMAP setup is required. I wonder what would happen for those having the issue to change their existing Authentication Method from OAuth2 to Normal Password? CAVEAT: Back up your profile first! I am not responsible if it busts a working profile.

Back to Bug 1978361 Comment 19