From: "James C. Sewell" 
At 07:34 PM 10/15/97 =A0Jorj Strumolo, whom God loves, said:
> =A0=A0=A0=A0James C. Sewell  writes:
>> The only difficulty is that according to the RFC, which is the
>> "standard ruleset" for mail, the headers may appear in any order.
>
> The program one uses to read the mail generally presents the
> (selected) headers in a consistent order, tho, and saves them in
> that order, often with a configurable separation line between
> messages. =A0Either point would allow automation.
This is, IMO, an unjust overgeneralization.  Although PINE on Unix seems to
do this both Elm and Eudora-Pro present the headers in the original order.
Repeating what I said in my last reply, and to bring this discussion back
to TSE, we should strive to make macros we plan to distribute handle ALL
situations and not just the one particular situation we have.  A perfect
example of this is Chris Antos' macro to handle projects.  It was written
with the various user configurations in mind and with changing only one
line in one file I can make the key to invoke it totally different.  If he
just wanted to make one for himself he would probably have written it
differently and to customize it for my settings would be a nightmare.
I apologize to all on this list if I seem too dogmatic about this issue,
but as a professional programmer myself it really bugs me to see people
(not implying anyone on this list!) slop by with code that suits their
needs or just barely works and maintains the "screw everyone else... it
works for me!" attitude.
---
---------------