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=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7270 invoked from network); 26 Dec 2020 19:31:45 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 26 Dec 2020 19:31:45 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1ktFHz-000pof-Io for ml@inbox.vuxu.org; Sat, 26 Dec 2020 13:31:43 -0600 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.94) (envelope-from ) id 1ktFHy-002HDU-Uw for ml@inbox.vuxu.org; Sat, 26 Dec 2020 13:31:42 -0600 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1ktFHw-002HDM-Sh for ding@lists.math.uh.edu; Sat, 26 Dec 2020 13:31:40 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1ktFHN-000poQ-Kq for ding@lists.math.uh.edu; Sat, 26 Dec 2020 13:31:40 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References :Message-ID:Date:Subject:From:To:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=4uW8ycrxvIryLPIfQLMzr24Rk3xorCbzhwT955w6680=; b=MR8+ynopm9vLqPR7Vc6D3my4qu V/XUKtP7CZCSXoXHneFA2Op8th8BRFPXZ3gUWBq5TQIzltPiDtw4Up1Lr66n0k0+gOF9xfr5h0I9K YeRSg4ANUlALMZijyTMXW5ScKC5Z3XozQzNqhZNhXlfn0YbG4AE5ZuIMiPcIBdr6mKm4=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ktFHF-0007eu-Va for ding@gnus.org; Sat, 26 Dec 2020 20:31:01 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1ktFHE-000627-44 for ding@gnus.org; Sat, 26 Dec 2020 20:30:56 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: Totally unrelated message shown in thread, sometimes Date: Sat, 26 Dec 2020 11:30:51 -0800 Message-ID: <871rfcuzys.fsf@ericabrahamsen.net> References: <877dq97pws.fsf@tullinup.koldfront.dk> <87r1ohtlfn.fsf@ericabrahamsen.net> <87eekh5olr.fsf@tullinup.koldfront.dk> <87d001nenj.fsf@ust.hk> <87k0u8zdv8.fsf@tullinup.koldfront.dk> <87pn3zkfos.fsf@ucl.ac.uk> <87wnx5jvzc.fsf@tullinup.koldfront.dk> <87o8ihun76.fsf@ericabrahamsen.net> <87czyw1wej.fsf@tullinup.koldfront.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cancel-Lock: sha1:45M500CiRmucijqNl7rhMlL6NFQ= List-ID: Precedence: bulk Adam Sjøgren writes: > Eric writes: > >> Does this only ever happen with delayed articles, or with other draft >> articles, too? > > Now that you ask, I can only ever remember seeing my long-lived delayed > article being mixed in. > > (I guess that points the suspicion towards the gnus-delay-send-queue > demon-handler.) > >> Was drafting and delaying the outgoing article the last thing you did >> before opening this group and seeing the fubar'ed headers? Or had you >> delayed it a while ago? > > It is an old delayed article that I hadn't touched recently - it was > last edited on October 4, 2020, and it's set to send on July 14, 2021. > >> And did you see the doubled headers on only one message in this group, >> or for every message? > > Only in the one specific message shown on the screenshot. > > > Eric writes: > >> I guess what I'm getting at with that last question is: is there any >> chance that the article number of the delayed message in the delayed >> group was the same as the article number of the article with doubled >> headers in the feedbase group? > > I suspected that too, but the delayed article is ~/News/drafts/delayed/2 > while the article from f.b.risks has this Xref header: > > Xref: feedbase.org feedbase.blog.risks:6131 Okay, thanks for all data points! > Anyway, given how rarely it happens and that it seems network > instability is "needed", I guess it isn't worth too much time to chase > down. The bug itself isn't too bad, but understanding why it's happening might lead to fixes for other stuff.