Macros with mc Configuration
The various FEATURE( )s of the mc configuration technique primarily use uppercase, single-character macro names. The complete list of them is shown in Table 21-5. Some of these are defined by using the appropriate mc configuration command (as you’ll see later). Others are predefined for you by the mc configuration technique. See the appropriate section reference for a full description of how to use each macro.
|
Macro |
§ |
Description |
|
|
The BITNET relay | |
|
|
The DECnet relay | |
|
|
The local domain (unused) | |
|
|
The X.400 relay (reserved for future use) | |
|
|
The fax relay | |
|
|
The mail hub | |
|
|
The unknown local user relay | |
|
|
Whom we are masquerading as | |
|
|
The relay for unqualified names (deprecated) | |
|
|
The smart host | |
|
|
The UUCP name to override $k | |
|
|
The UUCP relay for class | |
|
|
The UUCP relay for class | |
|
|
The UUCP relay for class | |
|
|
The UUCP relay for unclassified hosts | |
|
|
The version of this mc configuration |
A few macros can be defined by using an mc configuration command. For example, here is how you define the BITNET relay with the BITNET_RELAY keyword:
define(`BITNET_RELAY', `host.domain')See Table 21-6 for a list of the mc macros that can be defined. The leftmost column in that table shows the keyword to use.
|
mc name |
Macro |
§ |
Description ... |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access