From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 6125 invoked from network); 9 Dec 2023 14:16:40 -0000 Received: from lists.gnu.org (209.51.188.17) by inbox.vuxu.org with ESMTPUTF8; 9 Dec 2023 14:16:40 -0000 Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rBy7y-0000rd-DL; Sat, 09 Dec 2023 09:16:22 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rBy7r-0000p0-BF for info-gnus-english@gnu.org; Sat, 09 Dec 2023 09:16:18 -0500 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rBy7o-0008Dj-LT for info-gnus-english@gnu.org; Sat, 09 Dec 2023 09:16:15 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id ADC03240101 for ; Sat, 9 Dec 2023 15:16:10 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1702131370; bh=MlrFD2RCfvet3gG3UrwF90gpRlL7Zot0G5FcG+UWwkM=; h=MIME-Version:Content-Transfer-Encoding:Date:From:To:Cc:Subject: Message-ID:From; b=dwe3rENOu4fzrUORdHXgMREHfyBfHl3NDvv08gRjHA5ySVToPZNJ/ZTvL9NTNk2iJ gNUJ50beKAV+9QQbKet56mapAI/I1MAtF6yK9gDkocwd8TPpEOOnqpWIicpW2+m2C0 aAOT+Md6p4zBMpiklUP8jeF+GeqQFZ4DH2snPRs+5QaeRXQ/uluxOr0KsgB9bTNQiM jqxAkmBKSWHmAfk99GMYYiRvPmqofAL2muneyQ0OjQZ0ZLiDOOhocvGT50bRcRk5Cl 0Oakm67MWOTuIkHeJIF8BSqmpl21mp+2z5D9A25yD3qE9DydXB4MuZf2VcLm3tDmV+ OwHiwEj+iBqWg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4SnVRZ1hcGz6tyR; Sat, 9 Dec 2023 15:16:09 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Date: Sat, 09 Dec 2023 14:16:09 +0000 From: rameiko87@posteo.net To: Lars-Johan Liman Cc: info-gnus-english@gnu.org Subject: Re: Have message-ID set by my email server rather than by Message In-Reply-To: <22jzpnyi1c.fsf@floptop.liman.net> References: <02faa3f8a25dc94c6e745ba7e119711a@posteo.net> <22jzpnyi1c.fsf@floptop.liman.net> Message-ID: <8b21e2aa979f8c1944fc0b5ca4be1e5c@posteo.net> Received-SPF: pass client-ip=185.67.36.66; envelope-from=rameiko87@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: info-gnus-english-bounces+ml=inbox.vuxu.org@gnu.org Sender: info-gnus-english-bounces+ml=inbox.vuxu.org@gnu.org Dear Lars-Johan Liman, Thank you very much for your kind and exhaustive reply. I read in the=20 Gnus manual: > If you have no idea what to insert for "yourmachine.yourdomain.tld",=20 > you=E2=80=99ve got several choices. You can either ask your provider if h= e=20 > allows you to use something like yourUserName.userfqdn.provider.net, or= =20 > you can use somethingUnique.yourdomain.tld if you own the domain=20 > yourdomain.tld, or you can register at a service which gives private=20 > users a FQDN for free. None of these apply to me. Then I read just below: > Finally you can tell Gnus not to generate a Message-ID for News at all=20 > (and letting the server do the job) [...] you can also tell Gnus not to= =20 > generate Message-IDs for mail by saying: >=20 > //there's some code here// >=20 > , however some mail servers don=E2=80=99t generate proper Message-IDs, to= o, so=20 > test if your Mail Server behaves correctly by sending yourself a Mail=20 > and looking at the Message-ID. This is perfect! So I customized message-required-mail-headers. Now your=20 explanation shows why I should not remove the mail headers, but still I=20 wonder about the meaning of the lines cited above from the Gnus manual.=20 And I also wonder what is the meaning of the variable=20 message-required-mail-headers if it's essentially ignored by Message=20 when I remove the Message-ID header from the list. Anyway now I'm back to the original problem where I don't know what to=20 insert for Message-ID because the recommendations from the Gnus manual=20 above don't apply, and also I can't understand how Message generates the=20 portion which comes before the at-sign... And by the way, the standard for me would be=20 fedora.mail-host-address-is-not-set . Is this even a fully qualified=20 domain name, without extension? And how would I set mail host address?=20 Because I can only find the variable mail-host-address which is set to=20 system-name, which is fedora. Therefore I would expect the Message-ID to=20 be fsfxxxxxxx@fedora (which by the way I think would miss the extension). If I set=20 mail-host-address manually to fedora.ext, would Message-ID then be=20 fsfxxxxxxx@fedora.ext? Then why don't they say=20 mail-host-extension-is-not-set rather than mail-host-address-is-not-set=20 in the default Message-ID when the mail-host-address *is* set but has no=20 extension? So much confusion. On 09.12.2023 08:03, Lars-Johan Liman wrote: > Hi! >=20 > Message-ID is one of the very few _mandatory_ header lines, so a=20 > message > without one is not a valid RFC 5322 (the sucessor of RFC 822) message. > Therefore the message "must not/cannot" leave your computer without=20 > one. > It has to be set on the computer if it's being shipped by a=20 > mail-related > protocol ((E)SMTP/LMTP/IMAP/POP[23]/...). >=20 > What you _can_ do (if I remember my sendmail.cf right, it's been a few > years since I taught that course ... ;-) ) is to _modify_ the=20 > Message-ID > header in your mail server. "If it looks like it's coming from the > computer, then modify Message-ID to look like ... (bla)". But I=20 > wouldn't > recommend it. Message-ID is supposed to be set by the sending software > (the Mail User Agent (MUA)) and it's supposed to uniquely identify the > message across all messages in the world ... ever. Modifying it would > make it very difficult to trace and debug how the message traverses the > Internet (which includes your computer). You can probably also=20 > influence > exactly how Emacs generates the Message-ID, but again, it's probably=20 > not > a good idea to mess with that. >=20 > Can I ask what problem you see with having your Emacs generate the > Message-ID? >=20 > Best regards, > /Lars-Johan Liman