On Fri, Nov 08, 2002 at 03:05:25PM -0500, Drew Dowling wrote: > I've been a happy and silent user of SA for a while now. Running 2.30 now > for a whild I recently got a wild hair and decided to spend the ten > minutes needed to upgrade to 2.43. I'm just using SA as a user with > procmail, so the readme seemed cool to me. However upon upgrade I'm > getting a log to debug output that I don't understand where it's coming > from... and it's making mail that procmail filters invalid. Below are > details. > > A few hours of scanning docs havn't helped me find anything, and > sourcefourge's archive search leaves a bit to be desired. I have a > feeling this is something simply, but I seem to need some help being clued > in. > > > spanmassassin -V > SpamAssassin version 2.43 > > perl -v > This is perl, v5.6.1 built for i386-linux > [snip] > > > cat sample-nonspam.txt|spamassassin > debug: Number of lines: 108 > debug: Relative Line Numbers (in percent): 12.697333199579 29.519721770149 >40.8800726258374 63.8060390653807 74.5889492315516 93.5640391425596 > debug: Absolute Line Numbers: 13 31 44 68 80 101
Well, I don't think this debug info is from SA (I've never seen this info
before). Personally, I would run spamassassin with a -D. I'm going to
guess the debug info is from DCC, Pyzor, or Razor (although it doesn't
look like that either). The -D will give you SA debug info and should
show you where this stuff is coming from, or at least narrow it down.
--
Randomly Generated Tagline:
The choice of approaches could be made the responsibility of the
programmer.
-- Larry Wall in <[EMAIL PROTECTED]>
msg10055/pgp00000.pgp
Description: PGP signature
