Quick install instructions for WinPMail and Mercury in NDS mode. ---------------------------------------------------------------- Although we provide these quick install instructions for people who are impatient to get started, we REALLY, REALLY DO urge you to read the full README.TXT documentation file at some stage... * If you want to install WinPMail on your 4.1 server for simple local mail only, go to Section 1 below (search for "SECTION 1" using your editor's "Find" command). * If you want to install WinPMail and Mercury on your 4.1 server and want to use Mercury to manage all your mail (i.e, you do not want WinPMail to perform local delivery), go to Section 2 below. * If you want to install WinPMail and Mercury on your 4.1 server, and want to use WinPMail for local mail and Mercury for Internet mail, go to Section 3 below. ***** IMPORTANT NOTE!!! ***** The DOS utilities MAKEMBOX.EXE and PMIGRATE.EXE, and the Windows NICA enabler WPNNW4.DLL all need to be able to find the Novell Unicode files on your DOS path in order to operate. The unicode files are the 200 or so files that appear in SYS:PUBLIC/NLS on your file server. The easiest way to ensure that this happens is to map a search drive to that directory before using the utilities - use the command: MAP INS S16:=SYS:PUBLIC/NLS ----------------------------------------------------------------- SECTION 1: Installing WinPMail for Local Mail only. ----------------------------------------------------------------- STEP 1: Copy WPNNW4.DLL into the same directory as your copy of WinPMail v2.23 or later. STEP 2: Run the version of PCONFIG supplied with this archive. Choose a configuration context (the context into which PCONFIG should store the configuration profile). Make sure that "Enabled" is set to 'N' in both the SMTP and MHS configuration screens. Choose "Save and exit". STEP 3: Run MAKEMBOX to create the new mail directories for all your existing users. The usual way to do this is to issue the command "MAKEMBOX -r *". STEP 4: [Optional] Install PMUSER.NLM on your file server by copying it into SYS:SYSTEM then going to the file server console and typing the command "LOAD PMUSER". When PMUSER asks for a user and password, enter your Admin username and password (see the main reference document for details on using less priv- ileged accounts for this purpose). If you do not load PMUSER, mailboxes will not be created automatically for your users - you will have to create them manually using MAKEMBOX.EXE. STEP 5: [Optional] If you have previously been running Pegasus Mail in Bindery Emulation mode on your file server, migrate the user mailboxes from Bindery mode to NDS mode using the PMIGRATE command. The most usual way of doing this is to issue the command "PMIGRATE *". ----------------------------------------------------------------- SECTION 2: Installing WinPMail and Mercury on your server, and having Mercury process all your mail. ----------------------------------------------------------------- PART A - Installing WinPMail STEP 1: Copy WPNNW4.DLL into the same directory as your copy of WinPMail v2.23 or later. STEP 2: Run the version of PCONFIG supplied with this archive. Choose a configuration context (the context into which PCONFIG should store the configuration profile). Choose "SMTP Internet Mail Interfaces" from the Main Menu and fill in the blanks according to the guidelines you will find in WGUIDE.EXE. In particular, make sure that "Use always" is set to 'Y' to force WinPMail to pass all its outgoing mail to Mercury. When you have finished, press Ctrl+Enter to save the settings, then from the main menu, choose "Save and exit". STEP 3: Run MAKEMBOX to create the new mail directories for all your existing users. The usual way to do this is to issue the command "MAKEMBOX -r *". STEP 4: [Optional] Install PMUSER.NLM on your file server by copying it into SYS:SYSTEM then going to the file server console and typing the command "LOAD PMUSER". When PMUSER asks for a user and password, enter your Admin username and password (see the main reference document for details on using less priv- ileged accounts for this purpose). If you do not load PMUSER, mailboxes will not be created automatically for your users - you will have to create them manually using MAKEMBOX.EXE. STEP 5: [Optional] If you have previously been running Pegasus Mail in Bindery Emulation mode on your file server, migrate the user mailboxes from Bindery mode to NDS mode using the PMIGRATE command. The most usual way of doing this is to issue the command "PMIGRATE *". PART B - Installing Mercury If you have never installed Mercury on your file server before, run the program SETUP.EXE supplied with Mercury to install it, then once you have done so, go straight to step 4. If you already have Mercury installed on your server, or if you want a customized installation, follow steps 1-3. STEP 1: Copy the various Mercury NLM files to your file server's SYS:SYSTEM directory. You will need to copy MERCNDS.NLM, MERCNDSS.NLM, MERCURYC.NLM and optionally MERCNDSP.NLM. STEP 2: Create the Spool directory for Mercury - we recommend that you use SYS:SMTPMAIL, since this is the value in the default MERCURY.INI file. Make sure that all users have [C] rights in this directory. STEP 3: Copy the sample MERCURY.INI file supplied with Mercury to your file server's SYS:SYSTEM directory. Edit it using any text editor (even - - DOS EDIT) and change the various settings to reflect your system. In particular, you will probably have to change the following entries: In the [General] section: - myname - timezone - mailqueue and smtpqueue (if you used a directory other than SYS:SMTPMAIL in step 2) In the [Mercury] section: - scratch - postmaster - noticeboards (optional) In the [NDS] section: - username (although we strongly recommend using ADMIN). In the [MercuryC] section: - host In the [Groups] section: - any NetWare groups you want to enable for mailing In the [Domains] section: - see the detailed explanation in the sample INI file for instructions on this section. In a default installation, where you have used MINSTALL to install the files, you should not need to change any other entries in MERCURY.INI STEP 4: Load MERCNDS.NLM, MERCNDSS.NLM, MERCURYC.NLM and optionally MERCNDSP.NLM from the file server console. STEP 5: (Optional) Modify your file server's AUTOEXEC.NCF so that the Mercury modules are loaded automatically at startup. The LOAD statements for the Mercury NLMs should usually appear at the very end of your AUTOEXEC.NCF. Mercury Setup will offer to make this change for you if you run it to install the program. STEP 6: (Optional) Create any alias files you need on your server using the MALIAS alias compiler. See the sample ALIAS.MER file supplied with Mercury for details on aliasing. STEP 7: (Optional) If you need POP3 aliases (aliases to allow users to login to a specific context using a simple username), then create a POPALIAS.MER file in SYS:SYSTEM. See the sample POPALIAS.MER file supplied with Mercury for more details on this function. ----------------------------------------------------------------- SECTION 3: Installing WinPMail and Mercury on your server, using WinPMail for local mail and Mercury for Internet mail. ----------------------------------------------------------------- PART A - Installing WinPMail STEP 1: Copy WPNNW4.DLL into the same directory as your copy of WinPMail v2.23 or later. STEP 2: Run the version of PCONFIG supplied with this archive. Choose a configuration context (the context into which PCONFIG should store the configuration profile). Choose "SMTP Internet Mail Interfaces" from the Main Menu and fill in the blanks according to the guidelines you will find in WGUIDE.EXE. In particular, make sure that "Use always" is set to 'N' so that WinPMail can deliver mail locally. When you have finished, press Ctrl+Enter to save the settings, then from the main menu, choose "Save and exit". STEP 3: Run MAKEMBOX to create the new mail directories for all your existing users. The usual way to do this is to issue the command "MAKEMBOX -r *". STEP 4: [Optional] Install PMUSER.NLM on your file server by copying it into SYS:SYSTEM then going to the file server console and typing the command "LOAD PMUSER". When PMUSER asks for a user and password, enter your Admin username and password (see the main reference document for details on using less priv- ileged accounts for this purpose). If you do not load PMUSER, mailboxes will not be created automatically for your users - you will have to create them manually using MAKEMBOX.EXE. STEP 5: [Optional] If you have previously been running Pegasus Mail in Bindery Emulation mode on your file server, migrate the user mailboxes from Bindery mode to NDS mode using the PMIGRATE command. The most usual way of doing this is to issue the command "PMIGRATE *". PART B - Installing Mercury If you have never installed Mercury on your file server before, run the program SETUP.EXE supplied with Mercury to install it, then once you have done so, go straight to step 4. If you already have Mercury installed on your server, or if you want a customized installation, follow steps 1-3. STEP 1: Copy the various Mercury NLM files to your file server's SYS:SYSTEM directory. You will need to copy MERCNDS.NLM, MERCNDSS.NLM, MERCURYC.NLM and optionally MERCNDSP.NLM. STEP 2: Create the Spool directory for Mercury - we recommend that you use SYS:SMTPMAIL, since this is the value in the default MERCURY.INI file. Make sure that all users have [C] rights in this directory. STEP 3: Copy the sample MERCURY.INI file supplied with Mercury to your file server's SYS:SYSTEM directory. Edit it using any text editor (even - - DOS EDIT) and change the various settings to reflect your system. In particular, you will probably have to change the following entries: In the [General] section: - myname - timezone - mailqueue and smtpqueue (if you used a directory other than SYS:SMTPMAIL in step 2) In the [Mercury] section: - scratch - postmaster - noticeboards (optional) In the [NDS] section: - username (although we strongly recommend using ADMIN). In the [MercuryC] section: - host In the [Groups] section: - any NetWare groups you want to enable for mailing In the [Domains] section: - see the detailed explanation in the sample INI file for instructions on this section. In a default installation, where you have used MINSTALL to install the files, you should not need to change any other entries in MERCURY.INI STEP 4: Load MERCNDS.NLM, MERCNDSS.NLM, MERCURYC.NLM and optionally MERCNDSP.NLM from the file server console. STEP 5: (Optional) Modify your file server's AUTOEXEC.NCF so that the Mercury modules are loaded automatically at startup. The LOAD statements for the Mercury NLMs should usually appear at the very end of your AUTOEXEC.NCF. Mercury Setup will offer to make this change for you if you run it to install the program. STEP 6: (Optional) Create any alias files you need on your server using the MALIAS alias compiler. See the sample ALIAS.MER file supplied with Mercury for details on aliasing. STEP 7: (Optional) If you need POP3 aliases (aliases to allow users to login to a specific context using a simple username), then create a POPALIAS.MER file in SYS:SYSTEM. See the sample POPALIAS.MER file supplied with Mercury for more details on this function.