ou think of anything else that this might break?
> -Original Message-
> From: Dallas L. Engelken [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 30, 2003 9:43 AM
> To: Jeremy Kusnetz; [EMAIL PROTECTED]
> Subject: RE: [Qmail-scanner-general]Trying to daemonize uvscan thro
> -Original Message-
> From: Jeremy Kusnetz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 29, 2003 5:01 PM
>
> Actually I'm now looking at the uvscan docs, it seems by
> adding --mime and --mailbox to uvscan it should handle the
> unpacked email by itself. Maybe these should be added
> Actually I'm now looking at the uvscan docs, it seems by
> adding --mime and --mailbox to uvscan it should handle the
> unpacked email by itself. Maybe these should be added to
> qmail-scanner itself? Also qmail-scanner sets the --secure
> option, which activates --unzip, so should --unzip
> -Original Message-
> From: Jeremy Kusnetz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 29, 2003 5:01 PM
> To: Dallas L. Engelken; [EMAIL PROTECTED]
> Subject: RE: [Qmail-scanner-general]Trying to daemonize
> uvscan through spamd
>
> Actually I'm now l
> you are daemonizing a command line call? it's still a command line
> scanner. a daemonized uvscan would be one that loads virus defs into
> memory, and a message is piped through it... this is how spamc/spamd
> works. i guess i dont see what you are gaining by doing this?
Okay, so I'm not
> -Original Message-
> From: Jeremy Kusnetz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 29, 2003 3:29 PM
>
> I've been running with virus scanning through uvscan and spam
> scanning with spamassassin with no problems.
>
> I would now like to move to where both virus and spam
> scann
