Your email address seems to be broken ;) I tried from different networks. rcpt to:<[EMAIL PROTECTED]> 550 Relay denied -d
The original message was received at Sun, 8 Apr 2001 14:48:51 -0700 from [EMAIL PROTECTED] [208.179.59.198] ----- The following addresses had permanent fatal errors ----- <[EMAIL PROTECTED]> (reason: 550 Relay denied) ----- Transcript of session follows ----- ... while talking to host1.xmailserver.org.: >>> DATA <<< 550 Relay denied 550 5.1.1 <[EMAIL PROTECTED]>... User unknown <<< 503 Bad sequence of commandsReporting-MTA: dns; james.kalifornia.com Arrival-Date: Sun, 8 Apr 2001 14:48:51 -0700 Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.1.1 Remote-MTA: DNS; host1.xmailserver.org Diagnostic-Code: SMTP; 550 Relay denied Last-Attempt-Date: Sun, 8 Apr 2001 15:00:03 -0700
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.
