Re: Enabling and disabling maildir.synchronize_flags

diff --git a/73/fd9c444aa5d8edb46a80f6d6e00238e181c49a b/73/fd9c444aa5d8edb46a80f6d6e00238e181c49a
new file mode 100644 (file)
index 0000000..ad9aa69
--- /dev/null
+++ b/73/fd9c444aa5d8edb46a80f6d6e00238e181c49a
@@ -0,0 +1,88 @@
+Return-Path:\r
+ <return-y6xfje9utikfmhtxvrchdsbzc6@temporary-address.scs.stanford.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 8ED756DE021E\r
+ for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 03:15:55 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.792\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[AWL=0.315,\r
+  RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001,\r
+  URIBL_SBL=0.644, URIBL_SBL_A=0.1] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id WDuFymkohWjD for <notmuch@notmuchmail.org>;\r
+ Sun, 16 Aug 2015 03:15:53 -0700 (PDT)\r
+X-Greylist: delayed 1397 seconds by postgrey-1.35 at arlo;\r
+ Sun, 16 Aug 2015 03:15:53 PDT\r
+Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 8FD706DE009A\r
+ for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 03:15:53 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (localhost.scs.stanford.edu\r
+ [127.0.0.1]) by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id\r
+ t7G9qap6026130; Sun, 16 Aug 2015 02:52:36 -0700 (PDT)\r
+Received: (from dm@localhost)\r
+ by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id t7G9qaPb025981;\r
+ Sun, 16 Aug 2015 02:52:36 -0700 (PDT)\r
+X-Authentication-Warning: market.scs.stanford.edu: dm set sender to\r
+ return-y6xfje9utikfmhtxvrchdsbzc6@ta.scs.stanford.edu using -f\r
+From: David Mazieres <dm-list-email-notmuch@scs.stanford.edu>\r
+To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org\r
+Subject: Re: Enabling and disabling maildir.synchronize_flags\r
+In-Reply-To: <87r3n3fu7d.fsf@maritornes.cs.unb.ca>\r
+References: <87r3orbqfn.fsf@ta.scs.stanford.edu>\r
+ <87r3n3fu7d.fsf@maritornes.cs.unb.ca>\r
+Date: Sun, 16 Aug 2015 02:52:35 -0700\r
+Message-ID: <874mjzblwc.fsf@ta.scs.stanford.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.18\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 16 Aug 2015 10:15:55 -0000\r
+\r
+David Bremner <david@tethera.net> writes:\r
+\r
+> dm-list-email-notmuch@scs.stanford.edu writes:\r
+>\r
+>> It seems that disabling it should simply be safe.  But re-enabling, one\r
+>> risks losing tags, as the next notmuch new will cause old maildir flags\r
+>> to override the xapian database.  So that suggests something like:\r
+>>\r
+>>    notmuch dump > backup\r
+>>    notmuch config set maildir.synchronize_flags false\r
+>>    # Do I need to run notmuch new here?\r
+>>    notmuch restore < backup\r
+>\r
+> Hi David;\r
+>\r
+> Sorry about the long delay. I'm not sure I follow the connection between\r
+> your paragraph above and the the example. The example seems safe, but as\r
+> you say, disabling synching should bs safe anyway.\r
+\r
+It's not an example, it's kind of a worst case scenario if there's no\r
+easy and safe way way to enable synchronize_flags.  I want to try\r
+disabling flags, but if I change my mind and the only way to get it back\r
+is to do a full notmuch dump/restore, that's a pretty hefty penalty.\r
+Also, even if I do a full notmuch dump / restore, I'm not sure if the\r
+notmuch new is necessary in the middle.\r
+\r
+So my question remains, what's the easiest safe way to re-enable\r
+synchronize_flags after disabling it?  (Safe meaning it won't change any\r
+tags.)  It could be that there's a very simple answer, in which case\r
+sticking it in the man page might be nice.\r
+\r
+Thanks,\r
+David\r