The copy distributed with spamassassin 2.42 chokes because I don't have Mail/ArchiveIterator.pm installed (no, that's not what I'm asking about), so I diffed against 2.50-cvs (in which mass-check works) to see what had changed. I spotted this:
< $spamtest->remove_spamassassin_markup($ma); --- > > # this API doesn't work this way ;) anyway, slowing down mass-check to > # do this is not good. instead, remove the markup in advance. > #$spamtest->remove_spamassassin_markup($ma); > Does this mean I can't run mass-check against my archive of false negatives without first preprocessing that archive to delete the old spamassassin markup? In which case I might as well not use mass-check at all, but just "formail -s spamassassin ..."? ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
