From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Subject: Re: [Gnus 5.2.14] message-make-sender
Date: 10 Jun 1996 13:27:27 -0400 [thread overview]
Message-ID: <x7wx1flgcg.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: morioka@jaist.ac.jp's message of 11 Jun 1996 01:06:11 +0900
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "MT" == =?ISO-2022-JP?B?GyRCPGkyLBsoQiAbJEJDTkknGyhC?= / MORIOKA
>>>>> Tomohiko <morioka@jaist.ac.jp> writes:
MT> Thanks for your kind answer. Please confirm again.
MT> In my Emacs, (system-name) returns "is28e1s91", so message.el adds
MT> Sender: morioka@is28e1s91
MT> Of course, it is not valid mail address.
Actually, it is a valid local mailbox, which is what matters, in this
instance.
MT> I think Sender field is to identify the agent responsible for
MT> sending message, and it seems not enough to identify the agent.
'morioka@is28e1s91' certainly does identify you well enough for anyone
on is28e1s91, which is what matters.
MT> By the way, (system-name) should return FQDM?
That is FQDN, fully qualified domain name. And no, system-name returns
the name of the machine you are running on. Not all machines are
connected to the Internet, thus not all machines will have a fully
qualified domain name. To force system-name to return a meaningless
value is... meaningless.
Richard> No, that is the Reply-To: header.
MT> My from field is valid, so I does have such kind of problem.
But what you described is the Reply-To: header, which must be a valid
Internet address, and is used when replies are to be directed to someone
other than the originator (From:) of a message.
MT> My question is
MT> Sender: morioka@is28e1s91
MT> is valid or not.
According to RFC822, which defines the use of the Sender: header, this
is a valid Sender: header.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
iQCVAwUBMbxbDJ6VRH7BJMxHAQEeqwQAlzZpTkOdDLSwpsKaPv+uxx221CEgNP3/
J1U7xkJluD9dU+kEtnry4ZQIx1eSz9VY0zfUThKGUf1nDHoY04t8291/Mb6nvXDo
2OAxNNzFSgsafK4psM4NC0jXe5wnf4oy+mgHIBqHTyMPPY6ILh6JZ2WlWgxmGtYs
lqjymaoH3Ko=
=V5cv
-----END PGP SIGNATURE-----
--
Richard Pieri/Information Services \ Always give generously - a small bird or
<ratinox@unilab.dfci.harvard.edu> \ rodent left on the bed tells them, "I
http://www.dfci.harvard.edu/ \ care". -A cat's guide to life
next prev parent reply other threads:[~1996-06-10 17:27 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
1996-06-10 17:27 ` Richard Pieri [this message]
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=x7wx1flgcg.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).