Tbird Configuration for Yahoo/ATT Mail Not Working - "Unable to log in at server. Probably wrong configuration, username or password"
I'm setting up a new PC, and am using the same settings that have been on the old PC for three years and are in the Yahoo configuration guide: Pop3 inbound. att.net/outbound. att.net 995/465 SSL/TLS Normal Password
I've been at this for hours, and Tbird just won't connect. The error is "Unable to log in at server. Probably wrong configuration, username or password". I am stumped.
Được chỉnh sửa bởi Wayne Mery vào
Giải pháp được chọn
AT&T server settings:
POP incoming server settings: Email-Server is 'inbound.att.net', port 995, connection security SSL/TLS, Authentication Method: normal password. User name is full email address. The outgoing SMTP server is 'outbound.att.net' on port '465', Connection SEcurity: SSL/TLS, Authentication Method: normal password. User name is full email address.
OAuth2 is not supported for the AT&T servers. Use normal password authentication but enter a secure mail key.
You will need to set up an app specific password/secure mail key and then at prompt enter that secure mail key instead of usual normal password. Info: https://www.att.com/support/article/email-support/KM1240308
Đọc câu trả lời này trong ngữ cảnh 👍 1Tất cả các câu trả lời (2)
Giải pháp được chọn
AT&T server settings:
POP incoming server settings: Email-Server is 'inbound.att.net', port 995, connection security SSL/TLS, Authentication Method: normal password. User name is full email address. The outgoing SMTP server is 'outbound.att.net' on port '465', Connection SEcurity: SSL/TLS, Authentication Method: normal password. User name is full email address.
OAuth2 is not supported for the AT&T servers. Use normal password authentication but enter a secure mail key.
You will need to set up an app specific password/secure mail key and then at prompt enter that secure mail key instead of usual normal password. Info: https://www.att.com/support/article/email-support/KM1240308
Ugh. I forgot about the OAuth2 from the last time I did this. That did the trick. Thank you!