Netscape Messaging Server 4.0 Multiplexor

Netscape Messaging Multiplexor

The Netscape Messaging Multiplexor is a specialized messaging server that acts as a single point of connection to multiple mail servers. With the Multiplexor, large-scale mail-service providers can distribute POP and IMAP user mailboxes across many machines to increase messaging capacity. All users connect to the single Multiplexor server, which redirects each connection to the appropriate mail server.

If you provide electronic mail service to many users, you can install and configure the Messaging Multiplexor so that an entire array of mail servers will appear to your mail users to be a single host.

The Messaging Multiplexor supports both unencrypted and encrypted (SSL) communications with mail clients.

The Messaging Multiplexor is provided as part of Netscape Messaging Server 4.0. You can install the Messaging Multiplexor when first installing Messaging Server or other Netscape servers, or at a later time.

This document contains the following sections:

 


About the Messaging Multiplexor

Message stores on heavily used mail servers can grow quite large. Spreading user mailboxes and user connections across multiple servers can therefore improve capacity and performance. In addition, it may be more cost-effective to use several small server machines than one large, high-capacity, multiprocessor machine.

The Messaging Multiplexor is a multithreaded server that facilitates distributing mail users across multiple server machines. The Multiplexor handles incoming client connections destined for other server machines (the machines on which user mailboxes reside). Clients connect to the Multiplexor itself, which then redirects the session to the server with the correct mailbox. This capability allows Internet service providers and other large installations to spread message stores across multiple machines (to increase capacity) while providing the appearance of a single mail host for users (to increase efficiency) and for external clients (to increase security).

Figure 1 shows how servers and clients relate to each other in a Messaging Multiplexor installation.
 

Figure 1. How the Messaging Multiplexor interacts with clients and servers

 
 
All POP and IMAP clients work with the Messaging Multiplexor. The Messaging Multiplexor accepts connections, performs LDAP directory lookups, and routes the connections appropriately. As is typical with other mail-server installations, each user is assigned a specific address and mailbox on a specific mail server. However, all connections are routed through the Multiplexor. In slightly more detail, these are the steps involved in establishing a user connection:

  1. A user's client connects to a Multiplexor, which accepts preliminary authentication information (user name).
  2. The Multiplexor queries an LDAP directory server to determine which mail server contains that user's mailbox.
  3. The Multiplexor connects to the proper mail server, replays authentication, then acts as a pass-through pipe for the duration of the connection.
You can configure a single instance of Multiplexor to support both POP and IMAP protocols (as shown in Figure 1), or you can create separate Multiplexor instances for each protocol, as shown in Figure 2. By splitting messaging services across different machines, you can tune the resources on each computer for maximum performance.
 

Figure 2. Separate Multiplexors and mail servers for POP and IMAP support

Table 1 lists the principal files that make up a Messaging Multiplexor installation. (See Creating an Instance of the Messaging Multiplexor for definitions of the directories mmpRoot and instanceName.)
 
  Table 1. Messaging Multiplexor files
File Description
PopProxy, ImapProxy [Unix] 
PopProxy.exe, ImapProxy.exe [NT]
The executable Messaging Multiplexor programs for IMAP and POP services, respectively 
(installed in directory mmpRoot/bin/)
ImapMMP.config, PopMMP.config [Unix] Configuration files specifying environment variables used for IMAP and POP services, respectively 
(installed in directory mmpRoot/MMP_instanceName)
ImapMMP.sh, PopMMP.sh [Unix] Shell scripts that set environment variables and execute Multiplexor for IMAP and POP services, respectively 
(installed in directory mmpRoot/MMP_instanceName)
mmp-setup [Unix] The Multiplexor Installer 
(installed in directory mmpRoot/)
libldapv30 (or libldap32v30), 
libnspr21, libplc21, libplds21 
Shared libraries used by the Messaging Multiplexor; libraries have suffixes of .dll on NT, .so on most Unix platforms, .sl on HP-UX 
(installed in directory mmpRoot/lib/)
 


Benefits Provided by the Messaging Multiplexor

If the size of your mail-server installation requires the use of multiple mail servers, your organization can benefit in several ways from using the Messaging Multiplexor. The indirect connection between users and their mail stores, coupled with the ease of reconfiguration of user accounts among mail servers, simplifies the performance of the following tasks.
 

