Although I complete support what Mark has recommended, I would caution that 
there could easily be a future signature that will cause this same issue if the 
root cause of not upgrading to pcre2 is not accomplished, and figuring out what 
signature that is won’t be easy.

Sent from my iPad

-Al-

> On May 1, 2020, at 18:38, James Brown via clamav-users 
> <[email protected]> wrote:
> 
> On 1 May 2020, at 8:31 pm, Mark Allan via clamav-users 
> <[email protected]> wrote:
>> 
>> Try excluding Email.Exploit.Efail-6641027-1 from the main ClamAV set.
> 
> Thanks Mark. After over 12 hours clamd is still up and running. Looks like 
> that sig was causing the problem.
> 
> James.
> 
> _______________________________________________
> 
> clamav-users mailing list
> [email protected]
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

clamav-users mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to