Well, after further investigations it looks like it actually is spamassassin which is giving the problems. It checks the message in 0.00112 seconds with razor! The problem is when the message has big attachments!
- Peter > On Wed, 06 Nov 2002 10:40:34 +0100 > "Peter M. Nielsen" <[EMAIL PROTECTED]> wrote: > >> After upgrading to qmail-scanner 1.15 I suddenly get some >> x-spam-status Yes even though spamassassin is not even run. Further >> it is not spam. I just snip' ing one of the mailheaders. I'm running >> spamassasin 2.43 even though it keeps saying 2.20? (another >> weirdnes). I don't know if it is spamassassin or qmail.scanner >> generating this fault > > If spamasassin isn't even run it cant be it's fault now, cant it? ;) > >> Received: from [EMAIL PROTECTED] by web.ifka.dk by uid 503 with >> qmail-scanner-1.15 >> (spamassassin: 2.20. Clear:SA:1(0/0):. >> Processed in 4.976303 secs); 06 Nov 2002 09:22:13 -0000 >> X-Spam-Status: Yes, hits=0 required=0 > > Since both the X-Spam-status header and the qmail-scanner trace header > says the score was 0/0 i'd be very inclined to say it's a qmail-scanner > issue. > > --- > Lars Hansson > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