Installing and Configuring the Messaging Multiplexor on Unix

The Messaging Multiplexor is available as part of the Netscape Messaging Server 4.0 for Unix. You can install the Multiplexor at the same time as you install the Messaging Server, or you can install it later. Either way, you first need to prepare the system to support the Multiplexor.

Before You Install (Unix)

Before you install the Messaging Multiplexor on a Unix machine, perform the following tasks:

Server Setup and the Multiplexor Installer (Unix)

There are three different ways to install the Messaging Multiplexor on a machine: Note that installing the Messaging Multiplexor on a machine does not require you to also install the Messaging Server on the same machine.

Creating an Instance of the Messaging Multiplexor (Unix)

For the initial installation of the Messaging Multiplexor on a given host machine, the Server Setup program calls the Netscape Messaging Multiplexor Installer. For subsequent installations, you can call the Multiplexor Installer directly. When the Multiplexor Installer starts, follow these steps to install and configure the Multiplexor:
  1. When prompted for the user name that the Multiplexor should run as, enter the user name that you created for exclusive use of the Multiplexor (see Before You Install).

  2.  
    The default value is nobody.
     
  3. At the next prompt, enter the installation directory (called mmpRoot/ in this document), the directory path into which you want the Multiplexor to be installed.

  4.  
    To accept the default (/usr/netscape/suitespot4/mmp), press Enter. The installation program creates the directories for the Multiplexor installation and installs the files. (If you are creating a second or subsequent instance of the Multiplexor on this machine, the installation program uses the existing installed files.)
     
    The installer program starts to create an instance of the Multiplexor from those files. (If there is a previously installed instance of the Multiplexor, you can at this point choose to either configure the existing instance or create a new one.)
     
  5. If you choose to configure this instance of the Multiplexor, enter the name you want to give it.

  6.  
    To accept the default name (the host name of the machine you are installing Multiplexor onto) press Enter. The installation program finishes creating the new instance, installing it into the subdirectory mmpRoot/MMP-instanceName/.
     
  7. Enter one of the following numbers to specify which kind of mail service you want this instance to support:
    1.  
      Value
      Explanation
      1 Configure this instance for IMAP4 mail service
      2
      Configure this instance for POP3 mail service
      3
      Configure this instance for both IMAP4 and POP3 mail services
       
  8. Follow additional prompts to further configure this instance of the Multiplexor.

  9.  
    The table in the section Options for Configuring the Messaging Multiplexor gives you information about each prompt.
     
  10. The installer shows you a summary of the information you have entered.  If the information is correct, type y. If you need to make changes, type n, in which case the install program takes you back through the prompts again.
After you have approved the configuration options and the Multiplexor Installer has implemented them, the program displays the following information:

Changing the Configuration and Creating Additional Instances (Unix)

To modify the configuration of a previously installed instance of the Multiplexor, or to create a new instance after an initial installation, follow these steps to execute the Netscape Messaging Multiplexor Installer and make your changes:
  1. Go to the directory that contains the Multiplexor Installer. The program is installed at the top of the installation directory, under mmpRoot/.

  2.  
  3. From the command line, type mmp-setup.

  4.  
  5. The Multiplexor Installer asks whether you want to change an existing instance or create a new one.

  6.  
 NOTE: You can also change Multiplexor configuration for IMAP and POP services by directly modifying the configuration files ImapMMP.config and PopMMP.config, respectively. See Directly Setting Environment Variables in Configuration Files.
 

Installing the Messaging Multiplexor on Windows NT

The Messaging Multiplexor is available as part of the Netscape Messaging Server 4.0 for Windows NT. When you install the Messaging Server, it gives you the option to also install the Messaging Multiplexor. (For Messaging Server installation instructions, see Installing Messaging Server 4.0.)

Before You Install (Windows NT)

Before you install the Messaging Multiplexor on a Windows NT machine, perform the following tasks:

Installing the Messaging Multiplexor (Windows NT)

