Demo
Demo

Knowledge base

PMTA knowledge base›Command§ 6.3.11

schedule

Attempt delivery ahead of schedule
Do not wait for the retry schedule

Immediately assigns handlers to the selected queues — delivery attempts start without waiting for the retry interval. Stars in the target are allowed: */* means all queues.

The manual names the case: a connectivity problem with the domain has been fixed, and there is no point waiting for the usual retry interval.

–retry-recipients releases deferred recipients: those who got a 4xx error such as “mailbox full” and wait in a separate bucket until retry-recipients-after.

The main trap is releasing everything accumulated at once toward a receiver that was just refusing. If the cause is not fixed, an unscheduled wave of attempts only brings the queue back to the same refusals.
What the Hub does. It calls it — the “Retry deferred” operation goes through POST /command with the node key as schedule –retry-recipients target: with the option, that is, releasing deferred recipients as well.
Recommended values

When to call it:

Question This command or not
the problem is fixed, no point waiting for the retry yes
release recipients with a 4xx error yes — –retry-recipients
one attempt with the conversation logged no — trace
The action, stars, the use case and –retry-recipients come from the manual (§ 6.3.11). The trap analysis is ours.
Example configuration
# all node queues, and one queue together with deferred recipients
pmta schedule */*pmta schedule --retry-recipients yahoo.com/vmta1
The first line is the manual’s example; a response like “154 of 3888 matching queues scheduled.” says how many queues got attempts.
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

2 relations

Can be replaced by

Delivery attempt with the session loggedA neighboring command: the same subject from another side. § 6.3.23

Affects

Recipients deferred after a temporary refusalThe mechanism the command works with. § 6.3.11

How to check on the node
Check that the attempts started:
pmta show queues --connected=yes --no-rcpt-events
Queues with open connections are the ones being attempted right now.
◇

What else to read

3 articles

◇A queue is a receiving server together with a sending addressThe engine groups messages by the “recipient domain plus sending address” pair: one domain from two addresses is two independent queues with their own counters, connections and mode.◇Recipients deferred after a temporary refusalA recipient to whom the receiver responded with 4xx moves into a separate waiting area with a per-receiver interval; two commands can release it early.◇A retry ladder of your ownretry-after and backoff-retry-after accept a list of intervals — up to 30 steps, and the last one applies until the bounce.

In the Hub
Cost of a mistake
reversible: harms only while it is set
Scenarios
Tune the pace for a provider · Untangle a stuck queue