You can split it something like this:
DOMAIN(`our.domain.sun??)
DOMAIN(`our.domain.rules??)
Here, the first line causes the file our.domain.sun.m4 to be read. That file contains
the OSTYPE( ) declaration for all your Sun workstations. This DOMAIN( ) entry
would appear at the top of your mc file.
The second line causes the file our.domain.rules.m4 to be read. That file might contain
antispam rule sets. This second DOMAIN( ) entry would appear near the end of
your mc file, perhaps under LOCAL_RULESETS.
17.2.2.4 FEATURE( ) m4 macro
V8 sendmail offers a number of features that you might find very useful. To use a feature,
include an m4 command such as one of the following in your mc file:
FEATURE(keyword)
FEATURE(keyword, argument)
FEATURE(keyword, argument, argument, ... etc. )
These declarations cause a file of the name feature/keyword.m4 to be read at that
place in your mc file. The available keyword files are summarized in Table 17-7 on
page 612, and each is explained in the section at the end of this chapter. Note that
some keywords require additional arguments.
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
17.2 Configure with m4 | 593
17.2.3 The Order of mc Lines
As you have seen, some mc lines must precede others. This is necessary partly
because m4(1) is a one-pass program, and partly because the order of items in the
final sendmail.
Pages:
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044