v1: Duplicate MailboxUpdate generated upon Select

[simartin]

Noticed on aerc, that uses go-imap 1.2.1. I assume that this would not happen with v2, that simply ignores Recent AFAIU.

When one does something like Client.Select("directoryname", false) (aerc code), go-imap generates two MailboxUpdate in the same "10^(-toomuch) second", supposedly one for * 172 EXISTS and one for * 1 RECENT (see aerc log excerpt below).

However, since MailboxUpdates trigger a mail check in aerc, this duplication causes unneeded perceived latency, and it'd be great to fix this in go-imap v1.

Is it something you'd consider fixing? And if not, would you consider patches against v1 (and eventually release a 1.2.x), or should we consider v1 dead dead?

Thanks, Simon

aerc log excerpt

DEBUG 2025/04/08 10:29:34.946181 open.go:13: [WorkMail] Opening INBOX/Informatique/GCC
TRACE 2025/04/08 10:29:36.447913 idler.go:76: [WorkMail] idler (start): start idle after debounce
TRACE 2025/04/08 10:29:36.447981 worker.go:272: [WorkMail] (= *client.StatusUpdate
TRACE 2025/04/08 10:29:36.447995 worker.go:272: [WorkMail] (= *client.MailboxUpdate
TRACE 2025/04/08 10:29:36.448010 worker.go:272: [WorkMail] (= *client.MailboxUpdate

[emersion]

I am not actively working on nor reviewing v1 patches, sorry.

[simartin]

Understood, thanks for confirming. We'll then probably dedupe those on our side until/if we migrate to v2.