Ok,
I turned on the fast option but my users are used to the spam reports and it's nice when someone reports a false positive to have the report so you can figure out why, so I'm hoping to go back to verbose mode if I can figure out why this is happening.
Hi
I have done some tests to add the reports headers with fast_spamassassin (really with the sa_alt of 1.22st, that works in fast_spamassassin mode). The report is added to header without any problem, but sometimes there are some pieces of text not form the report that I can't clean accurately with the regex I use to do so.
I use this command inside qmail-scanner to generate the report
spamc -R -f < $scandir/$wmaildir/new/$file_id
And capture/clean output with this code
while (<SA>) {
if (!$sa_tag) {
chomp;
($sa_score,$required_hits)=split(/\//,$_,2);
# Clean some invalid returns from SA v.2.5x
$required_hits =~ s/\r//g;
chomp $required_hits;
$sa_tag++;
next;
}
if ( /^(\s|-)\d\.\d\s[A-Z].*$/ || /^\s\s\d\d\s[A-Z].*$/ ) {
$sa_report .= $_ ;
}
}If anybody has some idea to improve the regex, I will add an option in the next st patch to add the X-Spam-Report header.
Cheers
Salvatore
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
