rfc2822bis: "originator of the message" and "transmitter" not defined

Mark Martinec <[email protected]>
Newsgroups gmane.ietf.rfc822
Organization Jozef Stefan Institute
Message-ID <[email protected]>
> 3.6.2.
> [...]
>    The originator fields indicate the mailbox(es) of the source of the
>    message.  The "From:" field specifies the author(s) of the message,
>    that is, the mailbox(es) of the person(s) or system(s) responsible
>    for the writing of the message.  The "Sender:" field specifies the
>    mailbox of the agent responsible for the actual transmission of the
>    message.  For example, if a secretary were to send a message for
>    another person, the mailbox of the secretary would appear in the
>    "Sender:" field and the mailbox of the actual author would appear in
>    the "From:" field.  If the originator of the message can be indicated
                                ^^^^^^^^^^^^^^^^^^^^^^^^^
>    by a single mailbox and the author and transmitter are identical, the
                                            ^^^^^^^^^^^
>    "Sender:" field SHOULD NOT be used.  Otherwise, both fields SHOULD
>    appear.

In this paragraph a term "originator of the message" is used for the first
and the only time, and is nowhere defined. Other text only speaks of
"originator fields" (= From, Sender, Reply-To).

Also, the term "transmitter" is used here for the first time too,
and is never defined.



The proper term could be borrowed from the:

> The "Sender:" field specifies the mailbox of the agent responsible
> for the actual transmission of the message.

so
  'originator of the message'
should actually be:
  'mailbox of the agent responsible for the actual
   transmission of the message'
  (although this is unsightly long and repeating the just said)
or just:
  'transmitter' (if it were defined elsewhere)

Looks like a term needs to be invented for the agent specified in
a Sender field, or the text rephrased to avoid the need for a
new term.

  Mark
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.