QUOTE
As you can see, Sp@mX came up with "whoever"@CHINANET.CN.NET, while
APNIC has each corresponding recipient as "whoever"@NS.CHINANET.CN.NET.
It looks like Abuse.net has them wrong - again! I'll take a wild guess and say that ChinaNet's DNS service isn't translating CHINANET.CN.NET to NS.CHINANET.CN.NET any more. It used to work, but no more. I'm sorry I don't have any constructive suggestions.
APNIC has each corresponding recipient as "whoever"@NS.CHINANET.CN.NET.
It looks like Abuse.net has them wrong - again! I'll take a wild guess and say that ChinaNet's DNS service isn't translating CHINANET.CN.NET to NS.CHINANET.CN.NET any more. It used to work, but no more. I'm sorry I don't have any constructive suggestions.
Here's the response I got from Abuse.net:
QUOTE
> CHINANET.CN.NET: anti-spam@ns.chinanet.cn.net
What address do you think I have now?
Regards,
John Levine, postmaster@abuse.net
What address do you think I have now?
Regards,
John Levine, postmaster@abuse.net
He apparently thinks he has the correct address. I replied to him with the output from his own database:
QUOTE
Mr. Levine,
Here is the output from your lookup page:
postmaster@chinanet.cn.net (for chinanet.cn.net)
anti-spam@chinanet.cn.net (for chinanet.cn.net)
ctsummary@special.abuse.net (for chinanet.cn.net)
Note that the "ns." is absent following the @.
Sincerely,
Here is the output from your lookup page:
postmaster@chinanet.cn.net (for chinanet.cn.net)
anti-spam@chinanet.cn.net (for chinanet.cn.net)
ctsummary@special.abuse.net (for chinanet.cn.net)
Note that the "ns." is absent following the @.
Sincerely,
It was all very polite, so I'm hoping for a positive outcome. Still, it doesn't inspire hope when the postmaster doesn' check his own database before rejecting an update/correction.