Hi Jake,
The data center I rent is offering storage area network (SAN), 10GB. If
I load the /home/vpopmail directory in the SAN, will qmailtoaster be
able to work with that?
Best wishes,
Edwin
Jake Vickers wrote:
Edwin Casimero wrote:
Hi,
I have an inquiry to handle 10,000 email addresses.
I'm thinking 500 MB to 1,000 mb per email address.
Can QmailToaster handle 10,000 email addresses?
I am also thinking of the hardware specifications.
If at 500 MB per email address, easily I will need 5,000 GB of hard
drive space.
What kind of server will I need?
The traffic generated? Will 1 qmailtoaster on 1 super server do?
Will 64bit be needed?
Anyone who is managing such a monster right now share his story?
I've set up machines for ISPs that meet your requirements. First
thing you need to do is sit down for a day (at least) and plan this
all out. Think of your needs (and the needs of your users) 12 months
down the road, as well as 24 months and beyond. Will the user base
expand? By how much? You don't want to have to completely rebuild the
whole thing (and all the pains of moving email accounts, messages,
etc. associated with this) because of short sightedness.
You'll need strong hardware. I do not set up any 64 bit machines
since I do not see any benefits from this setup and only problems with
packages, compiling, compatibility, etc., that do not outweigh any
performance boost you'd get from 64 bit.
You will definitely need to setup mysql for a high load. The stock
mysql is not set up for this in any way, shape, or form. You also
need to look at setting up apache for high loads if you plan on users
using webmail as well. I would not run too many/any web pages off of
a mail server set up for this type of environment. If you're talking a
load like that, then you have the funds to put your websites on a
separate server.
If the users will be using IMAP, then you need to REALLY look at your
infrastructure. Courier is not set up for anything other than a small
office/home office by default and will really need tweaking.
In the past when I set up systems like this I normally went with
clustering. Share a common backend and the have multiple front end
machines accepting mail/delivering mail and all serving webmail. Each
machine you put in the cluster will decrease the load point by a
compounding factor. 2 machines decreases the load on each machine by
1/2, 3 by 1/3, etc. This also makes drive space easier in the event
you want to increase space at a later date. 2 machines running NFS
and replicated on a constant basis would allow you to either add
drives (depending on your setup) on the fly whenever needed.
Anyway, long and short of it, make sure you have it all planned out.
I've set up ISP style arrays with multiple machines that served (at
the time, no idea what they're running now) hundreds of thousands of
users. Qmail can handle it, as can any MTA. It all depends on how
well it was planned out and built for.
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
