Re: Enabling and disabling maildir.synchronize_flags

diff --git a/76/4996eb0dfd1a782a4e0db4c500b42a3ff07914 b/76/4996eb0dfd1a782a4e0db4c500b42a3ff07914
new file mode 100644 (file)
index 0000000..078e2a9
--- /dev/null
+++ b/76/4996eb0dfd1a782a4e0db4c500b42a3ff07914
@@ -0,0 +1,101 @@
+Return-Path:\r
+ <return-m5bnw98qfab3x8rrwucsc97r9e@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 E3ECE6DE0B26\r
+ for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 12:41:14 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "References"\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.798\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[AWL=0.309,\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 Hva2JRWxVmst for <notmuch@notmuchmail.org>;\r
+ Sun, 16 Aug 2015 12:41:13 -0700 (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 2713A6DE01D3\r
+ for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 12:41:13 -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
+ t7GJfCSm001264 for <notmuch@notmuchmail.org>; Sun, 16 Aug 2015 12:41:12 -0700\r
+ (PDT)\r
+Received: (from dm@localhost)\r
+ by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id t7GJfCXX012637;\r
+ Sun, 16 Aug 2015 12:41:12 -0700 (PDT)\r
+X-Authentication-Warning: market.scs.stanford.edu: dm set sender to\r
+ return-m5bnw98qfab3x8rrwucsc97r9e@ta.scs.stanford.edu using -f\r
+From: dm-list-email-notmuch@scs.stanford.edu\r
+To: notmuch@notmuchmail.org\r
+Subject: Re: Enabling and disabling maildir.synchronize_flags\r
+In-Reply-To: <87614ffl0t.fsf@maritornes.cs.unb.ca>\r
+Date: Sun, 16 Aug 2015 12:34:30 -0700\r
+References: <87r3orbqfn.fsf@ta.scs.stanford.edu>\r
+ <87r3n3fu7d.fsf@maritornes.cs.unb.ca> <874mjzblwc.fsf@ta.scs.stanford.edu>\r
+ <87614ffl0t.fsf@maritornes.cs.unb.ca> <87vbcf9ge1.fsf@ta.scs.stanford.edu>\r
+References: <87r3orbqfn.fsf@ta.scs.stanford.edu>\r
+ <87r3n3fu7d.fsf@maritornes.cs.unb.ca> <874mjzblwc.fsf@ta.scs.stanford.edu>\r
+ <87614ffl0t.fsf@maritornes.cs.unb.ca>\r
+Message-ID: <87pp2n9g2v.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 19:41:15 -0000\r
+\r
+David Bremner <david@tethera.net> writes:\r
+\r
+> David Mazieres <dm-list-email-notmuch@scs.stanford.edu> writes:\r
+>> So my question remains, what's the easiest safe way to re-enable\r
+[ 2 more citation lines. Click/Enter to show. ]\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
+> I can't think of a simple, safe, and fast answer.\r
+\r
+Okay, thanks.  At least I wasn't missing something obvious.\r
+\r
+> 2) when the lastmod changes go in, it seems like you could run the first\r
+>    notmuch new after enabling tag synchonizing, and dump only the tag\r
+>    changes since a checkpoint lastmod value. This would allow rolling\r
+>    back the unwanted tag changes.\r
+\r
+Indeed, one of many reasons I'm eagerly awaiting lastmod changes.\r
+\r
+> [1]: see this potential test, if for some reason we wanted to\r
+>      guarantee this behaviours.\r
+\r
+If we did want this, I'm assuming it would take the form of a new option\r
+to notmuch new (--override-flags) which says to do the synchronization\r
+in the other direction (Xapian -> Maildir)?  There would be benefit to\r
+having such a flag, but I don't know how hard it would be to implement,\r
+so I can't do the cost/benefit analysis.\r
+\r
+As a kind of aside, one reason people might want to synchronize flags is\r
+for mobile device support.  I don't regularly access my email from my\r
+mobile phone, but on those rare occasions when I might need to, I set up\r
+an IMAP server and use an imap client on the phone.  I wonder if anyone\r
+has thought about implementing an IMAP-ish server directly on top of\r
+libnotmuch.  (I say IMAP-ish because the obvious SEARCH command\r
+implementation wouldn't be RFC3501-compliant, but who cares when notmuch\r
+has something better.)\r
+\r
+Does anyone else use both notmuch but also access email from a mobile\r
+device?  If so what do you do?\r
+\r
+David\r