- Local Domains
These are the Internet domain names recognized by Internet Exchange as local. Local refers to the recipient's domain
name (e.g. ima.com) that is listed in the local domain listing under the Preprocessor settings. The Preprocessor
performs directory lookup on any local recipient to find out the corresponding connector. If the domain name does not
exist in the domain listing, the Preprocessor will route the message to the default non-local channel, which is the
SMTPC, to complete the routing. The MTA also handles the messages for the local domain. The MTA will either do the
final delivery to the recipient or bounce the message if the message is undeliverable.
A domain name may begin with an asterisk (*) to denote all sub-domains, not including the
main domain. For example, the entry "*.ima.com" will match entries that contains the local domain name as "ima.com"
(e.g. machinename.ima.com). The MTA will accept the mail for all the domains listed even if the recipient may not have
an entry in the Directory database. To configure the system to accept all mail for the primary domain plus all
sub-domains, two entries are required (i.e., ima.com and *.ima.com).
- Default Local Delivery Channel
This defines the channel processor that will handle non-mapable local recipients.
For example: "john@ima.com" is local because "ima.com" is defined in the
local domains list. If "john@ima.com" does not have an entry in the Directory Server, the Preprocessor will route the message
to the default local delivery channel, which can be local, cc:Mail or Notes. If the default channel finds out that recipient
does not exist in any of these channels, the message will be bounced. If the MTA receives a message for a local recipient who
does not have a directory entry, the MTA will deliver the message to the default local delivery channel. If the recipient has
directory entry but does not have any connectors defined, the MTA will deliver the message to the default local delivery
channel.
At present, only Notes, cc:Mail and SMTPC connectors can process messages for recipients who do not have entries in the
Directory Server. For the Notes and cc:Mail connectors, it is necessary to have the "unlimited user" license ti enable
the default mapping functionality.
- Internet Delivery Channel
The channel (e.g. SMTPC) used by the Preprocessor to deliver a message to the Internet. Although the entry is
configurable, Internet Exchange is initially setup to make use of the SMTPC channel as the default delivery channel. It
is recommended not to change the default setting.
- MQ Server
The NetBIOS (for Windows) or SMB (for Linux) name of the machine where the MQ (Message Queue) is located. The MQ Server can
reside on any NetBIOS compatible host, but the entry should correspond to the NetBIOS name of this server. The NetBIOS name
must be the same as the Internet host name. It is possible to configure Microsoft Windows to have two different names for
NetBIOS and the configure Microsoft Windows to have two different names for NetBIOS and the Internet name, but this will not
work for the system designated as the MQ Server.
- MQ Server Access Mask
A list of IP addresses describing the systems which are permitted to access the Preprocessor queues. Each entry can either
consist of a single dotted IP address (e.g. 192.168.1.10), a range of IP addresses (e.g. 192.168.1.10-192.168.1.12), or an
IP address with a mask (e.g. 192.168.1.0/28). The Preprocessor will log an error in the system log file, without listing the
IP address, if an application tries to access the channels.
- MQ Local directory
The directory path (e.g. C:\Program Files\IMA\Internet Exchange\msgqueue for Windows and /var/spool/iems/mqueue
for Linux) where the MQ databases and the sub-directories for the message files are installed. This directory is used by all
connectors running on the same system.
- MQ Remote Access directory (SMB mounted)
The directory path (e.g. /var/spool/iems/remotequeue for Linux and \\Station1\msgqueue for Windows)
where the message queue can be accessed remotely. This directory is used by all connectors not running on the
same system as the MQ Server.
For example, if the MQ Server was not running on a machine named Station1, a connector on a machine named Station2 could access
the queued messages using this directory prefix.
The system will not operate correctly across a network if the entries MQ Local Directory and MQ Remote Access Directory are
not pointing to the same directory. If all the connectors, Preprocessor and the MQ Server are running on the same system,
this directory will not be used.
-
Notification messages sent to
This refers to the email address of the person who is to receive notification messages.
- Notify postmaster on corrupt messages
Provides the system administrator an option whether he would like to receive notification messages (mark the check box) on
corrupted messages or not (leave the check box blank)