Demo
Demo

Knowledge base

PMTA knowledge base›Monitor screen§ 5.2

The monitor's home page

Home Display
The entry point to everything else

The web monitor’s start page: installation information, a table of the domains with the largest queue and links to the other screens — status, queues, domains, sending addresses, jobs, logs, console, license and configuration.

The console is not always in the list of links: the manual shows it only when the PowerMTA service on the machine is running.

The same page as a structure — /?format=json, without the /ui suffix.

By default the monitor is closed to everyone: http-access without lines is none, and the browser first gets “access denied” until the address is allowed in the configuration.

The main trap is opening the monitor to the whole network for a test. The manual’s example http-access 0/0 monitor is marked “for testing only”: such a line gives node state, queues and logs to anyone who reaches the port. The manual explicitly advises keeping the monitor on the local network and closed off from the internet.
What the Hub does. It does not use the page: it takes installation information — version, license, uptime — from /status on the “Overview” tab of the “PMTA monitoring” screen. The Hub gives its own addresses the monitor level in http-access, and the machine itself admin.
Recommended values

What question the page answers:

Question This one or not
what installation this is and what sections the monitor has yes
what is going on with the node now no — “Status”
the same information for a program no — /?format=json
what happened yesterday no — that is accounting
The page contents, the condition for the console appearing, access closed by default and the advice to keep the monitor on the local network come from the manual (§ 5.1, § 5.2, § 3.3.1.58.3). The split of questions is ours.
Example configuration
# open the monitor only to the local network and the machine itself
http-access 10.0.0.0/8 monitorhttp-access 127.0.0.1 admin
The lines are checked in the order they are written in the file — top to bottom.
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

Depends on

What protects the web monitor and what that protection is notAccess to the screen is decided by rights and addresses set at the node level. § 5.1

Where you can see it

ConsoleA neighboring catalog entry. § 5.2

How to check on the node
Check whether the monitor lets the browser’s address in:
curl -s -o /dev/null -w "%{http_code}\n" 'http://127.0.0.1:8080/'
grep -n 'http-access' /etc/pmta/config
Code 403 — the address is not allowed by the http-access lines; a redirect — http-redirect-to-https is in effect, open it over https. The monitor writes login attempts to pmtahttp.log together with the address.
◇

What else to read

3 articles

◇Who is allowed to submit mail and for whom to accept itOut of the box, the node accepts submission only from the machine itself; two different questions — “who can send through us” and “for whose addresses we accept mail” — are answered by different directives.◇The group that grants management rightsMembership in the pmta group gives an unprivileged user the right to call the node’s commands and use submission.◇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.

In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Node security