From what you said, I am guessing that a lot of AOL/Avast users are having the same issue. Thanks, tanstaafl, for your detailed explanation. I don't have a AOL or AIM account anymore (they were too unreliable a email provider) so I don't know why they are acting differently than Comcast and Yahoo's IMAP servers. If you get a security error and DON'T create a security exception I suspect it makes a insecure connection since you just said you didn't trust the certificate. If you create a security exception it should create a SSL connection to the mail server. But usually its not an intermittent error - it either works okay all the time or it always reports a security error (which you workaround via a security exception). Sometimes Thunderbird detects that Avast! is playing games with the certificates (in order to scan the SSL connection), and reports a security error about the certificate. This is basically a benign MITM (man in the middle) security attack that they do to scan SSL connections as its much easier for the user than configuring the email client to call a local Avast proxy using a insecure connection, and then configuring the Avast proxy to make a SSL connection to the real mail server like you have to do if you used AVG.
TB is set to not download complete messages for offline use, nor is indexing turned on.Īvast installs some certificates to let it transparently decrypt the SSL connection, scan it, and then re-encrypt it using SSL. This all started with recent versions of both TB and Avast. On the AOL IMAP account on port 993, the popup appears most of the times that TB checks for new mail - every few minutes. They require an initial acceptance of the security exception, but the popup does not reappear again. They also are using SSL connections on port 993.
I also have Comcast and Yahoo IMAP mail accounts running in the same installation of TB. Nothing works, the behavior just returns immediately. I have tried all of the fixes I can find on the web, such as exporting the Avast mail certificate and importing it into TB, deleting Avast certificate information from the Servers tab in TB, etc. Avast anti-virus is set to scan all SSL connections. In addition to being annoyed by the almost constant error popups, I am concerned that confirming the security exception and accepting these incorrect credentials has the effect of negating the security provided by the SSL connection to the mail server. Mail seems to come in whether or not I approve the suggested incorrect certificate credentials to be saved permanently. This happens very often, but not all of the time. I now get repeated error messages that TB thinks the AOL certificate for my IMAP mail on port 993 is incorrect. I have been having an ongoing problem that started appearing a few months ago.
0 kommentar(er)
