From: David <david@blue-labs.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: To: davidel@xmailserver.org [Fwd: Returned mail: see transcript for details]
Date: Sun, 08 Apr 2001 15:11:53 -0700 [thread overview]
Message-ID: <3AD0E229.6010807@blue-labs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 132 bytes --]
Your email address seems to be broken ;)
I tried from different networks.
rcpt to:<davidel@xmailserver.org>
550 Relay denied
-d
[-- Attachment #2: Returned mail: see transcript for details --]
[-- Type: message/rfc822, Size: 3768 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 457 bytes --]
The original message was received at Sun, 8 Apr 2001 14:48:51 -0700
from david@Huntington-Beach.Blue-Labs.org [208.179.59.198]
----- The following addresses had permanent fatal errors -----
<davidel@xmailserver.org>
(reason: 550 Relay denied)
----- Transcript of session follows -----
... while talking to host1.xmailserver.org.:
>>> DATA
<<< 550 Relay denied
550 5.1.1 <davidel@xmailserver.org>... User unknown
<<< 503 Bad sequence of commands
[-- Attachment #2.1.2: Type: message/delivery-status, Size: 294 bytes --]
[-- Attachment #2.1.3: Type: message/rfc822, Size: 1745 bytes --]
From: David <david@blue-labs.org>
To: Davide Libenzi <davidel@xmailserver.org>
Subject: Re: goodbye
Date: Sun, 08 Apr 2001 14:48:50 -0700
Message-ID: <3AD0DCC2.1020901@blue-labs.org>
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.
reply other threads:[~2001-04-08 22:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AD0E229.6010807@blue-labs.org \
--to=david@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox