Date: Mon, 17 Apr 2006 14:47:28 -0400 From: Chris Shenton <chris@shenton.org> To: robert <bsd@bathnetworks.com> Cc: Duane Whitty <duane@greenmeadow.ca>, freebsd-questions@freebsd.org Subject: Re: OT - Scalable email server solution needed Message-ID: <86lku411kv.fsf@PECTOPAH.shenton.org> In-Reply-To: <1144484393.9480.5.camel@localhost.localdomain> (bsd@bathnetworks.com's message of "Sat, 08 Apr 2006 09:19:52 %2B0100") References: <443731E5.9030209@greenmeadow.ca> <1144484393.9480.5.camel@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
robert <bsd@bathnetworks.com> writes: > Have a look at qmail, It is very scalable and well supported with > various sites and mailing lists. Iv'e been using it for well over a year > now. Most important thing, IMHO, is uptime. If you use the Maildir mailbox format you can put it on a solid NFS server like a NetApp and front it with any number of MTAs and IMAP servers. Maildir is NFS-safe. If a (used) netApp is too expensive for you, the same approach still keeps your complicated services off your most critical file server. I used qmail-ldap (qmail with LDAP for virtualization) and a handfull of 1U SMTP/IMAP/POP/Squirrelmail servers. Each server had a local read-only replica of the LDAP data sync'd from the LDAP master. Zero downtime in well over a year, even with taking individual boxes down (one at a time) for upgrades and such. You could also look at Vpopmail virtualization for qmail. I've not tried to scale that across multiple boxes so I don't know how you'd replicate the account info.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86lku411kv.fsf>