Sourceroute, percents, bangstyle, header 822, header 733, header uucp Channel Options

Address types and conventions
This group of destination channel options controls what types of addresses will be used in messages queued to the channel. A distinction is made between the addresses used in the transport layer (the message envelope) and those used in message headers.

The  option is the default and specifies that source routed envelope addresses should be used. This channel supports full RFC 5322 format envelope addressing conventions including source routes. The keyword  was a supported synonym for   in old configuration files but is not supported in XML-based configurations.

specifies that percent sign addressing conventions should be used in the envelope. The channel supports full RFC 5322 format envelope addressing with the exception of source routes; source routes will be rewritten using percent sign conventions instead. The channel keyword  was a supported synonym for   in old configuration files but is not supported in XML-based configurations.

Use of percent sign addresses on an SMTP channel will result in these conventions being carried over to the transport layer addresses in the SMTP envelope. This may violate RFC 5321. Only use percent sign addressing conventions when you are sure they are necessary.

The  channel option specifies that this channel uses addresses that conform  to RFC 976 bang-style address conventions in the envelope (i.e., this is a UUCP channel). The keyword  was a supported synonym for   in legacy configuration files but is not supported in unified configurations.

The  channel option specifies that source routes should be used in header addresses. This channel supports full RFC 5322 format header addressing conventions including source routes. This is the default if no other header address type option is specified.

The  channel option specifies that percent sign addresses should be used in the header. This channel supports RFC 5322 format header addressing with the exception of source routes; source routes should be rewritten using percent sign conventions instead.

Note that the use of 733 address conventions in message headers may violate RFC 5322 and RFC 976. Only use this option if messages are known to contain source route addresses in the header and you are sure that the channel connects to a system that simply cannot deal with source route addresses.

specifies that bang-style addresses should be used in the header. The use of this option is not recommended. Such usage grossly violates RFC 976.

See also:
 * Addresses channel options
 * Channel options