Follow these steps to install and configure the Messaging Multiplexor on Windows NT:
  1. Unpack the installation package and run the Server Setup program (setup.exe), as described in Installing Messaging Server 4.0.

  2.  
  3. When the Select Components screen is displayed, select Netscape Messaging Suites and click the Change button. This  brings up the Select Sub-Components screen.

  4.  
  5. Unselect the server itself and select the Netscape Messaging Multiplexor.

  6.  
  7. Press Continue and Next to start the installation.

  8.  
  9. Enter information about your installation and configuration in response to the prompts on the screen.

  10.  
    (For further information about how each prompt relates to the configuration of the Multiplexor, see Options for Configuring the Messaging Multiplexor, later in this document.)
     
  11. When you see the summary of the information you've entered, make sure the information is correct, and then click Next. The program files are now copied to your hard disk.
  12.  
  13. The setup program then runs each of the Multiplexors (first POP, then IMAP) in a special configuration mode to configure them according to the information you have entered.
Once the installation is complete, open the Services Control Panel to start the new Multiplexor services. The new services for POP and IMAP appear as "Netscape POP3 MMP" and "Netscape IMAP4 MMP", respectively. (If there are multiple instances of the Multiplexor, each appears with its instance name in parentheses.)

Uninstalling the Messaging Multiplexor (Windows NT)

To uninstall the Messaging Server 4.0 version of the Messaging Multiplexor, you follow the same process as for earlier versions. Open a command prompt window, change to the directory containing the Multiplexor, and type the following commands:

Changing the Configuration and Creating Additional Instances (Windows NT)

The Messaging Server setup program does not support modifying the configuration of an installed instance of the Messaging Multiplexor. To change the configuration of an existing instance, you may need to modify information in the NT Registry. See Directly Setting Environment Variables in Configuration Files.

To install an additional instance of the Multiplexor on a machine that already has an installed instance, re-run the Netscape Servers installation program. Choose a different directory into which to install the Multiplexor.
 


Options for Configuring the Messaging Multiplexor

This section describes the configuration prompts, command-line options, and environment variables that control the functioning of  the Messaging Multiplexor.

Listing Command-Line Options

To display a list of the command-line configuration options, you can execute Multiplexor for either POP or IMAP from the command line, using  the -h option with no attributes: The Multiplexor then displays the following list of options:
Usage:  [Pop,Imap]Proxy [options]
        Options:
         -t    NUM         number of threads (0 by default)
         -p    [IP:]NUM    address on which to listen (IPPORT_PROTOCOL by default)
         -c    PORT        backend connect port (IPPORT_PROTOCOL by default)
         -h    HOST[:PORT] LDAP server (localhost:IPPORT_LDAP by default)
         -b    DN          Root DN ("" by default)
         -D    DN          Bind DN (anonymous by default)
         -w    PASS        Bind passwd (none by default)
         -v    NUM         Verbosity level (0 by default)
         -o    DIR         Verbosity destination directory ($CWD by default)
         -x    STR         Capability replacement string ("IMAP4 IMAP4rev1 AUTH=LOGIN" by default)
         -ba   STR         Banner replacement string ("Netscape Messaging Multiplexor ready" by default)
         -us   STR         UidSearch replacement string ("(uid=%s)" by default)
         -ps   PORT        SSL listen port (IPPORT_SSLPROTOCOL by default)
         -s    SSLPARMS    To enable SSL, where SSLPARMS = SECMODFILE CERTFILE KEYFILE KEYPASS CIPHERS CERTNAME
         -vd   FILENAME    Virtual domain file location
         -vdd  STR         Virtual domain delimiter list ("+" by default)
         -vddc CHAR        Canonical virtual domain delimiter ("+" by default)
         -m    FILENAME    Spoof message file location

Option Descriptions

The following table explains the Multiplexor Installer prompts, command-line options , and environment variables in more detail.  On Unix, the environment variables listed here are set by the shell scripts ImapMMP.sh and PopMMP.sh; values for the variables are stored in the configuration files ImapMMP.config and PopMMP.config. (On Windows NT, configuration information is stored in the NT Registry.) When the Multiplexor program executes, it receives its configuration information directly from the command line (if options are specified) or from the environment variables or NT Registry (if options are not specified).

