Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Lars-Johan Liman <info-gnus-english@cafax.se>
To: rameiko87@posteo.net
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 10:01:45 +0100	[thread overview]
Message-ID: <22o7exnmdi.fsf@floptop.liman.net> (raw)
In-Reply-To: <m2edft5jrk.fsf@macmutant.fritz.box> (Arash Esbati's message of "Mon, 11 Dec 2023 07:35:27 +0100")

FWIW, I agree with Arash's sentiment. This, again, goes back to the
notion that a message without a Message-ID is (more or less) invalid.
Therefore any and all e-mail software (user agents and transport agents
alike) is disciplined to add a Message-ID to any message without one, to
avoid transferring invalid messages.

It boils down to Postel's principle: "Be liberal in what you accept, and
consevative in what you send!". ;-)

				Cheers,
				  /Liman


rameiko87@posteo.net writes:
>> 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?

arash@gnu.org 2023-12-11 07:35 [+0100]:
> As I already said: My guess was that your sendmail program adds a
> message-id.  You can set `message-generate-headers-first' to t and see
> what headers Message produces when you start editing a message, maybe
> that gives you a clue.  Besides that, I have no other idea.

> Best, Arash




  reply	other threads:[~2023-12-11  9:02 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 [this message]
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=22o7exnmdi.fsf@floptop.liman.net \
    --to=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).