From owner-freebsd-questions@FreeBSD.ORG Sat Jan 28 15:03:30 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EF2D106566B for ; Sat, 28 Jan 2012 15:03:30 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [99.69.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id CFBFF8FC0C for ; Sat, 28 Jan 2012 15:03:29 +0000 (UTC) Received: from vixen42.vulpes.vvelox.net (vixen42.vvpn.vvelox.net [10.69.0.2]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id E76E53F5B4 for ; Sat, 28 Jan 2012 09:04:48 -0600 (CST) Date: Sat, 28 Jan 2012 09:04:02 -0600 From: "Zane C. B-H." To: freebsd-questions@freebsd.org Message-ID: <20120128090402.087e7128@vixen42.vulpes.vvelox.net> In-Reply-To: <1fd6a9d732998ec0a9f3227e77bc9e1c.squirrel@pop.pknet.net> References: <1fd6a9d732998ec0a9f3227e77bc9e1c.squirrel@pop.pknet.net> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: email hosting - How do you do it? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2012 15:03:30 -0000 On Thu, 26 Jan 2012 15:51:05 -0700 "Peter" wrote: > Hello, > I've been on qmail/vpopmail combo forever and am looking to build > a new, mail server. As some one who has was once a unix admin for a ISP that ran Qmail for a SMTP server, I can safely say you should avoid it like the plague. Managing it is a bloody PITA given how incomplete it is in so many ways. > First choice so far is postfix, but almost all the virtual hosting > 'howtos' require an SQL database, or editing files by hand. The SQL > part seems like an overkill for ~20-50 email accounts, the editing > files by hand seems like a pain and requires me doing everything > but I'd rather let people manage their own domains. Postfix is a great choice. A lot more manageable than Qmail and it is pleasantly fast, easy to configure, and integrates nicely with Dovecot. If you are just dealing with a single domain, I would strongly suggest looking into just using system users. This works fairly nicely and you can lock down access via PAM. In regards to authentication, you will need to look into something other than the master.passwd stuff authentication as that is only usable as root. I would strongly suggest LDAP. In regards to managing users/groups in LDAP I would suggest sysutils/p5-Plugtools . It is something I wrong awhile back and maintain, so if you have any requests for add on to, please just let me know. > Just curious on how everyone else does small/medium/large email > hosting so that the users have an easy option to change passwords, > manage their domains, quotas, vacation auto responders, etc. ? My setup involves... backend - The backend server runs LDAP and has a nice bit of disk space shared via NFs. frontend - The frontend servver runs all the external facing stuff, webmail(horde), more web stuff, Dovecot(POP3/IMAP/Sieve), and Postfix(SMTP). NFS - Used for sharing home directories. LDAP - Used for authentication, addressbooks, and user/groups. Dovecot - Use for POP3/IMAP/Sieve. Postfix - Used for SMTP. syslogd - Used for centralized logging for logging from the frontend to the backend. Horde - It makes a truely kick ass webmail system. It is nice as allows easy integration of Sieve and LDAP addressooks. ZFS/gmirror - Gmirror backed ZFS pools work really nicely for if you need large amounts of storage.