Thanks for your suggestion, Stephen. By "distinction" is just meant
the differentation of mailing list messages addressed to me too from
those that aren't -- the purpose behind that kind of recipe.
Regards,
--
Rick Troxel Rick_Troxel(_at_)nih(_dot_)gov
rick(_at_)helix(_dot_)nih(_dot_)gov 301/435-2983
http://www.access.digex.net/%7Erobjen/dc-sage/bios/rick_troxel/
///////////////////////////////////////////////////////////////////
All effort and exertion put forth by man from the fullness of his
heart is worship, if it is prompted by the highest motives and
the will to do service to humanity. --Abdu'l-Baha
On Thu, 25 Jul 1996, Stephen R. van den Berg wrote:
Rick Troxel wrote:
This would break recipes I have for differentiating mailing list
arrivals addressed to me as well as a list, e.g.
# ISDN List
:0:
* ^TOisdn(-digest)?@(max\.)?bungi\.com
* ! ^TOrick(_at_)helix\(_dot_)nih\(_dot_)gov
isdn
True. However, this currently is not guaranteed to work as intended
either, because the ^TO expansion already includes things like
"X-Envelope-To:", which defeats the purpose you're checking for (crummy
English, I know, got lost in the sentence somewhere).
You'd be better off reformulating it similar to:
# ISDN List
:0:
* ^TOisdn(-digest)?@(max\.)?bungi\.com
* ! ^(To|Cc):(_dot_)*[^-a-z0-9(_dot_)]rick(_at_)helix\(_dot_)nih\(_dot_)gov
isdn
I think I could live with this breakage. However, the user community's
need for that kind of distinction strikes me as possibly not trivial.
Which kind of distinction? I don't quite understand what you are saying
(trying to say?) here, I think.