That this issue has persisted for over a week, with no solution from Avast, and in fact that Avast seems to insert a bogus(?) certificate for sites greatly shakes my confidence in Avast's security. ![]() It seems that MailShield (since V7.0?) inserts itself 'seamlessly' into the IMAP connection stream, and presents its own certificate to the mail client, but that has expired and does not get renewed). When I disable MailShield, I get no certificate issues, and in fact TB shows no certificate at all. But there are many other applications that need certificates to enable. Certainly, the most common applications are web-related and in this case, both the servers and the browsers need to trust each other. The security certificate that is shown apparently is issued by Avast! and has expired on 8/6/13 (I take that to be the 8h of June) The way they do this is by installing a digital certificate that references a common root Certificate Authority (CA) in their applications. With avast! MailShield enabled, I get a nasty warning. Imap.gmail certificate (avast! issued?) expired.ĭetails This issue has been discussed for over a week on the Avast! mac Forum, but there has been no action/resolution:įor over a week now, when accessing my IMAP mail accounts at gmail ( and ), ![]() ![]() I just raised a ticket on the avast! ticketing system on this:
0 Comments
Leave a Reply. |