Re: Disable generation of "Sender: " by default.

[Stainless Steel Rat <ratinox@peorth.gweep.net>]

* Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)  on Sun, 17 Dec 2000
| Gack.  I still feel that the intent of the Sender header is the same
| in RFC 822 and 1036, but it's only a feeling.

RFC 822: Sender is the agent responsibible for submitting a message to the
network when he is someone other than the originator of the message.  Ie,
if you write a message and I send it, you are the originator (From) and I
am the submitter (Sender).  Sender is generated by hand -- never software
-- when more than one agent is involved.  It exists only to denote this fact.

RFC 1036: Sender exists as a crude authentication mechanism.  Sender is the
authenticated (by software) local mailbox of the originator of the message
when that mailbox differs from the one in the originator header.  Ie, if I
am on, say, skuld.gweep.net w/ login 'ratinox' and I post a news article
with 'grumble@bogus.com' as my From header, then some program somewhere
must generate 'Sender: ratinox@skuld.gweep.net'.

They are not even vaguely close to each other.  My opinion is that RFC
1036's Sender is badly broken, because it utterly fails to accomplish its
goal.  RFC 822's Sender does exactly what it is intended to do, no more, no
less.
-- 
Rat <ratinox@peorth.gweep.net>    \ If Happy Fun Ball begins to smoke, get
Minion of Nathan - Nathan says Hi! \ away immediately. Seek shelter and cover
PGP Key: at a key server near you!  \ head.