Demo
Demo

Knowledge base

PMTA knowledge base›Command§ 6.3.31

deregister

Disconnect the node from the console
Break the link

Disconnects the node from PowerMTA Management Console.

By default it deletes data not yet uploaded to the console; accounting files configured by the user are not affected. –retain-unloaded keeps what has not been uploaded — for example, to disconnect and immediately reconnect the node without losses.

–local-only disconnects only on the node: the node’s record in the console itself remains and must be removed there.

The main trap is disconnecting without keeping what has not been uploaded. Without –retain-unloaded the command deletes everything the node has not yet passed to the console, and there is no way to get it back.
What the Hub does. It does not call it: the vendor console is not used in the fleet.
Recommended values

When to use it:

Question This command or not
disconnect the node from the console yes
reconnect without data loss yes — with –retain-unloaded
whether the node is connected now no — show registration
Deleting data not yet uploaded, –retain-unloaded and –local-only come from the manual (§ 6.3.31). The split of questions is ours.
Example configuration
# disconnect, keeping data not yet uploaded
pmta deregister --retain-unloaded
An example from the manual. Afterwards the node may need to be removed from the console manually — the command says so itself.
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

Can be replaced by

Connect the node to the vendor's consoleA neighboring command: the same subject from another side. § 6.3.31

How to check on the node
Check that the link is broken:
pmta show registration
If the output still shows the console address, the disconnection did not go through.
◇

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
dangerous: effects outlast a rollback
Scenarios
Prepare a node for sending