|
Mime-Version: |
1.0 |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Mon, 16 Dec 2002 16:23:03 -0500 |
In-Reply-To: |
<3DFDF39D.29242.101EAB3A@localhost> |
Content-Type: |
text/plain; charset="us-ascii"; format=flowed |
Reply-To: |
|
I lookedup MX hosts
1-6,8.
Though I did not try them all, 2-4 were BUSY (telnet port 25), but 1 was
OK. They all had the same MX precedence.
I suggest email to:
[log in to unmask]
and
[log in to unmask]
See also:
https://secure.name-space.com/cgi-bin/whois.pl?whois=ATT2-DOM
At 15:39 12/16/2002 Monday, Paul Karagianis wrote:
>I'm coming up on a 3 day queue for ATT:
>
>$ lscp show queue /sum /dest=*att.net
>SMTP entries:
>-#Rcp. -#Msg ---Size--- MRt -Oldest msg--
------------Destination--------------
> 4412 2121 13261910 1 2 21:41:36 ATT.NET
> 6 6 22328 1 0 05:25:36 POSTOFFICE.WORLDNET.ATT.NET
> 11203 3523 14964264 1 2 23:43:06 WORLDNET.ATT.NET
>------ ----- ---------- --- -------------
-------------------------------------
> 15621 5650 28248502 3 destination(s)
>
>...with the two big problem domains giving the same errors all weekend.
>The following is abbreviated:
>
>$ lscp resolve /connect WORLDNET.ATT.NET
>
>16:31:11 connecting to gateway4.WORLDNET.ATT.NET
>16:31:11 gateway4.WORLDNET.ATT.NET( 0) >>> 450 busy - please try later
>16:31:11 gateway4.WORLDNET.ATT.NET( 0) <<< QUIT
>16:31:11 error writing to network
>16:31:11 status = %SYSTEM-F-LINKDISCON, network partner disconnected
> logical link
>
>
>Everyone else is seeing this too, right? It seems like a suspiciously
>large problem given that I haven't heard anything about it yet.
>
> -Kary
|
|
|