From: yarnton@tutanota.com
To: ding@lists.math.uh.edu
Subject: mail-host-address and i-did-not-set--mail-host-address--so-tickle-me
Date: Sat, 12 Dec 2020 23:29:01 +0100 (CET) [thread overview]
Message-ID: <MOO3Zqd--3-2@tutanota.com> (raw)
Hi,
As far as I understand, the function message-make-fqdn in gnus/message.el concats the string "i-did-not-set--mail-host-address--so-tickle-me" to system-name if that is not a fully qualified domain name. This is used to construct a unique Message-ID.
To be a bit more precise, it also checks the values of user-mail-address and mail-host-address before defaulting to string with the "tickle-me" substring.
I used to use Gnus, but my MUA these days is Notmuch. Notmuch and other packages use message.el, and I am trying to understand why I need to set up mail-host-address to something arbitrary (I use "gnu.org") in order to avoid the "tickle-me" string.
Is this a bug from Notmuch when calling message.el, some ancient setting from Gnus that doesn't play well with other packages, or something I'm doing wrong? 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.
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. 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. Is there any technical reason for not constructing a random Message-ID like [UUID]@gnu.org?
Thanks.
next reply other threads:[~2020-12-12 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 22:29 yarnton [this message]
2020-12-12 22:53 ` Adam Sjøgren
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=MOO3Zqd--3-2@tutanota.com \
--to=yarnton@tutanota.com \
--cc=ding@lists.math.uh.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).