Page 16 - Mercury Manual.book

11 The Mercury Core Module
The “Mercury Core Module” Configuration menu option.

Options on the Local Domains page
This is probably the single most critical area of configuration in the Mercury system – if you
get this section wrong, you will inevitably get mail loops and other problems. In this section,
you must tell Mercury all the Internet domain names it should regard as “local” – that is, for
which it should attempt direct delivery on the local system rather than forwarding the mail to
another machine for processing. The host/server section of each definition is intended to al-
low Mercury to deliver mail to multiple file servers in supported network environments: if
you are running Mercury on a single system or serving Pegasus Mail in either networked or
multi-user standalone mode, the host/server entry is ignored. In the NetWare environment,
this entry is used to tell Mercury that a particular domain represents addresses on a specific
file server or tree. When entering domains into this section, you should usually provide three
entries per local Internet domain – a fully-qualified version, a simple version, and a special
entry called a domain literal version, which is the IP number of your system enclosed in
square brackets. For example, if your system’s Internet name was calli-
ope.pmail.gen.nz (192.156.225.76), you might create these domains definitions:

calliope calliope
calliope calliope.pmail.gen.nz
calliope [192.156.225.76]

If you are running Mercury on a network that is behind a NAT router, you typically should
not add the domain literal form, because the internal addresses have no meaning beyond the
NAT router.

Domain mailboxes
Mercury supports the idea of a domain mailbox, or a mailbox that accepts mail addressed to
any user at a given domain. To create a domain mailbox, first create the user account that is
to receive all mail addressed to the domain, then place an entry in the Domains recognized as
local by this server section in the following format:

DM=username domain address

username can be any valid reference to a single local user on your system. So, to create a
domain mailbox where user mailserver receives all mail addressed to any user in the domain
fish.net, you would create this entry:

DM=mailserver fish.net

With this entry in place, mail sent to [any address]@fish.net will be delivered into user
mailserver's mailbox.

Novell NetWare NDS Mode
In NetWare NDS mode, the domains section can be used to tie a domain to a specific portion
of your tree. So, if you have all mail sent to the domain myorg.com to a context in your NDS
tree called sales.us.myorg, you would use this entry:

sales.us.myorg myorg.com

When specifying an NDS domain, you can apply the definition to an entire portion of a tree
(including all sub-levels within the NDS tree) by prefixing the context name with the special
character / - so, in the example above, if you simply wanted to equate your entire NDS tree
with the domain myorg.com, you would use this entry:

/[root] myorg.com