Page 11 - Mercury Manual.book

The Mercury Core Module 6
Critical items

The Mercury Core Module

Like the NLM version of Mercury, Mercury/32 stores its configuration and settings in a file
called MERCURY.INI, located in the directory where it is installed, but in general you will not
modify this file directly - you will use the program's Configuration menu instead. In this
chapter, we will cover configuring the core module and its support modules while it is run-
ning, using the Configuration menu options.

Critical items

If you answer all the
questions in the installer There is a handful of configuration items in Mercury/32 that you must get right or the pro-
correctly, these items will gram will not work properly. The most important of these are the following:
all be set to reasonable
default values.
• The Local Domains section of the core module configuration dialog (see below)
• The computer's Internet name in the core module General configuration page
• The Mercury Primary Mail Queue directory in the core module Mail queue configura-
tion page
• The name of the local user who is to act as your postmaster

The computer must also have a properly-configured temporary files directory referenced in
either a TEMP or TMP environment variable. In practically all cases this is assured by Windows
itself, but we mention it here because it is a key requirement for the proper operation of Mer-
cury/32.

Configuring the Core Module

Various options on the Configuration menu directly control the operation of the Mercury core
module: the items on the Configuration menu that are covered in this chapter are the follow-
ing:

• Mercury Core Module is used to configure the general operation of the system. Many of
the settings made using this option will have a direct bearing on other modules in the
system.

• Template files is where you will configure the text of messages returned by Mercury
when errors or confirmations need to be generated automatically.

• Mail server allows you to configure Mercury’s autonomous mail server – a robotic proc-
ess that acts on commands sent to it via e-mail.

• Aliases allows you to create alternative versions of addresses on the system. An alias can
be used anywhere the real address would be used.

• Network support Mercury has specific support modules that allow it to interact intelli-
gently with various Local Area Network (LAN) environments. Network support is
loaded and maintained by the core module, so its configuration is covered in this chapter.
The Manage Local Users
option is disabled if you • Managing local users When you are not using a LAN personality module for Mercury,
are using a network per- it maintains its own database of users and their mailboxes. The Manage local users
sonality module, such as
the Novell NetWare mod- option is where you will create and manage your users and their mailboxes in this mode.
ules..