Ow Mun Heng wrote: > I see. I read that overall, parsing the queries to mysql can really bog > down the server anyway. So, it'll be a "to be looked at" once I get > things up and running and when time permits.
I have run cyrus-imapd in both configurations, one server with between 20 and 40K emails daily, 100+ users. Never had any problems, it just worked. I have not, however, benchmarked using mysql for authentication in a high volume environment. It would seem to me, however, that doing lookups via a piped connection to a cached query would be more efficient than filesystem calls. Can't say for sure though. There are some imap proxy utilities to cache connections but I have never messed with them. A couple of heads up on the client side.... The latest kmail has support for sieve, but you have to directly edit the sieve scripts. On the other hand kmail chokes on altnamespace when adding folders. Kmail allows you to set acls on mailboxes but does not support all of the acls in cyrus-imapd, post/admin for examples ;( Horde works very well for users maintaining sieve scripts and passwords. I have never used web-cyradm, I always used a perl package called webseive.pl, which handles sieve very well as well as password changes, setting acls, etc... -- [email protected] mailing list
