Hi Geoff, I will help you resolve the issue, please send us the screenshot of your settings of thunderbird and AVG email setting using this link Create a screenshot http://avgread.me/1aZxsAV
Thank you
I have a standard personal Plusnet account that I download as POP3. I also have a Gmail account and two voluntary clubs accounts that I access as IMAP both requiring secure login for sending and receiving. My email client is the latest Thunderbird running on Windows 8.1.
I use the free version of AVG 2015 and use the personal email scanner. (For years I purchased the paid version of AVG for the whole of a secondary shool when I was the Network Manager there.) Until yesterday I had no issues with email scanning then after the AVG program updated yesterday to the latest, email component stopped working properly with receiving and sending of emails, though it appears to be connecting to AVG via 127.0.01 and the dedicated port, but then times out.
I have rebooted the computer, disabled and re-enabled the scanner, removed and re-applied the settings for email servers, done the same in Thunderbird, etc but to no avail. The only way I can get it to work is to disable email scanning and set up Thunderbird to send and receive directly, with no scannign of emails. I have looked through the KB on AVG but cannot find anything relating to this type of issue. Anybody had this problem or similar in the past and can throw some light on what is happening? If not it looks like I'll have to uninstall and then re-install AVH and start from square one again.
I have found the answer in this subject in community support:
"New SSL email communication problem has happened since version 2015.0.6122 or 2015.0.6125 was installed" Dated 4th August 2015.
I used the following link as in one of AVG comments :
https://share.avg.com/steam/PSP/AVG/avg_isc_x64_all_2015_6134p1.exe
ran it and it resolved the issue. I would imagine that it returned the AVG to an intermediate version as the update that my instance of AVG downloaded on 13th broke it. This somewhat surprising as the fix was posted on 6th August 2015.
Hello Geoff, I really appreciate you in finding out the right solution by reading other posts. Yes, our engineers have just found the resolution and hope you wouldn't have any issues henceforth. Please feel free to contact us incase you need further help. Thank you.