From owner-freebsd-questions Mon Jun 1 10:59:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24650 for freebsd-questions-outgoing; Mon, 1 Jun 1998 10:59:28 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24638 for ; Mon, 1 Jun 1998 10:59:19 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.7/8.8.7) id KAA28227 for freebsd-questions@FreeBSD.ORG; Mon, 1 Jun 1998 10:58:49 -0700 (PDT) (envelope-from dhw) Date: Mon, 1 Jun 1998 10:58:49 -0700 (PDT) From: David Wolfskill Message-Id: <199806011758.KAA28227@pau-amma.whistle.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: Restricting mail server access Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 01 Jun 1998 11:24:43 -0700 >From: Bob Badaracco >Our mail server is running the latest version of Sendmail under FreeBSD >along with qpopper >as the POP3 mail server. We have 10 local accounts on this server and >would like to restrict >external access all together or from specific domains. In other words we >don't want our employees using our mail server address in their browsers >to access company email accounts from their personal >ISP connection. >I've read most of the Sendmail FAQ's and most of the FreeBSD docs >here but don't have a clue >how to handle this. You might take a look at sendmail's ability to use Wietse Venema's "tcp wrappers" package (via "-DTCPWRAPPERS" at compile time). david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message