sabat said: > This is a patch I always find myself making whenever I install SA on our > servers. It's useful to always have the spam report included in the > headers, even if a mail is not tagged as spam -- we often want to know > what rules the mail triggered, and maybe why it didn't get caught. > > The patch modifies Conf.pm and PerMsgStatus.pm, and adds a configuration > option 'always_report', which defaults to 0. It patches cleanly over the > current (Jan. 20) version of 2.50. The only issue with it is that the > report still says 'This message is probably spam', but I didn't feel > comfortable messing around with adding a new report or changing the > existing one. I don't think it matters, since this is primarily for > testing and debugging.
Thanks sabat -- that's now in. However I changed the name to always_add_report, so it's consistent with always_add_headers. --j. ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
