* This is also called xtext translation and is documented in RFC1891.
Table 21-4. Macros subject to xtext encoding
Macro ?§ Description
${auth_authen} ?§21.9.5 on page 804 RFC2554 AUTH credentials (xtext encoded with V8.13 and later)
${auth_author} ?§21.9.6 on page 805 RFC2554 AUTH= parameter (xtext encoded with V8.13 and later)
${cert_issuer} ?§21.9.13 on page 809 Distinguished name of certificate signer
${cert_subject} ?§21.9.15 on page 809 Distinguished name of certificate (owner)
${cn_issuer} ?§21.9.26 on page 815 Common name of certificate signer
${cn_subject} ?§21.9.27 on page 816 Common name of certificate
Table 21-5. Macros reserved with the mc configuration technique
Macro ?§ Description
$B ?§21.9.11 on page 808 The BITNET relay
$C ?§21.9.29 on page 817 The DECnet relay
$D ?§21.9.41 on page 823 The local domain (unused)
$E ?§21.9.44 on page 824 The X.400 relay (reserved for future use)
$F ?§21.9.46 on page 824 The fax relay
$H ?§21.9.51 on page 826 The mail hub
$L ?§21.9.63 on page 832 The unknown local user relay
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
21.7 Macros with mc Configuration | 797
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.
Pages:
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399