MailSite Uses Incorrect Hostname When Delivering Messages After upgrading to MailSite version 7, MailSite uses the wrong hostname when delivering to remote servers. Some strict MTA's perform a lookup on the hostname specified and so rejections can occur.

Knowledge base document 10367 provides a detailed explanation on how the hostname is obtained.

• You can identify what name MailSite will use for the hostname simply by opening up a telnet session to the server on port 25
• For example you may see: 220 server1 MailSite ESMTP Receiver Version 7.0.3.29 Ready
• SMTPDA will use 'ehlo server1' when delivering to remote domains

To change this name you can use the windows HOSTS file to specify the name you wish to use (Other solutions such as modifying DNS are suggested in 10367.

• Open Windows Explorer and navigate to
• 'C:\Windows\System32\Drivers\Etc' or 'C:\Winnt\System32\Drivers\Etc'
• Open the file called 'HOSTS'
• Add an entry below 127.0.0.1 Localhost similar to: 192.168.1.100 mail.domain.com
• Save the file
• Restart the Services
• Now when you perform a telnet you should see:
  • 220 mail.domain.com MailSite ESMTP Receiver Version 7.0.3.29 Ready
• SMTPDA will now use 'ehlo mail.domain.com' when delivering to remote domains.

Notes:

• You must be running SMTPRA.exe version 7.0.3.4 or later. You can obtain the latest version by installing the Rockliffe Rollup package available by logging into the Customer Downloads Area
• In the HOSTS file, you should add the IP address(es) that are bound to the local MailSite machine. Even if you are using a NAT, the local bounded IP's should be specified in the HOSTS file.