Mechiel Lukkien 9f3cb7340b

update modseq when changing mailbox/server metadata, and also for specialuse changes, and keep track of modseq for mailboxes ...

i added the metadata extension to the imapserver recently. then i wondered how
a client would efficiently find changed metadata. turns out the qresync rfc
mentions that metadata changes should set a new modseq on the mailbox.
shouldn't be hard, except that we were not explicitly keeping track of modseqs
per mailbox. we only kept them for messages, and we were just looking up the
latest message modseq when we needed the modseq (we keep db entries for
expunged messages, so this worked out fine). that approach isn't enough
anymore. so know we keep track of modseq & createseq for mailboxes, just as for
messages. and we also track modseq/createseq for annotations. there's a good
chance jmap is going to need it.

this also adds consistency checks for modseq/createseq on mailboxes and
annotations to the account storage. it helped spot cases i missed where the
values need to be updated.

2025-02-22 22:52:18 +01:00

..

export.go

add config options to disable a domain and to disable logins for an account

2025-01-25 20:39:20 +01:00

xops.go

update modseq when changing mailbox/server metadata, and also for specialuse changes, and keep track of modseq for mailboxes

2025-02-22 22:52:18 +01:00