Yahoo is blocking even sending email from them TO my domain.

Here is a copy of the error:

Message from yahoo.com.
Unable to deliver message to the following address(es).

<angelos@waxpo.com>:
209.152.172.192 does not like recipient.
Remote host said: 550-Verification failed for <adosoulas@yahoo.com>
550-Unrouteable address
550 Sender verify failed
Giving up on 209.152.172.192.

--- Original message follows.

Return-Path: <adosoulas@yahoo.com>
Message-ID: <20040309182250.60661.qmail@web11301.mail.yahoo.com>
Received: from [24.193.73.134] by web11301.mail.yahoo.com via HTTP;
Tue, 09 Mar 2004 10:22:50 PST
Date: Tue, 9 Mar 2004 10:22:50 -0800 (PST)
From: Angelos <adosoulas@yahoo.com>
Subject: yo
To: angelos@waxpo.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

man

I am not sure what to make of it. I can also not send mail to yahoo accounts.

Thx,
angelos

XX

We have a problem with server's reverse dns record(ptr).
We're fixing this right now.

XX

If you'll go to the http://dnsstuff.com/tools/ptr.ch?ip=209.152.172.192
you'll see the following:



As you can see there is an error at ns2-slip.net
It is not our network so we can't fix this. We're trying to contact them but still didn't get any result.

Will keep you informed.

So what's the deal?


is there an ETA on when silpnet can start receiving Yahoo emails?

We hope it will be soon

Would this also be the cause of sending to and from AOL?

Yes, probably it would.

Do we have an update on the status of this, or an ETA from slipnet?

This is getting pretty annoying.

Unfortunately we can't promise anything 'cause it is not our company

Don't they have a contract with you that binds them to supply reliable service? Just like your contract with us.. *wink wink*.

It IS getting very annoying, and it's been going on for quite a while too. The sent mails bouncing back I can sort of manage to send back manually from my own ISP, but there's a bunch of mails I'm not receiving and I don't even know about it. Perhaps there is a number or URL where we can bug them then, if they are to blame?

*turns up the heat one more notch*

It appears that COX.NET has the same issue. Since the users of your service cant make the change, or have any affect on this we need you "hostony" to work on getting this resolved ASAP.

Thanks,
Tom

It's been a week since the problem was brought up here, and a few more since it actually started manifesting. I understand you are not directly responsible for it, but at this point an estimate better than "ASAP" would be quite welcome. Or a status update. Or both.

We're talking about yahoo.com, aol.com, rr.net, cox.net, bellsouth.net, so far.. That's a significant portion of the possible emails out there for which we have all but ceased to exist.

slip.net was resolving our PTR DNS record earlier.
So I supposed to think that this issue is temporary.

A few weeks, temporary??

Does that mean you're expecting the issue to resolve itself soon, or steps have been taken to put pressure on them too? A DNS record only takes a day or two to propagate, what's taking them so long?

We've added PTR record to this server.
Please check email now

Yahoo.com emails are working! I guess I'll check the others over time

Thanks!

Edit (Update): Some are still failing:

<removed>@aol.com
retry time not reached for any host after a long failure period
<removed>@aol.com
retry time not reached for any host after a long failure period
<removed>@cfl.rr.com
Unrouteable address
<removed>@bellsouth.net
Unrouteable address

Not sure if it's a DNS propagation issue, but the reverse DNS lookup with dnsstuff is still failing, too.
http://dnsstuff.com/tools/ptr.ch?ip=209.152.172.192

http://www.dnsstuff.com/tools/ptr.ch?ip=209.152.171.253