At 11:51 PM 7/2/2003, Jason Haar wrote:
Arg. The Q-S code in question is blocking for what it thinks is a valid
reason, but then it skips to the next line - i.e. the invalid line doesn't
get written out...
Buglet: the intent is still correct, but this is sure making debugging
difficult. I'll see wh
Arg. The Q-S code in question is blocking for what it thinks is a valid
reason, but then it skips to the next line - i.e. the invalid line doesn't
get written out...
Buglet: the intent is still correct, but this is sure making debugging
difficult. I'll see what I can do ;-)
--
Cheers
Jason Haar
At 10:31 PM 7/2/2003, Jason wrote:
On Wed, Jul 02, 2003 at 09:55:20PM -0400, John Crawford wrote:
> Hi.
>
> A campus department sent out messages today that (each new one)
> kept triggering the
> $quarantine_description='Illegal breakage found in header name - potential
> virus';
Sounds like there
On Wed, Jul 02, 2003 at 09:55:20PM -0400, John Crawford wrote:
> Hi.
>
> A campus department sent out messages today that (each new one)
> kept triggering the
> $quarantine_description='Illegal breakage found in header name - potential
> virus';
Sounds like there was no empty line between the e
Hi.
A campus department sent out messages today that (each new one)
kept triggering the
$quarantine_description='Illegal breakage found in header name - potential
virus';
part of the qmail-scanner-queue code. I'm running stock v1.16
here with bad_mime = 1. If I look at the perl code and what's d
