mta(8) CLIX mta(8)
NAME
mta - Runs the Intergraph X.400 Message Handling Service (MHS) dispatcher
SYNOPSIS
mta
DESCRIPTION
The mta command monitors queues to determine when to submit or receive
X.400 mail messages. The command is known as the message transfer agent
(MTA).
The mta command monitors two queues: the submission queue (SQ) and the
input queue (IQ). The SQ contains messages submitted locally. The IQ
contains messages received from adjacent MTAs through the reliable
transfer server (RTS). Each of these queues is implemented as a
directory, with each message in a separate file in the directory.
Each message is parsed and the list of recipients is examined. For each
recipient, the dispatcher determines if the message can be delivered
locally or if it must be routed to an adjacent MTA.
The MTA uses a fixed routing table, which is set up by the MHS system
administrator using the md command, to make its routing decisions. The
mta command has a list of all local recipients in the registration table.
For each local recipient, a copy of the message is inserted in the
recipient's delivery queue (DQ).
FILES
/usr/lib/mhs/config.dat MTA configuration file.
/usr/lib/mhs/defertab MTA deferred authorization table file.
/usr/lib/mhs/neighbor.dat MTA neighbor table file.
DIAGNOSTICS
The following diagnostics messages are provided:
error getting semaphore; errno xxx
fopen failed
fread failed returned xxx
create lockfile filename errno xxx
remove semaphore failed; errno xxx
2/94 - Intergraph Corporation 1
mta(8) CLIX mta(8)
EXIT VALUES
Exit values are not valid.
CAUTION
The user should never invoke the mta command. This command is
automatically started by either the sendxmail or rts process. There
should never be more than one mta process running on a system at the same
time.
RELATED INFORMATION
Commands: mta(8), md(8), sendxmail(8)
Intergraph ISO/OSI Administrator's Guide
2 Intergraph Corporation - 2/94