All rights reserved.
21.9 Alphabetized sendmail Macros | 839
LOCAL_CONFIG, we first add the ${X-Notice} macro to the class $={persistentMacros}
(?§22.6.9 on page 873), which ensures that ${X-Notice} will retain its value despite the
message being queued. We then use the H configuration command to define the X-Notice:
header and to specify that the X-Notice: header??™s value must be processed by the
CheckNotice rule set. Finally, we declare a macro-type database map (?§23.7.12 on page 925)
which we will reference with the name store.
In the LOCAL_RULESETS section we set up two rule sets. The first rule set is the
CheckNotice rule set we referenced withth e H configuration command. That rule set
contains a single rule which stores a literal YES into the ${X-Notice} macro.
The second rule set is the check_compat rule set (?§7.1.5 on page 259) which is called just
prior to delivery. It contains four rules. The first rule fetches the current value (the $&) of
the ${X-Notice} macro and places that value into the workspace. The second rule clears the
${X-Notice} macro to ready it for any future message. The third rule looks for a literal YES
in the workspace, and if found, compares the value in the ${ntries} macro to a one. If
${ntries} is not less than one, a literal FALSE is placed into the workspace. The last rule
looks for a literal FALSE in the workspace, and if found, rejects (bounces) the message with
an appropriate notice.
Pages:
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480