On 9 Apr 2013 at 11:12, Steve Basford wrote:
Hi All,
Couple of updates..
I've just check end the Sanesecurity.TestSig.GTUBE signature name had
accidentally been renamed to Sanesecurity.TestSig.10616
I have, however, removed the checks for GTUBE, so at least ClamAV and
Third-Party
On Wed, Apr 10, 2013 at 9:54 AM, Paul Whelan paul...@blakecomp.co.uk wrote:
On 9 Apr 2013 at 11:12, Steve Basford wrote:
Hi All,
Couple of updates..
I've just check end the Sanesecurity.TestSig.GTUBE signature name had
accidentally been renamed to Sanesecurity.TestSig.10616
I have,
Given that a large proportion of the Sanesecurity sigs detect spam,
phishing, and other junk
mail (and folks use them as such), wouldn't it be useful to include a
standard spam test
signature by default?
It seems to be very controversial if ClamAV should include signatures
for other
Peter Bonivart skrev den 2013-04-10 10:10:
It seems to be very controversial if ClamAV should include signatures
for other things than classic malware. Why not have some kind of
classification of the signatures and let us control what we download
via Freshclam?
PUA categories ?
well i like
Hello,
I configured freshclam to not lookup the dns for existance of a new
patternversion. Instead freshclam contacts the
clamav-server and fire up HTTP Head queries. That way I could let run freshclam
once a minute.
Because I run a clamav-mirror in my local network, that's not a problem.
But
On 4/10/13 6:05 AM, Andreas Schulze wrote:
I configured freshclam to not lookup the dns for existance of a new
patternversion. Instead freshclam contacts the
clamav-server and fire up HTTP Head queries. That way I could let run
freshclam once a minute.
I thought the limit was four times an
I just compiled clamav 0.97.7 on SANS SIFT Linux.
Reviewing the README file and google, it appears that clamscan should be
able to review/scan mbox files, but any attempt at using --mbox, such as
clamscan --mbox or clamscan -d /tmp/virdir --mbox /path/to/mboxfile,
reports an error with the --mbox
Scott,
Looking at the code, I think the option is 'scan-mail'. It defaults as yes,
so you shouldn't need to do anything special, just clamscan /path/to/mbox/.
Let us know if that is not working.
Steve
On Wed, Apr 10, 2013 at 4:46 PM, Scott Ehrlich sc...@ehrlichtronics.comwrote:
I just
In the past I've addressed most of my ClamAV® Database mirror issues directly
with luca.
Is there someone else I should be working with or post to the list?
And speaking of Luca, he's still listed as administrator at the bottom of all
the ClamAV Mailing Lists
You may be correct, though recalling my command-line options, including
verbose mode, the mbox file is very large, yet the scan took just a few
seconds.There is no indication that the mbox file is being properly
scanned, and knowing the base64 attachments that appear via xxd and grep, I
have
On Apr 10, 2013, at 4:41 PM, Scott Ehrlich sc...@ehrlichtronics.com wrote:
You may be correct, though recalling my command-line options, including
verbose mode, the mbox file is very large, yet the scan took just a few
seconds.
Then you'll need to change:
--max-filesize=#n
On Apr 10, 2013, at 4:59 PM, A K Varnell alvarn...@mac.com wrote:
On Apr 10, 2013, at 4:41 PM, Scott Ehrlich sc...@ehrlichtronics.com wrote:
You may be correct, though recalling my command-line options, including
verbose mode, the mbox file is very large, yet the scan took just a few
12 matches
Mail list logo
