Original message below:
----------------------
Message: 4
Date: Tue, 18 Feb 2003 16:01:56 -0500 (EST)
Subject: Re: [SM-USERS] Replacement for UW-IMAP
From: "Rick Castello" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
If you'll search the archives listed at the bottom of each message
to this list, you'll see that many others have asked this same
question.
The responses vary, from Konstantin's excellent QVCS (QMail-Vmailmgr-
CourierIMAP-SquirrelMail) install [http://qvcs-guide.sourceforge.net/]
to other options.
Try the search, there's good stuff there.
-Rick
-------------------------
My question:
In the guide mentioned above (the Redhat version of the guide), in section
11.1, it states:
"11.1 Why this is not recommended for large systems
The only reason this is not recommended for large systems is because
Squirrel-Mail is currently not very scalable � you cannot easily run it on
a server farm, since both SquirrelMail and Vadmin save their preferences
onto the HDD (a trade-off for not requiring a database engine). However,
if you decide not to use SquirrelMail/Vadmin, then Qmail-VmailMgr-Courier
is definitely a strong enough solution to be run on high-demand servers,
but this has its own set of requirements and is not covered under this
guide."
I want to know how to design a system such as this that _is_ scalable, and
squirrelmail being a part of it is a must. How would I design a system
that is scalable to many thousands of users using SM?
Thanks in advance,
=Rob
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
--
squirrelmail-users mailing list
List Address: [EMAIL PROTECTED]
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id)95
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
