Knowledge base
Lift a pause
Resumes delivery for queues stopped with pause queue; the target is domain[/address], stars are allowed.
The bounce lifetime kept running during the pause: messages that waited longer than bounce-after bounce by expiry — the pause does not protect them.
The main trap is resuming a queue that something other than a pause is holding. If the queue is also in backoff mode, resuming does not speed it up: the mode is changed with set queue.
What the Hub does. It calls it — the “Resume” operation goes through POST /command with the node key; the Hub also runs it itself when a pause set in control or by a policy expires. The result is checked with a snapshot of paused queues.
Recommended values
When to call it:
| Question | This command or not |
|---|---|
| lift the pause from a queue | yes |
| take a queue out of backoff mode | no — set queue |
| lift the pause from a campaign | no — resume job |
The action and the target form come from the manual (§ 6.3.27). The analysis of lifetime and mode is ours.
Example configuration
# lift the pause from all queues of a sending address pmta resume queue */customer1
The manual’s example — the counterpart of stopping with pmta pause queue */customer1.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
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.
⇄
Related entries
1 relation
How to check on the node
Check that the pause is lifted:
pmta show queues --paused=yes --no-rcpt-events --maxitems=1000
Queues with this target should disappear from the paused selection.
◇
What else to read
2 articles
◇How to name a queue in a commandHow to name a queue in a command argument: the same “receiving server and sending address” pair with asterisks added.◇Two tags the sender puts on a messageA job groups messages, an envelope identifier identifies one; the submitting side sets both, and only by them can you later select your mail in the node’s queue.
In the Hub
- Cost of a mistake
- safe: a wrong value breaks nothing
- Scenarios
- Emergency stop
- Priority
- critical