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.
-Dan
Jim Maul wrote:
Also, i dont see how it would break alphabetical sorting any more than mail
clients inserting Re: before the subject.
All I have to test with here is Outlook, Outlook Express, and Mozilla Thunderbird. They all ignore RE: and FWD: when sorting by subject. They don't ignore [LISTNAME] and they don't ignore RE: or FWD: if it appears AFTER listname because someone's broken mail client changed it all around.
So
Re: [LISTNAME] Subject does not come out anywhere near [LISTNAME] Re: Subject. Probably I'm the only person on the planet that has this particular peeve. I vote for per-user settings, and if that's not available I vote for postpending it, and if that's not available I vote for "Hey, I hate them and deal with it, so you deal with it when they're NOT there!"
--
"You're not normal!"
-Michael G. Kessler, referring to my modem online time.
--------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---------------------------
