1.3 on page 257) rule set performs the lookup, and the relationship
found (friend or hater) determines whether the check_mail (?§7.1.2 on page 255)
and check_relay (?§7.1.1 on page 252) rule sets should be called to perform further
checks.
If the extra argument is friend and if the database lookup returns FRIEND, those
further rule set checks will be skipped and the message will be accepted. But if the
database lookup fails to find the address, or returns something other than FRIEND,
further screening by the check_mail and check_relay rule sets is performed.
If the extra argument is hater and the database lookup returns HATER, further
screening by the check_mail and check_relay rule sets is performed. But if the database
lookup fails to find the address, or returns something other than HATER, those
additional rule sets will be skipped.
As a first step, decide which of the two forms you prefer (remember, you can do only
one or the other), and then add the new definition to your mc file, generate a new
configuration file, and install it. Once the new configuration is ready, you can use
one of two new righthand-side keywords in your access database:
SPAMFRIEND (V8.10 through V8.11) or FRIEND (V8.12)
This address is allowed to receive messages that would otherwise be rejected by
the check_mail and check_relay rule sets. You can use this keyword only if you
defined friend when you declared the FEATURE(delay_checks).
Pages:
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531