On Sun, 6 Oct 2002, Tom Coady wrote: > I don't quite know how to resolve a mail server but the mail is actually > routed through Received: from whirlwind.systems.pipex.net [62.241.160.7] for > incoming mail and shockwave.systems.pipex.net for outgoing mail. > Apparently the list accepts from dial.pipex.com but not dsl.pipex.com so > it's not the entire domain that is blocked.
I doubt its resolving issue for dsl.pipex.net (see blow) Its not RBL blocked afaics, it is most likely doing what is becoming every common in teh fight agaisnt spamming gits, and thats force a mail server to resolve to be allowed to pass mail, some, mine included go one step further and require reverse zone entries, these practices again are becoming more prevailant, so get used to it :) Funny redhats box's doesn't accept esmtp, hahaha. ehlo fox.auschat.net 500 5.5.1 Command unrecognized: "XXXX auschat" Now whats interesting..... mail from: [EMAIL PROTECTED] 250 2.1.0 [EMAIL PROTECTED] Sender ok So.. I suggest whatever mail server is trying to talk to redhats is a bit fuzzled, only your admin can sort it from checking the logs to see the errors. Good luck.
