This
means you can have more secure permissions for the authinfo database than for the access
database. FEATURE(authinfo) is declared like this:
FEATURE(`authinfo??)
This creates a default configuration declaration that looks like this:
Kauthinfo hash /etc/mail/authinfo
Here the hash is derived from the setting of the DATABASE_MAP_TYPE mc configuration
macro (?§23.5.1 on page 897) and the /etc/mail is derived from the setting of the MAIL_
SETTINGS_DIR mc macro (?§2.5.6 on page 68). If you wish to change the defaults without
having to change these two mc configuration macros, you can simply define that new
default by adding a second argument to the feature declaration:
FEATURE(`authinfo??, `hash /etc/private/authinfo??)
If you provide a second argument and the second argument is a literal LDAP:
FEATURE(`authinfo??, `LDAP??)
the default becomes the following (we have wrapped the lines to fit the page):
Kauthinfo ldap -1 -v sendmailMTAMapValue -k (&(objectClass=sendmailMTAMapObject)
(|(sendmailMTACluster=${sendmailMTACluster})(sendmailMTAHost=$j))
(sendmailMTAMapName=authinfo)(sendmailMTAKey=%0))
See ?§23.7.11 on page 912 for a description of the ldap database type and its -1, -v, and -k
switches. See ?§5.1.5.1 on page 195 for a description of the authinfo database??™s contents
and how to create that database.
17.8.7 FEATURE(badmx)
Reject a domain with bad MX record V8.
Pages:
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085