Skip to content
emailservicesolutions

PowerMTA install guide

We install licensed PowerMTA on a server you control, configure it with safe defaults and prove the setup with a test message.

Versions and install credits

  • Which PowerMTA versions you can install depends on your plan. The pricing page lists them per plan.
  • Each plan includes install credits. Some plans grant them once for the life of the account, others each billing period.
  • A new install uses one credit. Reinstalling or changing the version on a server you already installed does not use another.
  • An install that fails costs nothing. The server slot is released and no credit is used.

Packages are the genuine, unmodified vendor packages. We never patch or relabel them.

What happens during an install

  1. Check. We log in, test the connection and read the system. Nothing is reserved yet.
  2. Confirm. You see exactly what will be installed and changed, and confirm.
  3. Prepare. We create a temporary folder with a random name on your server and place our install script in it.
  4. Download. The server downloads the package for your version from our servers, using a short-lived link that works only from your server's addresses.
  5. Install and configure. We install PowerMTA, write the configuration with safe defaults (TLS on, authenticated submission, a closed management interface) and set up IP rotation for the addresses you chose.
  6. Clean up. We delete the temporary folder and every installer file. This happens on success and on failure, and also if the connection drops partway.
  7. Authenticate and test. We generate DKIM keys on our side and give you the records to publish, then send a test message to your private test inbox and show the graded result.

What stays on your server

Only the PowerMTA installation and its configuration, recorded in an install manifest you can read. We install no agent, no scheduled job and no callback. After the install we connect only when you ask us to.

If something fails

You see which step failed and why, with the log. You can retry without losing anything. If the connection drops, we resume where it stopped or clean up, whichever is safe.

Supported systems

Fresh RHEL-compatible servers (version 8 or 9) with root or sudo access are supported. Other systems are added once they have been tested end to end on real machines.