cf
file, and include in the mc file, for that creation, a definition for that new group with
the RunAsUser option (?§4.8.2.2 on page 176), like this:
FEATURE(`msp')
define(`confRUN_AS_USER', `:nullgroup')
Note that the same option sets both the user and the group. A combined declaration
might look like this:
FEATURE(`msp')
define(`confRUN_AS_USER??, `nullmail:nullgroup??)
If you don??™t change the group, sendmail will use the group smmsp.
Whether you keep the group name chosen by the sendmail distribution, or choose a
name of your own, you will need to add that name to your system??™s group(5) services.
Here we show how to do this with the traditional Unix group(5) file. Consider
the lessons taught here, and apply them to your group(5) services in the manner most
suitable to your Unix system:
nullgroup:*:32764:
In this example of a line from a traditional Unix group(5) file, we have elected to create
the group named nullgroup. The line is divided into four fields by colons. The
first field is the name of the new group. The second field is the group??™s password.
Because this group is not used by actual people, we disable the password with an
asterisk. On some systems you will put an x in this field, or the word NOPASSWORD.
See your system documentation to learn what is best to use in this field to
disable a password for this new group.
Pages:
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139