From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id IEGlErJpcGKsXQEAbAwnHQ (envelope-from ) for ; Tue, 03 May 2022 01:30:58 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id GF/WErJpcGLM2gAA9RJhRA (envelope-from ) for ; Tue, 03 May 2022 01:30:58 +0200 Received: from mail.notmuchmail.org (yantan.tethera.net [135.181.149.255]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C4B653225B for ; Tue, 3 May 2022 01:30:57 +0200 (CEST) Received: from yantan.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id E57895F6DC; Mon, 2 May 2022 23:30:54 +0000 (UTC) X-Greylist: delayed 391 seconds by postgrey-1.36 at yantan; Mon, 02 May 2022 23:30:52 UTC Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mail.notmuchmail.org (Postfix) with ESMTPS id 217855F6BE for ; Mon, 2 May 2022 23:30:52 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4C3895C010B; Mon, 2 May 2022 19:24:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 02 May 2022 19:24:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spwhitton.name; h=cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1651533860; x=1651620260; bh=Tr7pu6Wbod iWqUNUN48+kiN3OVWZScBvAm3f+0iMUHQ=; b=CARLAET12/RDqjBLerqiLq2FmC Ov5706X7gkyZ+/lr7oHwm3hNb61RxKinXjhYpT8k4gGMezYu4C8E4OfmDbp70tYO HVzMbZ/VGiQSVrfx2U78MAmi4r8RfSl1+rlVonf42JS7in7Xzd5FWEuxeRLK9khC VC8Keol7L/gc7J9Ir6nuIs/t07PJkWKYlcpWuGmz027kEYvl5v2dzlTmtNHG4Dzp bzhR64Vfj2gz4KFXy4AcDh5R/Tl8ywEGH6f+/x7xtCPgB9GzXOLwhonn8wP4mcf6 cObWynHhT1JZEOCP6KBctTRczKEWna9MzWC5N5e7w/qbd8MlDUFXqZprxA9g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1651533860; x= 1651620260; bh=Tr7pu6WbodiWqUNUN48+kiN3OVWZScBvAm3f+0iMUHQ=; b=L Qm+rPyq0UpkXx0YoQoSkV7qCvzlTHrDKgVhW7c02hja+2MuGAm0g6N8VA3rxlEZl rCO72QFPOkn/+Vn20p+l/vzgbIsx31BM9fEoBPdOXVFthsLF/1bn6Xp4hJvaXZ5n 2K04zs/s0v+2MKLqeWMYjiI5UkTbJhoQFaeDDe04WDH+8Z7oBkW4oHp244UP0cC0 Aw2jwsoCD7zAiZLeJiMIOOoP//Cjx2KsD/CxyyJLbq+EvXqahS9wSM5dskh/WQTf 1SLYNEYn82Ll76Jo3zgGcl8+dBA6JGNffgHm7QwEWOuunUpBTP4UGbxh56HNQk7T Oz2jBBFxk3AhBjNCs4tPg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdeigddvtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffujghffgffkfggtgesthdttddttdertdenucfhrhhomhepufgvrghnucgh hhhithhtohhnuceoshhpfihhihhtthhonhesshhpfihhihhtthhonhdrnhgrmhgvqeenuc ggtffrrghtthgvrhhnpeelgeeggfdvieejvdfhudfggeetgfekkeeuieeljeejhedugeeg feetgefhueffkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehsphifhhhithhtohhnsehsphifhhhithhtohhnrdhnrghmvg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 2 May 2022 19:24:19 -0400 (EDT) Received: by melete.silentflame.com (Postfix, from userid 1000) id B77AA7E52A6; Mon, 2 May 2022 16:24:18 -0700 (MST) From: Sean Whitton To: David Bremner , notmuch@notmuchmail.org Subject: Re: Forcing a sync of maildir flags? In-Reply-To: <87ee1c7s7s.fsf@tethera.net> References: <871rqp97o0.fsf@iris.silentflame.com> <87r1ypsb1p.fsf@tethera.net> <87r1yp6joi.fsf@iris.silentflame.com> <87mu9cg5xy.fsf@tethera.net> <87d0a7zpfd.fsf@iris.silentflame.com> <87ee1c7s7s.fsf@tethera.net> User-Agent: Notmuch/0.35 Emacs/29.0.50 (x86_64-pc-linux-gnu) Date: Mon, 02 May 2022 16:24:18 -0700 Message-ID: <87wnf334d9.fsf@melete.silentflame.com> MIME-Version: 1.0 Message-ID-Hash: FX7LPMJ6YBAWUCEPGMNPSAUX27QPYDAP X-Message-ID-Hash: FX7LPMJ6YBAWUCEPGMNPSAUX27QPYDAP X-MailFrom: spwhitton@spwhitton.name X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: DE ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1651534258; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=7W2BHsdlTUwhqBRjKY/zvymxFQ4xWYmIVxMwng2+O6g=; b=H9ODYbiRvctARyCtrXjEhmZB/SWEF9leEqeb4UfEITtjNT0XI6wt9HhgHLkqrVJjxMHLjH avVC80iM+FHCLsQyvVjk4qVWp9eZkcirDskdwwtAVKJN2YM/gJfwOYjKkpUjQMdfmG1oXl hX2PDFg1DV7YbiRebohqIVhFk+62Np/EaeDNmTnwpIouQNEGwAPrpiTLDAeUzlVkARtG7W Ll+lPSaHtVEjsojjRsSF55Hruu1CQJ7lOMy9DRJBhf7p/A8FzbRhrfkm+KxLOVaCRd+ttu 5GYSa9KF3+OmvjSAWxbfLwDvBzZouSOGU45a0RMyBONGcjwEwciOJr/QjtiuLA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1651534258; a=rsa-sha256; cv=none; b=miVtUX0iEADJhF8DmlydJXM1unZr/PS4a2zKacKlEkED8dKu823JDr3FjiquYArOM7xavk CDc0H+zq8H+0yW7F0iWc7BABLNDNGrxB9nYsixusBGH8t+MfrKwuf+cf4iGH/dgIW5j0oJ Fr0gMk+UzhrDHStK+L36qmY3Jr2YtYRTsIAb89TB4iNoNS3R//TzN9ARJ64W2NQS5T7Rse b5soZLn7qfuylB97o48uy4OTXEbYL7OOXUZgzo5AZgcOP/i7f8rib7dYAqpTcE0xWWkGob 5uYzF5bca8UZy9Kf38xealWzz/l5Wtama+zBRrL/Fw3yEkJ8QjlTc+UHdS858A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=spwhitton.name header.s=fm3 header.b=CARLAET1; dkim=fail ("body hash did not verify") header.d=messagingengine.com header.s=fm1 header.b="L Qm+rPy"; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 135.181.149.255 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Spam-Score: 3.00 Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=spwhitton.name header.s=fm3 header.b=CARLAET1; dkim=fail ("body hash did not verify") header.d=messagingengine.com header.s=fm1 header.b="L Qm+rPy"; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 135.181.149.255 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Queue-Id: C4B653225B X-Spam-Score: 3.00 X-Migadu-Scanner: scn1.migadu.com X-TUID: +priHWGyjahv Hello David, On Sun 01 May 2022 at 08:23PM -03, David Bremner wrote: > Sean Whitton writes: >> >> Thanks. Let me record in this thread what I will believe it will take a >> reproduce this in a test: >> >> 1) inbox and sent are Maildirs >> >> 1) Compose mail to a mailing list which will return copies of >> submissions, with `Fcc: sent -unread` > > Since you mention Fcc, are you using notmuch insert? notmuch-maildir-use-notmuch-insert is t so I think I am? > # next line is a no-op, because it already doesn't have the unread tag > notmuch tag -unread folder:sent Seems also worth noting that to my mind it ultimately shouldn't be necessary to run that command -- notmuch should notice that one copy of the message has different maildir flags to the other in a way that's out of sync with the notmuch tags it has. > The key point is that from notmuch's point of view the message never has > the unread tag, so there is no change for "notmuch tag" to sync with > maildir flags. > > It doesn't seem to make a difference if I put the copy in inbox/new or > inbox/cur, so I don't think it is related to the previous efforts not to > prematurely move files out of new/. > > As far as I can tell, notmuch-new (unlike notmuch-insert) does not call > notmuch_message_tags_to_maildir_flags, so the maildir flags on the newly > discovered copy are not updated. Perhaps it should, but that seems like > a pretty big change, so I want to proceed with caution. It makes sense to me for notmuch-new to call that function too, fwiw. -- Sean Whitton