From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS7859 209.68.0.0/18 X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 1360E1FAA8 for ; Tue, 16 May 2017 17:11:05 +0000 (UTC) Received: from orac.inputplus.co.uk (unknown [81.174.175.110]) by relay01.pair.com (Postfix) with ESMTP id DF557D01207 for ; Tue, 16 May 2017 13:11:03 -0400 (EDT) Received: from orac.inputplus.co.uk (orac.inputplus.co.uk [IPv6:::1]) by orac.inputplus.co.uk (Postfix) with ESMTP id 0B89721DF7; Tue, 16 May 2017 18:11:03 +0100 (BST) To: meta@public-inbox.org From: Ralph Corderoy Subject: ssoma_repository.txt on Duplicate Message-IDs. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Date: Tue, 16 May 2017 18:11:03 +0100 Message-Id: <20170516171103.0B89721DF7@orac.inputplus.co.uk> List-Id: Hi, https://ssoma.public-inbox.org/ssoma_repository.txt says Thus the blobs for conflicting Message-IDs will be the SHA-1 hexdigest of the Subject header and raw body (no extra whitespace delimiting the two). PFX=21/4527ce3741f50bb9afa65e7c5003c8a8ddc4b1 $PFX/287d8b67bf8ebdb30e34cb4ca9995dbd465f37aa # first copy $PFX/287d8b67bf8ebdb30e34cb4ca9995dbd465f37ab # second copy $PFX/287d8b67bf8ebdb30e34cb4ca9995dbd465f37ac # third copy So what happens when a second email with the same (message-ID, subject, body) arrives, but different Date, CC, etc? Also, how do the three copies above have near identical digests? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy