From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Status: No, score=-2.7 required=3.0 tests=AWL,BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_PASS,UNPARSEABLE_RELAY shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 83FCC1F97E for ; Tue, 20 Nov 2018 12:43:05 +0000 (UTC) Received: by mail-wr1-f51.google.com with SMTP id v6so1803426wrr.12 for ; Tue, 20 Nov 2018 04:43:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=28Iq9icpqUYwJacWuwB1BlpxPTIno/If9EKF4Xb2+T8=; b=iGbCNu7ZZlFVDdqTH0KkBQfYRWdlPX9yi9GpAa38+27ry7PwDovrOdcbPP6Zw7tLsh iUgLANVtYkFXLLemGi5HnYRrHF4qo1iISQxgQcBvRrd9EqgqGbX4ydZcjMtn8dUfubQE fgKgdHULQ7qreIEEnRmRPvUGtsTcWPziTiE32cobI/r2wdqPjqSJHX7uj5GgIeKg39Xg jn3GTBngesS6IXh3eX30pa7rvzJrOpVI8SyofJLxr5TpuafyF1gIN0kD0Ouqp+VGWz0c YB0QNFs8xID6vvgwzH0gP+Y5AiEKT2F57Uipr8EK6NF8zQsdK9L0o/O/16cVozddYwDJ mBdw== X-Gm-Message-State: AA+aEWbPo3RsHzvvrJqpas+t3E7/uhgvsL1U5ncRYfHHezh1yDlUNIvA SoL6VYaf1sqjgMkMyfZrilzWQVJh X-Google-Smtp-Source: AFSGD/UL4yrnpiUvHlw/6uZ4ofCNtMSE0eH7tPlrhkAZEeDg5maO4j539yoy9JdYYsv0qic1FkbdFw== X-Received: by 2002:adf:eec9:: with SMTP id a9mr1808080wrp.242.1542717783602; Tue, 20 Nov 2018 04:43:03 -0800 (PST) Received: from juno.home.vuxu.org ([2001:4ca0:0:f233:a288:b4ff:fea1:ce50]) by smtp.gmail.com with ESMTPSA id 4-v6sm25529159wmd.18.2018.11.20.04.43.02 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 20 Nov 2018 04:43:02 -0800 (PST) Received: from localhost (juno.home.vuxu.org [local]) by juno.home.vuxu.org (OpenSMTPD) with ESMTPA id b190f0f7; Tue, 20 Nov 2018 12:43:01 +0000 (UTC) From: Leah Neukirchen To: Eric Wong Cc: =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , meta@public-inbox.org Subject: Re: BUG?: The UI shows an "In-Reply-To" value different than the actual value References: <87tvkczqk8.fsf@evledraar.gmail.com> <20181120074553.72ayiqorwdsvdfoi@dcvr> Date: Tue, 20 Nov 2018 13:43:01 +0100 In-Reply-To: <20181120074553.72ayiqorwdsvdfoi@dcvr> (Eric Wong's message of "Tue, 20 Nov 2018 07:45:53 +0000") Message-ID: <87y39n9ay2.fsf@vuxu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain List-Id: Eric Wong writes: > When I was working on this, I found References: more consistent > and easier-to-parse than In-Reply-To; as the latter could > contain random human-readable phrases. Thus the code favors > using the References header for threading. > > lib/PublicInbox/MID.pm has this, currently: > > # last References should be IRT, but some mail clients do things > # out of order, so trust IRT over References iff IRT exists This is also what jwz recommends (https://www.jwz.org/doc/threading.html): >> I've been informed that recent versions of Eudora violate this >> standard: they put the parent Message-ID in the In-Reply-To header, >> but do not duplicate it in the References header: instead, the >> References header contains the grandparent, great-grand-parent, >> etc. >> This implies that to properly reconstruct the thread of a message >> in the face of this nonstandard behavior, we need to append any >> In-Reply-To message IDs to References. (mthread(1) of mblaze does the same.) -- Leah Neukirchen http://leah.zone