Page 21 - Mercury Manual.book

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

if an address is local, by comparing the address with your local users' names, as they appear
in the Mercury "Manage local users" dialog. Note that at present, Mercury does not support
these options if either of its NetWare-specific identity modules is active – these options only
work with Mercury's own internal user database ("standalone mode").

In the examples below, we use myname.com to represent your Internet mail domain.

Automatically recognize “Firstname.Lastname” forms This is one of the most common In-
ternet addressing formats: if you have a user whose username is peter and whose full name
is Peter Smith, then his e-mail address is both peter@myname.com and
Peter.Smith@myname.com.

Automatically recognize “Initial.Lastname” forms This is like the previous setting, but it
combines your user's Initials and surname. So, given our hypothetical Peter Smith user,
with this setting enabled, his address is both peter@myname.com and P.Smith@my-
name.com.

Recognize variants using either periods or underscores This setting combines with either of
the previous two settings, by allowing either an underscore character or a period to appear in
place of spaces in your users' addresses. So, if all three controls in this group were checked,
our Peter Smith user could be mailed using any of the following addresses:

peter@myname.com
Peter.Smith@myname.com
P.Smith@myname.com
P_Smith@myname.com
Peter_Smith@myname.com

All of these settings are smart enough to handle multiple names or initials. So, if our Peter
Smith was actually Peter O.Smith, then his addresses would be P.O.Smith, Peter.O.Smith or
whatever.

It is up to you to ensure that your usernames are sufficiently distinct from each other if you
use these settings - Mercury will use the first valid match it can find. So, if you have both
Peter Smith and Patricia Smith on your system, and you use the Initial.Lastname format, you
should make sure you enter a middle initial for at least one of the two so their addresses be-
come distinct.

Allow the use of "+" forms in addresses to carry user-specified data If this control is
checked, then Mercury will support a specialized address variation where the user can append
data to his address using a "+" sign, and Mercury will still recognize it as local. An example
might serve to explain how this could be useful: user bob@mydomain.com has subscribed
to the Useful widgets mailing list and wants to use the filtering features of his mail pro-
gram to move all mail from that list into a folder automatically... To do this, he subscribes to
the list using the following address: bob+widgets@mydomain.com When the mailing list
software sends the message to Mercury, Mercury ignores the "+widgets" part and correctly
identifies the message as being for bob, delivering it accordingly. Bob's mail program can
then filter on the address and when it sees the "+widgets", recognize that the message should
be moved into the Useful widgets folder.

Daily maintenance settings Once a day, Mercury performs a certain number of routine main-
tenance tasks (such as handling automatic expirations in mailing lists). These settings allow
you to control when that maintenance should occur, and to force Mercury to perform a grace-
ful restart each day.