Deliveryflags, flagtransfer, noflagtransfer Channel Options
From MsgServerDocWiki
Delivery flags (deliveryflags, flagtransfer, noflagtransfer)
The deliveryflags channel option may be placed on source or destination channels. It takes a required, bit-encoded integer argument, which controls various options regarding message delivery:
| Bit | Value | Usage |
|---|---|---|
| 0 | 1 | Interpret subaddresses as folder names for delivery |
| 1 | 2 | When placed on a source channel, enable quota bypass (that is, delivery even if the recipient user is overquota) for messages enqueued by this channel |
| 2 | 4 | Messages do not require SMTP dot stuffing |
| 4 | 16 | Force single copy per recipient |
| 5 | 32 | Ignore discard or jettison actions ( e.g., from Sieve filters). This corresponds to setting the message envelope bit normally set automatically by the MTA when applying a discard or jettison action, enqueueing to the FILTER_DISCARD or FILTER_JETTISON channel, so that if a "retrieval" procedure should later be performed on such a "discarded" message (such as moving the message to the reprocess channel), the message will then get delivered bypassing any discard or jettison actions.
|
| 6 | 64 | When placed on a destination channel, enable transfer of delivery flags; equivalent to the flagtransfer channel option
|
| 7 | 128 | Messages enqueued to the channel are considered, for purposes of CONVERSION mapping table testing, to have a conversion tag set |
| 8 | 256 | Handle as if address is a result of a " redirect" action
|
| 9 | 512 | Handle as if SMTP AUTH (SASL) had been used as far as access checks are concerned |
| 10 | 1024 | Handle as if TLS had been used |
| 11 | 2048 | Handle as if address produced by alias |
The default value for deliveryflags is 0.
The flagtransfer channel option may be placed on a destination TCP/IP channel (more generally, SMTP client channel). It enables SMTP client support of the XDFLG private SMTP extension command. If the client is sending to an SMTP server that supports this extension, the SMTP client will pass along (transfer) the delivery flags. For instance, this can be useful when user filters (performing fileinto Sieve operations) will be performed on a "front-line" system that must then relay the messages to a "back-end" system. noflagtransfer disables delivery flag transfer and is the default.
Setting flagtransfer is equivalent to setting bit 6 (value 64) of the deliveryflags channel option.
Categories: MTA | Channels | Reference

