> ESM> The reason I ask is that it would be useful to be able to have it
> ESM> manufacture a subject such as "[$LIST]: <no subject>" or some such, so
> ESM> that users who process their mail upon receipt by subject can do so
> ESM> reliably.
>
> Users shouldn't be processing their mail based upon its subject. That just
> isn't a very robust way of doing it.
I find myself using the subject code since I run several
related mailing lists and it is nice to be able to decide which
list to read in your mailier. With elm I can use CTRL-D (delete
pattern) to delete all messages from a list if I don't want to
read them.
I also find the subject code repulsive. IMHO you should
define a subject prefix, which always appears at the beginning
of a line. The reason is this problem: (sequence of subject headers)
Subject: My message (first message)
Subject: LIST: My message (Sent to list as)
Subject: Re: LIST: My message (Replies come in and
go out as)
Notice if you anchor the prefix (^LIST) the Re's build
up (Re: LIST: Re: LIST: ....), if you don't anchor majordomo sees
it already exists in the third subject and doesn't add anything.
What I would like is for it to take the incoming
reply and rewrite it to:
LIST: Re: My message
So you can properly delete "^LIST". Right now deleting
"LIST" can remove non-list mail that happens to have the same
string in the subject.
In any event, you're right, this is not the correct way
to sort incoming mail, but it is a very conveniant way to do
it visually, or with the tools available in many mailers. Maybe
one day we'll have support for an X-From-Mailing-List: name
header...
--
Leo Bicknell - TMBG List Admin - tmbg-list-request@tmbg.org
System Administrator / Network Technician
bicknell@ufp.org - bicknell@vt.edu - bicknell@tmbg.org
Follow-Ups:
References:
|
|
