In <200410222036(_dot_)22336(_dot_)blilly(_at_)erols(_dot_)com> Bruce Lilly
<blilly(_at_)erols(_dot_)com> writes:
It would help if you would actually read the documents that
you are referred to. RFC 3028 (a Standards Track RFC) is
quite clear:
That is, routes and group syntax are not permitted. If multiple
addresses are required, use a string list. Named groups are not used
here.
[...]
The address primitive never acts on the phrase part of an email
address, nor on comments within that address. It also never acts on
group names, although it does act on the addresses within the group
construct.
Thank you for proving my point. All that says is that RFC 3028 provides no
machinery for sieving based on the group name (as opposed to procmail
which could do it quite well). Likewise, it cannot sieve out messages
From: "John Smith". So what? It may be regrettable, but it does not outlaw
the use of group names in emails, and is totally neutral as to whether a
convention of using the group name "LIST" would be a Good Thing or not.
It would help even more if you would familiarize yourself with
relevant Standards Track RFCs and Standards so as to avoid
proposing cockamamie schemes.
I am still awaiting your better suggestion.
--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: chl(_at_)clerew(_dot_)man(_dot_)ac(_dot_)uk Snail: 5 Clerewood Ave,
CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5