On Thu, 24 Jul 2008 23:13:38 -0400
"Chris Lewis" <[EMAIL PROTECTED]> wrote:
> Hanno Hecker wrote:
> >> clamdscan. $transaction->body_filename doesn't seem to have the headers.
> > It does. There's everything received by the client.
>
> I thought it should too.
>
> I modified clamdscan to syste
Hanno Hecker wrote:
Is there a quick way of doing this other than creating a new file,
writing header->as_string and the body before stuffing in the clamd socket?
Are you talking about clamscan or clamdscan? Clamdscan is just given
the filename of the spool file, while clamscan is fed by qpsmtp
On Wed, 23 Jul 2008 20:10:21 -0400
"Chris Lewis" <[EMAIL PROTECTED]> wrote:
> Hanno Hecker wrote:
> > On Wed, 23 Jul 2008 15:42:21 -0400
> > "Chris Lewis" <[EMAIL PROTECTED]> wrote:
> >> If you take the "standard" ClamAV test executable (clam.exe), attach it
> >> to an email (I'm using swaks for
Hanno Hecker wrote:
On Wed, 23 Jul 2008 15:42:21 -0400
"Chris Lewis" <[EMAIL PROTECTED]> wrote:
If you take the "standard" ClamAV test executable (clam.exe), attach it
to an email (I'm using swaks for testing) and send it thru qpsmtpd, the
clamdscan plugin doesn't catch it.
If you take a copy
On Wed, 23 Jul 2008 15:42:21 -0400
"Chris Lewis" <[EMAIL PROTECTED]> wrote:
> If you take the "standard" ClamAV test executable (clam.exe), attach it
> to an email (I'm using swaks for testing) and send it thru qpsmtpd, the
> clamdscan plugin doesn't catch it.
>
> If you take a copy of the gener
If you take the "standard" ClamAV test executable (clam.exe), attach it
to an email (I'm using swaks for testing) and send it thru qpsmtpd, the
clamdscan plugin doesn't catch it.
If you take a copy of the generated email (full headers), OR the bare
executable, and run clamdscan (ClamAV command
