On Fri, 27 Aug 2004, Mark Powell wrote:
> Ok, tracked it down to this code in "sub spamassassin". I put some
> debugging in:
>
> &debug("SA: 0.0");
> while (<SIN>) {
> &debug("SA: 0.0.0");
> print (SOUT $_) || &debug("SA: print error");
> }
> &debug("SA: 0.1");
I put in more debugging and it's the print that is causing QS to die. Big
surprise :( It occurs just after it's written ~250K to spamc. I guess the
extra is buffering. You can demonstrate that spamc stops accepting data
after around the 250K mark:
# mkfile 300k c
# cat c | tee d | spamc -c
0/0
# wc -c d
270336 d
Although the new 1.23 method seems good idea in principle it seems a
mistake to keep sending all the data of a 50MB email to spamc when it will
stop accepting data after it's seen 250K?
I've also tried this on perl 5.8.4 and spamassassin 2.63 with the same
failure.
Can someone please confirm that QS 1.23 works fine for them when spam
checking emails over 250K? That would help a great deal.
Cheers.
--
Mark Powell - UNIX System Administrator - The University of Salford
Information Services Division, Clifford Whitworth Building,
Salford University, Manchester, M5 4WT, UK.
Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
