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

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

On 17 Dec 2000, Stainless Steel Rat wrote:

> 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.

But one of the examples given in RFC 1036 is exactly the same as the
example given in RFC 822!

/----
|     For example, if John Smith is visiting CCA and wishes to post a
|     message to the network, using friend Sarah Jones' account, the
|     message might read:
| 
|               From: smith@ucbvax.Berkeley.EDU (John Smith)
|               Sender: jones@cca.COM (Sarah Jones)
\----

This is just like the secretary example in RFC 822.  Hence, there is
at least some overlap between the intentions of the Sender header.
(The RFC 1036 Sender header can be used in more situations, of
course.)

Hm.

Oh, RFC 822 kinda assumes that the secretary was typing the message,
too, whereas here, it's clear that Sarah is NOT typing the message.
Hm.  But that's not the big deal, is it?

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)