Knowledge base

License

License Page
View and replace the key

Shows the engine license and lets you add or replace it. The key is stored as a file — on Linux this is /etc/pmta/license.

The license cuts the connection ceiling: the connections section on the “Status” page shows the maximum number of simultaneous connections given the key and the configured limits.

Replacing the key changes the node’s state — the manual assigns such actions to the admin level in http-access.

The main trap is looking for the tier here. The page and the /status response give the serial number, not the license level: how many connections are allowed is visible from the ceiling in the connections section of “Status”.
What the Hub does. It does not use the page. It takes the license serial number from /status and shows it on the “Overview” tab of the “PMTA monitoring” screen; the license level is not visible from there, and the connection ceiling is unknown to the Hub (licensing).
Recommended values

What question the page answers:

Question This one or not
which license is installed yes
replace the key yes — the admin level
how many connections it allows no — the ceiling in the connections section of “Status”
The page’s purpose and the connection ceiling given the key come from the manual (§ 5.7, § 5.3); assigning changes to the admin level is § 3.3.1.58.3. The split of questions is ours.
Example configuration
# the license in the console
pmta show license
The command prints the same as the page — without a browser.
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
Compare the serial number and the connection ceiling:
pmta show license
curl -s 'http://127.0.0.1:8080/status?format=json' | grep -A3 '"lak"'
The serial number must match in both responses; the connection ceiling is in the conn section of the /status response.
In the Hub
Cost of a mistake
reversible: harms only while it is set
Scenarios
Prepare a node for sending