Managing internet protocol bindings on a multi-port Domino Server

When you configure a Domino server to use multiple ports the order in which the ports are started can be important, while port 1352, will bind to all configured ports, and HTTP Binding is configured in the Server Document, other internet protocols (SMTP, POP3, LDAP, IMAP) will bind to the first port on the PORTS= line in the notes.ini.  So for example if a Domino server is configured with two ports named public and private so the notes.ini looks like this PORTS=public, private if no further configuration is done SMTP for example would bind to the public port, however if the public port was disabled and then re-enabled, the PORTS= line would be rewritten like this PORTS=private, public Therefore on the next server restart SMTP would bind to private, most likely rendering it unreachable. There are two ways to manage the server to prevent this from happening 1. Specify the port for each protocol in the notes.ini as documents in Technote 1097004

To force IMAP, LDAP, POP3, or SMTP to bind to a TCP/IP port other than the first listed port, use the following notes.ini parameter: NotesPort=

This method was introduced in Domino 6.0 2. Specify the port order in the notes.ini as documented in Technote 1279003

The PortOrder parameter is used as a state variable to hold the location of disabled ports so that if the disabled port is ever re-enabled, it will be added back to the Ports parameter in its previous position in the list. Here’s an example: State 0: Ports=Port_1, Port_2, Port_3

This method was introduced in Domino 7.0