Demo
Demo

Knowledge base

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

disable-mx-rollup

<domain>

Whether to exclude this recipient from queue combining
in the configuration this is a linedisable-mx-rollup falseinside the block <domain>
Keep the recipient with its own separate queue

It cancels combining for one recipient. When it is enabled, this domain’s DNS records are not compared with the manual list <mx-rollup-list> and are not considered for automatic combining (auto-mx-rollup). One line closes both roads.

The domain keeps its own separate queue: its own pace, its own connection ceiling, its own backoff mode, its own line in the monitor.

The line is needed where combining gets in the way. The usual case is an important recipient behind a hosting provider’s shared gateway: combining would put it on a par with thousands of other domains, while you need separate control over this one in particular.

The main trap. A separate queue does not mean a separate gateway. The receiver still sees the total load from all your queues that come to it — you have just stopped accounting for it. Excluding a domain from combining without recalculating its limit usually means the total rate to the gateway has grown.
What the Hub does. It does not write it — nor does it write either of the combining mechanisms this line cancels. As long as the Hub’s configuration is per-domain, the line is not needed: there is nothing to cancel.
Recommended values

Only selectively. The point of the line is an exception to the rule. Enabled in the wildcard block, it cancels combining entirely, and then it is simpler not to set combining up at all.

Recalculate the limit after excluding. A domain taken out of the shared queue gets its own pace on top of what the other queues already send to the same gateway.

Check that there is something to exclude. If neither the manual list nor automatic combining is set up, the line does nothing.

The requirement to recalculate the limit and the warning about the wildcard are ours. From the manual here come the false default and the fact that the line closes both roads at once: comparison with the list and automatic combining.
Example configuration
# an important recipient behind a shared gateway — handled separately
<domain client.example.com>
    disable-mx-rollup true    max-smtp-out 5
    max-msg-rate 200/h
</domain>
The limits next to it are not for show: a domain taken out of the shared queue stops sharing its pace and gets its own — on top of what already goes to the same gateway.
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▶

Excluding a domain without touching its limits

our experience

What it costsThe domain gets its own pace on top of what the other queues already send to the same gateway. The total load on the receiver grows exactly when it was supposed to be brought under control.
How to spot itAfter the exclusion, the share of temporary refusals grew for all domains behind this gateway, not only for the excluded one.
How to do it rightGive the excluded domain a limit carved out of the gateway’s shared budget, not on top of it.

Setting it in the wildcard block

§ 3.3.10.103

What it costsCombining is canceled for all recipients at once. The manual list and automatic grouping stay in the configuration and look operational, although they affect no one.
How to spot itThere are no queues ending in .rollup in the list at all, although the combining list is set.
How to do it rightPut the line only in blocks for specific recipients.
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
disable-mx-rollup <boolean>
Values
yes or no; true and false are accepted on a par with them
Default
false § 3.3.10.103
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 value merges across <domain> blocks from general to specific: the best-matching block wins, not the last one in the file. It cancels both kinds of combining regardless of where they are set: the manual list is at the node level, and so is auto-mx-rollup. It is picked up by pmta reload.
⇄

Related directives

2 relations

Conflicts with

auto-mx-rollupGlobalThe automatic combining this line cancels for one recipient. § 3.3.10.103

Can be replaced by

queue-to<domain>The opposite action: that one combines domains into a shared queue at your direction, this one takes a domain out of any combining. § 3.3.10.103

How to check on the node
The result is visible from the queue list: an excluded domain’s queue is named with its own name, not the name of the combined one:
pmta show settings client.example.com/vmta1 | grep -i disable-mx-rollup
pmta show queues | grep -i client.example.com
If in the second command the domain appears in a queue ending in .rollup or .arollup, the line did not take effect. The Hub does not set up combining, so all its queues are per-domain even without this line.
◇

What else to read

3 articles

◇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.◇Two inbound report processors and what to do with themBounces by message and complaints are parsed by two identically structured blocks; each has its own address list and its own pair of decisions about the message’s fate.◇How the policy for a receiver is assembledSettings are assembled from the most general pattern to the most precise; the order of blocks in the file means nothing.

In the Hub
Cost of a mistake
reversible: harms only while it is set
Scenarios
Bounce classification · Tune the pace for a provider
Neighboring settings of the block <domain>:reroute-to-virtual-mtabackoff-reroute-to-virtual-mtasmtp-hostsqueue-torouteAll 135 directives of the block →