On Tuesday 20 Apr 2004 3:04 pm, jef moskot wrote:
> > ...remember that enabling debug now also leaves the temporary files
> > around to aid (of course!) debugging.
> Where does it leave these files?
In clamscan's temporary directory.
> Jeffrey Moskot
> System Administrator
> [EMAIL PROTECTED]
Oops. Didn't mean to spam the world with this, but since I've already
done it...
> ...remember that enabling debug now also leaves the temporary files
> around to aid (of course!) debugging.
Where does it leave these files?
Jeffrey Moskot
System Administrator
[EMAIL PROTECTED]
--
> > Is keeping a message counter feasible, given the design of the code?
> It's perfectly feasable and I've just done it when you enable debug to help
> you (look in the CVS code I've just committed - mbox.c version 1.66). However
> please don't enable debug all the time, and remember that enabling
On Wed, 14 Apr 2004, Nigel Horne wrote:
> On Wednesday 14 Apr 2004 12:58 am, jef moskot wrote:
> > Is keeping a message counter feasible, given the design of the code?
> It's perfectly feasable and I've just done it when you enable debug to help
> you (look in the CVS code I've just committed - mbo
On Wednesday 14 Apr 2004 12:58 am, jef moskot wrote:
> Is keeping a message counter feasible, given the design of the code?
It's perfectly feasable and I've just done it when you enable debug to help
you (look in the CVS code I've just committed - mbox.c version 1.66). However
please don't enable
On Fri, 9 Apr 2004, Tomasz Kojm wrote:
> jef moskot <[EMAIL PROTECTED]> wrote:
> > Is there no way to get Clam to report which message the infected file
> > (or at least the FIRST infected file) is in?
> You may try with clamscan -m --debug
Could you give some tips on how to use that to figure out
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jack
> London Networks
> Sent: Thursday, April 08, 2004 6:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Clamav-users] Cleaning MBOX files?
>
>
> If I use the --remove flag
On Fri, 9 Apr 2004 00:01:42 -0400 (EDT)
jef moskot <[EMAIL PROTECTED]> wrote:
> Is there no way to get Clam to report which message the infected file
> (or at least the FIRST infected file) is in? Or does that add too
> much overhead? Someone once suggested turning verbose mode on, but
> that st
Is there no way to get Clam to report which message the infected file (or
at least the FIRST infected file) is in? Or does that add too much
overhead? Someone once suggested turning verbose mode on, but that still
didn't help to pin down specific messages.
Jeffrey Moskot
System Administrator
[EM
I'm running CommuniGatePro. It can store mail two ways - MBOX (one big
file)and MailDir (each msg in a seperate file). The default,
unfortunately, is MBOX. I'm going to create a new MailDir-style folder
and copy all the mail to it, that should help me in the short term.
Need to see what it
What configuration are you running? (e.g. qmail+vpopmail + courierimap)
In the setup that I am running each message is stored as a seperate file
within the mail box setup.
I have the following directory structure
/home/vpopmail/domains/sampledomain.com/username/Maildir/cur
/home/vpopmail/domains/
If I use the --remove flag, it removes the whole mailbox file, not just
the infected message. Glad I tested on a copy of an infected mailbox
and not the real thing! :)
I'm looking at the other solutions proposed, but they're going to take
more work, obviously..and I don't think that it'll
On Thu, 8 Apr 2004, Jack London Networks wrote:
> Okay, I like the --mbox support of clamscan. Problem is - now that I
> know there are infected messages in people's inboxes/other folders, I
> have very little information to go on to find and clean those
> messages. For example, I know a few pe
If you want to scan all mailboxes the following command is what I use to
do a manual scan. This example is for qmail with vpopmail.
clamscan -r /home/vpopmail/domains --mbox -i --remove
If you want to scan an individual domain use
clamscan -r /home/vpopmail/domains/sampledomain.com --mbox -i --r
Antony Stone wrote:
On Thursday 08 April 2004 8:45 pm, Jack London Networks wrote:
Okay, I like the --mbox support of clamscan. Problem is - now that I
know there are infected messages in people's inboxes/other folders, I
have very little information to go on to find and clean those
messages.
Quoting Antony Stone <[EMAIL PROTECTED]>:
On Thursday 08 April 2004 8:45 pm, Jack London Networks wrote:
Okay, I like the --mbox support of clamscan. Problem is - now that I
know there are infected messages in people's inboxes/other folders, I
have very little information to go on to find and cl
On Thursday 08 April 2004 8:45 pm, Jack London Networks wrote:
> Okay, I like the --mbox support of clamscan. Problem is - now that I
> know there are infected messages in people's inboxes/other folders, I
> have very little information to go on to find and clean those
> messages. For example,
Okay, I like the --mbox support of clamscan. Problem is - now that I
know there are infected messages in people's inboxes/other folders, I
have very little information to go on to find and clean those
messages. For example, I know a few people have copies of Bagle,
SomeFool/Netsky and so fo
18 matches
Mail list logo
