We're running a back end exchange server behind an ISA firewall. We're having issues getting email to one specific domain... the first part we figured out (and already fixed) is that our domain name ended up on a couple of spam lists. (Despite no open relay and an SPF record).
The second part to this mystery is when we do an smtpdiag on the destination server. After "ehlo", we get the response "250-[receivingServername]
Hello [wrongServerName].domain.c
om [IP Address] (may be forged), please to meet you.
The [wrongServerName] part of the response *is* a server in our domain, but is *not* an email server and is behind our firewall. Here's the trick... the [IP Addess] *is* the correct IP. (The external facing NIC on our firewall). The rest of the smtpdiag shows that the smtp connection sends and recives correctly, which makes sense considering the IP is correct. However, it also makes sense that it's getting the "(may be forged)" tag since the server name it's pulling is wrong.
I'm totally confused. Where is it getting the wrong server name from? If I can figure that out, then I presume I can fix it and resolve the (may be forged) tag. I suspect it may also explain how we got on a couple spam lists....
Your help is much appricated,
Kevin
Start Free Trial
