But still I wonder why Avast doesn't have a FAQ or install tip to tell folks about this...
because Avast cannot know in advance what your mail provider requires, and what email client you use. It's up to the mail provider to tell you about client settings. the only thing that's different when running avast mail scanner is the change of ports in the client for ssl connections, and that's an easy guess...don't know what the help files say about it. If you first get the message that Avast detected an sll connection and it can't scan it, you can trust that, it just means what it says, that your mail provider is using ssl (not talking about authentication now, just sending and receiving protocol). So to allow the mail shield to scan your mails, providing your server requires ssl, you must set the client (Thunderbird in this case) to non-ssl ports, because avast cannot scan, obviously, encrypted stuff. So the trick is to use a proxy, now integrated in avast mail scanner (V5 only) that will recreate the ssl connections between you and your mail server, and will also take care of the decryption with the client, Thunderbird >>> that's when it can scan the mails.
Also, may be your mail server requires authentication now because it detects the man in the middle (avast mail proxy) no idea... still weird you didn't have to do that with V4....anyway it works now
