From: rameiko87@posteo.net
To: Lars-Johan Liman <info-gnus-english@cafax.se>
Cc: info-gnus-english@gnu.org
Subject: Re: Have message-ID set by my email server rather than by Message
Date: Mon, 11 Dec 2023 21:07:36 +0000 [thread overview]
Message-ID: <f3f46d154d7bac59ae429479db8eaa46@posteo.net> (raw)
In-Reply-To: <22edfuwc5r.fsf@floptop.liman.net>
Dear Liman,
> Am I right in understanding it as "my host doesn't know its own
> hostname (identity), so it's unable to create a useful Message-ID"?
Not sure, because my original problem was that Emacs or one of the
components which intervene *locally* generate and introduce the
Message-ID no matter the value of message-required-mail-headers. This is
still unresolved. The underlying intellectual conundrum I think you
summarize well:
> "Which entity (i.e., which device) should be responsible for adding the
> Message-ID header to a message composed on a device which has little or
> no notion of its own host identity, and in those cases what should the
> Message-ID be?"
My device composes the message before posteo.de transmits it. What is my
authority to use the formula xxxx@posteo.de in the Message-ID,
especially because the mix of self-generated xxxx and official-looking
@posteo.de looks intellectually confusing. Think of physical post: the
post office will stamp the branch number and timestamp the envelope when
they accept my parcel. posteo.de are charged with transmitting my email:
it only sounds reasonable they would add the Message-ID, which is
essentially hostname plus timestamp. Now one could make the case for the
added freedom which comes with deciding the Message-ID of your own
emails: but if the host can overwrite this anyway, then the benefit of
the potential added privacy which comes from setting Message-ID at the
MUA level is not guaranteed, but the drawback of having possibly same
Message-ID's for different emails (sent through the same host or even
distinct hosts) is real.
> I happen to know the author of the mail specification RFC, and I'm
> thinking about asking him for his thoughts. Would you object to that?
I don't object.
next prev parent reply other threads:[~2023-12-11 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 18:44 rameiko87
2023-12-09 7:03 ` Lars-Johan Liman
2023-12-09 14:16 ` rameiko87
2023-12-09 16:57 ` Arash Esbati
2023-12-09 20:21 ` rameiko87
2023-12-09 21:30 ` Bob Newell
2023-12-11 6:35 ` Arash Esbati
2023-12-11 9:01 ` Lars-Johan Liman
2023-12-11 14:42 ` Otto J. Makela
2023-12-11 21:23 ` rameiko87
2023-12-11 21:31 ` rameiko87
2023-12-10 11:05 ` Lars-Johan Liman
2023-12-11 21:07 ` rameiko87 [this message]
2023-12-11 21:22 ` Adam Sjøgren
2023-12-11 22:25 ` rameiko87
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=f3f46d154d7bac59ae429479db8eaa46@posteo.net \
--to=rameiko87@posteo.net \
--cc=info-gnus-english@cafax.se \
--cc=info-gnus-english@gnu.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).