In case people have been ignoring the Subject Line thread, I wanted to really make sure people had a look at this post. I use the example below for many things. When I write a particularly interesting SARE rule I am testing, I will have procmail/formail tag the subject if the rule hits. This way I can easily see what the rule is hitting on.
This makes overnight testing a breeze on new spams. I just check my trap for subjects with the tag. For instance you could write one that looks for an SURBL hit, and put those in an even more special folder. Because usually those are 100% spam. I sit down every morning and look at my nightly spamtrap. I may have 300 in it. Sort by the BigEvil tag, look real quick, delete by that tag, *poof* I have about 30 new spams to look at. Procmail/Formail make very fast work of it. So This is why I want to make sure people who use Procmail take a good look at the example Dan wrote below. MIND THE WORD WRAPS in his example. --Chris >-----Original Message----- >From: Dan Mahoney, System Admin [mailto:[EMAIL PROTECTED] >Sent: Tuesday, September 14, 2004 5:38 PM >To: Tom Meunier >Cc: users@spamassassin.apache.org >Subject: Re: Subject line > > >On Tue, 14 Sep 2004, Tom Meunier wrote: > >Well, if anyone cares, here's how you do it in procmail...you can use >anything you want instead of $DEFAULT. > >Have fun. > >----------------------- > ># this just captures the subject into a variable, strips spaces from ># beginning and end. >SUBJ_=`formail -xSubject: | expand | sed -e 's/^[ ]*//g' -e >'s/[ ]*$//g'` > ># this block prevents a list item from being tagged multiple times. > >:0: >* Subject.*\[.*\] >* List-Id:.*users.spamassassin.apache.org >$DEFAULT > ># and this line tags it otherwise. > >:0 >* List-Id:.*users.spamassassin.apache.org >{ > :0 fwh > | formail -I"Subject: [sa-list] ${SUBJ_}" > > :0: > $DEFAULT > >} > >------------------------ > >I've implemented this, thus I will no longer complain. >
