--- /dev/null
+Return-Path: <jani@nikula.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id CD014431FAF\r
+ for <notmuch@notmuchmail.org>; Sat, 24 Mar 2012 05:04:39 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 8H4ytb6DhmPc for <notmuch@notmuchmail.org>;\r
+ Sat, 24 Mar 2012 05:04:39 -0700 (PDT)\r
+Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com\r
+ [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 100FC431FAE\r
+ for <notmuch@notmuchmail.org>; Sat, 24 Mar 2012 05:04:38 -0700 (PDT)\r
+Received: by lbok6 with SMTP id k6so3270657lbo.26\r
+ for <notmuch@notmuchmail.org>; Sat, 24 Mar 2012 05:04:37 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=google.com; s=20120113;\r
+ h=from:to:cc:subject:in-reply-to:references:user-agent:date\r
+ :message-id:mime-version:content-type:x-gm-message-state;\r
+ bh=1NvgL3fWRrFn0ZN+xMh5uSKzaj0eWNr/a8w9N6EqvMY=;\r
+ b=fywOJwnoJoH0i016a4+PTT5R7AujzKwMw6QEzxCbSTIIgvbKVltBRvIEiN1aP8Kosu\r
+ ozmcQ/Z5id/sl7ucw9otSpgxbI84bxmUgMGNYIb6q59heEs/zn+e5lKkVgr8r7t08bqn\r
+ +hYrwJPYLwiJP7cJEdt1yoEwSsjdL+gWPpk4X2v0UjiIC9wwBzR+8mr8KIbVMnzi5zmM\r
+ AG1VumlN+qe8jc45IyKCkHdDWuX7+8kgsgNCzDZR82FDliQFgD5XyYeD8XdUjjYxHjAb\r
+ d4NahEUHfRjm6ifjRTtEvXPvVYLDgQufDfLZsoocjNBcJULyp1q8F1nTSaQqw2exWB1V\r
+ r2XQ==\r
+Received: by 10.112.103.74 with SMTP id fu10mr948141lbb.1.1332590677171;\r
+ Sat, 24 Mar 2012 05:04:37 -0700 (PDT)\r
+Received: from localhost (dsl-hkibrasgw4-fe50f800-253.dhcp.inet.fi.\r
+ [84.248.80.253])\r
+ by mx.google.com with ESMTPS id py12sm10871262lab.4.2012.03.24.05.04.34\r
+ (version=SSLv3 cipher=OTHER); Sat, 24 Mar 2012 05:04:35 -0700 (PDT)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Austin Clements <amdragon@MIT.EDU>, Kyle Sexton <ks@mocker.org>\r
+Subject: Re: Questions from a user new to notmuch\r
+In-Reply-To: <20120322223907.GO2670@mit.edu>\r
+References: <m2k42d9v7i.fsf@Kyles-MacBook-Pro-2.local.i-did-not-set--mail-host-address--so-tickle-me> <20120322223907.GO2670@mit.edu>\r
+User-Agent: Notmuch/0.11.1+295~g780f284 (http://notmuchmail.org) Emacs/23.3.1\r
+ (i686-pc-linux-gnu)\r
+Date: Sat, 24 Mar 2012 14:04:32 +0200\r
+Message-ID: <87bonmqk6n.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Gm-Message-State:\r
+ ALoCoQmT3LTg/Dyfa18ygYlrIn+PFRwkf+kKQ7i/a5mw/Ptip+sNtvIZ/6k2JovjBEtqWCpONr6O\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\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: Sat, 24 Mar 2012 12:04:39 -0000\r
+\r
+On Thu, 22 Mar 2012 18:39:07 -0400, Austin Clements <amdragon@MIT.EDU> wrote:\r
+> Quoth Kyle Sexton on Mar 21 at 10:21 pm:\r
+> > 1. Using offlineimap to store mail into a Maildir, is it safe to move an\r
+> > already indexed message to a different folder from some other client?\r
+> \r
+> Yes, mostly. You'll have to run notmuch new for notmuch to detect the\r
+> move, but it will detect it as a move. I say "mostly" because until\r
+> you run notmuch new, notmuch won't find the message file, so it won't\r
+> be able to display the message and won't be able to synchronize any\r
+> tag changes to its maildir flags.\r
+\r
+If maildir.synchronize_flags is enabled (it is by default) you should\r
+take extra care to have the mail store and notmuch database in sync (by\r
+running "notmuch new") before changing tags that are synced with maildir\r
+flags. Otherwise, the following scenario is possible:\r
+\r
+1) Rename file with id:message-id in another client. Note that maildir\r
+ flag changes are also renames.\r
+\r
+2) "notmuch tag -unread id:message-id" will remove unread tag from the\r
+ message, but won't find the message file, and is thus unable to sync\r
+ the tag change to the S maildir flag. The syncing just silently\r
+ fails.\r
+\r
+3) The next "notmuch new" syncs maildir flags to tags, adding unread tag\r
+ back to id:message-id, losing your tag change.\r
+\r
+This could be considered a bug in notmuch, but not an easy one to fix\r
+race free. See http://notmuchmail.org/special-tags/ and your\r
+.notmuch-config for details about maildir flag synchronization.\r
+\r
+\r
+BR,\r
+Jani.\r