TCPIP-channel-specific options

TCP/IP-channel-specific options
TCP/IP channels  support, in addition to the usual  channel options, a number of TCP/IP-channel-specific  options.1   These TCP/IP-channel-specific options are set in legacy configuration in a channel-specific option file, or in Unified Configuration are set under the channel&#x27;s   option. For instance: msconfig&#x3e; set channel:tcp_local.options.BANNER_PURGE_DELAY 200 Note that in Unified Configuration such channel-specific options (those set under the   option)  are not (currently) schema checked: be careful when setting them as    will not warn of invalid values or syntax as it would for regular channel options! (Nor will  show whether or not such channel-specific options have any default value.)

In legacy configuration, where an option file is used, such an option file must be named    where   is the  name of the channel, and stored in the MTA table directory. Since the name of the default channel for the SMTP server is usually ,  the option file for the SMTP server is usually    on UNIX; similarly, the name of the default channel for the SMTP SUBMIT server is usually   , so the option file for the SMTP SUBMIT server is usually.

For incoming messages, such TCP/IP-channel-specific options are actually options for the server (SMTP, SMTP SUBMIT, or LMTPSS) as a  whole. In particular, the only TCP/IP-channel-specific options that matter for incoming  SMTP submissions are those for the SMTP server&#x27;s default channel, not  any channel options for possible other channels that may putatively  handle the incoming message due to a     channel option based "switching". Thus for instance in a typical configuration, for all incoming SMTP messages to port 25, it is only  the channel-specific options set under    that matter (in legacy configuration, only the    file that matters); similarly, the  channel-specific options set under    affect all SMTP SUBMIT submissions (in legacy configuration, the   file affects all SMTP SUBMIT  submissions); and the channel-specific options set under   affect all messages accepted by the LMTP server (in legacy configuration, the   file affects all  messages accepted by the LMTP server). Any other channel-specific options (in legacy configuration, any other   file(s)) would only be potentially relevant  for outgoing SMTP or LMTP messages---only affect SMTP or LMTP client  operation.

Note that while master channel programs (the outgoing channel direction or SMTP client) read their option file each time they run and usually  do not keep running for an especially long time, a slave channel  program (each SMTP, SMTP SUBMIT, or LMTP server process) reads its options (in legacy configuration, its  option file) only when it is first started, hence will not see changes  while it continues to run, and its running time may be on the scale of  hours. Server processes do automatically shut down periodically, and the Dispatcher  creates new server processes in replacement, as  required; so changes affecting server processes can get seen  eventually, even in the absence of an explicit restart of the relevant  server processes---but the change is likely not to take effect  "quickly" in the absence of an explicit restart.

Note also that as of Messaging Server 7.0, TCP/IP channel option files for SMTP channels and  LMTP client channels (but not yet LMTP server channels) are  incorporated as part of a compiled configuration, if one exists. So as of Messaging Server 7.0, if a compiled configuration exists, it is necessary to  recompile to get changes seen: Then, no different than ever, when it is important or essential to get changes to take effect quickly, as opposed to waiting for  existing server processes and channel delivery processes to naturally age, executing will restart (the otherwise often quite long-running) SMTP, SMTP SUBMIT, and LMTP server processes; and see the     utility&#x27;s   and   commands, or alternatively its   and   commands, which may be used to  force  quick replacement of the (usually relatively short-lived in any case)  SMTP and LMTP client processes (master channel jobs).
 * 1) imsimta cnbuild
 * 1) imsimta restart &#x2a;

 1Most of the options described         actually relate to the SMTP protocol itself, rather than to the TCP/IP          transport. As such, other MTA channels that use the SMTP protocol over         other transports may have similar options.

See also:
 * switchchannel Option
 * cnbuild utility
 * restart utility
 * qm utility
 * PERMANENT_ERROR_STRING_552
 * ALLOW_ETRNS_PER_SESSION
 * ALLOW_RECIPIENTS_PER_TRANSACTION
 * ALLOW_REJECTIONS_BEFORE_DEFERRAL
 * ALLOW_SESSION_BLOCKS
 * ALLOW_TRANSACTION_BLOCKS
 * ALLOW_TRANSACTIONS_PER_SESSION
 * ATTEMPT_TRANSACTIONS_PER_SESSION
 * AUTH_DEBUG
 * AUTH_PASSWORD and AUTH_USERNAME and EXTERNAL_IDENTITY
 * BANNER_ADDITION
 * BANNER_HOST
 * BANNER_RECEIVE_TIME
 * BANNER_REVERSE_HOST
 * BANNER_PURGE_DELAY
 * BUFFER_SIZE TCPIP-channel-specific option
 * CHECK_SOURCE
 * CLIENT_CERT_NICKNAME
 * CLIENT_STACK_SIZE
 * COMMAND_RECEIVE_TIME
 * COMMAND_TRANSMIT_TIME
 * CONTINUATION_CHARS
 * CUSTOM_VERSION_STRING
 * DATA_RECEIVE_TIME
 * DATA_TRANSMIT_TIME
 * DISABLE_ADDRESS
 * DISABLE_CIRCUIT
 * DISABLE_EXPAND
 * DISABLE_GENERAL
 * DISABLE_SEND
 * DISABLE_STATUS
 * DOT_TRANSMIT_TIME
 * FAST_SMTP_SESSION_TIME_LIMIT
 * HELLO_RECEIVE_TIME
 * HIDE_VERIFY
 * IGNORE_BAD_CERT
 * INITIAL_COMMAND
 * KILLED_IP_TIMEOUT
 * KILLED_USER_TIMEOUT
 * LOG_BANNER
 * LOG_CONNECTION TCPIP-channel-specific option
 * LOG_TRANSPORTINFO
 * MAIL_TRANSMIT_TIME
 * MAILBOX_BUSY_FAST_RETRY
 * MAX_A_RECORDS
 * MAX_B_ENTRIES
 * MAX_CLIENT_THREADS
 * MAX_H_ENTRIES
 * MAX_HELO_DOMAIN_LENGTH
 * MAX_J_ENTRIES
 * MAX_MX_RECORDS
 * MAX_SERVER_THREADS
 * OPEN_CONNECTION_TIME
 * PACKET_SIZE_LIMIT
 * PROXY_PASSWORD
 * RCPT_TRANSMIT_TIME
 * REJECT_RECIPIENTS_PER_TRANSACTION
 * REUSE_TIMED_OUT_TRANSFERS
 * SESSION_TIME
 * Delay threshold TCPIP-channel-specific options
 * SSL_CLIENT
 * STARTTLS_FAILURE_RECONNECT_DELAY
 * STATUS_DATA_RECEIVE_TIME
 * STATUS_DATA_RECV_PER_ADDR_TIME
 * STATUS_DATA_RECV_PER_BLOCK_TIME
 * STATUS_DATA_RECV_PER_ADDR_PER_BLK_TIME
 * STATUS_MAIL_RECEIVE_TIME
 * STATUS_RCPT_RECEIVE_TIME
 * STATUS_RECEIVE_TIME
 * STATUS_TRANSMIT_TIME
 * TLS_NEGOTIATION_TIME
 * TIMEOUT_MULTIPLIER
 * TRACE_LEVEL
 * TRANSACTION_LIMIT_RCPT_TO
 * TRANSACTION_TIME
 * WINDDOWN_TIMEOUT
 * TCPIP channels