I’ve done some reading, messed the settings and was able to make the scanner partially work (only sending, not for all acc), but as I am no PRO, did not wanted to mess any settings so returned to the defaults. Maybe some kind soul could point what am I missing? I’m assuming, that have to add few entries in the SSL settings adnd tick off secured connectons (as I have done and few account worked) Mail client is Opera M2, protocol of choice POP/SMTP (and I will not change to IMAP).
First, you shouldn’t need to add anything to the avast! SSL settings, avast! should normally do it for you.
Figure 1 looks like you have smtp and pop reversed-or maybe I misunderstand what you mean by a gmail in your own domain. In general, the “use SSL” should be unchecked, port 110 used for pop.gmail.com, port 587 for smtp.gmail.com.
No, Google Highly recommend to use it over SSL and port 995 for POP and also Port 465 or 587 for SMTP (both 465 and 587 works)
Default Google Setting:
POP: pop.gmail.com - SSL Enabled - Port 995 (Secure Password Authentication must be disabled)
SMTP: smtp.gmail.com - SSL Enabled - Port 465 or 587 (Outgoing mail requires authentication) (Secure Password Authentication must be disabled)
Yes but if you use the standard Gmail settings with SSL then avast can`t scan the mail, so you remove the SSL settings in your mail program and use port 110/587 and avast will do the SSL 465/995 for you
And Gmail have also scanned the mail at gmail server before you get it, so you are still protected if you don`t use the avast mail scan. Gmail is using two mail scanners McAfee and Authentium
Omid, the difference is that avast! normally does the translation to these ports for you as part of its SSL/TLS connection replacing Stunnel. With Thunderbird (and even my PopMan checker) I use 110 and 587 with “use SSL” unchecked and let the SSL just happen through avast!. If I try to use 995 as my gmail pop port, with ssl unchecked, I can’t get a connection. Others have reported some different results, and I suspect is has to do with the SSL settings under mail shield that are set automatically by avast! One thing that has made it more confusing to some is that the warning not to check SSL only happens once now from avast! because it was too annoying. If you have “Use SSL” connected in a client, avast! can’t scan the mail, although it will usually go in and out ok otherwise.
If avast! does not scan the mails, I would hope avast! shield catch the nasty stuff if it has been loaded via mail! am I thinking wrong? (even though dear Pondus noticed Gmail scan the mails with it’s own Antivirus too.)
Since you aren’t using avast5 I think you don’t understand how it works.
In relatively simple terms:
If your email program accounts settings are set to use SSL then at the time of sending the email is already encrypted and can’t be scanned.
If you do as suggested (by sded) and don’t set SSL in the email account settings, avast intercepts the unencrypted email and scans it.
It then (in the case of SMTP) handles the STARTTLS function that encrypts the email and sends it on its way.
Thank you all for your answers. Changing ports to 110 for incoming, and 587 for outgoing + SSL off does work.
Still, as a non technical user, I do have doubts, whether I am safer now. I thought that SSL secured path from my pc to the mail server, so noone could i.e. ‘overhear’ the password. So now avast does communicate with the mail server in an encrypted manner? Like a proxy, to which I am connecting without encryption, but everything beneath that point is encrypted?
As an explanation, by gmail in my own domain I’ve meant a gmail account linked to my own webdomain, where you have a gmail account looking like login@mywebaddress.com. Quite useful, was free for private use, but am not sure if it still is for new users.
The only difference now is that the secured path is from avast! in your computer to the mail server instead of from your email client to the mail server. If you encrypt your messages in the client, avast! can’t scan them. So your client passes the messages to avast! unencrypted via a localhost proxy, and avast! scans for viruses and uses OpenSSL to set up a normal SSL session with your mail server. Similarly for incoming. So between your computer and the mail server everything is still encrypted; it is just done at a different point within your computer.
