Return-Path: Received: from blue-labs.org (david@Huntington-Beach.Blue-Labs.org [208.179.59.198]) (authenticated (0 bits)) by james.kalifornia.com (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f38Lmol6027750 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for ; Sun, 8 Apr 2001 14:48:51 -0700 Message-ID: <3AD0DCC2.1020901@blue-labs.org> Date: Sun, 08 Apr 2001 14:48:50 -0700 From: David User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3-pre8 i686; en-US; 0.8.1) X-Accept-Language: en MIME-Version: 1.0 To: Davide Libenzi Subject: Re: goodbye In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Most MTAs already have capabilities developed to grant or revoke relay access based upon IP or host mask. -d Davide Libenzi wrote: > I had the same problem of shifting down along the mail chain the knowledge of > the incoming IP address. > We develop VirusScreening and ContentFiltering MTA ( and appliances ) that > usually goes in front of customers MTA. > By putting our MTA in front of the customer MTAs chain We hide the peer IP > address to MTAs that comes next in the mail chain. > Our MTA uses a new ESMTP command : > > XRMTIP remote-ip-address > > to let customers MTA to know the remote IP address and let them to take all > relay and generic permissions decisions about the mail path. > We're going to distribute patches for most common MTAs like qmail, sendmail, > exim, XMail and postfix. > The patch rely on the presence of a file ( /etc/xrmtip.hosts ) that list the IPs > from which the XRMTIP command sould be accepted.