1 Return-Path: <rjhorn@alum.mit.edu>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 61128431FBC
\r
6 for <notmuch@notmuchmail.org>; Thu, 28 Jun 2012 13:41:42 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id LdSsJxv6yQwK for <notmuch@notmuchmail.org>;
\r
16 Thu, 28 Jun 2012 13:41:41 -0700 (PDT)
\r
17 Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
\r
18 by olra.theworths.org (Postfix) with ESMTP id D364B431FB6
\r
19 for <notmuch@notmuchmail.org>; Thu, 28 Jun 2012 13:41:41 -0700 (PDT)
\r
20 Received: from quad.robs.office (panix3.panix.com [166.84.1.3])
\r
21 by mailbackend.panix.com (Postfix) with ESMTP id 5B15F288CD;
\r
22 Thu, 28 Jun 2012 16:41:40 -0400 (EDT)
\r
23 From: Robert Horn <rjhorn@alum.mit.edu>
\r
24 To: David Bremner <david@tethera.net>, Ethan <ethan.glasser.camp@gmail.com>,
\r
25 Mark Walters <markwalters1009@gmail.com>
\r
26 Subject: Re: [RFC PATCH 00/14] modular mail stores based on URIs
\r
27 In-Reply-To: <87hatvlba8.fsf@zancas.localnet>
\r
28 References: <1340656899-5644-1-git-send-email-ethan@betacantrips.com>
\r
29 <877gutnmf1.fsf@qmul.ac.uk>
\r
30 <CAOJ+Ob0Kw0Kkhh9C27Xv9gvqtNowzQiNqrLAtvti7fL8NND2+w@mail.gmail.com>
\r
31 <87hatvlba8.fsf@zancas.localnet>
\r
32 User-Agent: Notmuch/0.13 (http://notmuchmail.org) Emacs/23.3.1
\r
33 (x86_64-suse-linux-gnu)
\r
34 Date: Thu, 28 Jun 2012 16:41:40 -0400
\r
35 Message-ID: <m3r4szmanv.fsf@quad.robs.office>
\r
37 Content-Type: text/plain; charset=us-ascii
\r
38 Cc: notmuch@notmuchmail.org
\r
39 X-BeenThere: notmuch@notmuchmail.org
\r
40 X-Mailman-Version: 2.1.13
\r
42 List-Id: "Use and development of the notmuch mail system."
\r
43 <notmuch.notmuchmail.org>
\r
44 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
45 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
46 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
47 List-Post: <mailto:notmuch@notmuchmail.org>
\r
48 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
49 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
51 X-List-Received-Date: Thu, 28 Jun 2012 20:41:42 -0000
\r
53 David Bremner <david@tethera.net> writes:
\r
55 > Ethan <ethan.glasser.camp@gmail.com> writes:
\r
57 >> Yeah, I don't even know how an mbox message gets flagged read and I don't
\r
58 >> know how I would support it.
\r
61 > I think read only access to mboxes is fine. Yes, somebody will be
\r
62 > unhappy, but the only convincing argument I have heard for mboxes or
\r
63 > similar formats is archival use.
\r
66 That would also deal with the potential that edits shuffle the mbox
\r
67 structure, breaking all references except those that use the message-ID
\r
68 as a search string. Alternatively, the URI form will need to use
\r
69 message-ID to avoid breakage when an mbox change includes garbage
\r
70 collection or relocation of email messages within the mbox file.
\r