From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 4B2946DE0355 for ; Thu, 20 Feb 2020 13:26:13 -0800 (PST) Authentication-Results: arlo.cworth.org; dkim=pass (2048-bit key; unprotected) header.d=spwhitton.name header.i=@spwhitton.name header.b="C4fFtxgj"; dkim=pass (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.b="eOunwKoo"; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -2.708 X-Spam-Level: X-Spam-Status: No, score=-2.708 tagged_above=-999 required=5 tests=[AWL=-1.808, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cBAujpfALv3q for ; Thu, 20 Feb 2020 13:26:12 -0800 (PST) X-Greylist: delayed 400 seconds by postgrey-1.36 at arlo; Thu, 20 Feb 2020 13:26:11 PST Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by arlo.cworth.org (Postfix) with ESMTPS id 262296DE0352 for ; Thu, 20 Feb 2020 13:26:11 -0800 (PST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 87A6C21B55; Thu, 20 Feb 2020 16:19:27 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 20 Feb 2020 16:19:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spwhitton.name; h=from:to:subject:in-reply-to:references:date:message-id :mime-version:content-type; s=fm2; bh=wBKuh/it8yrCPpsMhX4nt4dzkK ysLB/VAxbq9jElYGY=; b=C4fFtxgjM+3ZFQqI6XsWBHNUUV9RvQtLWnVyGQAd+I 4ldW8Br0b157m/FT/Vs9ofN4S/OAGffJkIk5yKlc2c6Qo4DdRa543Rj8Mz1h7Lma 9UcvHM7mratCeDzzY+EWVRYYtxnF9E17ozEvUKH+ZF1Qm8fEIrB5Ba7Sr1B30fmr N7Vy1pRW7JxaHlEhPef8P99ZIQShoL/DLTJpulUVglH7uBwt5nh2BfDB4BEk1TwW 19KAM69tW//YIs3IJNzBv0LuG92QoASJ4HpR/cth2eEtL9hcPDz0YawOndXeIhNw BxetCIGTDzfzbQWZ4jLfFvxHWQi+O2dYff6YtOUvnZKQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=wBKuh/ it8yrCPpsMhX4nt4dzkKysLB/VAxbq9jElYGY=; b=eOunwKooNOuqyDKUu6x2/4 DFU1M1yvhqnI2eDi6Ns2+Ax4rvX/EXGFBVZdMaGWDdXd3/1/CUvJN0x+IMhWf2k/ 0P9oCEd4mN+eHuwnJ/n1/gp5nVPO49DPvvrdK4V2S8pl0wQn560/El9Oo69aPhTR lQX8JoWUxT6tNUJeiLRzqcnvi13W6bI2lGRmzIrqjtkliuBcvWFwFv16wAI+aLYr l3w4bVNYxkh+oR2k3lmsWVKCWedc+B3OPsz+Ab4SxubPK9ULRt2SO83Fc4Rd7L8a QhNJrcC8eCzztlBAgEJEyiaMaY+ZC8CsdTX4FgCgmpvPYR+ndQ2vE5E7B5ZSg06w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrkedvgdduhedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufgjfhffkfggtgesthdtredttddttdenucfhrhhomhepufgvrghnucgh hhhithhtohhnuceoshhpfihhihhtthhonhesshhpfihhihhtthhonhdrnhgrmhgvqeenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsphifhhhi thhtohhnsehsphifhhhithhtohhnrdhnrghmvg X-ME-Proxy: From: Sean Whitton To: David Bremner , notmuch@notmuchmail.org Subject: Re: Forcing a sync of maildir flags? In-Reply-To: <87r1ypsb1p.fsf@tethera.net> References: <871rqp97o0.fsf@iris.silentflame.com> <87r1ypsb1p.fsf@tethera.net> Date: Thu, 20 Feb 2020 14:19:25 -0700 Message-ID: <87r1yp6joi.fsf@iris.silentflame.com> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Feb 2020 21:26:13 -0000 Hello David, Thank you for your reply. On Thu 20 Feb 2020 at 08:22AM -04, David Bremner wrote: > Sean Whitton writes: > >> I have this in my post-new hook: >> >> notmuch tag -unread -- folder:sent >> >> The idea is that copies of my sent mail which get returned to me and >> stored in my inbox, e.g. by mailing lists, would get maildir Seen tags >> added to them. But that does not happen. > > I guess this is most likely a bug. It would be nice to have a test in > T340-maildir-sync.sh that duplicated it. I suspect the problem is > related to messages in the new/ subdirectory. Some non-notmuch clients > (prominently mutt) interpret being in new/ has having user-visible > semantics, so notmuch tries not to move files out of there > unnecessarily, On the other hand the maildir spec says that files in > new/ cannot have flags, so they cannot have their unread tag removed > without moving the file to cur/ So, your hypothesis is that notmuch is opting not to add the Seen flag in order to avoid having to move the message from new to cur, for the sake of mutt, but that's a bug because I've explicitly requested adding Seen, so it ought to go ahead and move it from new to cur? >> This works: >> >> notmuch tag +unread -- folder:sent >> notmuch tag -unread -- folder:sent >> >> Is there some more elegant way to force a sync of maildir flags? Am I >> the only one that has copies of my own mail in my inbox folder, not >> marked as read from the point of view of anything except notmuch? > > I guess my workflow doesn't expose this problem as I leave many messages > unread (relying on the inbox flag). I'm not sure about the locking > implications, but having sent messages delivered to cur/ instead of to > new/ would probably workaround the problem. In this case it's mbsync downloading messages from IMAP, and there doesn't seem to be a way to configure it to deliver to cur instead of new. On Thu 20 Feb 2020 at 09:21AM -04, David Bremner wrote: > I guess the other thing is that I have > > [new] > tags=unread;inbox;new > > in .notmuch-config, which means that "notmuch new" moves things into > cur/. Maybe you can use that effect? To be honest that doesn't seem really better than the workaround I'm currently using. -- Sean Whitton