I just match on either the "Sender: owner-ietf@xxxxxxxx" header, or the ML specific email address I've created. I'm using Sylpheed though, it seems to be more flexible on matching header fields than most other email clients I've used in the past. On Wed, 17 Dec 2003 09:13:13 -0500 Gordon Cook <cook@xxxxxxxxxxxxxx> wrote: > >On Wed, Dec 17, 2003 at 08:00:38AM +0200, Pekka Savola wrote: > >> > >> I don't- IMHO it's stupid to waste the precious bits in the subject > >> line to say "[ietf] " because there is no need for such. The messages > >> can be filtered better using other thods as well, and humans can look > >> at the headers.. > > > >I agree, for filtering everything's in the header already. > > > >Tim > > I do not use eudora to forward list mail to separate mail boxes. > therefore if i don't start list filtering into seperate mail boxes, i > am forced to guess where a piece of mail might be ietf since adding 6 > characters to ever subject headers is judged unhelpful and > unacceptable? > > There is no sure way at all to tell from a subject line whether its > IETF and to complain about adding 6 ascii characters to a subject > line wasting bits if it gives several thousand humans a hint as to > whether to open and read, or delete unopened, or delete mail to spam > mail box seems to be strange. But this point of view i guess is why > the list keepers have not yet and probably never will do what most of > the other lists that I receive do. > > -- > ============================================================= > The COOK Report on Internet Protocol, 609 882-2572 (PSTN) 703 738-6031 > (Vonage) Subscription info & prices at > http://cookreport.com/subscriptions.shtml > Googin on real time global corp. http://cookreport.com/12.11.shtml Purchase 10 > years of back issues at http://www.cafeshops.com/cookreportinter.6936314 > E-mail cook@xxxxxxxxxxxxxx or use cook@xxxxxxxxxxx Free World Dial up 17318 > ============================================================= >