Bug 1978361 Comment 30 Edit History

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

Original comment by
on 
Hi guys,

I wanted to update everyone with what I did on my Mom's PC that worked.

1. I changed Auth method from OAuth2 > Normal Password
2. Restarted TB and it prompted me for a password
3. I used the Security Key / Secure Mail Key password and chose to let TB save the password (for inbound and outbound server)

All fixed. that was it. makes me wonder if AT&T silently ditched strict OAuth2 method and is just using the Security Key / Secure Mail Key password as the "Normal Password" now?

I did catch something in Error Console after I switched from OAuth2 to Normal Password but it might be a red herring. This was throw when I was trying to send a test email from/to her own account.

mailnews.smtp: Authentication failed: Socket closed. SmtpClient.sys.mjs:762:17
    _onAuthFailed resource:///modules/SmtpClient.sys.mjs:762
    _onClose resource:///modules/SmtpClient.sys.mjs:555
uncaught exception: initFromOutgoing failed, hostname: smtp.mail.att.net
Revision 1 by
on 
Hi guys,

I wanted to update everyone with what I did on my Mom's PC that worked.

1. I changed Auth method from OAuth2 > Normal Password
2. Restarted TB and it prompted me for a password
3. I used the Security Key / Secure Mail Key password and chose to let TB save the password (for inbound and outbound server)

All fixed. That was it. Makes me wonder if AT&T silently ditched strict OAuth2 method and is just using the Security Key / Secure Mail Key password as the "Normal Password" now?

I did catch something in Error Console after I switched from OAuth2 to Normal Password but it might be a red herring. This was throw when I was trying to send a test email from/to her own account.

mailnews.smtp: Authentication failed: Socket closed. SmtpClient.sys.mjs:762:17
    _onAuthFailed resource:///modules/SmtpClient.sys.mjs:762
    _onClose resource:///modules/SmtpClient.sys.mjs:555
uncaught exception: initFromOutgoing failed, hostname: smtp.mail.att.net
Revision 2 by
on 
Hi guys,

I wanted to update everyone with what I did on my Mom's PC that worked.

1. I changed Auth method from OAuth2 > Normal Password (for both Inbound and Outbound servers)
2. Restarted TB and it prompted me for a password
3. I used the Security Key / Secure Mail Key password and chose to let TB save the password (for inbound and outbound server)

All fixed. That was it. Makes me wonder if AT&T silently ditched strict OAuth2 method and is just using the Security Key / Secure Mail Key password as the "Normal Password" now?

I did catch something in Error Console after I switched from OAuth2 to Normal Password but it might be a red herring. This was throw when I was trying to send a test email from/to her own account.

mailnews.smtp: Authentication failed: Socket closed. SmtpClient.sys.mjs:762:17
    _onAuthFailed resource:///modules/SmtpClient.sys.mjs:762
    _onClose resource:///modules/SmtpClient.sys.mjs:555
uncaught exception: initFromOutgoing failed, hostname: smtp.mail.att.net
Revision 3 by
on 
Hi guys,

I wanted to update everyone with what I did on my Mom's PC that worked.

1. I changed Auth method from OAuth2 > Normal Password (for both Inbound and Outbound AT&T servers)
2. Restarted TB and it prompted me for a password
3. I used the Security Key / Secure Mail Key password and chose to let TB save the password (for inbound and outbound server)

All fixed. That was it. Makes me wonder if AT&T silently ditched strict OAuth2 method and is just using the Security Key / Secure Mail Key password as the "Normal Password" now?

I did catch something in Error Console after I switched from OAuth2 to Normal Password but it might be a red herring. This was throw when I was trying to send a test email from/to her own account.

mailnews.smtp: Authentication failed: Socket closed. SmtpClient.sys.mjs:762:17
    _onAuthFailed resource:///modules/SmtpClient.sys.mjs:762
    _onClose resource:///modules/SmtpClient.sys.mjs:555
uncaught exception: initFromOutgoing failed, hostname: smtp.mail.att.net
Revision 4 by
on 
Hi guys,

I wanted to update everyone with what I did on my Mom's PC that worked. She was on 128.12.0. I updated her to 128.13.0. Then to 140.1.0 ESR.

1. I changed Auth method from OAuth2 > Normal Password (for both Inbound and Outbound AT&T servers)
2. Restarted TB and it prompted me for a password
3. I used the Security Key / Secure Mail Key password and chose to let TB save the password (for inbound and outbound server)

All fixed. That was it. Makes me wonder if AT&T silently ditched strict OAuth2 method and is just using the Security Key / Secure Mail Key password as the "Normal Password" now?

I did catch something in Error Console after I switched from OAuth2 to Normal Password but it might be a red herring. This was throw when I was trying to send a test email from/to her own account.

mailnews.smtp: Authentication failed: Socket closed. SmtpClient.sys.mjs:762:17
    _onAuthFailed resource:///modules/SmtpClient.sys.mjs:762
    _onClose resource:///modules/SmtpClient.sys.mjs:555
uncaught exception: initFromOutgoing failed, hostname: smtp.mail.att.net

Back to Bug 1978361 Comment 30