Demo
Demo

Knowledge base

PMTA knowledge base›Command§ 6.3.20

show version

Engine version
What exactly is installed

Prints the engine version, build date and revision on one line.

The first thing asked when diagnosing strange behavior: some features appeared or changed between versions.

The main trap is checking only the number. The build date and revision distinguish builds with the same version number; when contacting the vendor, the whole line is needed.
What the Hub does. It calls it over SSH: after installation — checking that the engine responds — and when it determines the engine version on the node; from the line it takes a number like 6.0r3.
Recommended values

When to use it:

Question This command or not
what exactly is installed yes
machine and license information no — show status, show license
The output contents come from the manual (§ 6.3.20). The split of questions is ours.
Example configuration
# engine version
pmta show version
Example output from the manual: PowerMTA v5.0r1 (2019-09-13 16:27:31, 64-bit; v5_0r1@190913.ba26ec5).
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

Works together with

Upgrading the engineThe procedure in which this command is one of the steps. inference

How to check on the node
Compare the engine version with the installed package:
pmta show version
rpm -q PowerMTA 2>/dev/null || dpkg -s pmta 2>/dev/null | grep Version
A mismatch means the running build is not the one installed as a package — for example, the service was not restarted after an upgrade.
◇

What else to read

3 articles

◇The activation key is a prerequisite for installation, not a step after itWithout an activation key from SparkPost support the engine neither installs nor runs, and the license tier sets the outbound connection ceiling: on Standard everything above 200 is ignored.◇Cloud restrictionsClouds restrict outbound mail on port 25 until you ask them to lift the limit, and mailbox providers treat their address ranges with suspicion.◇How to turn a sending plan into hardwareTwo constants for sizing any node: about 2 KB of memory per queued recipient and spool space proportional to the total size of the messages.

In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Prepare a node for sending