Keywords in the tailor file are not case-sensitive; however, case is important for filenames and similar values. Use quotation marks to delimit strings to prevent them from being parsed into separate words accidentally.
The following alphabetical list describes most of the information you can set in the mmdftailor file. For information about additional channel-specific settings, refer to the documentation about the particular channel.
Here is an example:
ALIAS table=sysaliases, trusted, nobypass
Logging files and levels can also be specified in the channel descriptions. The logging file, if specified there, overrides the MCHANLOG definition. The logging level for the channel is set to the maximum of the MCHANLOG level and the channel description's level. The MCHANLOG level can therefore be used to increase logging on all channels at once.
Here is an example:
MCHANLOG /tmp/mmdfchan.log, level=FST, size=40, stat=SOMEAn argument without an equal sign is taken as the name of the log. Logging levels are:
The size parameter is the number of 25 1KB block units you will allow your log file to grow to. When a log file reaches that size, that logging either stops or cycles around overwriting old data (see cycle).
The stat parameter sets up various status flags for logging:
Tailoring of the log files is generally performed at the end of the
tailor file to prevent logging the tailoring action itself,
thereby needlessly filling the log files when higher tracing
levels are enabled.
If you have bugs in the tailoring, you can move
the log-file tailoring closer to the top of the tailor file.
Here is a simple example:
MCHN name=local, que=local, tbl=local, show="Local Delivery", pgm=local, poll=0, mod=imm, ap=822, level=BSTIf the first argument does not have an equal sign, the values of the name, que, tbl, pgm, and show parameters take on this value.
Here is an example:
MDMN name="Root", dmn="", show="Root Domain", table=rootdomainIf the first argument does not have an equal sign, the values of the name, dmn, and show parameters take on this value. If no table parameter is specified, it defaults to the value of the name parameter.
| Keyword | Lock file |
|---|---|
| advisory | System V fcntl() kernel file locking |
| v7 | Version 7 and System V Release 3, and earlier file locking |
| xenix | XENIX file locking |
| all | all known locking protocols |
MLCKTYPE advisory, xenix
MMBXPREF "\001\001\001\001\n"See also MMBXSUFF.
The values of MMBXPREF and MMBXSUFF should consist of non-printable characters only and must end in a newline.
MMBXSUFF "\001\001\001\001\n"See also MMBXPREF.
The following are possible values for flags:
Note that MMDF treats flags=file and flags=dbm the same. In the case of an ns-type table, the flags field specifies the type of nameserver lookup (either domain, channel, or alias).
A typical example might be:
MTBL name=aliases, file=aliases, show="User & list aliases"
If the first argument does not have an equal sign,
the values of the other parameters take on this value.
The following example sets the
name, file, and show
parameters to the string ``aliases'',
then resets the show
parameter to the string ``Alias table''.
MTBL aliases, show="Alias table"
Do not include any characters in TAGCHARS that are needed for the local part of email addresses. For example, if aliases of the form some-address@your.domain are in use, - should not be included in TAGCHARS, because it will cause mail to such an alias to be treated as though it were addressed to some@your.domain.
Mail and Messaging Guide