On Jun 9, 2008, at 5:02 AM, Sam Varshavchik wrote: > > In any case, the server seems to reread the keyword database for the > simple reason that something else might've modified the keyword > data, like another IMAP process that has the same folder open, and > any chances to the keyword data need to be reported to the client. > I'll need to see if there might be ways to optimize it by futzing > around with directory's timestamps. Stay tuned.
An idea I was messing around with is to keep a :list file per imapd process and periodically merge them. Then the operation could look like: keyword set -> write keyword file -> append personal :list file. A read would read :list and then every other :list. If it was a worry for multiple clients updating keywords on the same message, a timestamp could be stored for each entry in each :list file. Just an idea. I don't have the time to do anything myself and I doubt I have the impulse anymore, because I solved my problem by not using Mail.app for the IMAP account. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
