Addrtypescan, addrtypescanbccdefault, noaddrtypescan channel options

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

Address type flags (addrtypescan, addrtypescanbccdefault, noaddrtypescan)

(New in 7.0.5.) If the addrtypescan channel option is set, then RCPT TO addresses (that is, envelope recipients) are compared with header recipient fields (To:, Cc:, Bcc:, Resent-To:, Resent-Cc:, and Resent-Bcc:). When a match is found, that fact is recorded in the delivery flags associated with that envelope recipient. Those flags are then used when generating the report part of Microsoft® Exchange 2007 envelope journaling archive messages, distinguishing between various types of envelope recipient addresses.

addrtypescanbccdefaultoperates in the same way as addrtypescan, except that when no matches are found for a given address, that address is assumed to be a blind carbon (Bcc:) recipient. This option should only be used when it is certain the messages have come directly from a client that implements Bcc: by simply omitting the blind carbon recipient from the header and which doesn't support any form of local mailing lists. Use in any other context is guaranteed to result in incorrect types being attached!

noaddrtypescanis the default.

Also note that since the MTA's delivery flags are used to store this informtion, the MTA's delivery flag transfer facilities may be used to transport this information between MTAs; see the deliveryflags channel option.

See also: