Our mail server computer is offline at the moment, so we substituted a spare, which generally has the same OS and software, but differs in a few regards. It turns out that one major difference is that the substitute computer runs an older version of SA; it runs v. 2.20, while the main computer had been upgraded to 2.41. The drop back to v. 2.20 led to a rather curious circumstance:
The procmail filing recipe that invoked SA seemed to mysteriously quit working. Mail that had been properly diagnosed as spam by SA mysteriously was still filed in the user's mail box, instead of being deposited into the "dumpster" mail folder. Here's the procmail recipe: :0 fw * ? test -x /usr/bin/spamassassin | /usr/bin/spamassassin -a :0 * ^X-Spam-Flag: YES dumpster What happened? Setting VERBOSE inside the recipe indicated things were basically working, but X-Spam-Flag was never detected. Well, notice that there's no -P flag on the invocation of SA above. The -P flag tells SA to act as a filter (in v. 2.20); without the flag SA deposits the processed message directly into the default user mail box. The -P flag used to be in the recipe, but I removed it after upgrading to v. 2.41 because I saw warning messages in procmail log file, where the new version of SA noted that the -P flag is no longer necessary. Suggestion: remove the -P warning. The presence of -P doesn't hurt anything, and the lack of backward compatibility can cause some surprising behavior. ------------------------------------------------------- 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
