Channel configuration

From Messaging Server Technical Reference Wiki
Jump to: navigation, search

In Unified Configuration, each MTA channel is configured as a named set of options under a channel group. For instance, configuration of the tcp_local channel (the typical channel used to communicate with the Internet) could be along the lines of:

msconfig> show channel:tcp_local = tcp-daemon (novalue) (novalue) (novalue) (novalue) (novalue) (novalue) = SMTP_POOL (novalue) = tcp_auth (novalue) (novalue) (novalue)

In legacy configuration, each MTA channel was configured in the imta.cnf file, with blank lines separating distinct channel definitions. For instance, a tcp_local channel definition in imta.cnf might appear as (with a blank line before and after these lines):

tcp_local smtp mx single_sys identnonenumeric pool SMTP_POOL \
  switchchannel maysaslserver saslswitchchannel tcp_auth maytlsserver \
  inner loopcheck remotehost 

Note that in Unified Configuration, the edit channels command may be used to edit channel definitions "as if" they were in the familiar, legacy configuration file form:

msconfig> edit channels

Note that the channel-specific options -- those set in legacy configuration in channel option files, rather than as legacy configuration channel keywords -- in Unified Configuration are set under the options named group, e.g.,

msconfig> set channel:tcp_local.options.ALLOW_ETRNS_PER_SESSION 2

Since channel-specific options are specific to the type of channel in question -- different types of channels tend to have completely different channel-specific options -- look under the discussions of the specific channel type to find out details of what channel-specific options are available for a particular channel type, as channel-specific options do not appear under the general list of options.

See also: