From owner-freebsd-security Sun Jan 13 17:17:40 2002 Delivered-To: freebsd-security@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-168.zoominternet.net [24.154.28.168]) by hub.freebsd.org (Postfix) with ESMTP id E4E1537B400 for ; Sun, 13 Jan 2002 17:17:37 -0800 (PST) Received: from topperwein (topperwein [192.168.168.10]) by topperwein.dyndns.org (8.11.6/8.11.6) with ESMTP id g0E1HRG76659 for ; Sun, 13 Jan 2002 20:17:27 -0500 (EST) (envelope-from behanna@zbzoom.net) Date: Sun, 13 Jan 2002 20:17:22 -0500 (EST) From: Chris BeHanna Reply-To: Chris BeHanna To: Subject: Re: smtpproxy In-Reply-To: <20020112005425.GA69702@pc5.abc> Message-ID: <20020113201536.G76617-100000@topperwein.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 12 Jan 2002, Nicolas Rachinsky wrote: > I'm looking for a smtpproxy or something similar to accept mails via > smtp on the firewall and forward them to the internal sendmail. > > It should be as simple as possible, there would be very low traffic > some mails per day (some mails per hour maximum). And there should no > exploitable bugs, of course ;-) > > I'm looking for such a thing because I don't want to expose the > internal sendmail to the bad outside world. You will lose the anti-spam capabilities of sendmail in the process. To me, those are of considerable value. Others have pointed out postfix, smtpd, smapd, and the like. If you're really hard-up and don't like any of those, then you need to write your own smtpd. In concept it's easy, but getting it tight and secure is the hard part. -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message