Tickets :: Comment on [#11590] Kolab backend: IMAP cache does not get updated

* Your Email Address
* Spam protection	Enter the letters below: __..__ . ,.___.___ (__ [__) \./ [__ [__ .__)[__) \| \| \|
Comment	>> I lack a final plan concerning the synchronization strategy. The >> problem with the synchronization is that each list synchronization >> costs two IMAP calls (LIST and METADATA) and each data >> synchronization as well (STATUS and SEARCH - the latter identifies >> deleted messages). > > Any reason you are not using CONDSTORE/QRESYNC if it is available? > QRESYNC solves the last issue entirely (and CONDSTORE solves the last > issue transparently within the Imap driver). However, a cache > backend is needed to use these. > > Given the activesync may use MODSEQs also without using a cache > driver, it may be useful to allow a MODSEQ to be explicitly given to > the openMailbox command. Although this has major drawbacks, since > openMailbox() is called extensively within the IMAP driver itself so > a mailbox may already be open by the time a MODSEQ can be provided. > > A better option might be to create a custom cache driver to pass to > the IMAP driver.
Attachment
Watch this ticket