To make permanent configuration changes, use the Multiplexor Installer (on Unix) or uninstall and then re-install the Multiplexor (on Windows NT). (see Changing the Configuration of a Messaging Multiplexor Instance).
 
 

     
    Installer prompt
    Command-line option Environment Variable
    Description
    Unix  
    LDAP Host: 
     
    NT 
    Host Name: 
    Server Port: 
     
    -h host[:port] LDAPHost The host machine name and port of the LDAP server that contains your user database (among other things). You must set up the LDAP host before the Multiplexor can work properly. 
     
    Default = Localhost:IPPORT_LDAP ( = port 389) 
     
    Unix 
    Base DN: 
      
    NT 
    Base 
    Distinguished Name: 
     
    -b baseDN BaseDN The  distinguished name (DN) to use as the search base for LDAP user queries. The BaseDN must specify an entry to which the bind distinguished name (bindDN) has access privileges for operations on the directory database.  
     
    Default = "" 
     
    Unix 
     [IMAP4/POP3] MMP LogDir: 
      
    NT 
    Log Directory
    -o directory LogDir The directory in which the Multiplexor creates log files. If you specify a directory that doesn't exist, no log file is created. 
     
    Log file names have the following format: MMP_yyyymmdd.log 
     
    Default = current directory (the directory that contains Multiplexor) 
     
    Unix 
    Log Level: 
        
    NT 
    (no prompt)
    -v num LogLevel The logging verbosity level--the amount of information written into log files. You can specify a number from 0 through 10, with 10 representing the highest level of verbosity. At higher levels, more events are logged. 
     
    Default = 1 
     
    Unix 
    Should the MMP bind to LDAP as someone in particular (y/n): 
      
    NT 
    LDAP Bind DN: 
     
    -D bindDN BindDN The bind distinguished name--the DN used by the Multiplexor to authenticate to an LDAP server when performing an operation. Some LDAP servers may require that a client (in this case the Messaging Multiplexor) be authenticated before it can search the database for certain information.  If your server has ACLs that require some level of authentication for getting a user's mail information, set this option. 
     
    Default = Anonymous 
    (select n on Unix installer to choose default) 
    (leave field blank on NT installer to choose default) 
     
    Unix 
    What's the password for "BindDN": 
      
    NT 
    Password: 
     
    -w password BindPassword The password associated with the bind distinguished name, for authenticating to an LDAP server. 
     
    Default = none 
     
    Unix 
    Number of Threads: 
      
    NT 
    (no prompt) 
    -t num NumThreads The maximum number of worker threads to allocate to the machine on which Multiplexor runs. If the  machine has multiple CPUs, running the Multiplexor with worker threads will improve performance. The optimal number of work threads is the number of processors on the machine. For example if your machine has two CPUs, specify 2 processes. If this is a single-processor machine, specify zero for optimal performance. 
     
    Default = 0 (the main thread does all the work) 
     
    Unix 
    Should the MMP listen on a non-default port (y/n): 
      
    NT 
    (POP3 Ports) 
    Incoming: 
    (IMAP4 Ports) 
    Incoming: 
    -p [IP:]port ListenPort The port on which to listen for incoming client connections. 
     
    Default = 110 for POP3; 143 for IMAP (the standard ports) 
    (select n on Unix installer to choose defaults) 
     
    Command line: IP is an optional bind address for a machine that is multihomed (has more than one IP address). 
      
    Keep the following in mind when entering a port number: 
    • Port numbers can be any number from 1 to 65535.
    • If you choose a port number 1024 or lower, you must (on Unix) start all processes as root (superuser). 
    • On Unix, make sure the port you choose isn't already in use or reserved for another service. Look at the file /etc/services on the Multiplexor machine to make sure you don't assign a port number that is used by another service. (On NT, the installer checks for conflicts.)
    Unix 
    Do your main [IMAP4/POP3] servers listen on non-default ports (y/n): 
      
    NT 
    (POP3 Ports) 
    Outgoing: 
    (IMAP4 Ports) 
    Outgoing: 
    -c port BacksidePort The port on which to connect to the store server. Using a non-default value here allows you to, for example, run a store server on the same machine as the Multiplexor. You might want to do this if you want a flat configuration--that is, if you want to run Multiplexors on all machines. 
     
    Default = 110 for POP3; 143 for IMAP (the standard ports) 
    (select n on Unix installer to choose defaults) 
     
    Keep the following in mind when entering a port number: 
    • Port numbers can be any number from 1 to 65535.
    • If you choose a port number 1024 or lower, you must (on Unix) start all processes as root (superuser). 
    • On Unix, make sure the port you choose isn't already in use or reserved for another service. Look at the file /etc/services on the Multiplexor machine to make sure you don't assign a port number that is used by another service. (On NT, the installer checks for conflicts.)
     Unix 
    Would you like to override the IMAP4 MMP's CAPABILITY response (y/n): 
      
    NT 
    IMAP4 Capability Response 
    -x STR Capability Capability replacement string. If you are using Netscape Servers and want to use the Manage Mail Account feature, you must specify this Capability configuration parameter to change the Multiplexor's capability. The Multiplexor uses the string you specify (STR) instead of its own (default) capability to tell IMAP clients what the Multiplexor (or the servers behind it) can do. This option has no effect on POP3. 
     
    Default: 
    IMAP4 IMAP4rev1 AUTH=LOGIN AUTH=PLAIN 
    (select n on Unix installer to choose default) 

    Suggested string to support Manage Mail Account: IMAP4 IMAP4rev1 AUTH=LOGIN AUTH=PLAIN X-NETSCAPE 
     

    Unix 
    Would you like to override the MMP's banner (y/n): 
      
    NT 
    POP3 Banner 
     
    IMAP4 Banner 
     
    -ba STR Banner Banner replacement string. The Multiplexor uses STR instead of its default banner for its greeting line. 
     
    Default = "Netscape Messaging Multiplexor ready" 
    (select n on Unix installer to choose default) 
     
    Unix 
    Would you like to override the MMP's LDAP search string (y/n): 
      
    NT 
    LDAP Search 
     
    -us STR UidSearch String for UID search. When performing LDAP directory searches, the Multiplexor uses STR instead of  the default. 
     
    You can use this option to change the attributes used in directory searches.  You can replace the default with any valid LDAP search string (for example, "|(uid=%s)(cn=%s)"). %s in the search string is replaced by the user name the Multiplexor receives for user authentication. 
       
    Default: "uid=%s" 
     (select n on Unix installer to choose default) 
     
    Unix 
    Should this MMP do virtual domain mapping (y/n): 
     
    Please type the location of the mapping file, and hit return.: 
      
    NT 
    [Use | Do Not Use] Virtual Domain Mapping 
     
    Virtual Domain File 
    -vd filename VirtualDomainFile The Multiplexor  can map IP addresses to domain names for searching an LDAP directory and for logging in to the store server.  When a connection is accepted from a client, if the client's IP address is in the virtual domain mapping file, the domain is appended to the userid and used for the LDAP search and for subsequent replay of authentication. This capability is useful for hosting multiple domains with overlapping userid name spaces. 
     
    Each line in the virtual domain mapping file contains one IP-to-domain mapping (the IP address, then a space, then the domain name). Lines that start with '#' are ignored. 

    Default = n (no virtual domain mapping) 
     

    Unix 
    Do you want to specify a list of virtual domain delimiters? (y/n) 
     
    -vdd STR VirtualDomainDelim A string containing the acceptable delimiter characters for virtual domains. If virtual-domain mapping is activated, the last character in the ID string received by the Multiplexor that matches a character in this string is considered a delimiter separating the userid from the domain name. (The Multiplexor searches for the delimiter backwards from the end of the received ID string.) 

    Default = "+" 
    (used if you specify no delimiters) 
     

    Unix 
    Do you want to specify a canonical virtual domain delimiter? (y/n)
    -vddc CHAR CanonicalVirtualDomainDelim If virtual-domain mapping is activated, the character the the Multiplexor itself inserts to separate the userid received by the Multiplexor from the virtual domain that the Multiplexor appends to it for LDAP searching or for authentication to the store server. 

    Default = "+" 
    (default string passed to directory is "userid+virtual.domain") 
     

    Unix 
    Would you like to provide a "spoof" message for POP3 (y/n): 
     
    Please type in the location of the file to be used, and hit return.: 
     
    NT 
    [Use | Do Not Use] a "spoof" message 
     
    "Spoof" Message File 
     
    -m filename SpoofMessageFile The file to use for POP3 inbox spoofing. The MMP can imitate a base-functionality POP3 server in case the Multiplexor can't connect to a client's store machine.  In such a  situation, the Multiplexor creates an inbox for the user and places this one message into it. 

    The format of the message contained in this file should conform to  RFC 822 (including the final  '.'). 
     
    Default = no spoof message.

    Unix 
    Should the IMAP4 MMP do SSL (y/n): 
      
    NT 
    [Allow | Do Not Allow] IMAP over SSL 

     

    -s SSLParms SSLEnable  Whether or not to enable SSL connections with clients. If you enable SSL, the Multiplexor  listens on both normal and SSL ports. 
     
    Default = n (SSL not enabled) 
     
    If you do enable SSL, you must set the following environment variables (SSLParms)
     
    SSLSecmodFile 
    SSLCertFile 
    SSLKeyFile 
    SSLKeyPasswd 
    SSLCipherSpecs 
    SSLCertNickname 

    If you specify the -s option in the command line, all six parameters (SSLParms) must appear, in this order, on the command line: 
     
    -s SECMODFILE CERTFILE KEYFILE KEYPASS CIPHERS CERTNAME 

    The parameters are described below. You can specify an empty parameter with empty quotes (""). 
     

    Unix 
    Should the MMP listen for SSL on a non-default port (y/n): 
      
    NT 
     IMAP4 SSL Port 
     
    -ps port SSLListenPort The port on which to listen for incoming client SSL connections. 
     
    Default = 993 for IMAP (the standard SSL IMAP port) 
    (select n on Unix installer to choose default) 
     
    Unix 
    Do you have a secmod database (y/n): 
     
    Please type the location of the secmod database.: 
      
    NT 
    [Yes, I have | No, I don't have] a secmod database 
     
    Secmod Database File 
     
     
    SECMODFILE (parameter of SSLParms) SSLSecmodFile Security module database file location (usually null). If you have hardware accelerators for SSL ciphers, this file describes them to the Multiplexor. 

    Default = no secmod database. 
    (select n on Unix installer to choose default) 
     

    Unix 
    Please type the location of the certificate database.: 
      
    NT 
    Certificate Database File 
     
    CERTFILE (parameter of SSLParms) SSLCertFile Server certificate database file location (defined when you obtained a certificate for this server). The Multiplexor needs a server certificate to offer to clients in the handshake phase of SSL. The location specified here should be absolute, not relative to the Multiplexor installation directory. 
     
    Default = cert7.db 
     
    Unix 
    Please type the location of the key database.: 
      
    NT 
    Key Database File 
     
    KEYFILE (parameter of SSLParms) SSLKeyFile Key database file location (defined when you obtained a certificate for this server). The Multiplexor needs a private key corresponding to its SSL server certificate.  The location specified here should be absolute, not relative to the Multiplexor installation directory. 
     
    Default = key3.db 
        
    Unix 
    Is the key file password protected (y/n): 
     
    Please type the key file password.: 
      
    NT 
    Password 
     
    KEYPASS  (parameter of SSLParms) SSLKeyPasswd Password that protects access to the private key file. 
    The password may be null if the key is not password-protected. 
     
    Default = no password protection
    Unix 
    Please type the names of the desired cipher specs, separated by colons, or the word "all".: 
      
    NT 
    SSL uses a set of widely-known cipher algorithms... 
     
    CIPHERS (parameter of SSLParms) SSLCipherSpecs A colon-separated list of ciphers (or the string "all") representing the cipher algorithms that this server can use to encrypt SSL sessions.  The client and server agree to one of them when a session is established.  These are the available cipher specifications: 
    SSL_RSA_WITH_RC4_128_MD5 
    SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA 
    SSL_RSA_WITH_3DES_EDE_CBC_SHA 
    SSL_RSA_FIPS_WITH_DES_CBC_SHA 
    SSL_RSA_WITH_DES_CBC_SHA 
    SSL_RSA_EXPORT_WITH_RC4_40_MD5 
    SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5 
    SSL_RSA_WITH_NULL_MD5 
     
    Default = all
    Unix 
    Please type the name of the certificate in the database.: 
      
    NT 
    Certificate Name 
     
    CERTNAME  (parameter of SSLParms) SSLCertNickname Name of this server's SSL server certificate (defined when you obtained the certificate). The Multiplexor uses this string to identify the certificate in its certificate database (SSLCertFile). 
     
     
 

Directly Setting Environment Variables in Configuration Files

On Unix, you can set configuration options by directly modifying environment-variable specifications in the configuration files ImapMMP.config and PopMMP.config. On Windows NT, you can similarly set options by modifying entries in the NT Registry at \\HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\MMP.

For example, on Unix you can specify the Capability configuration option by adding it as an environment variable to the ImapMMP.config file in the /MMPRoot/InstanceName directory (such as /home/netscape.mmp/mmp-sandpit) instead of specifying it from the command line. To specify IMAP capability with Netscape servers, as a specific example, you would add this line:

    Capability="IMAP IMAP4rev1 AUTH=LOGIN AUTH=PLAIN X-NETSCAPE"

Example Multiplexor Configuration Files

Messaging Multiplexor configurations are stored as configuration files (ImapMMP.config and PopMMP.config) in the directory mmp/MMP-servername. This section shows example Multiplexor configuration files for a simple network topology with multiple mail servers.

Example Messaging Topology

In the example shown in Figure 3, the fictional Airius Corporation has two Multiplexors (on separate machines), each supporting several Netscape Messaging Servers. POP and IMAP user mailboxes are split across the Messaging Server machines, with each server dedicated exclusively to POP or exclusively to IMAP. (You can restrict client access to POP services alone by removing the IMAP-server binary; likewise, you can restrict client access to IMAP services alone by removing the POP-server binary.) Each Multiplexor also supports only POP or only IMAP. The LDAP directory service is on a separate, dedicated machine.
 
Figure 3. Example Multiplexor Topology
 

 

 
Configuration Example for IMAP Connections

The IMAP Multiplexor in Figure 3 is installed on sandpit, a machine with 2 processors. This Multiplexor is listening to the standard port for IMAP connections (143). The Multiplexor communicates with the LDAP server on the host phonebook for user mailbox information, and it routes the connection to the appropriate IMAP server. It overrides the IMAP capability string, provides a virtual domain file, and supports SSL communications. This is its configuration file:
    LDAPHost=phonebook
    BaseDN="o=Airius.com"
    LogDir="/usr/netscape/suitespot/mmp/MMP_sandpit/log"
    LogLevel=5
    BindDN="cn=Directory Manager"
    BindPassword="password"
    NumThreads=2
    ListenPort=143
    BacksidePort=143
    Capability="IMAP4 IMAP4rev1 AUTH=LOGIN AUTH=PLAIN X-NETSCAPE"
    VirtualDomainFile="/usr/netscape/suitespot/mmp/vdfile.txt"
    SSLEnable=y
    SSLListenPort=993
    SSLSecmodFile="/usr/netscape/suitespot/mmp/secmod.db"
    SSLCertFile="/usr/netscape/suitespot/mmp/cert7.db"
    SSLKeyFile="/usr/netscape/suitespot/mmp/key3.db"
    SSLKeyPasswd=""
    SSLCipherSpecs="all"
    SSLCertNickname="Airius.com Server Cert"

Configuration Example for POP Connections

The POP Multiplexor in Figure 3 is installed on tarpit, a machine with 4 processors. This Multiplexor is listening to the standard port for POP connections (110). The Multiplexor communicates with the LDAP server on the host phonebook for user mailbox information, and it routes the connection to the appropriate POP server. It also provides a spoof message file. This is its configuration file:
    LDAPHost=phonebook
    BaseDN="o=Airius.com"
    LogDir="/usr/netscape/suitespot/mmp/MMP_tarpit/log"
    LogLevel=10
    BindDN="cn=Directory Manager"
    BindPassword="password"
    NumThreads=4
    ListenPort=
    BacksidePort=
    SpoofMessageFile="/usr/netscape/suitespot/mmp/pop3spoof.txt"
    SSLEnable=n

Copyright 1998 Netscape Communications Corporation. All rights reserved.