🚀 go-pugleaf

>All vey motherhood and apple-pie, but what is the relevance to the
>discussion?

Because the broken software in question is the program that put the
broken header in that line in the first place. Don't change all of elm's
user interface just to satisfy some broken software that certain sites
run. My novice user's like elm. If you want a more powerful user agent, use
gnu or mh or mush. Lets keep elm's objectives in focus - the novice user
has precedent.

>  Doesn't elm already allow you to edit the headers?  The
>suggestion is only that it be done in a more consistent, useful way.  In
>what way does this "break everything else"?

The explicit suggestion was to put header info in with the reply,
thereby allowing novice users to nuke messages with simple editing
errors and confusing them even more with archaic and meaningless lines.
Right now, it is somewhat hidden. Please follow the discussion - 
I have stated this already.

>>Users care about CONTENT
>>not PROCESS. They give not one whit about HOW it happened, just that it did.
>
>Until things start going wrong.....

Then they hassle the local system admin. Do you really believe they
solve the problem for themselves? If you do, you work with programmers,
or very computer literate non-programmers. I work with scientists and 
administrators, who are not stupid, just uninterested in details that 
don't directly contribute to doing their job as they perceive it.
And are certainly uninterested in mailer details.