Communications Suite InformationConfiguring Individual Ports for Multiple Installations of the Same Product on One Host
In a multiple installation of the same Communications Suite product on the same host, the different instances of the product are initially configured to use the same ports. If you run both instances of the product simultaneously, the ports will conflict.
One solution is to configure the individual ports on each installation so that they are different.
For example, for Messaging Server, you need to change the following ports in one instance:
- SMTP
- IMAP
- POP
- HTTPD
- ENS
- job_controller
- watcher
The ports have SSL versions, too. Also, there may be other ports to use like SMTP SUBMIT.
The best place to look for MTA-related processes is the dispatcher.cnf file. store and mshttpd ports are probably in configutil. MMP ports may be in configutil and/or its configuration files.
In addition, you can identify ports by taking these actions:
- See Default Port Numbers in the Communications Suite Component Products Release Notes.
- See "Configuring POP, IMAP, and HTTP Services" in the Messaging Server Administration Guide.
- You can grep the masterconfig file (lib/config.meta) for "port".
- Query the following configutil variables as shown in the following table:
| Service | configutil Variable | Default Value |
Comments |
|---|---|---|---|
| watcher | local.watcher.port | 49994 | |
| metermaid | metermaid.config.port | 63837 | |
| IMAP | service.imap.port | 143 | |
| IMAP SSL | service.imap.sslport | 993 | |
| POP | service.pop.port | 110 | |
| POP over SSL | service.pop.sslport | 995 | |
| Webmail | service.http.port | 80 | |
| Webmail SSL | service.http.sslport | 443 | |
| ens | local.store.notifyplugin.ensport | 7997 | |
| jmq | local.store.notifyplugin.jmqport | 7676 |
Sign up or Log in to add a comment or watch this page.