|
$email_localname [CFG] |
  
|
|
$email_localname [CFG] |
|
Specify E-Mail Local Name
$email_localname line iname
This command specifies the full Internet name (not just the nodename) of the machine being used to transmit e-mail. This name is used on the HELO command used to initiate an SMTP or ESMTP session with a remote mail server.
CopiaFacts begins with the HELO command even if the remote mail transfer agent (MTA) identifies itself as ESMTP, because some MTAs reject the ESMTP command EHLO even though they identify themselves as ESMTP.
The parameters on this command are used as follows:
| line | the line group(s) affected, or * for all lines. Note that this parameter specifies a line group and not a node name. |
| iname | the internet address to use to sign on to the remote MTA. This should either be a fully qualified domain name (for example "copiam1.mycompany.com") or an internet IP address in square brackets (for example "[123.231.213.132]"). If the entry appears to be an IP address without brackets, they will automatically be added. |
Many mail servers will ignore the name supplied, but an increasing number will check it. If not ignored, the supplied name will usually be checked against the name identified in your IP headers. In addition the receiving site may do a reverse DNS lookup to check that there is a registered domain name for the numeric address you quote. It is therefore essential to specify this command with a value which corresponds to that in the IP headers. You must determine the value on the actual machine that is running CopiaFacts to send e-mail. Separate commands, with different line group values, should be used if you have more than one CopiaFacts node sending e-mail.
If you know of a mailserver which always displays on login the value in the IP headers, you can run the EMSETUP program with the name of this mailserver on the command line, and then press the Test button. This will attempt a login to the specified mailserver and display the result. Alternatively if you have a browser installed on the CopiaFacts machine you may visit www.copia.com/ip, which displays the IP headers of the connecting machine.
Make a note of the reported IP address and use it on the $email_localname command. Remember to re-check the address if your network configuration changes, because the address reported may be the address of your firewall or router.
If you fail to supply this command the name used will be the local machine name. In most e-mail transmission scenarios, this will be the wrong name to use; however as indicated above, the remote MTA will often ignore this error. You may be forced to proceed in this way if you connect to the Internet via an ISP which assigns an Internet address dynamically on each connection; however this is not a recommended configuration for sending e-mail from CopiaFacts.
If you have multiple NIC cards and want to use different IP routing for different e-mails, use the $email_node_localnames and $email_node_bindnames commands, which override $email_localname.
It is possible to override this name for specific jobs or specific transmissions using the EMAIL_LOCALNAME system variable, and to select a specific network binding with the EMAIL_BINDNAME system variable. These features are only needed for non-standard applications, and the use of these variables is now deprecated; it is recommended to use the $email_node_localnames and $email_node_bindnames commands instead.
Default: (see above)
Examples:
$email_localname * [123.231.213.132]
$email_localname * "copiam1.mycompany.com"
Topic url: http://www.copia.com/support/refmanual/index.html?$email_localname.htm