Aha! I knew I was including that header for a reason! Brilliant Michael, thanks.
C On 3/11/02 9:24 AM, "Michael Moncur" <[EMAIL PROTECTED]> wrote: > Here's a cute idea for those of us who admit to using Outlook. Inspired by the > X-message-flag headers that certain people put in their mail to annoy Outlook > users, I added the following procmail recipe after the message has been piped > through SpamAssassin and before the delivery recipe: > > :0fw > * ^X-Spam-Report: \/.*; > | formail -I "X-message-flag: $MATCH" -I "X-Spam-Status: Yes" > > This takes each message marked as spam and adds an X-message-flag header with > the first line of the spam report, i.e. "11.8 hits, 7 required;". This > displays > at the top of the message window when you open it in Outlook. > > More importantly, you can add the Follow Up Flag field to your message list > display, and get an instant spam reading without opening the message. You can > also sort by this field to look at the messages in order of spammishness. > > This might be a neat user-configurable (and off by default) feature for > SpamAssassin at some point. It would be a very user-friendly way for Outlook > users to spot spam without looking at the headers. > > Technical notes: This requires that report_header and use_terse_report be > turned on. The procmail recipe also replaces the X-Spam-Status header with a > shorter one - this is because the long list of tests in this header tends to > confuse Outlook and prevent the message flag display. The list of matched > tests > will be in the spam report anyway. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
