OmniMessaging Functional Description 8.3

OmniMessaging Functional Description
07/22/04 Opsol Integrators Inc. Confidential and Proprietary Page 25 of 68
When a receiving MTA process receives a message that needs to be sent to a
remote domain it passes this message to a sending MTA process to be relayed
on.
Since the neither the distributor nor the receiving MTA use Pathsend for
dynamic load balancing, you must add additional receiving and sending MTA
processes (using the OmniMessaging Application Manager) to increase the
number of MTA server-class processes for increasing loads.
10.1.2 Message Store
A Local Delivery Server (LDS) enters the messages into the MS and the MBM
and MAS processes maintain the messages.
You configure the LDS and MBM and MAS as NonStop™ TS/MP processes
running under the control of a PATHMON process.
10.1.3 Local Delivery Server (LDS)
The LDS is configured as a static NonStop™ TS/MP process. It may have
multiple server classes, and each server class may have multiple processes. If
needed, the operator may configure multiple LDS NonStop™ TS/MP server
classes and start and stop the classes based on local-message load.
The process’s tasks are the following:
• get local messages from the OmniMessaging MTA
• store messages in the MS
• explode redirection lists
• enforce quotas
• generate non delivery reports and vacation messages
The LDS process does not analyse or decode message content.
If all recipients are invalid, the message is rejected, and a non-delivery report is
sent to the originator via the MTA. If the message contains both valid and
invalid recipients, the LDS generates non-delivery reports for the invalid
recipients (one report for each message). OmniMessaging allows the
configuration of whether the whole message, the headers or no message
content is returned in a non-delivery report.
10.1.4 Mailbox Maintenance Server (MBM)
The MBM performs deferred cleanup activities for ensuring that all MS
operations complete successfully, and that the database remains in a logically
consistent state.
Each MBM process is a static NonStop™ TS/MP process that runs as a
background task. It deletes messages, mailbox folders, namespaces,
submission addresses, domains, user entries and accounts from the MS as
requested by the Provisioning, MAS, POP3, IMAP4, LDS and MTA Servers.
MBM functions are determined by queue entries.