To: [email protected] [Fwd: Returned mail: see transcript for details]
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.:
Quoted 1 line
Quoted 1 line
Quoted 1 line
DATA
<<< 550 Relay denied
550 5.1.1 <[email protected]>... User unknown <<< 503 Bad sequence of commands
Most MTAs already have capabilities developed to grant or revoke relay access based upon IP or host mask.
-d
Quoted 16 lines · Davide Libenzi
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.