[Karl Prince]
Anyway moving on, the quality of HELO's is a major
issue, particularly from sites using Active Directory
and Exchange.
...
So I propose that FQDN HELO's ending in .local are not
processed, including the bounce scenario, (unless the
connecting IP is defined as local)
Fixing the external HELO name used by Windows & Exchange 2000/2003 SMTP
takes 30 seconds. Perhaps we should document this somewhere on the
"administrators guide" as a necessary step before publishing (if you run
Windows)?
Something like this maybe:
-----------------------------------
If you run Windows or Exchange SMTP servers:
Your mail servers might actually be using your internal Active Directory
domain name when communicating with the outside world. You need to
ensure that all of your mail servers issue the proper domain in order
for SenderID to work.
To change this setting for non-Exchange Windows SMTP servers:
1) Open up IIS manager,
2) Expand the list of items under your server.
3) Right-click on your SMTP server (usually called "Default SMTP
virtual server"), then choose properties.
4) Click on the delivery tab.
5) Hit the Advanced button.
6) In the "masquerade domain" box, type in the fully-qualified
domain
name of that mail sever as it is seen from the outside
world in
your public DNS servers. For example, if your public
internet
domain is example.com, then this would probably be set
to something
like "mail.example.com" or "smtp.example.com".
7) Save your changes by clicking on OK on all windows still
open.
If you run Exchange server, the SMTP settings are moved into the
Exchange system manager, under the protocol section for each server. The
steps to change the domain are the same, once you find your SMTP server
in Exchange system manager, proceed with steps 3-7 above.