On Thu, Apr 29, 2010 at 1:16 PM, Timo Sirainen <tss@iki.fi> wrote:
On Fri, 2010-04-23 at 17:26 -0500, Pat wrote:
- I insert into dovecot-uidlist manually when I deliver new messages, or discover a message that is not in uidlist for some reason. For compatability reasons I maintain a completely separate cache. If there is a better way to keep the uidlist up to date when the user isn't necessarily accessing the account via dovecot imap, I'm open to suggestions. However my situation is fairly unique I think.
Why do you need to update uidlist at all? Or do you need access to IMAP UIDs outside Dovecot? I've changed the uidlist writing rules/locking already a few times and probably will change in future versions, so changing it without Dovecot's code doesn't seem all that good of an idea to me.
Yes, we use the dovecot UIDs as the key for our webmail cache. It was easier to do it this way than to make dovecot use our existing keys. And I'm sure much more stable for a novice C developer like myself since I have modify dovecot less.
Also we do not plan to upgrade our version of dovecot once it is stable on our end, so I think that changes to locking are OK. If we do have to upgrade I will keep this in mind.
If you need the uidlist updated, what about if you just tell Dovecot to update it, for example one easy way is to use http://wiki.dovecot.org/PreAuth
printf "1 examine inbox\n2 logout\n" | dovecot --exec-mail imap
Thanks, this is very interesting I wasn't aware of this feature, I will look into it some more.
Pat