FILES(5)

NAME
MMDF FILES -- overview

SYNOPSIS
Names, locations, and file modes for MMDF programs and files

DESCRIPTION

MMDF files separate into documentation, source code, mail queue, channel host name tables, programs, and logs.

Pathnames to constructed files (i.e., everything other than source code and documentation) are derived as a function of a default directory specification and the specific filename. The default directory can be overridden, for a specific file, by having the filename be a fully-specified path (starting with a slash). The default directories are defined in conf.c.

  Documentation

Documentation is located in the MMDF distribution tape directories doc and man. The manuals are subdivided by directories for each part of mail software, according to the V7 manual sections.

  Source Code

The layout and contents of the source directories are described in the document ``Installing and Operating MMDFII'' (normally in doc/administrators/* in the MMDF source directories.

  Queue

The queue, for storing mail in transit, is described in queue(5).

  Tables

The tables, for listing extensions to the list of local mailbox names and names of known hosts, are described in tables(5).

  Logs

MMDF system logs are described in logs(5).

  Programs

It is assumed that a login and uid have been assigned to MMDF. The default assumption, throughout the distribution tape, is that the login name is `mmdf'. The default location for MMDF programs is specified in cmddfldir[], for MMDF ``commands'' and in chndfldir[], for MMDF channel programs which are invoked by deliver. Both variables are specified in conf.c.

    submit
        Enqueues mail. Its location is specified by pathsubmit[]. Its protection modes should be 04711, and it should be owned by MMDF, so that it can chdir(2) past the quedfldir[] locking directory for the queue.

    deliver
        Manages message transmission. Its location is specified by pathmailer[]. Its protection modes should be 04711, and it should be owned by root.

    slave
        Runs as the server process, when other sites call over a phone channel. Protection should be 0711, since it needs no special privileges.

    channel programs
        These perform actual data transfers, at the invocation of deliver. They are named to reflect their actual task Their locations are specified by the channel definitions in conf_chan.c and default to the chndfdir[] directory. It is very important that the directory containing the channel programs be accessible only by MMDF processes, or else anyone could invoke one and send unverified mail; hence make the "chans" directory have protection 0700 and be owned by MMDF. The ownership and protection modes of the channel programs depend upon the resources they consume. For example, the program which delivers mail to the local machine, ch_local, must be 04711 and owned by root, so that it can manipulate recipient's protected mailboxes. At some sites, telephone dial-out may be a protected resource, so that ch_phone should be 04711 and owned by the same user as owns the dial-out.

    cleanque
        Garbage-collects the queue. It should be run regularly, such as overnight by cron. Its protection modes should be 04711, and it should be owned by root.

    setlogs
        Resets the logs and may save message and channel statistics. It is a shell file and should be run as MMDF. It should be run regularly, such as daily, by cron, unless system performance needs close monitoring. In this case, the logs should be retained longer.

SEE ALSO
logs(5), queue(5), tables(5), cleanque(8), deliver(8), submit(8)
Installing and Operating MMDF II