Port Usage

PureMessage contains a number of discrete components (for example, the milter interface, the Manager, the End User Web Interface, the PostgreSQL database), and interacts with external components (such as the Postfix or sendmail mail transfer agents). These components can all be deployed on the same server, or can be distributed among multiple servers. In either case, the components must have the ability to communicate with one another on various TCP ports.

Postfix
By default, Postfix receives incoming SMTP connections on port 25 and communicates with PureMessage using the content_filter mechanism on ports 10025 and 10026.
sendmail
By default, sendmail receives incoming SMTP connections on port 25 and communicates with PureMessage using the milter protocol on TCP port 3366.
Oracle Communications Messaging Exchange Server
By default, Oracle Communications Messaging Exchange Server receives incoming SMTP connections on port 25 and communicates with PureMessage through port 3366. For more informationi, see "Configuring PureMessage for Oracle Communications Messaging Exchange Server" in the Sophos Knowledgebase.
PureMessage Manager
Day-to-day management of the PureMessage system using the Manager interface occurs using a TCP connection to port 18080 (configurable) on the PureMessage server. This port must be open between the administrator's workstation and the PureMessage server.
SSH or Telnet
Many administrators choose to work with PureMessage from the command line, which requires ssh (port 22) or telnet (port 23) access to the PureMessage server.
DNS and DNSBL checks
PureMessage can be configured to perform a variety of network checks as part of its spam heuristic analysis. These include DNS, DNSBL (DNS Black List), and SXL lookups (port 53 UDP and TCP).
Updates
PureMessage updates occur via HTTP over port 80. (Updates can also be installed from a local tarball, if required.)
Central Server Management
The Central Server Management (Server Groups) aspect of PureMessage identifies PureMessage servers on the network via UDP queries on port 18080. Synchronization between the PureMessage servers occurs over port 18080. Quarantine consolidation occurs using scp, which runs over port 22.
End User Web Interface
By default, the End User Web Interface runs on port 28443. Users must be able to connect to this port on the server from their workstations.
Groups Web Interface
By default, the Groups Web Interface runs on port 28443. Group administrators must be able to connect to this port on the server from their workstations.
PostgreSQL
By default, PostgreSQL listens on port 5432. If PureMessage is running on a separate server, it must access the PostgreSQL host on this port.