GNU bug report logs - #64454
30.0.50; In-Reply-To header obsolete content

Previous Next

Full log

Message #17 received at 64454 <at> debbugs.gnu.org (full text, mbox):

From: Robert Pluim <rpluim <at> gmail.com>
To: Björn Bidar <bjorn.bidar <at> thaodan.de>
Cc: Andrew Cohen <acohen <at> ust.hk>, 64454 <at> debbugs.gnu.org
Subject: Re: bug#64454: 30.0.50; In-Reply-To header obsolete content
Date: Mon, 18 Sep 2023 11:59:25 +0200

>>>>> On Sun, 17 Sep 2023 02:51:00 +0300, Björn Bidar <bjorn.bidar <at> thaodan.de> said:

    Björn> Robert Pluim <rpluim <at> gmail.com> writes:
    >>>>>>> On Tue, 04 Jul 2023 14:11:35 +0800, Andrew Cohen <acohen <at> ust.hk> said:
    >> 
    Andrew> When replying to an email, gnus constructs an In-Reply-To: header that
    Andrew> contains the message-id of the originating email followed by a phrase of
    Andrew> the form:
    >> 
    Andrew> (User's  message of "Wed, 17 Nov 2021 22:16:04 -0800")
    >> 
    Andrew> While allowed, the addition of this parenthetical phrase has been made
    Andrew> obsolete as of RFC5322. I suggest removing it, or wrapping it in a
    Andrew> defcustom 'message-strict-rfc5322. Any preferences?
    >> 
    >> Iʼd remove it, document its removal, but have a defcustom to get it
    >> back.
    >> 
    >> Robert

    Björn> Could it still be relevant when interacting with clients that confirm to
    Björn> that rfc?

I donʼt see how: that RFC makes that phrasing obsolete, so there will
no doubt be a client that at some point interprets the header
strictly, in which you donʼt want to be outputting the old format, so
we should output the new one by default.

Robert
-- 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.