Delivery options MTA option

Direct LDAP attribute interpretation MTA options:  (list of strings)
The  MTA option controls the effect of  possible values of the LDAP attribute named by the    MTA  option, (by default, the   attribute). It takes a list of up to twenty strings. Each such string specifies the effect of a particular supported value for the   attribute. The syntax for an individual string (among the list of strings) is: ModifierValue=Effect where   consists of one or more of the optional modifier letters listed in the table Modifier letters for, where   is a supported value for the   attribute,  and where   describes the intended effect of the corresponding   value. Note that if neither   nor   is present, then the  delivery option entry is taken to apply to both users and groups. 

For instance,  normally has the modifier   meaning that it applies (only) to users, whereas   normally has the modifier   meaning that it applies (only) to groups.

And while  normally has the modifier   meaning that it applies (only) to users (and so normally mailing list and group entries cannot use autoreply/vacation functionality), if it is desired to allow mailing list and groups to generate their own autoreply/vacation messages, then removing the   modifier from the   clause will allow this---from the MTA point of view. (Note that the Sun schema as distributed normally does not expect/permit   attributes to be set on mailing list or group entries. So for purposes of placating the Directory Server side, you will likely also need to either extend the schema, or disable schema checking.) As mentioned above, each   should be a supported value for the   LDAP attribute (more precisely, the attribute named by the    MTA  option). And each such supported value for   must have exactly one corresponding string in   describing its intended  effect.

Each   specifies what happens to an original address that has a specified  value. For instance, a  value of   (which is intended to mean delivery to the message store) is implemented by forcing the address local-part onto the   or   channel (Message Store delivery channels); a   value of   is implemented by routing the address local-part to the legacy native channel (the UNIX native mailbox delivery channel). The   definition may make use of LDAP URL substitution sequences. In addition, an   of merely  means to simply  substitute back in the original address specified; an   of   means to substitute the value of the   attribute (more precisely, the attribute named by the    MTA  option).

The current default for this option is (note that line breaks below are present merely for typographic reasons---the actual default value should be considered to appear all on one line): &#x2a;mailbox=$M%$\$2I$_+$2S@ims-ms-daemon,&members=&#x2a;, &#x2a;native=$M@native-daemon,/hold=@hold-daemon:$1L+$2S@$D, &#x2a;unix=$M@native-daemon,&file=+$F@native-daemon, &@members_offline=&#x2a;,program=$M%$P@pipe-daemon, This value first appeared in 8.0.1. The previous value, established in 7.0.5, differed in that it failed to preserve subaddresses in held messages: &#x2a;mailbox=$M%$\$2I$_+$2S@ims-ms-daemon,&members=&#x2a;, &#x2a;native=$M@native-daemon,/hold=@hold-daemon:$A, &#x2a;unix=$M@native-daemon,&file=+$F@native-daemon, &@members_offline=&#x2a;,program=$M%$P@pipe-daemon, Note the addition of the new-in-7.0.5 " " clause. Setting a user to have the " " delivery option causes the address to act as a valid recipient but silently delete all messages; this setting is useful for setting up an LDAP entry for a valid-but-unmonitored e-mail address. Formerly, prior to 7.0.5, the default had been: &#x2a;mailbox=$M%$\$2I$_+$2S@ims-ms-daemon,&members=&#x2a;, &#x2a;native=$M@native-daemon,/hold=@hold-daemon:$A, &#x2a;unix=$M@native-daemon,&file=+$F@native-daemon, &@members_offline=&#x2a;,program=$M%$P@pipe-daemon, On a system doing LMTP delivery (via LMTP client channels),  this option would normally be set to (on a MS 6.1 or later system): &members=&#x2a;, &#x2a;native=$M@native-daemon, /hold=@hold-daemon:$1L+$2S@$D, &#x2a;unix=$M@native-daemon, &file=+$F@native-daemon, &@members_offline=&#x2a;, program=$M%$P@pipe-daemon, &#x2a;^!autoreply=$M+$D@bitbucket, where that assumes the use of rewrite rules along the lines of .LMTP   $E$F$U%$H.LMTP@lmtpcs-daemon .LMTP  $B$F$U%$H@$H@lmtpcs-daemon and an outbound  channel, (typically but not necessarily named  ), corresponding to the  ; official channel host name, and where the channel is marked with the   channel option.
 * 1) forward=&#x2a;&#x2a;,&#x2a;^!autoreply=$M+$D@bitbucket,
 * 2) &#x2a;&nomail=$M+$D@bitbucket
 * 1) forward=&#x2a;&#x2a;,&#x2a;^!autoreply=$M+$D@bitbucket,
 * 2) &#x2a;&nomail=$M+$D@bitbucket
 * 1) forward=&#x2a;&#x2a;,&#x2a;^!autoreply=$M+$D@bitbucket
 * 1) &#x2a;mailbox=@$X.LMTP:$M%$\$2I$_+$2S@lmtpcs-daemon,
 * 1) forward=&#x2a;&#x2a;,
 * 1) &#x2a;&nomail=$M+$D@bitbucket

