Does anyone have any problem with Avast! redirecting ports 465 and ports 995
to scan e-mail through a secure socket layer like Google® Mail uses? I have
not problem with any of my providers that use the standard ports. But if I
add ports 465 or 995 (as in 25,465 or 110,995) then my e-mail program can no
longer connect with the e-mail provider that is using SSL. The other e-mail
providers continue to connect fine so I have the feeling Avast! doesn't know
how to handle an SSL connection. Anyone else having this problem?

--
Mark R. Cusumano
eMail: (E-Mail Removed)
Skype Name: mark.cusumano

On Wed, 4 Jul 2007 09:13:36 -0400 "Mark R. Cusumano"
<(E-Mail Removed)> wrote:

>Does anyone have any problem with Avast! redirecting ports 465 and ports 995
>to scan e-mail through a secure socket layer like Google® Mail uses? I have
>not problem with any of my providers that use the standard ports. But if I
>add ports 465 or 995 (as in 25,465 or 110,995) then my e-mail program can no
>longer connect with the e-mail provider that is using SSL. The other e-mail
>providers continue to connect fine so I have the feeling Avast! doesn't know
>how to handle an SSL connection. Anyone else having this problem?

No anti-virus can check SSL email and if they could it wouldn't say much for
SSL.

Check out http://forum.avast.com/index.php?topic=10428.0 for a possible
workaround for you.