From: Ralph Corderoy <ralph@inputplus.co.uk>
To: meta@public-inbox.org
Subject: ssoma_repository.txt on Duplicate Message-IDs.
Date: Tue, 16 May 2017 18:11:03 +0100 [thread overview]
Message-ID: <20170516171103.0B89721DF7@orac.inputplus.co.uk> (raw)
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
next reply other threads:[~2017-05-16 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 17:11 Ralph Corderoy [this message]
2017-05-16 17:31 ` ssoma_repository.txt on Duplicate Message-IDs Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170516171103.0B89721DF7@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).