POP issue - Mail shield - SSL

Hi everyone,
I must say I use Avast for years and I’m very satisfied!

I had a problem regarding configuring email account on Outlook Express on Win XP.
POP server constantly reported error and I couldn’t receive emails.
Therefore I changed settings in Avast → Mail shield → Expert settings → SSL accounts and set it to “None” instead “SSL”.
(SSL was selected by default!)

I just wanted to let you know if you have similar problem, how to deal with it.

I also wanted to suggest to Avast developers to make it “None” by default, not SSL!

Anyway, keep up the good work!

Best regards
Imbrod

Your POP3 account required normally the SSL or not?
If the answer is yes, you must remove SSL protection from outlook, and let avast to make the SSL connection.

But Yes, I’ve a similar issue with SMTP connection account.
My provider doesn’t require the SSL protection, but avast protect it anyway, then i must remove SSL protection in avast…
Probably it’s a good idea :slight_smile:

Just to reinforce your post; it is a good idea if that is the correct configuration for your specific email provider (no SSL required).

If SSL is required by the email provider, then the good idea would be to find out where exactly the problem is and solve the conflict, instead of just lowering the email protection.

Obviously Ady4um :slight_smile:
But in fact, if I NOT remove the SSL protection by avast (which is not required by my ISP) my SMTP server does not work.

Now is not a problem for me, but maybe someone who does not know it, has the mail does not work.

Perhaps it would be better, during installation that avast asks if you want to secure SSL ports.

What do you think?

@giogio,

I respectfully disagree. The problem here would be siting on the chair :). How a simple common average user would know if the problem with the email is:

A_ SSL not used by the email provider, so it is recommended to disable it to get the email to work (with Avast scans and protection); OR,

B_ SSl is used by the email provider, and it is currently not working for the user, just because a bad configuration or some other conflict?

In case #A, disabling is the correct path, while in #B the user might think that “hey, it’s working” but in fact it is working without protection. Both #A and #B problems and consequences are almost the same to the eyes of the user (and the difference would be seen only if the user is looking for it).

So, the user MUST investigate first if the email provider uses SSL, so to evaluate the problem correctly.

In the same line of thinking, a simple average user installing Avast probably would not know in advance if the email provider uses SSL or not. In addition, the user still needs to configure the email client accordingly, so Avast asking the user is no real solution.

In fact, the solution is not on Avast’s side, but on the user’s side: ask, read, request for help, learn. Avast is only the second line of defense. The user is the first one ;).

+1
I agree with you! But, in my area, about 80-90% of users do not know what is a Secure Sockets Layer! ;D