> Cyrus caches seen state in memory for a time before flushing it to > disk. Generally this works quite well; I use Outlook Express and > don't seem to have this problem, but perhaps I just don't do this > exact sequence of clicks. > > It's possible to force Cyrus to synchronize seen state more quickly > with the comparable loss of performance/scalability. > I certainly see this problem. Not regularly enough to have made me try and actually do something about it, but certainly I respond to a few support requests per week over this. Our web app at fastmail.fm runs multiple processes (being Apache 1.x + mod_perl) and I've written a socket pooling daemon to hand authenticated IMAP sockets to authenticated httpd processes. Because of how things are set up it's not unusual for multiple processes to end up with different IMAP connections and just occassionally they will end up showing the user the incorrect read/unread state as a result.
I also see this problem in OE 5.0, 5.5, and 6.0. Again, only enough to be mildly annoying. I guess whether syncing should occur more quickly depends on the detail of just how much scalability is lost as a result.
