*_block_limit priority limit MTA options

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



Size effects of message priority MTA options: non_urgent_block_limit (integer), normal_block_limit (integer), second_class_block_limit (integer), urgent_block_limit (integer)

Note that as of the 8.0 release, these size-based priority override MTA option effects are nullified if the MT-PRIORITY SMTP extension has been used to set an explicit priority value.

non_urgent_block_limit

The non_urgent_block_limit MTA option may be used to instruct the MTA to downgrade the priority of messages based on size: messages above the specified size will be downgraded to lower than non-urgent priority, meaning that they will not be processed immediately and will wait for processing until the next periodic delivery run. The value is interpreted in terms of MTA blocks, as specified by the block_size MTA option. Note also that the nonurgentblocklimit channel option may be used to impose such downgrade thresholds on a per-channel basis.

normal_block_limit

The normal_block_limit MTA option may be used to instruct the MTA to downgrade the priority of messages based on size: messages above the specified size will be downgraded to non-urgent priority. The Job Controller automatically pays attention to message effective processing priority when scheduling delivery attempts. The value is interpreted in terms of MTA blocks, as specified by the block_size MTA option. Note also that the normalblocklimit channel option may be used to impose such downgrade thresholds on a per-channel basis.

second_class_block_limit

The second_class_block_limit MTA option may be used to instruct the MTA to downgrade the priority of messages based on size: messages above the specified size will be downgraded to third class priority. The value is interpreted in terms of MTA blocks, as specified by the block_size MTA option. Note also that the secondclassblocklimit channel option may be used to impose such downgrade thresholds on a per-channel basis.

urgent_block_limit

The urgent_block_limit MTA option may be used to instruct the MTA to downgrade the priority of messages based on size: messages above the specified size will be downgraded to normal priority. The Job Controller automatically pays attention to message effective processing priority when scheduling delivery attempts. The value is interpreted in terms of MTA blocks, as specified by the block_size MTA option. Note also that the urgentblocklimit channel option may be used to impose such downgrade thresholds on a per-channel basis.


See also: