15 messages in net.sourceforge.lists.courier-usersRe: [courier-users] World domination ...
FromSent OnAttachments
Sam VarshavchikMar 19, 2003 9:30 pm 
Eduardo RoldanMar 20, 2003 8:00 am 
Mitch (WebCob)Mar 20, 2003 9:35 am 
Gordon MessmerMar 20, 2003 9:57 am 
Jon NelsonMar 21, 2003 6:28 am 
Daniel HigginsMar 21, 2003 6:43 am 
Mark ConstableMar 21, 2003 8:27 am 
Peter C. NortonMar 21, 2003 11:11 am 
Gordon MessmerMar 21, 2003 12:53 pm 
Jon NelsonMar 21, 2003 1:37 pm 
Gordon MessmerMar 21, 2003 4:20 pm 
Peter C. NortonMar 21, 2003 5:11 pm 
Sam VarshavchikMar 21, 2003 5:53 pm 
Brian CandlerMar 22, 2003 1:17 am 
Mitch (WebCob)Mar 22, 2003 9:53 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] World domination update.Actions...
From:Daniel Higgins (dhig@netc.net)
Date:Mar 21, 2003 6:43:43 am
List:net.sourceforge.lists.courier-users

while we're on the subject. we currently have about 4000 addresses in the database, running on a (backup) netfinity 3300 (Dual 450 Xeon, 256 megs, 18 Gigabytes in Raid5)

my primary mail server recently blew up (major hardware problems, not courier's fault) and i'm in the process of building a new one. to be sure i'm going for a cluster of servers using CODA as the filesystem backend. has anyone implemented such a cluster?

i know a lot of peoples uses nfs. the problem with nfs is if the primary server goes down you're out of luck. coda's support for disconnected operations and server replication makes it ideal for such a task, especially with the maildir format. i'm a bit concerned about the performances though.

your experiences? does it work? does it not? why?

----- Original Message ----- From: "Gordon Messmer" <yiny@eburg.com> To: "Courier Mailing List" <cour@lists.sourceforge.net> Sent: Thursday, March 20, 2003 12:58 PM Subject: Re: [courier-users] World domination update.

Eduardo Roldan wrote:

On Thu, 2003-03-20 at 02:29, Sam Varshavchik wrote:

Came across the following while browsing:

http://www.cs.helsinki.fi/compfac/ohjeet/posti/uudistus2003.en.html#techni cal

You should add a 'Success Stories' page to courier mta site. :)

Seriously. Maybe a form to submit existent deployments of courier-mta helps new users get confident.

Indeed. Such a thing would have helped me out the first time I tried to migrate to Courier at Real Networks. It would be helpful to have a list of users, and maybe throw in some hardware specs, configuration details, and performance metrics.

This weekend we're replacing a $50,000 machine that's running sendmail with a small cluster running Courier.

The old system is one server running Slackware Linux 8.0, dual 933 Mhz proc, 2GB RAM, 700GB of disk that's mostly unusable, and averages a load of 40-50 during the afternoon.

On the 13th (just to pick a day) there were 74 errors due to insufficient resources (procmail either didn't start or segv'd) and 8944 errors talking to another local sendmail server (the outbound MX) out of 141542 messages total. Only 19611 messages were destined for other mail servers. Delivery times ranged from 1 second to almost 3 hours (the long delays are the result of the procmail errors). The system supports fewer than 1000 users, but is very sluggish and requires a lot of maintenance.

The new system cost about $15000. It is built with an NFS backend running Red Hat Linux 7.3 on a 1TB RAID 5 set attached to a 3ware 7500 card, one 1.8 Ghz CPU and 1GB of RAM. There are two Courier servers configured identically, load balanced with DNS round-robin. Each has an 800Mhz CPU and 500 MB of RAM; they're RLX Technologies 300i blades and they also run Red Hat Linux 7.3. Mail is filtered through spamassassin (spamd) and amavis/OpenAntiVirus. For backward compatibility, POP3 service is provided by qmail-popup with an APOP checkpw. All other mail services (including POP3S) are provided by Courier. User information is stored in an iPlanet directory server. Although these systems have a fraction of the hardware resources, and a good deal of additional processing, we expect their capacity to be 5 to 10 times that of the old sendmail system (our tests indicate so, but real life use may prove different).

If we're still discussing it then, I'll provide performance metrics on the new system after it goes live.

If anyone has any comments on the new system's setup, my managers are interested in feedback from other Courier users.