RE: Checking NDR

2002-10-30 Thread Tom Meunier
It's saying that when it does a reverse DNS lookup of 64.45.174.203, it expects to see the name that was presented in the HELO line, ie msexpkce.pkce.com. However, it's seeing 64.45.174.203.cypresscom.net and therefore deciding it's a forged communication. C:\nslookup 64.45.174.203 Server:

RE: Checking NDR

2002-10-30 Thread Roger Seielstad
That very easily could be a misconfiguration on their end. -- Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA -Original Message- From: Rachel Pickens

RE: Checking NDR

2002-10-30 Thread Daniel Chenault
Cornerstonesurveying is doing rDNS; the FQDN your server is sending out does not match the IP address in DNS. -Original Message- From: Rachel Pickens [mailto:rpickens;pkce.com] Sent: Wednesday, October 30, 2002 9:59 AM To: Exchange Discussions Subject: Checking NDR Hello All, can you

RE: Checking NDR

2002-10-30 Thread Rachel Pickens
: Wednesday, October 30, 2002 10:20 AM To: Exchange Discussions Subject: RE: Checking NDR It's saying that when it does a reverse DNS lookup of 64.45.174.203, it expects to see the name that was presented in the HELO line, ie msexpkce.pkce.com. However, it's seeing 64.45.174.203.cypresscom.net

RE: Checking NDR

2002-10-30 Thread Andrey Fyodorov
It looks like you don't have reverse DNS and the remote machine does not like that. Or it maybe that your server's name as supplied in the HELO is different from the reverse DNS value, I have seen some mail servers that don't like that. -Original Message- From: Rachel Pickens