The code for loading the data directories will give priority to loading the
ignore list (from ign2 files and from the daily.ign2 inside daily.cvd)
before loading signatures, which is just a list of signature names.
The rest of the signatures are loaded after that. Then every signature name
is chec
Thanks,
I send you an example of a live mail.
On the other hand, I am surprised that clamd does not stop the analysis if
ReadTimeout is exceeded and if there is no more "contact" with clamdscan! What
is this Timout for otherwise?
It's a pity that clamd is using resources unnecessarily in
Hello again,
On Mon, 8 Apr 2019, Arnaud Jacques wrote:
Le 07/04/2019 ? 18:18, G.W. Haywood via clamav-users a ?crit?:
> > grep -a '^Phishtank.Phishing' daily.cld | cut -d':' -f1 >
> ~/phishtank.ign2
This is not optimized :
Phishtank.Phishing are loaded in memory.
Then phishtank.ign2 is loaded
G’day,
Based on your clamdtop screenshot, it looks like your signature database is up
to date with today’s update. Friday’s daily update included a large number of
signatures that slowed everything down, but they were dropped on Saturday so I
don’t _think_ that should be the reason why you’re
Morning,
Some email scan are very slow. This is happening more and more often, and
seems more related to Clamd's demime problems than real email attachments
concerns.
Here is an example of an email that takes several minutes to analyze:
# time clamdscan 1hDTxy-0002Dk-Lc.eml
/tmp/eml/1hDTx
Hi guys,
Thanks a lot for your help, so I think as long as it is GPL I will be safe
by installing it on educational institutions for what I am reading from you
guys.
Thanks again
Tim
On Sat, Apr 6, 2019, 2:47 PM Scott Kitterman via clamav-users <
clamav-users@lists.clamav.net> wrote:
> On Sat
