[Dovecot] Courier migrating issues: indexes, maildirsize, update query

[Jan van den Berg]

Hi,

(my first post to the list) 

I'm in the process of testing Dovecot to see whether it meets our needs
to replace our current Courier setup which serves well over 100.000
mailboxes (pop3 and imap: mysql with NFS)
So far dovecot seems pretty straight forward; however I ran into a
couple of things that I'm curious about.

1. What's the deal with
dovecot.index/dovecot.index.log/dovecot.index.cache. I understand
Dovecot uses this for POP3 primarily but this will no doubt cause a lot
of overhead on our platform. Also getting this to work with our NFS
setup would be a pain (locking etc.). I've been following this
discussion:
http://www.dovecot.org/list/dovecot/2006-January/thread.html#10758; and
it ends with C. Malony suggesting that an disable index option would be
in place; but no further action is taken. Basically I want to get rid of
the index files (courier also doesn't use any). Any suggestions; will
there be a disable-index option?

2. One of the reasons we want to get rid of Courier is because the
maildirsize is often incorrect. Whether this is because of a bad Courier
implementation or NFS issues or whatever, I haven't figured out yet. But
I'd like to test this function in Dovecot; but there seems to be very
little documentation. I  read the link
http://wiki.dovecot.org/Quota/Dict but this info is too scarce. Any
pointers on where to go?

3. In our MySQL setup we have a field with the latest poptime and
pophost (IP). This info can come in handy when troubleshooting or
filtering out inactive mailboxes. With our Courier setup this field gets
updated by a rather elaborate script that checks the logs and runs
updates queries. I could get this to work for Dovecot; but with Dovecot
being more actively in development, I wonder could this be a feature;
like after a user_query, another update query?

Cheers,

Jan