Demo
Demo

Knowledge base

PMTA knowledge base›Monitor screen§ 5.10

Jobs

Jobs Display
A breakdown by campaign

Lists jobs that have mail in the queue: the number of recipients and volume. Without filtering this is “Top jobs” — the length is set by http-default-max-items.

The job is assigned to a message by the submitting side: with the X-Job header if process-x-job is allowed for the source, or with the *jobid merge variable. An empty page with a full queue more often means “jobs were not assigned” than “nothing to send”.

The same response as a structure — /jobs?format=json, one job — /jobDetail?format=json&jobid=….

Access is decided by http-access based on the address the browser is opened from — the monitor level is enough for viewing.

The main trap is judging a campaign’s outcome by the page. It shows how many of the job’s messages are still in the queue, but not how many of them were delivered or bounced: that is a question for accounting, where the job is recorded in the jobId field.
What the Hub does. It does not use the page: the “vMTAs and jobs” tab of the “PMTA monitoring” screen takes /jobs?format=json. Mail submitted through node logins does not form jobs — there the Hub writes process-x-job false.
Recommended values

What question the page answers:

Question This one or not
which campaigns are in the queue now yes, if jobs are assigned
how many of the job’s messages were delivered no — accounting, the jobId field
pause one campaign no — the pause job command
The page contents, the single job page and the ways to assign a job come from the manual (§ 5.10, § 3.3.7.49). The split of questions is ours.
Example configuration
# the same in the console, and pausing one job
pmta show jobspmta pause job weeklyNews22100
The identifier is the one the submitting side passed in X-Job; this one is taken from the command output example in the manual.
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 thing, returned by a request. § 5.10

Referenced from

JobsThe same list on the monitor screen. § 6.3.15

How to check on the node
If there are no jobs, check whether their header is allowed:
pmta show jobs
grep -rn 'process-x-job' /etc/pmta/
An empty list with a full queue — first check whether the job header is allowed in the source the submission went through.
◇

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