From: morioka@jaist.ac.jp (守岡 知彦 / MORIOKA Tomohiko)
Subject: Re: [Gnus 5.2.14] message-make-sender
Date: 11 Jun 1996 01:06:11 +0900 [thread overview]
Message-ID: <s1civczsky4.fsf@jaist.ac.jp> (raw)
In-Reply-To: Richard Pieri's message of 10 Jun 1996 10:14:23 -0400
>>>>> In <x7g283u4ow.fsf@unilab.dfci.harvard.edu>
>>>>> Richard Pieri <ratinox@unilab.dfci.harvard.edu> wrote:
Richard> >>>>> "aj" == =?ISO-2022-JP?Q?=1B$B<morioka@jaist ac jp
Richard> >>>>> <morioka@jaist.ac.jp> writes:
aj> Sender field must include a mail reachable real address.
Richard> Nope. From RFC822:
(snip)
Richard> [For instance, a mailing list manager will set the Sender:
Richard> field because it is responsible for sending messages but it
Richard> does not originate messages. --Rat]
(snip)
Richard> The Sender mailbox specification includes a word
Richard> sequence which must correspond to a specific agent
Richard> (i.e., a human user or a computer program) rather
Richard> than a standard address. This indicates the
Richard> expectation that the field will identify the single
Richard> agent (person, system, or process) responsible for
Richard> sending the mail and not simply include the name of a
Richard> mailbox from which the mail was sent. For example in
Richard> the case of a shared login name, the name, by itself,
Richard> would not be adequate. The local-part address unit,
Richard> which refers to this agent, is expected to be a
Richard> computer system term, and not (for example) a
Richard> generalized person reference which can be used
Richard> outside the network text message context.
Richard> [In fact, not only does Sender: not need to contain a valid
Richard> Internet mail address, it generally should not contain
Richard> one. --Rat]
Thanks for your kind answer. Please confirm again.
In my Emacs, (system-name) returns "is28e1s91", so message.el adds
Sender: morioka@is28e1s91
Of course, it is not valid mail address. I think Sender field is to
identify the agent responsible for sending message, and it seems not
enough to identify the agent.
By the way, (system-name) should return FQDM?
Richard> No, that is the Reply-To: header.
My from field is valid, so I does have such kind of problem.
My question is
Sender: morioka@is28e1s91
is valid or not.
Thanks,
--
----------------------------------------------------------------------
Morioka Tomohiko <morioka@jaist.ac.jp>
(`Morioka' is my family name, `Tomohiko' is my personal name.)
---------------- I protest continuation of Chinese nuclear testing.---
next prev parent reply other threads:[~1996-06-10 16:06 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
1996-06-10 16:06 ` 守岡 知彦 / MORIOKA Tomohiko [this message]
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=s1civczsky4.fsf@jaist.ac.jp \
--to=morioka@jaist.ac.jp \
/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).