Why won't Thunderbird SEND email all of a sudden?
I don't know if THIS is a support request - or not? If it is - what I really need to know is what can I do to fix my Thunderbird email problem with trying to SEND email? I've done pretty much everything I can find to do! ATT verifies my settings are correct and had no idea what the problem was except it had to be a "Client issue". My own research found that ATT now requires a SECURE MAIL KEY for Thunderbird. Did that. Email worked once! Then not again. After several different attempts at changing various things - I could Send ONE email each time - then no more! Last nite it sent TWO emails and I thought it was fixed. But today - it's back to NOT sending ANY email! I've read and reread the Mozilla/Thunderbird articles as well as anything ATT has that seems relevant - to no avail. I'm not going to Remove Thunderbird from my computer then add it again because I would lose hundreds of important emails! I'm thinking of installing a newer version of Thunderbird on my laptop to see if it makes any difference. But that's a lot of work for nothing - when I have to believe there's some "little" 'thing' that can be fixed on my current version of Thunderbird. I have not had this problem in all the years I've been using Thunderbird which is at least 8. I'm attaching a screen capture of my current settings that have always worked & one of the boxes that come up with the so-called reason my email won't Send. Please help if you can!! PS - I've tried to add images to this question in Firefox and Chrome and for some reason they won't load. They're jpg so not big files. Will try once more and resend this question either way. Sorry for the duplicate - but wanted you to know I DO have photos that show relevant info. Thanks! WELL what do you know - this time the images loaded. Hope they help.
All Replies (4)
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20100101 Firefox/15.0.1
Windows XP?
Which version of Thunderbird?
You possibly don't have support for present day security protocols.
Why don't we keep this all in one thread?
You asked the same question here: https://support.mozilla.org/en-US/questions/1208719
where I started answering it.
The "wall of text" was because I didn't know if the number of characters was limited. Never used this before.
XP is my OS. Thunderbird version is old, but until 48 hrs ago worked perfectly!
2.0.0.23 (20090812) is the Thunderbird version. Yeah I know it's ancient but it does everything I want it to - until today. So why update? From what I've read about the newer versions - I don't like them. At this stage I don't think a newer version would make any difference. I've read tons of stories from people with my exact same problem! All with a variety of versions. I've read everything I can find on Mozilla/Thunderbird site and ATT sites. Wasted 3 days! Have tried every combination of things to do and some of them will work 1 time and then never again. Makes no sense. One guy on this site was told by a Moderator to use the exact settings I have and it worked for him. Other people with identical settings said it did NOT work for them. So there's no logic to this. I still think ATT is at fault.
The fact that a box comes up saying "Thunderbird can't connect securely to smtp.att.yahoo.com because the site uses a security protocol which isn't enabled"! means - WHAT security protocol? Is it referring to ATT's site? If ATT-Yahoo needs to "enable" a security protocol for Thunderbird to work - how in the world do we get ATT to do that?! I'm tired, lost, pissed, and going to sleep. I give up unless someone has a miracle fix!? Thanks!
All security protocols are at some point retired and replaced by improved and stronger methods. We had SSL 1.0, 2.0 and 3.0, then TLS 1.0, 1.1 and 1.2. SSL is now forbidden. TLS 1.3 is currently in preparation. I suspect that between them, XP and the version of Thunderbird you're using don't measure up to today's requirements.
That is, the security protocol being used by AT&T/Yahoo right now may not be supported by your software. You can't enable something that isn't there.