From owner-freebsd-questions@FreeBSD.ORG Thu Dec 21 18:02:27 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D2F9C16A494 for ; Thu, 21 Dec 2006 18:02:27 +0000 (UTC) (envelope-from ggroth@gregs-garage.com) Received: from mail.gregs-garage.com (h-64-105-8-34.chcgilgm.covad.net [64.105.8.34]) by mx1.freebsd.org (Postfix) with ESMTP id 7B38113C45A for ; Thu, 21 Dec 2006 18:02:27 +0000 (UTC) (envelope-from ggroth@gregs-garage.com) Received: from [192.168.0.150] ([192.168.0.150]) (authenticated bits=0) by mail.gregs-garage.com (8.13.8/8.13.8) with ESMTP id kBLHQfi7039453 for ; Thu, 21 Dec 2006 11:26:41 -0600 (CST) (envelope-from ggroth@gregs-garage.com) Message-ID: <458AC3C3.5040703@gregs-garage.com> Date: Thu, 21 Dec 2006 11:26:27 -0600 From: Greg Groth User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <45891D18.8010205@chamonix.reportlab.co.uk> In-Reply-To: <45891D18.8010205@chamonix.reportlab.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on mail.gregs-garage.com Subject: Re: small mail server 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: Thu, 21 Dec 2006 18:02:27 -0000 Robin Becker wrote: > I'm looking for some advice on using one of our existing freebsd 6.x > servers as > a mail server for a small number (<20) of users. > > Our existing provider gives us > > 1) pop3/IMAP for reading mail > 2) SMTP for sending, but we need to read mail before using smtp; I guess > this implies we don't need to authenticate directly. > 3) web based interface for adding users and redirections etc etc > 4) spam filtering (presumably based on their large user mail volume). > 5) white/grey listing > 1. If your users save a lot of mail on the server, check out Dovecot (or any of the IMAP servers that use Maildir). I started with IMAP-UW, but the response time on web frontends for users with large Inboxes was dismal. IMAP-UW is simple as an anvil as far as getting it up and running, Dovecot requires a tad more work. While setting up either one of these is trivial, converting existing formats to another (Mbox to Maildir) is not, choose wisely now, and save yourself a headache down the road. 2. Pick your poison. I've been using Sendmail for years and find it simple for small installations such as mine, and found Postfix confusing simply because of my familiarity with Sendmail, YMMV. 3. a. IMHO, simplest web front end for email - Squirrelmail b. My personal favorite web front end for email - Horde c. Web front end to add users, only Webmin comes to mind. (Webmin is for server administration only. There is a companion for users called Usermin that has an email frontend, but I didn't care for it all that much - YMMV) 4&5. spamassasin. White listing is a breeze. I never tried grey-listing, although it's my understanding that spamassasin can do this as well. A couple of other things that you may not have thought about regarding off-site access. Currently we need to allow our users to be able to send remotely. In order to do this, we needed to do two additional things, set up SASL for SMTP authentication was the first - so we didn't have an open relay. Second - we ran into an issue with the ISPs of certain users blocking the SMTP port. We installed stunnel for SMTPS, which isn't currently being blocked, and no issues so far. Another thought is to investigate any software you plan on installing with the email client your users have on their desktops. I currently have everyone using Thunderbird, which plays nice with everything I've installed on the server. Clients such as Outlook can have issues with certain software, and workarounds have to be implemented. Once you choose an MTA or IMAP server, google around and make sure you know what you're getting into in regards to your mail client. Best regards, Greg Groth