For another example of an alternate setting of, see Additional    channels.

Since up to twenty comma-separated strings may be specified for this option, note that up to twenty different possible delivery option values can be supported.

Note that the value clauses in the first two positions have special meaning as far as being the default delivery approaches for users and groups, respectively, which is why those first two value clauses are normally set to define  and. (That is, in the case of a user who has no   value specified in their LDAP entry, the first value clause of  ---normally  ---will be assumed: a user with no   set gets messages delivered to their mailbox. Similarly, a group that has no   value specified will get the treatment specified by the second value clause of   -- normally  : a group with no   set gets messages delivered to the members of the group.) Thus if defining additional, site-specific mailbox delivery option values, be sure to add the custom values later in the list of option values.

Also note that when setting this option in the legacy configuration MTA option file, if using the backslash continuation line  character to continue to additional lines, be aware of a potential  confusion with "comment characters". Any line that begins in column one with one of the MTA option file&#x27;s comment characters  will be interpreted as  a comment regardless of whether the line above ended with a  backslash. This issue can be worked around using the fact that the MTA ignores leading spaces after the comma separating individual strings  within  ; so you can use a definition such as  DELIVERY_OPTIONS=\ &#x2a;mailbox=$M%$\$2I$_+$2S@ims-ms-daemon,&members=&#x2a;,\ &#x2a;native=$M@native-daemon,hold=$M?$I@hold-daemon,\ &#x2a;unix=$M@native-daemon,&file=+$F@native-daemon,\ &@members_offline=&#x2a;,program=$M%$P@pipe-daemon,\ #forward=&#x2a;&#x2a;,^&#x2a;!autoreply=$M+$D@bitbucket where note the critical initial space on the line that does the  value definition.

New in 7.0-0.04, there is some "sanity checking" on individual clauses within, with an MM initialization  error issued ("    ")  if such a check fails. Previously, certain sorts of problems in clauses would instead cause the clause to be silently ignored, with no warning or error.

In particular, prior to 7.0-0.04 the overall length limit for a clause was 81 characters, with at most 40 characters allowed left of the equals sign and at most 40 characters allowed right of the equals sign. As of 7.0-0.04, the overall length limit for each clause is 256 characters (though exceeding this limit will merely cause silent truncation rather than an error), with at most 40 characters not including leading modifier characters to the left of the equals sign (that is, at most 40 characters in the actual "name" in the clause), and whatever remains of the 256 characters allowed on the right of the equals sign. Furthermore, as of 7.0-0.04, omission of an equals sign in a supposed clause will result in an MM initialization error.

See also:
 * Direct LDAP attribute interpretation MTA options
 * Overview of Direct LDAP configuration
 * Direct LDAP usergroup lookup MTA options
 * ldap_delivery_option MTA Option
 * ldap_forwarding_address MTA Option
 * ldap_autoreply_text MTA Option
 * ldap_start_date MTA Option
 * ldap_end_date MTA Option
 * ldap_mailhost MTA Option
 * Sieve vacation extension
 * LDAP URL substitution sequences
 * LMTP client TCPIP channels
 * official_host_name Option
 * multigate Option
 * Additional ims-ms channels
 * ims-ms channels
 * Process and reprocess channels
 * Hold channel
 * Bitbucket channel
 * Pipe options
 * User LDAP attributes for pipe channel processing