From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>, meta@public-inbox.org
Subject: Re: [v2] introduction of content_id
Date: Fri, 9 Feb 2018 14:40:59 -0500 [thread overview]
Message-ID: <5d025ad2-9824-876d-09d1-3302886579a8@linuxfoundation.org> (raw)
In-Reply-To: <20180209181718.GA8847@dcvr>
[-- Attachment #1.1: Type: text/plain, Size: 1966 bytes --]
On 02/09/18 13:17, Eric Wong wrote:
> In addition to the git object_id (blob SHA-1) and Message-Id
> header; it seems necessary to introduce an in-between identifier
> for deduplicating which isn't as loose as Message-Id or as
> strict as object_id: content_id
>
> I think a hash of the following raw headers + raw body will
> suffice:
>
> Subject, From, Date, Message-Id, References, To, Cc,
> In-Reply-To, MIME-Version, Content-Type,
> Content-Disposition, Content-Transfer-Encoding
That's similar to what ARC/DKIM do. E.g. in my mailbox the message has
the following headers sealed:
h=archived-at:list-post:list-owner:list-subscribe:list-unsubscribe
:list-help:list-archive:precedence:list-id:content-disposition
:mime-version:message-id:subject:to:from:date
:arc-authentication-results;
If we trim the arc- and list-specific headers, that's:
precedence
content-disposition
mime-version
message-id
subject
to
from
date
I'm not sure we should care about content-transfer-encoding, because
that can be mangled by intermediate MTAs (at least that used to happen
all the time in the past -- not sure if it's still the case).
> List-Id, X-Mailing-List should be left out so different
> readers/lists can share spam removals in cross posts.
Note, that mailing lists that modify the Subject header (e.g. to add
[mailinglist] identifier) will also be impacted similarly.
> (*) I noticed the first Received: header (last hop) is missing
> from the cregit sources; but the first remaining Received:
> header also includes the identity of the recipient in more
> recent mails...
I specifically sanitized all Received: headers that didn't say "by
vger.kernel.org" because these are donated by individual users and I
didn't want to expose their potentially private info.
Best,
--
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-02-09 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 18:17 [v2] introduction of content_id Eric Wong
2018-02-09 19:40 ` Konstantin Ryabitsev [this message]
2018-02-09 20:11 ` Eric Wong
2018-02-22 21:12 ` 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=5d025ad2-9824-876d-09d1-3302886579a8@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).