[13060] in Athena Bugs
Re: comp is not RFC822-compliant
daemon@ATHENA.MIT.EDU (cfields@MIT.EDU)
Sun Jan 1 19:43:29 1995
From: cfields@MIT.EDU
Date: Sun, 1 Jan 1995 19:42:44 -0500
To: jcb@MIT.EDU
Cc: bugs@MIT.EDU
Hi! You reported:
> I tried to use comp to send a message with a "Sender:" line (which was
> different from the "From:" line, as permitted in RFC822) in the header,
> and it gave the following error message:
>
> For your convenience, here is the part of RFC822 that describes the
> "From" and "Sender" fields:
>
> 4.4.2. SENDER / RESENT-SENDER
>
> This field contains the authenticated identity of the AGENT
> (person, system or process) that sends the message. It is
> intended for use when the sender is not the author of the mes-
> sage, or to indicate who among a group of authors actually
> sent the message.
I'm not an expert on RFC822, nor do I play one on TV (and what a
boring TV show that would be!). But, as I read this, the sender is to
be an "authenticated identity." How can this have any prayer of being
true if the user is allowed to specify it? As I understand it, if the
from field doesn't match the machine's concept of who you are, it adds
the sender field to say so.
Does this sound reasonable, or did I just make it up?
Craig Fields
I/S DCNS Development
cfields@mit.edu
