Managing mail with MMDF

Processing outgoing mail

Outgoing mail starts when the user invokes an MUA, such as mail(C) or scomail(XC) to compose a mail message, or when incoming mail is accepted for routing through the local host to another destination. How MMDF handles outgoing mail is illustrated in ``Outgoing mail''.

Outgoing mail

A mail message is sent using this procedure:

  1. When the user sends the messages for delivery, the MUA ensures that the message has the required mail headers.

  2. The MUA transfers the message to execmail, which sends it to submit(ADM). Alternatively, submit may accept the incoming mail from a channel.

  3. The submit program builds the fully qualified domain name for the recipient by mapping the information in the ``To:'' field with the information in the domain tables.

  4. submit then looks up the fully qualified domain name in the channel tables to determine the appropriate channel through which to send the message, and places the message in the appropriate channel queue.

  5. The deliver(ADM) program, which runs periodically (by default, deliver runs every 10 minutes), transfers the message from the channel queue to the appropriate channel program, which routes it to its destination.

For example, you send a message with this ``To:'' line:

The submit program looks in the appropriate MMDF configuration table for your_company and builds the fully qualified domain name; for example:
Now, submit determines the appropriate channel to use to send the message. In this example, all messages in the domain are sent to the outside world on the UUCP channel, so submit puts the message in the UUCP channel queue. Then deliver picks up the message and passes it to the channel program. The channel program transfers the message out of the MMDF mail system and into the UUCP subsystem where it is queued and sent via UUCP.
Next topic: How MMDF routes mail
Previous topic: Incoming mail

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003