Having Netscape Mail Server Coexist with ListManager

The way to have Netscape Mail Server coexist with ListManager is to have Netscape listen to another port besides port 25 (the SMTP mail default port). Let ListManager listen on port 25, and then tell it to forward non-ListManager mail on to the Netscape Mail Server.

Here are the steps to have Netscape Mail Server and ListManager coexist:

1) Install ListManager and then make sure that it is not currently running.

2) Create an 'A' record in your DNS, which is an alternate name for the current machine. The mail that should be accepted by ListManager will be sent to this address. All mail delivered to ListManager which does not have this name will be forwarded on to Netscape Mail Server.

For example, if your machine is currently called "mail" in your DNS, add another entry below it that has the same data, but with a new name, as in:

mail IN A 207.105.6.2 ; the original host name
listmanager IN A 207.105.6.2 ; the new "alias" host name

After this change, restart your DNS server.

3) Use the registry editor (regedt32.exe) to move Netscape Mail Server port 26. The key you want to change is located at

HKEY_LOCAL_MACHINE\Software\Netscape\MailServer\SMTP-Accept\Config\Socket

Change this value from "25" to "26"

4) Restart your Netscape Mail Server.

5) Start your ListManager in the foreground, by clicking the "Run ListManager Now" icon.

6) In Utilities: Administration: Server: Server Settings: Network Settings: Receive Email, find the field that says "Forward Mail:". Type this in the Forward Mail field:

127.0.0.1 26

This instructs ListManager to forward non-ListManager mail to port 26, where Netscape Mail Server is listening.

Now, go to Utilities: Administration: Server: Server Settings: Security: Bans and find "Mail Receive Rules". Type the name (or names) of the host names that ListManager should accept mail for. Any mail that comes in for ListManager, which is not addressed, to these hosts will automatically be forwarded to your Netscape Mail Server.

For example, if your machine was called "mail.mycorp.com" and you made an alias for it (in step 2) called "listmanager.mycorp.com", then in the "Mail Receive Rules" field enter this data:

@listmanager.mycorp.com

If you have multiple names for your ListManager, which it should answer, enter each of them here, separated by a carriage return. This means that all mail addressed to "@listmanager.mycorp.com" will be accepted and processed by ListManager and any mail not addressed to "@listmanager.mycorp.com" will be forwarded to your Netscape Mail Server.

7) Type "shutdown" on your ListManager console. Wait for ListManager to shutdown, then start it again, by clicking the "Run ListManager Now" icon.

8) Start your mail program and send mail to lyris@ your ListManager hostname. For example, if your alias is "listmanager.mycorp.com", send mail to "lyris@listmanager.mycorp.com". A minute or two after sending your message, ListManager should have sent you a response back. Now, send a test message to a user on your Netscape Mail Server to make sure that is working.

Notes

Netscape Mail Server appears to not have the capability to forward to an alternate TCP/IP port, unlike Post.Office, which it was derived from. We also believe that Netscape Mail Server is not able to leave a TCP/IP address unused on a machine. If it could, ListManager would be able to use just that TCP/IP address to coexist with it. If you know otherwise, please let us know at private-support@lyris.com. Netscape has told us that they plan to address this in a future version of their product.