>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".
>How do most people in a similar situation handle this? I did make a change
>in the mail server's IMail registry settings to change the host name to
>mail.uhsweb.com instead of the nextlink.net entry.
That won't make a difference -- IMail isn't answering the SMTP port. You
need to find out what is (a firewall or another mail server in front of
IMail, most likely).
>I don't like seeing the nextlink.net in all of our transactions. I prefer
>to see our own domain
>name - our business name - whenever possible.
That's not a problem -- the problem right now is figuring out what is
answering on port 25 (the SMTP port). It isn't IMail.
-Scott
---
Declude: Anti-virus, Anti-spam and Anti-hijacking solutions for
IMail. http://www.declude.com
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
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/
