unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Sean Whitton <spwhitton@spwhitton.name>, notmuch@notmuchmail.org
Subject: Re: Forcing a sync of maildir flags?
Date: Thu, 20 Feb 2020 08:22:42 -0400	[thread overview]
Message-ID: <87r1ypsb1p.fsf@tethera.net> (raw)
In-Reply-To: <871rqp97o0.fsf@iris.silentflame.com>

Sean Whitton <spwhitton@spwhitton.name> 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/

> 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.

d

  reply	other threads:[~2020-02-20 12:22 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 [this message]
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

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=87r1ypsb1p.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=spwhitton@spwhitton.name \
    /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).