From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: mail-host-address and i-did-not-set--mail-host-address--so-tickle-me
Date: Sat, 12 Dec 2020 23:53:15 +0100 [thread overview]
Message-ID: <877dpmab6s.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <MOO3Zqd--3-2@tutanota.com>
yarnton@tutanota.com writes:
> In principle, I don't see why I need to set my email parameters in my
> .emacs. Those are a concern of Notmuch and MSTMP only.
If Emacs is generating the Message-ID, I'd say Emacs needs enough
information to do so - the recommended way is to put the host after the @.
You could argue that the recommendation is outdated.
> I think Message-ID should reveal as little information as possible
> these days, as it can be used for identifying or at least
> fingerprinting messages.
(The whole purpose of the Message-ID is to uniquely identify the
message! I guess you mean identifying... the sender? But that's also
done in From:, right? If you are thinking of identifying the machine
sending, then that is recorded in the Received headers as well, right?)
> Whenever I use Emacs from a device where the hostname returns a fully
> qualified name like an IP address, that will leak into my Message-ID.
(It is usually also recorded in the headers the MTAs add.)
> Is there any technical reason for not constructing a random Message-ID
> like [UUID]@gnu.org?
Not except for what RFC 2822 recommends:
· https://tools.ietf.org/html/rfc2822#section-3.6.4
At least according to the logic in the RFC, you should put something you
control on the right side of the @, and not somebody else's host/domain
- but as long as the whole thing is unique, you should be good.
Best regards,
Adam
--
"I could't find my perfect attendance pencil, which Adam Sjøgren
is the only pencil I turned in [for sharpening]" asjo@koldfront.dk
next prev parent reply other threads:[~2020-12-12 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 22:29 yarnton
2020-12-12 22:53 ` Adam Sjøgren [this message]
2020-12-13 3:48 ` 황병희
2020-12-13 18:10 ` yarnton
2020-12-13 21:28 ` Adam Sjøgren
2020-12-14 11:14 ` 황병희
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=877dpmab6s.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
/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).