3 years ago I tried to deploy Squirrelmail for system a little bit
larger than yours, it failed miserably.
We found out the reason was authentication, so we deployed imapproxy.
Once we did that squirrelmail was able to handle
things much better. This was on a cluster of about 5 RHAS boxes, and
mysql for authentication. Changing mail specially webmail
for such a large number of users may not be as ok as you think. If
you're a shared hosting provider like we were, you better do your tests
and load balancing, or you're be firefighting a lot :).
On Oct 13, 2005, at 10:26 PM, Christopher A. Watford wrote:
On 10/13/05, Ross Poulton ross@rossp.org wrote:
Christopher,
As far as I'm aware (from my involvement in this list) there are
currently no sites as large as that in use. You're obviously
welcome to test it out with a handful of users and let us know how
it goes :)Be aware that the software is, according to www.roundcube.net,
still in the Alpha stage. This should be considered when looking
for possible replacements for a 700k user setup - I'm assuming
with that many users, any downtime means big dramas and buckets of
fun for you and/or your team :)Ross
We'll I'm just the programmer, downtime is ok if things get accomplished. Moreover, I'm willing to contribute any changes I make back to the community, but only if the underlying IMAP code can handle the load. It'd be a beotch and a half to throw in the SM code at this point if the Iloha can't handle it. Granted it may not be as bad as I make it out to be, but it wouldn't be worth it to me to help that along.
However, as far as caching goes, if I end up using RC I will be submitting patches to have memcached handle all the caching rather than files or databases.
-- Christopher A. Watford christopher.watford@gmail.com http://dorm.tunkeymicket.com http://www.theroadtrip2005.com