22.3 Classes with mc Configuration
In configuring with the
mc technique, many classes are defined for your
convenience. You need to be aware of these, not only to take
advantage of them, but also to avoid reusing their names by mistake.
Table 22-2 lists all the macros that the
mc technique uses as of version 8.12. Most are
described in other sections, but a few are described here. See a
description of LOCAL_CONFIG (Section 4.3.3.1) for the
general method used for adding members and new class names using the
mc configuration technique.
Table 22-2. Class macros used with the mc configuration technique
|
$={Accept}
|
Section 7.5.1
|
With the access_db feature, the possible
acceptance strings from the access database (V8.10 and above)
|
|
$=B
|
FEATURE(bestmx_is_local)
|
With the bestmx_is_local feature, the domains to
look up in bestmx in place of $=w
|
|
$={Canonify}
|
FEATURE(nocanonify)
|
With CANONIFY_DOMAIN or CANONIFY_DOMAIN_FILE, do canonify these
domains (V8.10 and above)
|
|
$=E
|
Section 4.4.1
|
With EXPOSED_USER or EXPOSED_USER_FILE, the list of exposed users
|
|
$=G
|
Section 4.8.1
|
With GENERICS_DOMAIN or GENERICS_DOMAIN_FILE, list of domains to look
up in generics table
|
|
$=L
|
Section 4.5.5
|
With LOCAL_USER or LOCAL_USER_FILE, the list of local users
|
|
$={LDAPRoute}
|
See this section
|
With LDAPROUTE_DOMAIN or LDAPROUTE_DOMAIN_FILE, route only LDAP hosts
in this class
|
|
$={LDAPRouteEquiv}
|
See this section
|
With LDAPROUTE_EQUIVALENT or LDAPROUTE_EQUIVALENT_FILE, the host to
treat as equivalent to $M for LDAP routing lookups
(V8.12 and above)
|
|
$=M
|
Section 4.4.3
|
With MASQUERADE_DOMAIN or MASQUERADE_DOMAIN_FILE, the list of hosts
to masquerade
|
|
$=N
|
Section 4.4.5
|
With MASQUERADE_EXCEPTION or MASQUERADE_EXCEPTION_FILE, the hosts
excepted from masquerading
|
|
$=O
|
follows table
|
The list of non-username characters that can cause forwarding <,
>, %, and possibly !)
|
|
$=P
|
follows table
|
The list of pseudo top-level domains (e.g., .uucp
and .fax)
|
|
$={ResOk}
|
$={ResOk}
|
Mark a successful DNS lookup
|
|
$=R
|
Section 7.4.1.1
|
With RELAY_DOMAIN or RELAY_DOMAIN_FILE, the list of domains and hosts
for which to relay
|
|
$={SpamTag}
|
Section 7.5.6
|
With the delay_checks feature, holds the strings
SPAMFRIEND and SPAMHATER (V8.10 and above)
|
|
$={src}
|
follows table
|
List of rule sets to call for searching the
access database map
|
|
$={tls}
|
$={tls}
|
Possible values for TLS policy in the access
database map
|
|
$={TrustAuthMech}
|
Section 10.9.3
|
With TRUST_AUTH_MECH, the mechanisms used to allow relaying (V8.10
and above)
|
|
$=U
|
Section 4.6
|
With MAILER(uucp), the locally connected UUCP hosts
|
|
$=V
|
Section 4.6
|
With MAILER(uucp), the hosts connected to UUCP
relay $V
|
|
$={VirtHost}
|
FEATURE(virtuser_entire_domain)
|
With VIRTUSER_DOMAIN or VIRTUSER_DOMAIN_FILE, the list of additional
domains to look up in virtuser beyond
$=w (V8.10 and above)
|
|
$=W
|
Section 4.6
|
With MAILER(uucp), the hosts connected to UUCP
relay $W
|
|
$=X
|
Section 4.6
|
With MAILER(uucp), the hosts connected to UUCP
relay $X
|
|
$=Y
|
Section 4.6
|
With MAILER(uucp), the locally connected smart
UUCP hosts
|
|
$=Z
|
Section 4.6
|
With MAILER(uucp), the locally connected
domainized UUCP hosts
|
The class $=O is used by the
m4 technique to hold a list of characters that
cannot be used in local usernames. This list is used to detect
certain kinds of routing addresses that might otherwise be difficult
to detect. This list initially contains:
@ %
but can also contain an ! if UUCP support is
included.
The class $=P holds a list of pseudodomains that
will not be looked up using DNS. Unless you use a FEATURE, this class
will contain a dot only. Various FEATUREs will add appropriate
pseudodomains to it, such as .UUCP and .REDIRECT.
The class $={src} holds a list of rule set names
that can be called to look up items in the
access database. It is a clever trick that you
might wish to copy for use in your own rule sets. To see how this
trick is performed, look for $={src} in your
configuration file.
|
