Scott, I appreciate your help here, by the way. Just for clarity, though, Nextlink is our ISP and *.nextlink.net is what you would get from a reverse lookup on our IPs - although I did get them to create a PTR record for our email server so that 64.50.28.126 returns mail.uhsweb.com.
We use Watchguard, which does have some default behaviors that I can't seem to change. I was not aware that it was changing the way smtp answers, though. When I go to a command prompt and telnet to my email server on the other side of the firewall (optional or "de-militarized zone"), I see the following response: 220 X1 [EMAIL PROTECTED] ready! Is that not what you see from the outside? Joseph Marlin Director of Information Technology Unified Health Services -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry Sent: Monday, December 31, 2001 12:22 PM To: [EMAIL PROTECTED] Subject: RE: [IMail Forum] Declude DNS report on IMail server >Like many other companies, our block of IP addresses is owned by our current >ISP. Thus our "real" host names are all *.nextlink.net. But we own our >domain name, and we are who we claim to be, so that is the source of our >"forging". No. It's fine for your mail server to claim to be "smtp.nextlink.net", or for your reverse DNS entry to point to smtp.nextlink.net (assuming that your ISP doesn't mind). It's also fine for your to have your mail server claim and reverse DNS entries to be smtp.example.com (where example.com is your domain). The problem is that your mail server is claiming to be "SMTP". Not "SMTP.nextlink.net" or "SMTP.example.com", just "SMTP". Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
