Central Server Management

PureMessage can be deployed in multi-server configurations. “Server groups” consist of a central server and one or more edge servers. The edge servers are managed, configured, and maintained from the central server, which has connection and authentication profiles for the other machines. Centralized management of server groups is achieved through remote procedure calls (RPC) run from the central server.

By default, PureMessage has an “RPC User” account configured for the HTTPD (Manager) service. This user has a limited set of privileges, sufficient for starting and stopping services and updating configuration files.

Central server management makes it possible to:

  • view the status of all PureMessage servers on the network
  • add and remove edge servers
  • start and stop PureMessage services on edge servers
  • build and test configurations on the central server; distribute configurations to edge servers
  • generate reports for edge servers (or groups of edge servers) from the central server


PureMessage uses “publications” to distribute the configuration files on the central server to edge servers. Edge servers are “subscribed” to these publications.

By default, PureMessage includes publications with configuration files for major aspects of the program’s functionality, such as Sophos-Anti-Virus-Conf and Anti-Spam-Config. Existing publications can be viewed and edited on the Server Groups tab of the PureMessage Manager.

Optionally, create custom publications using either the PureMessage Manager, or the pmx-share command-line program.