From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Sun Feb 2 17:18:27 EST 2020 Received: from abbatoir.fios-router.home (pool-162-83-132-245.nycmny.fios.verizon.net [162.83.132.245]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 9841b594 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO); Sun, 2 Feb 2020 14:18:18 -0800 (PST) Message-ID: <7217BD625086D47AA842D31975A43E5D@eigenstate.org> To: theinicke@bss-wf.de, 9front@9front.org Subject: Re: [9front] upas/fs plumb modify for self-made flag changes Date: Sun, 2 Feb 2020 14:18:17 -0800 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: HTTP strategy GPU generator > Currently upas/fs plumbs modify messages only if the flag changes are made by another imap connection. If the flag changes are made within the running upas/fs no modify message is plumbed. > > Assuming this is not intentionally and we want to get a modify plumb message after flags were changed in running upas/fs the attached patch fixes this by making sure to send a modify for pending changes upon mbox sync. > > The modify could be plumbed earlier, but this way it costs us almost nothing and changed flags from outside upas/fs are noticed in the same time interval anyway. > > -- > Tobias Heinicke This is probably the right thing to do. Acme Mail both modifies messages and watches for modification notifications. Have you made sure sure that it does the right thing in all cases?