there is a new beta version ready - 22.9.6033 (build 22.9.7539).
What was fixed
Mail Shield connection problems - additional fix (again to be verified in this Beta), do not hesitate to confirm if any Mail Shield related issue still perists
Avoid extra data download by Emergency Update component (full/diff update package)
6032 and 6033 are breaking access to local devices with self signed certificates… I thought I had it fixed in Firefox with 6032 (import new Avast certificate) then 6033 broke it all again. Worse, I have a PaleMoon configuration to specifically access a local device that only has RC4. Avast now appears to block or break any RC4 encryption completely which is ok for the web as a whole, but not fine for a designated local sub-net – browsers already provide that protection. Clearly turning off HTTPS scanning solves the problem, but also opens up a big hole in protection. Please go back to before 6032!
Hi petr, I believe I successfully reproduced the mail shield issue on Windows 7 VM, and unfortunately the issue is still there with this latest beta.
No problem with Win10 machine.
Here is what I found:
For Receiving:
The issue only happens when SSL/TLS encryption for POP3 is used. Plain-text POP3 is not affected
If I specify encryption protocols as “TLS1.2”, it works fine. When set to “Automatic” (default), it fails
The client throws error code 0x80090304, saying “Failed to initialize SSL”
For Sending:
The issue only happens when SSL/TLS encryption for SMTP is used. Plain-text SMTP is not affected - Specifying encryption protocols does not work for SMTP
If I specify encryption protocols as “TLS1.2”, it works fine. When set to “Automatic” (default), it fails
The client throws error code 0x80090308 or 0x80090304 depending on e-mail providers, saying “Failed to initialize SSL”
The client uses SChannel for SSL/TLS encryption.
Support package ID is: 9EGMP
Hope this helps.
Edit: I found a wrong setting in testing environment. Specifying protocols works for SMTP too when correctly set.