Demo
Demo

Knowledge base

PMTA knowledge base›Monitor screen§ 5.9

Sending addresses

VirtualMTAs Display
Who is busy with what right now

Lists sending addresses that currently have mail in the queue, by number of recipients in descending order.

Each address has its own top domains page: the ten receivers with the largest queue for that particular address — recipients, volume, open connections and the last error.

It shows how addresses work, not their settings: an address with an empty queue is not visible here, and the values in force for a pair are printed by the show settings command.

The same response as a structure — /vmtas?format=json; the queues of one address — /queues?format=json&queue=*/address-name.

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 looking here for an idle address. An address without mail in the queue is not shown at all, and “the address is not in the list” does not mean “the address is not configured” — it only means it has nothing to send right now.
What the Hub does. It does not use the page: the “vMTAs and jobs” tab of the “PMTA monitoring” screen takes /vmtas?format=json and adds the addresses the Hub created itself — which is why an idle address is visible there, unlike on this page.
Recommended values

What question the page answers:

Question This one or not
which addresses are busy now yes
which receivers one address is stuck on yes — its top domains page
which values apply to a pair no — show settings
all node addresses, including idle ones no
The “only with mail in the queue” filter, the order and the address’s top domains page come from the manual (§ 5.9); the pair settings command is § 6.3.16. The split of questions is ours.
Example configuration
# the same in the console: addresses and the resulting values of one pair
pmta show vmtaspmta show settings gmail.com/vmta1
The second command shows not the load but the values in force for a “receiver and sending address” queue.
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

3 relations

Can be replaced by

Sending addresses that have a queueThe same thing, returned by a request. § 5.9

Applies to

A queue is a receiving server together with a sending addressThe mechanism that is visible here. § 5.9

Where you can see it

The sending address — what it is made ofThe mechanism that is visible here. § 5.9

Referenced from

Sending address summaryThe same list on the monitor screen. § 6.3.21

How to check on the node
Compare the page with the console:
pmta show vmtas
curl -s 'http://127.0.0.1:8080/vmtas?format=json' | head -40
The command prints all addresses with a queue by default, while the page and its request show the top by http-default-max-items.
◇

What else to read

3 articles

◇Warm-up built into the engineA warmed-up address hands the first N messages of the day for each receiver to its cold partner; the partner sends them itself and builds history.◇The sending address — what it is made ofA named set of everything that is a property of the address: which IP the message leaves from, how the node introduces itself, what it signs with and how fast it sends.◇A group of sending addresses with traffic sharesA named group of sending addresses; without shares messages are distributed in rotation, with shares in the given proportion, in steps of a tenth of a percent.

In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Sending address rotation · Address warm-up