From: Arash Esbati <arash@gnu.org>
To: rameiko87@posteo.net
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: Sat, 09 Dec 2023 17:57:45 +0100 [thread overview]
Message-ID: <m2edfvz52u.fsf@macmutant.fritz.box> (raw)
In-Reply-To: <8b21e2aa979f8c1944fc0b5ca4be1e5c@posteo.net> (rameiko's message of "Sat, 09 Dec 2023 14:16:09 +0000")
rameiko87@posteo.net writes:
> This is perfect! So I customized message-required-mail-headers. Now
> your explanation shows why I should not remove the mail headers, but
> still I wonder about the meaning of the lines cited above from the
> Gnus manual. And I also wonder what is the meaning of the variable
> message-required-mail-headers if it's essentially ignored by Message
> when I remove the Message-ID header from the list.
I'm not sure if Message is ignoring the value of
`message-required-mail-headers'.
> Anyway now I'm back to the original problem where I don't know what to
> insert for Message-ID because the recommendations from the Gnus manual
> above don't apply, and also I can't understand how Message generates
> the portion which comes before the at-sign...
My guess is that your message-id like this:
Message-ID: <8b21e2aa979f8c1944fc0b5ca4be1e5c@posteo.net>
is generated by your sendmail program. I use msmtp which has an option:
‘set_msgid_header [(auto|off)]’
When to set a Message-ID header: ‘auto’ adds a Message-ID header if
the mail does not have one (this is the default), and ‘off’ never sets
a Message-ID header. Message-IDs have the form ‘hash@domain’, where
‘hash’ is a hash over some values that uniquely identify the mail, and
‘domain’ is either the value of the domain command (unless that is the
default value ‘localhost’), or the domain part of the envelope-from
address (if available), or the host name of the SMTP server.
Maybe you want to check your sendmail program.
Best, Arash
next prev parent reply other threads:[~2023-12-09 17:16 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 [this message]
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
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=m2edfvz52u.fsf@macmutant.fritz.box \
--to=arash@gnu.org \
--cc=info-gnus-english@cafax.se \
--cc=info-gnus-english@gnu.org \
--cc=rameiko87@posteo.net \
/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).