12-10-2013 08:59:02 AM
I've searched for an answer to this for a while but now that ssl is apparently being forced I need to solve it.
My Thunderbird client won't connect to inbound.ATT.net if SSL is selected with port 995. It works fine if no encryption and port 110 are selected. I've tried deleting and resetting the password. I've tried deleting the account from Thunderbird and resetting it. No change. Outgoing email is no problem using SSL and port 465.
When I was resetting the account and Thunderbird was automatically establishing the account settings, it said my login or password were not correct. I have no problem logging in using that address and password on webmail or if SSL is not selected so I have no reason to doubt the accuracy of either.
Solved! Go to Solution.
12-11-2013 02:09:28 PM
Thanks for posting. We can definitely help! Please send us a private message by clicking here, and we'll try to find an alternative for you.
In your message, please provide your name, phone number, email address, and the best time to reach you. You can expect a reply within two business days, so keep an eye on the little blue envelope icon in the top right corner of your screen.
In the meantime, feel free to message me with any other questions or concerns!
12-13-2013 10:16:06 AM
Tim from ATT support called to help with this and I have to say the support was some of the best I've ever received. Eventually traced it to a firewall issue. Some accounts worked on the same port but this one didn't. I wrote a new rule to open port 995 for Thunderbird and it started working.
I'm amazed by the effort ATT support extended. Thanks!
12-15-2013 11:33:57 AM - edited 12-16-2013 10:03:56 AM
I use Windows firewall. In Windows 7 open Windows Firewall in Control Panel.
- Select Outbound Rules on the left.
- Select New Rule on the right.
- Select Port in the new window, next
- Select TCP and Specific remote port (enter 995), next
- Select Allow this Connection, next
- Select all three options, next
- Name it and hit finish
- Select the new rule from the list and select properties
- Under the Programs and Services tab select "This program" and browse to Thunderbird.exe"
- click OK and you should be done.
Entering Thunderbird.exe limits the rule to that email client so no malware can use the rule. If you don't use Thunderbird enter whanever mail client you do use.
EDIT: I also should have mentioned that if you just switched to SSL and can't send or receive email try shutting off your antivirus email scanner. Avira won't work with SSL and I'm sure others have the same issue.