Just thought I’d point out that the problem with Avast and Thunderbird, where Avast changes the Mail Shield settings to SSL without warning and stops your email working, exists with Avast v6 as well as v5, and so is a current problem as of Jan 2012.
Please dont double post as it makes it very hard to follow for those that wish to help.
Avast doesnt change any email settings on it’s own.
Quote from: Dodgy Geezer on Today at 02:18:49
Yup - I have T-bird 2 and 3, and I’m running Avast!v6 on an XP system. The same thing happened to me three days ago (Jan 19 2012) - I could receive emails, but not send them. Looked in my Mail Shield, and all my POPs and SMTPs were set to SSL. Took them back to NONE and the problem went away.
So it seems to be a general problem with Avast!, and they haven’t bothered to fix it. They probably have too many customers, and want to lose a few…
What you need to have done is set the outgoing and incoming security in thunderbird to none so that avast can then handle the security for you, then avast will automatically put the accounts back in the mail shield when you send and recieve mail, those POP’s and SMTP that were set to SSL are supposed to be there.
Why are you running TB 2 and 3 when the latest version is now 9.1 i believe
There are multiple instances of Thunderbird Portable 2.0.0.24 and 3.1.17 (which is the current ‘legacy’ version - about 14.
The system was running smoothly until a few days ago, when my email stopped being able to send, with an SSL-associated error message. I had made no alterations to any settings before this.
I googled on that message, and found the corresponding thread on this board about Avast 5, which asserted that the Avast Mail Shield incorrectly set POP and SMTP settings to require SSL, and that resetting these would cure the problem.
I checked those fields - they were set to SSL. I reset those fields from SSL to NONE, and the mail started working again. So I am now happy. I left this message on your forum because the only message there talks about problems with Avast 5, and I wanted to warn people that Avast 6 also seems to be associated with the issue…