On 02:14 PM 1/16/01, Vincent Poy wrote:
>On Tue, 16 Jan 2001, Byron Lunz wrote:
>
>> For the last week or so, we've had several thousand messages queued for
>> delivery to @home.com addresses. Some subscribers are complaining of
delays
>> in getting list messages. Does anyone know what's going on (or not going
>> on) @home.com?
>
> I have no idea except do traceroutes work to @home's backbone for
>you? Yesterday, @Home will not talk to AT&T WorldNet (ip.att.net).
On the inet-access list last week, in a thread regarding @home mail
delivery issues, there were several relevant posts:
>I haven't had any problem with IP traffic to their servers, but
>for several days was getting "Access denied" messages while talking
>smtp to their mail servers. It was as if they had selectively blocked
>my mail server from sending them mail, including email from my domain
>and from various of my clients' domains.
>
>I found their listed "whois" info was not very helpful for contacting a human
>there, and didn't receive responses to voicemail messages, and email message
>sent from elsewhere, or even a fax I sent them, inquiring about what the
>problem was.
>
>A day or so later the problem stopped, however I never did hear from them.
and
>Here's another problem they have quite often:
>
><[EMAIL PROTECTED]>: host mx-a-east.mail.home.com[24.2.2.192] said: 452
>4.4.5 <[EMAIL PROTECTED]>... Insufficient disk space; try
>again later
jc
