--- /dev/null
+Return-Path:\r
+ <return-8va43byzm2pw5643unfnu6c7i6@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 499326DE0B2F\r
+ for <notmuch@notmuchmail.org>; Mon, 31 Aug 2015 10:27:48 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.301\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[AWL=0.550,\r
+ RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001]\r
+ 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 9J50nmrL0pfj for <notmuch@notmuchmail.org>;\r
+ Mon, 31 Aug 2015 10:27:46 -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 231326DE0AC2\r
+ for <notmuch@notmuchmail.org>; Mon, 31 Aug 2015 10:27:46 -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
+ t7VHRbWX015282; Mon, 31 Aug 2015 10:27:37 -0700 (PDT)\r
+Received: (from dm@localhost)\r
+ by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id t7VHRaWF016532;\r
+ Mon, 31 Aug 2015 10:27:36 -0700 (PDT)\r
+X-Authentication-Warning: market.scs.stanford.edu: dm set sender to\r
+ return-8va43byzm2pw5643unfnu6c7i6@ta.scs.stanford.edu using -f\r
+From: dm-list-email-notmuch@scs.stanford.edu\r
+To: Amadeusz =?utf-8?B?xbtvxYJub3dza2k=?= <aidecoe@aidecoe.name>\r
+Subject: Re: muchsync files renames\r
+In-Reply-To: <87k2sbmzww.fsf@freja.aidecoe.name>\r
+References: <878u93ujdo.fsf@freja.aidecoe.name>\r
+ <876146o920.fsf@ta.scs.stanford.edu> <871teu8kdd.fsf@freja.aidecoe.name>\r
+ <87oahxojlv.fsf@ta.scs.stanford.edu> <87vbbwnbb4.fsf@freja.aidecoe.name>\r
+ <87io7wr50y.fsf@ta.scs.stanford.edu> <87k2sbmzww.fsf@freja.aidecoe.name>\r
+Reply-To: David Mazieres expires 2015-11-29 PST\r
+ <mazieres-27wj757hqhcqs9vy6uqq3div7e@temporary-address.scs.stanford.edu>\r
+Date: Mon, 31 Aug 2015 10:27:36 -0700\r
+Message-ID: <87oahnmkqf.fsf@ta.scs.stanford.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+Cc: notmuch@notmuchmail.org\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: Mon, 31 Aug 2015 17:27:48 -0000\r
+\r
+Amadeusz =C5=BBo=C5=82nowski <aidecoe@aidecoe.name> writes:\r
+\r
+>> So... based on all the evidence so fare the culprit seems to be that\r
+>> something is moving mail files into your Spam folder on the client.\r
+>> If that rings any bells and solves the problem, great. If not, here\r
+>> is what we need to do to track it down further.\r
+>\r
+> I have followed you hints to track down the issue. All of these\r
+> messages are spam. What I suspect follows.\r
+>\r
+> All of these files have been placed to new/ subdir by maildrop and\r
+> during posthook (afew) have been stripped of any tags besides 'spam'\r
+> tag, in particular 'unread' tag has been removed, but files still remain\r
+> in new/ subdir. So... what had to happen is that during muchsync these\r
+> messages have been discovered as already read, so they don't belong to\r
+> new/ but must be moved to cur/. And this is what happened on client\r
+> side. During next muchsync these changes had to be pushed to server,\r
+> i.e. move from new/ to cur/.\r
+\r
+Right. Muchsync checks to see if maildir.synchronize_flags is true on\r
+the client. If it is, then muchsync calls\r
+notmuch_message_tags_to_maildir_flags after setting the flags (which is\r
+the same as what would happen if you set the tags manually with the\r
+"notmuch tag" command).\r
+\r
+A maildir file in the new/ directory can't have any tags (except the\r
+implicit unread flag, which is indicated by the absence of "S" in the\r
+end of the filename). So the notmuch_message_tags_to_maildir_flags()\r
+function is renaming the file to the cur subdirectory, and then\r
+propagating this rename back to the server.\r
+\r
+The one thing I'm still unclear on is whether afew is running on the\r
+client of the server. If you are running it on the client, then this\r
+makes sense. If you are running it on the server, then somehow afew\r
+must not be respecting the maildir.synchronize_flags setting.\r
+Otherwise, the file should already be moved to the cur directory after\r
+having the unread tag stripped off on the server. I guess the other\r
+option is that your maildir.synchronize_flags false on the server and\r
+true on the client.\r
+\r
+> So if my assumptions are correct, actually there is no issue! I would\r
+> just have to adjust afew filtering to prevent this behaviour.\r
+\r
+Right. You could have afew preserve the unread flag on spam.\r
+Alternatively, you could just disable maildir.synchronize_flags on both\r
+the client and server. Finally, you could just accept the performance\r
+penalty, as one would hope that this is a one-time thing and that\r
+usually you don't have 5000 new spam messages every time you synchronize\r
+your mail.\r
+\r
+David\r
projects / notmuch-archives.git / commitdiff