From owner-freebsd-isp Fri Apr 5 17:29:09 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA27282 for isp-outgoing; Fri, 5 Apr 1996 17:29:09 -0800 (PST) Received: from okjunc.junction.net (root@okjunc.junction.net [199.166.227.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA27261 Fri, 5 Apr 1996 17:29:04 -0800 (PST) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id RAA14348; Fri, 5 Apr 1996 17:39:53 -0800 Date: Fri, 5 Apr 1996 18:27:19 -0800 (PST) From: Michael Dillon To: freebsd-isp@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: Recommendation Needed for server setup In-Reply-To: Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Apr 1996, Alan Batie wrote: > about once a month (well, maybe a quarter). If all the crackers are > poking at sendmail and ignoring smail, that's still a good reason to > use in my book. Besides, the main reason I run it is that you can > actually configure it without a configuration compiler and a personal > guru :-) If anyone is seriously considering switching to smail, you should also have a look at smapd from the TIS firewall toolkit at ftp.tis.com. SMAPD acts as an SMTP proxy giving hackers nothing to poke at. It passes the mail over to sendmail for the normal processing. This way, sendmail only talks to the simpleminded and well-known smapd which is totally under your control. Michael Dillon Voice: +1-604-546-8022 Memra Software Inc. Fax: +1-604-546-3049 http://www.memra.com E-mail: michael@memra.com