From owner-freebsd-isp Mon Sep 18 2:12: 3 2000 Delivered-To: freebsd-isp@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id C0F5237B424 for ; Mon, 18 Sep 2000 02:11:58 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13awx8-000ILk-00; Mon, 18 Sep 2000 11:11:06 +0200 Date: Mon, 18 Sep 2000 11:11:06 +0200 From: Neil Blakey-Milner To: sthaug@nethelp.no Cc: bvt@zenon.net, alex@aspenworks.com, freebsd-isp@freebsd.org Subject: Re: I-Mail on NT equivalent for FreeBSD? Message-ID: <20000918111106.A70503@mithrandr.moria.org> References: <20000918105913.A70395@mithrandr.moria.org> <56633.969267873@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <56633.969267873@verdi.nethelp.no>; from sthaug@nethelp.no on Mon, Sep 18, 2000 at 11:04:33AM +0200 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon 2000-09-18 (11:04), sthaug@nethelp.no wrote: > > qmail, ezmlm, vchkpw, qmailadmin, courier-imap, and some other little > > bits can build something that rivals CommuniGatePro. I tend to do the > > ezmlm stuff with ezmlm-web though (that may be because I had a little to > > do with testing and developing it). > > > > For the ssl stuff, I put sendmail-tls in front of qmail for tls over > > smtp, and stunnel for smtps. There's also a tls patch for qmail around > > somewhere to do it internally, and for sending smtps. Courier-IMAP > > supports TLS now, and you can put a stunnel in front of qmail-pop3d for > > pop3s. > > > > The stuff isn't perfectly there yet (at least not three or four months > > ago when I looked at it), but it's definitely something you can hack on > > for a short time and get it to behave exactly the way you want. > > The question is, how much time do you need to setup and maintain this? Now, it's just a matter of installing qmail, courier-imap, ezmlm-idx, and ezmlm-web from ports, and then installing qmailadmin and vchkpw by hand. They're both well documented. Putting the stunnel stuff in front is really easy. If you need TLS smtp (not common), you need to download sendmail-tls, and change two lines (which you can get from me). Then you have working basic web-configurable system. I'm working on ports for qmailadmin and vchkpw, so it may soon be even easier. Oh, and for sendmail-tls, if I ever remember to email the author about something. > We run both CommuniGatePro and postfix here (for somewhat different > purposes), and are happy with both. We concluded that CommuniGatePro was > worth it, even if it's definitely not free. It took me less than two days part-time to whip up the replacement for CommuniGatePro for my (ex-)company, and it was well worth the money saved. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message