From: rameiko87@posteo.net
To: Arash Esbati <arash@gnu.org>
Cc: Lars-Johan Liman <info-gnus-english@cafax.se>, 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:23:55 +0000 [thread overview]
Message-ID: <1b09a2ca927d9fc7150fde2032b53d86@posteo.net> (raw)
In-Reply-To: <m2edft5jrk.fsf@macmutant.fritz.box>
>> Well, how else do you explain that when I remove Message-ID from
>> message-required-mail-headers and send my email, then the Message-ID
>> is given by the value of message-user-fqdn or when nil, by
>> system-name?
>
> As I already said: My guess was that your sendmail program adds a
> message-id.
But then why does such Message-ID always reflect the value of
message-user-fqdn ? If it really were sendmail adding it and not
Message, then why would sendmail set the value of the Message-ID header
according to the value of the variable message-user-fqdn? I think that
sendmail doesn't even know about the message-user-fqdn variable.
> You can set `message-generate-headers-first' to t and see what headers
> Message produces when you start editing a message.
Good suggestion: I just tried. Now message-generate-headers-first is
true, and Message-ID doesn't appear in the
message-required-mail-headers. Result: my emails all have Message-ID
header, and it always reflects the value of message-user-fqdn!
The mystery persists.
next prev parent reply other threads:[~2023-12-11 21:27 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 [this message]
2023-12-11 21:31 ` rameiko87
2023-12-10 11:05 ` Lars-Johan Liman
2023-12-11 21:07 ` rameiko87
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=1b09a2ca927d9fc7150fde2032b53d86@posteo.net \
--to=rameiko87@posteo.net \
--cc=arash@gnu.org \
--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).