Attn:AT&T Postmaster
Irwin Lazar
ILazar at burtongroup.com
Fri Feb 1 18:59:57 UTC 2002
If there is an AT&T postmaster responsible for "attrh3i.attrh.att.com" or
"wsscan.att.com" out there, please respond to me off-list. Your server is
sending the below error message to mpls-ops at mpslrc.com
<mailto:mpls-ops at mpslrc.com> , but the error message doesn't identify the
offending account so short of removing all AT&T accounts, I'm at a loss as
to how to fix it.
I've sent numerous messages to postmaster at att.com
<mailto:postmaster at att.com> have not received a response.
X-POP3-Rcpt: mplsrc12 at mplsrc.com
Date: Fri, 1 Feb 2002 12:56:01 -0500
X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to
mpls-ops-request at mplsrc.com using -f
X-From_: Fri Feb 1 12:55:57 2002
Old-Date: Fri, Feb 1 2002 12:54:45 EST
From: MAILER-DAEMON at attrh3i.attrh.att.com
To: mpls-ops-request at mplsrc.com
Subject: Message status notification
X-Diagnostic: Mail coming from a daemon, ignored
X-Diagnostic: Possible loopback problem
X-Envelope-To: mpls-ops-request
The mail routing agent encountered the following class of error:
No entries found in directory for query
----- Original Message Text Follows -----
Received: from wsscan.att.com (135.71.63.10) by attrh3i.attrh.att.com
(5.5.029)
id 3C06950500ECC026; Fri, 1 Feb 2002 12:54:43 -0500
Received: by wsscan.att.com; id MAA04196; Fri, 1 Feb 2002 12:55:33 -0500
(EST)
Received: from almsi2.proxy.att.com(192.168.108.71) by cyrus0.wsscan.att.com
via csmap (V4.1)
id srcAAAoCaqmi; Fri, 1 Feb 02 12:55:33 -0500
Received: from host.secure4-hosting.net ([209.239.41.31])
by almsi2.proxy.att.com (AT&T IPNS/MSI-3.0) with ESMTP id
g11HtXV24334;
Fri, 1 Feb 2002 12:55:34 -0500 (EST)
Received: (from mplsrc12 at localhost)
by host.secure4-hosting.net (8.10.2/8.10.2) id g11HtXm19174;
Fri, 1 Feb 2002 12:55:33 -0500
Resent-Date: Fri, 1 Feb 2002 12:55:33 -0500
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20020201/1894e255/attachment.html>
More information about the NANOG
mailing list