Demo
Demo

Knowledge base

PMTA knowledge base›Block <domain>›Directive§ 3.3.10.16

delivery-priority

<domain>deprecated

Delivery priority — a deprecated name
in the configuration this is a linedelivery-priorityinside the block <domain>
A line with nothing left but its name

The manual gives the directive a section (§ 3.3.10.16) and writes two things in it: the mark Deprecated and the replacement — queue-priority.

No syntax, no default, no description of behavior there: all of that moved to the replacement’s section.

Judging by the names, both are about the same thing — the order in which queues are served when connections run short. But this is an inference from the name, not a statement of the manual: it gives no way to compare the behavior of the two lines.

The main trap is keeping both lines. What happens if one block contains both the deprecated and the new line, the manual does not specify. It would have to be found out by experiment — and there is no need: the replacement is named directly.

The other half: the deprecated line does not give itself away in any way. It causes no apply error, is not noted in the log, and looks like a working setting in the configuration.

What the Hub does. It writes neither the deprecated line nor its replacement: queue priorities are not set by it at all.

The deprecated one is worth looking for in configurations assembled by hand before the move to the Hub.

Recommended values

What to set. Nothing: the line should be replaced.

Value When
do not write always: priority is set with the new line
any value only in an old configuration that has not been migrated yet

The migration is mechanical: the name changes to the new one, the value stays — the replacement has the same scale, from zero to a hundred with fifty in the middle.

The deprecation mark and the pointer to the replacement are the only things the manual says about this directive, § 3.3.10.16. The replacement’s scale is § 3.3.10.14. The conclusion that the meaning coincides is ours, from the names.
Example configuration
# this is how it was before — today the same is written under the new name
<domain someplace.com>
    delivery-priority 75</domain>
The value carries over as is: the replacement has the same scale. Keeping both lines in one block is not a good idea — the manual does not say which wins.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
▲

Common mistakes and problems

what people get wrong and how it ends2 mistakes▶

Leaving the deprecated line next to the new one

§ 3.3.10.16

What it costsWhich wins, the manual does not specify. It would have to be found out by experiment, even though the replacement is named directly and there is no need for that.
How to spot itBoth lines appear in the configuration.
How to do it rightRemove the deprecated one, carry the value into the new one.

Considering the line working because it causes no errors

our experience

What it costsA deprecated directive is noted neither in the log nor when the configuration is applied. It looks like a setting whose effect nothing is known about.
How to spot itThe line has been there for years, and nobody has checked whether it works.
How to do it rightMove to the replacement — then the behavior can be read in a description rather than guessed.
Compatibility
PowerMTA 6.0
described in the manual of this version · platform: any
The vendor does not state the first version for every directive — there is no note here. The name also appears in the 5.0 edition of the manual.
Reference data
Syntax
delivery-priority <integer>
Values
not described in the manual
Applying
reload, no restart needed
Queue
will not touch what is already queued
Where to write it
<domain>
How many times
once in the block
Everything here comes from the manual, with the section.
Inheritance
The directive lives in <domain> and follows the merging of recipient blocks — as does its replacement. There is no difference in scope between them: the replacement touched the name, not the mechanism.
⇄

Related directives

1 relation

Replaced by

queue-priority<domain>The replacement named directly by the manual; its scale and scope are the same. § 3.3.10.16

How to check on the node
The deprecated line is worth looking for together with its replacement:
grep -n 'delivery-priority\|queue-priority' /etc/pmta/config /etc/pmta/virtualhost.txt
If both are found, the configuration should be brought to one. The deprecated line gives itself away in no way: no apply error, no log entry.
◇

What else to read

3 articles

◇Accept, route, deliverA message’s path inside the node: accept, decide where, deliver — and all the settings live between these three steps.◇Four value types the whole config is written inBoolean, domain pattern, regular expression and time interval — defined once in § 3.2 and then used by all directives.◇Reloading settings versus restarting the serviceThe configuration is read at startup, and after that edits are picked up by the reload command — except for the directives the manual marks as requiring a restart.

In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Configuration lifecycle
Neighboring settings of the block <domain>:queue-priorityallow-priority-interruptionallow-priority-interruption-during-transferdisable-acct-recordsdkim-signAll 135 directives of the block →