Demo
Demo

Knowledge base

PMTA knowledge base›Command§ 6.3.15

show jobs

Jobs
A breakdown by campaign

Prints jobs in the queue: recipients and volume. By default — all jobs; –maxitems limits them, –sort sets the order.

The job is assigned by the submitting side: with the X-Job header if process-x-job is allowed for the source, or with the *jobid merge variable.

The main trap is taking an empty list for no campaigns. Messages without an assigned job do not get into the list: empty output with a full queue means “jobs were not assigned”.
What the Hub does. It does not call it itself: it takes jobs for the “PMTA monitoring” screen with the /jobs request. Mail through node logins does not form jobs — there the Hub writes process-x-job false.
Recommended values

When to use it:

Question This command or not
which campaigns are in the queue yes
stop one of them no — pause job
how a campaign was delivered no — pmtastats with –byJobId
The “all jobs” default, the options and the output format come from the manual (§ 6.3.15); job assignment is § 3.3.7.49. The split of questions is ours.
Example configuration
# jobs, largest first
pmta show jobs --sort=rcpt
An output line is the job identifier, recipients and kilobytes; at the bottom — “Total of N job(s).”.
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

Can be replaced by

JobsThe same list on the monitor screen. § 6.3.15

How to check on the node
If the list is empty, check whether the job header is allowed:
pmta show jobs
grep -rn 'process-x-job' /etc/pmta/
process-x-job false in the submission source — jobs will not be assigned, no matter how many messages arrive.
◇

What else to read

3 articles

◇A license for a fleet, not for a serverThe license is not bound to a server: it is installed on as many machines as the instance limit allows, and the nodes send volume statistics to the vendor every hour.◇How the node selects a source and combines its settingsA connection falls under all source blocks whose addresses cover it, and they act merged — the narrow one overrides the wide one; named blocks are attached only by direct reference.◇Address lists — named and unnamedA list of addresses, domains, patterns or hashes; a named one is attached by directives such as suppression, an unnamed one lives inside an inbound mail processor.

In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Sender isolation