From: Gregor Zattler <telegraph@gmx.net>
To: notmuch@notmuchmail.org
Subject: Re: Forcing a sync of maildir flags?
Date: Wed, 13 Apr 2022 12:27:10 +0200 [thread overview]
Message-ID: <87a6cp2s8x.fsf@no.workgroup> (raw)
In-Reply-To: <87y20k9lu2.fsf@athena.silentflame.com>
Hi Sean,
* Sean Whitton <spwhitton@spwhitton.name> [2022-04-04; 21:48]:
> On Tue 22 Mar 2022 at 12:44pm -07, Sean Whitton wrote:
>
>> I am seeing this bug, or a closely related one, a whole lot right now.
>> Messages are coming back as unread over and over again.
me too. And it's not only messages from me, but also
messages from other people appear as unread of which I'm
quite certain I already read them.
>> I recently made some changes to my notmuch cronjobs, so
>> that probably has something to do with it, but I have no
>> guesses as to what the problem is.
>>
>> As a first thing to try, I am going to add something to my pre-new hook
>> to perform the new/ -> cur/ move as specified by maildir(5) on all my
>> synced maildirs, so that notmuch never sees messages in new/ except when
>> it writes new drafts and sent mail there (and they'll get moved on the
>> next sync).
Would you please disclose your workaround? I'm very much
interested.
Ciao; Gregor
--
-... --- .-. . -.. ..--.. ...-.-
prev parent reply other threads:[~2022-04-13 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 4:58 Forcing a sync of maildir flags? Sean Whitton
2020-02-20 12:22 ` David Bremner
2020-02-20 13:21 ` David Bremner
2020-02-20 21:19 ` Sean Whitton
2020-02-21 0:06 ` David Bremner
2020-02-21 19:54 ` Sean Whitton
2022-05-01 23:23 ` David Bremner
2022-05-02 23:24 ` Sean Whitton
2022-05-03 12:14 ` David Bremner
2022-05-03 23:59 ` Sean Whitton
2022-03-22 19:44 ` Sean Whitton
2022-04-05 4:48 ` Sean Whitton
2022-04-13 10:27 ` Gregor Zattler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6cp2s8x.fsf@no.workgroup \
--to=telegraph@gmx.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).