PF skrev: > Hi there. I wander if anyone could recommend a minimal hardware requirement > for running TSL 3 as in IMAP mail server and the best way to choose qmail > vs. Postfix and Courier vs. Cyrus vs. uw-imap. I am looking to support up to > 150 light-medium users.
I got 250 users on a Intel(R) Xeon(TM) CPU 3.20GHz, 1GB RAM. Handles about 500 emails a day. The box does IMAP (courier), SMTP (with spamassassin/amavisd/clamav/sqlgrey), HTTP (not too busy), and runs cacti with 4k items. Cacti eats most CPU and is not relevant to your setup. The average CPU-load is less than 10%. It uses 2MB of swap right now, so I will probably be adding some RAM (mysql, clamd, amavisd uses most memory). Since we switched to IMAP users have stored 11GB of email. The figure has been stable for the past 3 months, but has fluxed a tiny bit over in June. 100 of these 250 are officeworkers that have their email client constantly running. I use Courier, mainly because Cyrus can be bothersome to set up and I was on a tight schedule. In hindsight I would have preferred Cyrus because of shared mailboxes (IIRC). > What I would also like to know is a typical backup/recovery procedure in the > event that such a server had to be rebuilt. I'm particularly interested in > knowing what happens to a user's (MS Outlook/Outlook Express) mail if the > server is rebuilt (like is there a way that the client cached messages can > go back to the server?) I backup config and user email. Not sure I follow you on this one. With IMAP all mail is stored on the server. Rebuild it and it's there. RAID-5 is my main line of defense, with hot spare. > > Finally a totally non TSL or linux related question. Does anyone know of a > way(s) that using W2K3 server you could "push" a user's e-mail settings to > their Outlook/Outlook Express? As we are stuck with Office 2k I haven't looked into how this is possible with Outlook. The way I do it is deploy a new machine through RIS and include default settings for Express. When a user starts the application a short wizard appears and asks for name, email and password. Works decently and support via phone completes it. There might be a Group Policy template for it, I don't know. I made a short guide for my users and then traveled each location and was availible for support at predetermined times. This worked well, and only the overly scared ones bugged me. > Thanks! > > > _______________________________________________ > tsl-discuss mailing list > [email protected] > http://lists.trustix.org/mailman/listinfo/tsl-discuss
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
