I happen to be a Sympatico user I have turned off outbound scanning and WLM works fine for me.
I find that the File System Shield has adequate protection.
im a little confused now, my present set up, i sent test email from sympatico (thru WLM) to gmail, and the scanner seems to work on it, more test to do though…
are you saying that at present it would be as if im using a totally UNSECURED connection for smtp sympatico (mail client has SSL unchecked, and avast ssl accounts - entered smtp #25 isnt really an SSL )???
(sympatico did tell me never uncheck SSL, and they didnt understand trying to have avast scan emails…, but then again no surprise because they (Bell) are out of control!)
No, that’s not what the article says. It states that Sympatico is using encryption on a port that is normally used unencrypted. That’s why others have had problems scanning outgoing email. Others seemed to have problems using port 25 and SSL with Avast not being able to scan. There is a solution and that is to use smtp port 587 and TLS in the Avast SSL accounts. That’s all. It doesn’t seem like the correct way of doing things with port 25 in both locations. That’s why I think you should change it to port 587 and TLS in Avast SSL accounts. Then test it’s operation. I think it will work just fine this way. Go back to reply #19 and give it a try. I’m going to be gone for the rest of this weekend so I won’t be able to reply. Good Luck and I will have a look when I get back. Maybe someone else can help in the meantime. I can’t say whether or not if using port 25 in both locations would allow Windows Live Mail to work outside of Avast’s protection. It seem like it could be a possibility though. That’s why I think you should change it to port 587 and TLS in Avast SSL accounts.
I can't say whether or not if using port 25 in both locations would allow Windows Live Mail to work outside of Avast's protection. It seem like it could be a possibility though. That's why I think you should change it to port 587 and TLS in Avast SSL accounts.
thanks for the caution, thats quite disturbing…i thought if it “looks” like the mails are being scanned, then thats good enough, but if something else is actually going on, or is comprimised, or more importantly if this has the effect to remove a secured encrypted (ssl) connection between Avast and my mail server, then thats a different matter…
so ill try using the other port (587) to be sure. thank you
After some more thought into it, if it was working outside of Avast you would probably receive an error message because your email client is unencrypted and the server is encrypted. Something like “error WLM was unable to communicate with server”. I don’t know what the exact message would be. In this case the mail would not be sent. If it sends and receives properly and is scanned while doing so then you are probably good to go.
You can also add notes to incoming and outgoing mail showing that they have been scanned by Avast. See attachments. Then you will have no doubts. Good way to advertise for Avast too!