EDU. One boilerplate file, named generic.m4, can be used as a starting
point for your own domain-wide file. For example, if all hosts at your site masquerade
behind one email name, you might want to put MASQUERADE_AS (?§17.4.2 on
page 600) in your domain file. Domain files also form a natural location for the definition
of site-specific relays (?§17.5 on page 602).
If the domain that is specified does not exist or is misspelled, an error similar to the
following will be printed:
m4: Can't open ../domain/generik.m4: No such file or directory
The use of DOMAIN( ) is not mandatory but is recommended. Note that problems
can arise because the items inside your domain file will determine where the
DOMAIN( ) declaration must go in the mc file. If, for example, the domain file contains
MAILER( ) definitions, DOMAIN( ) should appear near the end of the mc file
with the MAILER( ) definitions. If the domain file contains rules and rule sets, the
DOMAIN( ) must be last in the mc file, but if the domain file contains OSTYPE( ),
DOMAIN( ) must be first in the mc file. So, consider well what you place in your
domain file. Avoid defining anything in your domain file that restricts where the
DOMAIN( ) definition must go in your mc file.
In the event that your domain file contains many position-dependent commands,
such as rule sets and an OSTYPE( ) command, you might need to split that file into
pieces.
Pages:
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043