8.55 on page 643 $=t
EXPOSED_USER_FILE ?§17.4.1 on page 599 $=E
GENERICS_DOMAIN_FILE ?§17.8.18 on page 622 $=G
LDAPROUTE_DOMAIN_FILE ?§23.7.11.23 on page 924 $={LDAPRoute}
LDAPROUTE_EQUIVALENT_FILE ?§23.7.11.23 on page 924 $={LDAPRouteEquiv}
LOCAL_DOMAIN ?§22.6.16 on page 876 $=w
LOCAL_USER_FILE ?§17.5.5 on page 605 $=L
MASQUERADE_DOMAIN_FILE ?§17.4.3 on page 600 $=M
MASQUERADE_EXCEPTION_FILE ?§17.4.6 on page 602 $=N
RELAY_DOMAIN_FILE ?§7.4.1.2 on page 269 $=R
VIRTUSER_DOMAIN_FILE ?§17.8.58 on page 645 $={VirtHost}
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
862 | Chapter 22: The C and F (Class Macro) Configuration Commands
our.domain, their.domain, and another.domain. You could perform that lookup with
an mc configuration line such as this:
RELAY_DOMAIN_FILE(`DomainList:@hash:/etc/mail/access??)
Here, DomainList: (colon included) is the key looked up in the hash-type databasemap
located in the database file /etc/mail/access. The presence of the literal @ tells
sendmail this is a database-map lookup, and not the name of a file to read.
To use an example from the previous section, consider adding a user-id name to the
EXPOSED_USER class (?§17.4.1 on page 599) like this:
EXPOSED_USER_FILE(`0@text:-k2 -v0 -z: /etc/passwd??)
This lookup would result in the addition of the name boss (from the previous section)
to the EXPOSED_USER class.
Pages:
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521