From: yarnton@tutanota.com
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: ding@gnus.org
Subject: Re: mail-host-address and i-did-not-set--mail-host-address--so-tickle-me
Date: Sun, 13 Dec 2020 19:10:44 +0100 (CET) [thread overview]
Message-ID: <MOSAiwi--3-2@tutanota.com> (raw)
In-Reply-To: <877dpmab6s.fsf@tullinup.koldfront.dk>
> (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?)
>
Sure, but identifying a message in a unique way does not require leaking unnecessary information about the host. That was my point. The vast majority of the email clients put something pretty non-unique on the right hand side of the Message-ID like @emailservice.com or @localhost.localdomain (literally).
This still respects RFC 2822, as the left hand side of Message-ID is what makes the whole Message-ID likely to be unique.
From: and my IP address can be fairly anonymous, but that is not useful if Message-ID leaks my exact domain. For example, say my localhost gets set to some local domain name that is quite representative of where I am by dhcpd e.g., lab21.bio.dtu.dk. I am inadvertendly leaking more or less who I am.
An additional problem is that message-make-fqdn will concat the string ".i-did-not-set-mail-host-address--so-tickle-me" into Message-ID if it cannot construct a valid Message-ID. Gnus checks the Message-ID before sending, but other Emacs email clients do not. A different way of flagging an error might be more appropriate here.
In other words, I think the logic inside the message-mode function message-make-fqdn is a bit outdated for today's Internet. Furthermore, returning a special value to flag an error is not playing very will with other Emacs email clients aside from Gnus, as these do not check for the presence of "[...]-tickle-me" to flag an error before sending an email, nor show the Message-ID header when composing a message.
next prev parent reply other threads:[~2020-12-13 18:10 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
2020-12-13 3:48 ` 황병희
2020-12-13 18:10 ` yarnton [this message]
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=MOSAiwi--3-2@tutanota.com \
--to=yarnton@tutanota.com \
--cc=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).