Page 27 - Mercury Manual.book

The Mercury Core Module 22
Network support

ation at install time. When this module is loaded, selecting Network support will bring up a
dialog allowing you to configure Mercury to support multiple file servers.

In multi-server mode, Mercury requires privileged access to every server to which it is to pro-
vide mail services. You should enter in this dialog the name of the server, the username Mer-
cury should use to login to that server (we recommend that you use SUPERVISOR or ADMIN)
and the password matching that username. Passwords are stored in a heavily encrypted local
format, safe from prying eyes.

When using Mercury in multiserver mode, there must be some way for Mercury to tell which
server is the destination for any given address: the easiest way to do this is to assign a differ-
ent Internet domain name to each server, then have multiple entries in the [Domains] section
of MERCURY.INI, one for each server. If you want Mercury to service all your servers under
a common domain name (that is, you want one Internet domain name to apply to all your file
servers) then every user will need a unique address and an entry in the alias file. The alias
entry should resolve to a standard NetWare SERVER/USER reference – so, if the address
bob@foo.com referred to a user called “BOB” on a server called “STAFF”, your alias entry
would look like this: bob@foo.com == STAFF/BOB.

NetWare NDS Mode Support
Mercury's NetWare NDS Mode support is provided by a file called MN_NW4.DLL, which will
be installed by the Mercury installer if you choose NetWare NDS mode operation at install
time. NetWare NDS mode requires slightly more configuration than Bindery mode, but takes
Each user’s mailbox full advantage of the features offered by NDS. When running Mercury in NDS mode, you
must be created using will need to use the NCONFIG utility (supplied as part of the Mercury/32 distribution archive,
the NCONFIG utility be-
fore the user can receive and installed in the directory where Mercury is installed) to create mailboxes on the file serv-
mail. er for your NDS users. For more information on issues associated with NDS mode installa-
tion, please see the NCONFIG help file.
.
When running in NDS mode, selecting Network Support from the Mercury Configuration
menu will bring up a dialog containing only one item – Use LDAP synonyms: if this option
The user’s LDAP Syno-
nym can be edited using is enabled, then Mercury will use the special NDS user attribute called Internet Email Ad-
the NCONFIG utility, or dress when working out delivery addresses for your users. In this mode, the NDS database is
the Novell NWADMN32
system utility. searched for the address synonym, and a conventional Mercury synonym database is not re-
quired.

Managing local users
This option is only available when no Network personality module is loaded. It allows you
to create and manage users and mailboxes on the local system. This option directly manipu-
lates the Pegasus Mail user database file, PMAIL.USR, and is compatible with Pegasus Mail
in its multi-user standalone modes. Selecting this option presents a list of users known to
Mercury on the current system: users with administrative privileges (that is, users who are
permitted to add and edit the details for other users) are shown with an * next to their user-
name. To edit a user, double-click his or her entry in the list.

POP3 password, APOP secret These values are used by the MercuryP POP3 server to con-
trol access to user mailboxes via the POP3 protocol. The APOP secret is an optional extra
password that can be used to increase the security of the connection: the user must be using
a mail program that supports the APOP protocol (Pegasus Mail v2.75 and later, and Eudora
support APOP) and must enter the same secret value into that client as the value entered in
this dialog. When APOP is used, the user’s POP3 password is not required, and no plain text
version of a password is ever passed across the network: using APOP is strongly recommend-
ed in Local Area Network environments.