From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Subject: Re: [Gnus 5.2.14] message-make-sender
Date: 10 Jun 1996 10:14:23 -0400 [thread overview]
Message-ID: <x7g283u4ow.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: morioka@jaist.ac.jp's message of 10 Jun 1996 20:18:52 +0900
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "aj" == =?ISO-2022-JP?Q?=1B$B<morioka@jaist ac jp
>>>>> <morioka@jaist.ac.jp> writes:
aj> Sender field must include a mail reachable real address.
Nope. From RFC822:
authentic = "From" ":" mailbox ; Single author
/ ( "Sender" ":" mailbox ; Actual submittor
"From" ":" 1#mailbox) ; Multiple authors
; or not sender
[...]
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. If the contents of the "Sender" field would
be completely redundant with the "From" field, then the
"Sender" field need not be present and its use is discouraged
(though still legal). In particular, the "Sender" field must
be present if it is not the same as the "From" Field.
[For instance, a mailing list manager will set the Sender: field because
it is responsible for sending messages but it does not originate
messages. --Rat]
The Sender mailbox specification includes a word sequence
which must correspond to a specific agent (i.e., a human user
or a computer program) rather than a standard address. This
indicates the expectation that the field will identify the
single agent (person, system, or process) responsible for
sending the mail and not simply include the name of a mailbox
from which the mail was sent. For example in the case of a
shared login name, the name, by itself, would not be adequate.
The local-part address unit, which refers to this agent, is
expected to be a computer system term, and not (for example) a
generalized person reference which can be used outside the
network text message context.
[In fact, not only does Sender: not need to contain a valid Internet
mail address, it generally should not contain one. --Rat]
Since the critical function served by the "Sender" field is
identification of the agent responsible for sending mail and
since computer programs cannot be held accountable for their
behavior, it is strongly recommended that when a computer pro-
gram generates a message, the human who is responsible for
that program be referenced as part of the "Sender" field mail-
box specification.
[Back to mailing lists, Majordomo sets Sender: to the list owner's
address. --Rat]
aj> It is used when mailbox of From field is not senders real address or
aj> it contains multiple mailboxes.
No, that is the Reply-To: header.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
iQCVAwUBMbwtwJ6VRH7BJMxHAQErjgP/Uz0KqL5jqg0r5eTeoCGZiPtc3pQ+rqV+
Quo3Uxbh6HAEhY3eRHe2BWIXUR9Y2IQjLJh/KML9hctxfwofYyyEKXu4pI4SEEBI
kbp1crqzXgB9Nrxie8sjqovG+15PaFXmZSnCwT71y8DkxINqC2D8hzqvLozmDZyi
VA0bQMjNLyI=
=JpK1
-----END PGP SIGNATURE-----
--
Richard Pieri/Information Services \ When in doubt, cop an attitude. -A cat's
<ratinox@unilab.dfci.harvard.edu> \ guide to life
http://www.dfci.harvard.edu/ \
next prev parent reply other threads:[~1996-06-10 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-10 7:04 =?ISO-2022-JP?Q?=1B$B<morioka@jaist.ac.jp
1996-06-10 9:26 ` Per Abrahamsen
1996-06-10 11:18 ` =?ISO-2022-JP?Q?=1B$B<morioka@jaist.ac.jp
1996-06-10 12:59 ` Per Abrahamsen
1996-06-10 14:14 ` Richard Pieri [this message]
1996-06-10 16:06 ` 守岡 知彦 / MORIOKA Tomohiko
1996-06-10 17:27 ` Richard Pieri
1996-06-11 8:31 ` 守岡 知彦 / MORIOKA Tomohiko
1996-06-11 18:24 ` Lars Magne Ingebrigtsen
1996-06-11 0:40 ` Sudish Joseph
1996-06-11 14:09 ` Richard Pieri
1996-06-11 23:57 ` Sudish Joseph
1996-06-10 14:04 ` Richard Pieri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x7g283u4ow.fsf@unilab.dfci.harvard.edu \
--to=ratinox@unilab.dfci.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).