Knowledge base

show domains

Per-receiver summary
Sending addresses summed up

Prints recipient domains, summing all sending addresses for each — or only one address, with –vmta. A line holds recipients, volume, connections and the last error.

Twenty domains by default; more with –maxitems, selection with –connected, errors with –errors, order with –sort. The last output line says how many are shown out of how many.

A second cut of the same data as show queues: their numbers do not match — these are different aggregates, not an error.

The main trap is the default twenty lines. On a node with a hundred receivers the output without the option shows the top; the last line like “20 of 130 domains shown” says so, but it is easy to miss.
What the Hub does. It calls it through POST /command with the node key — to offer domains from the queue as operation targets in control. It passes the length explicitly, –maxitems=10000, so the list is not cut at twenty domains.
Recommended values

Options for the question:

Task How to call it
all receivers, not twenty –maxitems=1000 –sort=rcpt
receivers of one sending address –vmta=name
where the errors are –errors
stuck without connections –connected=no
The options, the default of twenty domains and summing across addresses come from the manual (§ 6.3.13). The option advice is ours.
Example configuration
# all receivers with errors, largest first
pmta show domains --maxitems=1000 --sort=rcpt --errors
Without –maxitems the output stops at twenty domains.
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.
How to check on the node
Find out how many domains are in the queue in total:
pmta show domains --maxitems=1000 | tail -1
The last line is “N of M domains shown”: M is the number of receivers in the queue.
In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Troubleshoot deliverability