Page 26 - Mercury Manual.book

21 The Mercury Core Module
Network support

Resetting notifications If you find, for some reason, that you want to reset Mercury so that
you receive all existing notifications again, delete the file MLNOTIFY.MER from the directory
where MERCURY.EXE is installed. Notifications are usually purged from the development
server after a couple of months.

Notification host This is the name of the host Mercury should check for new advisories. The
default value is notify.pmail.com, and you should only change it if specifically instructed
to do so by the Mercury Technical Support group.

Check for advisories every This control specifies how often Mercury should check for new
advisories, in hours. You cannot specify a value lower than four hours in this field.

Distribute advisories to In this field, you can type any number of valid local usernames, sep-
arated by commas: Mercury will deliver any advisories it downloads as mail messages to
these local users. It is important to understand that you can only enter local usernames in this
field – you cannot enter an alias or any address containing '@', and no filtering, content con-
trol, policy or autoforwarding will be applied to the advisories (which guarantees that you
won't miss an important notification through an over-zealous spam filter). You can be confi-
dent about the messages you retrieve from this service – we have taken elaborate steps to en-
sure that they are safe and secure, and pre-scan them to verify that they are completely free
from any type of malicious content.

Notification types
You can specify the types of advisory you want to receive using the 'Enable' checkboxes.

Security and vulnerability advisories These are the highest priority notifications: they will
detail any potential security weaknesses that might be discovered in Mercury, and will pro-
vide any known workarounds for avoiding them. All licensed sites should check this control.

Updates, patches and new releases These advisories will appear any time there is a new or
updated version of Mercury, or a patch for any Mercury component.

General information and news This type of advisory is informational and will usually be fair-
ly infrequent (typically not more than one per month at most). They might give an overview
of what we're working on, upcoming release schedules, or long-term planning overviews.

Network support

The Network support configuration menu option is only available if you are using a Network
personality module for Mercury. Network personality modules allow Mercury to take advan-
tage of specialised features of the Local Area Network system you use – at the time of writ-
ing, network personality modules are available for Mercury/32 providing support for Novell
NetWare bindery based file servers (that is, NetWare 3.x – 6.x using Bindery emulation), and
also for Native Novell NetWare NDS mode on NetWare 4.x, 5.x and 6.x file servers.

Note: because of deficiencies in the way Bindery Emulation is managed on NetWare 4.x and We do not recommend us-
later systems, we do not recommend that you use the Bindery mode personality module ing NetWare Bindery
(MN_NW3.DLL) on these servers – use the native NDS mode module instead. mode on NetWare 4.x or
later servers - use the
NDS module instead.
NetWare Bindery Mode Support
Mercury's NetWare Bindery mode support is implemented in a file called MN_NW3.DLL,
which will be installed by the Mercury installer if you choose NetWare Bindery mode oper-