2 <return-y6xfje9utikfmhtxvrchdsbzc6@temporary-address.scs.stanford.edu>
\r
3 X-Original-To: notmuch@notmuchmail.org
\r
4 Delivered-To: notmuch@notmuchmail.org
\r
5 Received: from localhost (localhost [127.0.0.1])
\r
6 by arlo.cworth.org (Postfix) with ESMTP id 8ED756DE021E
\r
7 for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 03:15:55 -0700 (PDT)
\r
8 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
10 X-Spam-Score: -1.792
\r
12 X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[AWL=0.315,
\r
13 RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001,
\r
14 URIBL_SBL=0.644, URIBL_SBL_A=0.1] autolearn=disabled
\r
15 Received: from arlo.cworth.org ([127.0.0.1])
\r
16 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
17 with ESMTP id WDuFymkohWjD for <notmuch@notmuchmail.org>;
\r
18 Sun, 16 Aug 2015 03:15:53 -0700 (PDT)
\r
19 X-Greylist: delayed 1397 seconds by postgrey-1.35 at arlo;
\r
20 Sun, 16 Aug 2015 03:15:53 PDT
\r
21 Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10])
\r
22 by arlo.cworth.org (Postfix) with ESMTPS id 8FD706DE009A
\r
23 for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 03:15:53 -0700 (PDT)
\r
24 Received: from market.scs.stanford.edu (localhost.scs.stanford.edu
\r
25 [127.0.0.1]) by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id
\r
26 t7G9qap6026130; Sun, 16 Aug 2015 02:52:36 -0700 (PDT)
\r
27 Received: (from dm@localhost)
\r
28 by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id t7G9qaPb025981;
\r
29 Sun, 16 Aug 2015 02:52:36 -0700 (PDT)
\r
30 X-Authentication-Warning: market.scs.stanford.edu: dm set sender to
\r
31 return-y6xfje9utikfmhtxvrchdsbzc6@ta.scs.stanford.edu using -f
\r
32 From: David Mazieres <dm-list-email-notmuch@scs.stanford.edu>
\r
33 To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
\r
34 Subject: Re: Enabling and disabling maildir.synchronize_flags
\r
35 In-Reply-To: <87r3n3fu7d.fsf@maritornes.cs.unb.ca>
\r
36 References: <87r3orbqfn.fsf@ta.scs.stanford.edu>
\r
37 <87r3n3fu7d.fsf@maritornes.cs.unb.ca>
\r
38 Date: Sun, 16 Aug 2015 02:52:35 -0700
\r
39 Message-ID: <874mjzblwc.fsf@ta.scs.stanford.edu>
\r
41 Content-Type: text/plain
\r
42 X-BeenThere: notmuch@notmuchmail.org
\r
43 X-Mailman-Version: 2.1.18
\r
45 List-Id: "Use and development of the notmuch mail system."
\r
46 <notmuch.notmuchmail.org>
\r
47 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
48 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
49 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
50 List-Post: <mailto:notmuch@notmuchmail.org>
\r
51 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
52 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
54 X-List-Received-Date: Sun, 16 Aug 2015 10:15:55 -0000
\r
56 David Bremner <david@tethera.net> writes:
\r
58 > dm-list-email-notmuch@scs.stanford.edu writes:
\r
60 >> It seems that disabling it should simply be safe. But re-enabling, one
\r
61 >> risks losing tags, as the next notmuch new will cause old maildir flags
\r
62 >> to override the xapian database. So that suggests something like:
\r
64 >> notmuch dump > backup
\r
65 >> notmuch config set maildir.synchronize_flags false
\r
66 >> # Do I need to run notmuch new here?
\r
67 >> notmuch restore < backup
\r
71 > Sorry about the long delay. I'm not sure I follow the connection between
\r
72 > your paragraph above and the the example. The example seems safe, but as
\r
73 > you say, disabling synching should bs safe anyway.
\r
75 It's not an example, it's kind of a worst case scenario if there's no
\r
76 easy and safe way way to enable synchronize_flags. I want to try
\r
77 disabling flags, but if I change my mind and the only way to get it back
\r
78 is to do a full notmuch dump/restore, that's a pretty hefty penalty.
\r
79 Also, even if I do a full notmuch dump / restore, I'm not sure if the
\r
80 notmuch new is necessary in the middle.
\r
82 So my question remains, what's the easiest safe way to re-enable
\r
83 synchronize_flags after disabling it? (Safe meaning it won't change any
\r
84 tags.) It could be that there's a very simple answer, in which case
\r
85 sticking it in the man page might be nice.
\r