Inspite of numerous post on this, let me come back to the subject again. Under 4.8 scanning mails worked in both directions and I was not asked for SSL or whatever. Now with 5. Avast automatically creates an SSL entry for POP3 with port 995 to work and it does.
But when sending, Thunderbird (set to encryption none) cannot connect to the server. So for SMTP I have either to disable outbound or to manually create an entry with port 25 under SSL, encryption none. Then it works, why? As said, Thunderbird is set to none. Why all this?
Well that may have appeared to be the case, but if your email was SSL, it wasn’t scanned as avast can’t scan the encrypted SSL traffic, that is the whole point of secure encrypted traffic.
Avast 5 works differently in that it can handle the secure forwarding of your email after scanning it.
What is the full text of the error message ?
The link you posted is working for me, see image1.
I’m using thunderbird, 3.1.7 and no problems with SSL set to none in the TB account settings. I only have one account that avast has detected as requiring SSL, for me that has been set to SMTP port 465 (image2).
What is the ISP/domain name of the problematic email account ?
Does that account actually require SSL, e.g. was it required in the original email account ?
What about the questions ?
The one about ISP is crucial as some use the normal SMTP port 25 for SSL rather than what it should be the secure SMTP port 465 and if it actually is an SSL: email account.
Just had a small break…
Look at TB.png with my TB settings saying NO encryption and POP3 on 110.
My provider also supports SSL but I chosed “none” and set also SMTP to port 25 by default.
Avast.png shows what Avast created when first time using mail. SMTP didnt work. Self creating SMPTP port 25 “none” does.
Will test tomorrow with your settings, thanks for a while…
I know that is what it says now, but was it originally meant to be an SSL account and that is only the POP3 settings and not the SMTP settings. Scroll right down to the bottom of the TB account settings, to the Outgoing Server (SMTP) Settings and click that.
There you will see all your accounts select the troublesome one and click the Edit Button and ensure that doesn’t have Connection security set to SSL/TLS.
For some reason you have no SMTP settings in the avast Mail Shield, Expert Settings, SSL Accounts
Good morning, yes, among others the above seems to be true. See my TB server setting image here.
Statement 1. In TB both in/out are set to none with standard ports 110 and 25
Statement 2. Without self adding “SSL 25 none” in Avast, outbound doesnt work
Avast detected POP3 as requiring SSL (!) which is not true (see 1.) and changed the port to 995, SSL for what ever reason.
Statement 3. With this automatic Avast POP3 setting inbound works.
Statement 4. If I change this POP3 in Avast to 110, none (like you) inbound doesnt work!
Same behaviour on 3 computers. Somehow confusing i.e. contradictory, or?
Hello David, it seems to work now with both POP and SMTP set in Avast to their defaults and encryption none. Resume:
POP3 can be left at SSL/995 as set by Avast, or NONE/110 set manually, both work.
SMTP MUST be set manually to whatever, as Avast didnt create any entry.