I would recommend that users having this issue go back and double check their providers recommended settings for their Incoming email in POP3. Today, I returned to that recommended setting for 'Incoming' and this solved the problem with accessing Sympatico mail through Thunderbird. When I had originally installed Thunderbird, it took me two days to figure out the settings needed to make Sympatico work since Thunderbird was not able to do it automatically and, of course, I had an older version of Avast.įor incoming mail settings, Bell recommended 'Yes' for'SSL required' which would set the Port to 995 however, I had to set it to 'None' which changed the Port to 110. The issue was with the 'Incoming' settings. This morning I went to Bell Canada to double check the settings needed for POP3 thinking that perhaps Bell had made changes. I tried the fixes suggested and nothing worked. I had the same issue after updating my mom's computer (Vista OS) to Avast on the 9th - her email is Sympatico. Even an experience googler will find it VERY difficult to attribute the problem to Avast. Thunderbird puts up a generic SMTP error. I am amazed that Avast expects people to 1) FIGURE OUT the cause of this problem. I am an IT guy and this was anything but straightforward I pity the average home user who encounters this issue. Got mine working by following the export/import certificate dance. I had to delete the existing certificate in Thunderbird to get this working There is simply no other reasonable conclusion but that Avast SSL mail scanning does not presently work properly with at least some SSL accounts set up on Thunderbird. It took my whole sunday to figure this out, so not too confident i should bother to take the additional steps to import the certificate/exception per steps (if i must do this everytime i change or setup a new machine - at least past versions would provide user info/option to change ports to enable SSL scanning etc.) specially, if scanning mail isnt that critical or advisable if AV programs detect and stop viruses as soon as they try to execute and the risk of allowing an AV to delete or quarantine virus could result in the whole email folder (your inbox) to disappear. deleting the exception, using TB 995 SSL and turning off 'scan inbound mail' in settings released the grip avast had on my keyboard and allowed my SSL port: 995 email to download properly. but that same "on" setting also caused elements on my keyboard to stop working incl. Turning on 'inbound mail scanner' not only threw the certificate dialog which worked for only that session if i accept the exception 'permanently' and the mail stops downloading after that session. Happened to me too on a brand new windows 8 asus fresh factory install using latest avast īut i want to note a few other items i also discovered in a weekend troubleshooting process before following a hunch that avast port/ssl might be worth looking into. I hope Avast acknowledges this problem and commits to identifying and correcting its source. I tried importing the Avast security certificate to Thunderbird, but that made no difference (and I had never received any warning that the "mail server certificate is invalid" as described here on the site one contributor to this thread recommended: ). My choices are either to revert to non-SSL on Thunderbird or to untick the "Scan SSL connections" box in the Mail Shield settings on Avast. On both Windows 7 and Windows 8 laptops, I cannot send or receive mail when Avast is set to "scan SSL connections" in the Mail Shield. My Verizon (FiOS) email account on Thunderbird is set to SSL with the proper ports (POP incoming, 995, and outgoing, 465), servers, etc. Here are my details: I am running the latest version of both Thunderbird and Avast 8. Quote from: Bolt on March 19, 2013, 07:06:31 PM I'm not sure what I can add except to confirm that this problem is very real - others reporting it here are not imagining things.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |