mbauhardt
commented
4 years ago I stumbled over the same confusion when checking my cur and new folders. But I'm not sure which piece of software in my mail chain (mbsync, notmuch, afew, mblaze) is responsible for that behaviour.
So I will check if my afew setup is responsible for this.
Hi, I've been using notmuch + afew for some time now and I recently noticed email from the
new/dir is never moved tocur/after being read, apparently makingnotmuch newslow (2 minutes to find 10 new emails in 11k emails in the new/ dir).I decided to do some tests on another box and I see that if I use
notmuch insertinstead, something else happens:new.tags = inbox;unread;in notmuch-config new email is delivered tonew/and moved tocur/and flagged as seen after being read (ok)new.tags = newas required byafew, new email is delivered tocur/and flagged as seen inmediately (bad)afew -v --new --tagafter this, it complains that the file incur/is a single message mbox "likely caused by misconfigured mail delivery" and the email is taggedinboxbut notunread(bad)Now if I move back to delivering email directly to maildir and use
notmuch newI see:new.tags = inbox;unread;new emails are delivered tonew/and moved tocur/after runningemacs newand reading them (ok)new.tags = newas required byafew, new emails are delivered tonew/, markedinbox unreadbyafew -v --new --tagwithout complaining about single message mbox, moved tocur/and flagged as seen after being read (ok)So... I couldn't reproduce the issue I had in the first place (though in tests I'm using
afewfrom today), but it seems thatafewdoesn't play nicely withnotmuch insert...maildir.synchronize_flagsis always set totrue. Email delivery is performed bypostfixwithmailbox = Maildir/for direct delivery andmailbox_command = /usr/bin/notmuch insertfor delivery + indexing.Any ideas? If you think this is a query I should send to the notmuch mailing list please say so. Thanks!