Note that the $: part contains the
reason the message is being quarantined.
Note that rule set quarantining affects all recipients of that envelope.
To illustrate rule set quarantining, consider the following mc configuration lines that
cause any message which contains a special X-review: header to be held for review:
LOCAL_CONFIG
HX-review: $>Xreview
LOCAL_RULESETS
SXreview
R YES $#error $@ quarantine $: X-review held for review
The first part of our example, the LOCAL_CONFIG part, defines a header. This header
definition tells sendmail to pass all X-Review: header values through (the $>) th e
Xreview rule set.
The second part (LOCAL_RULESETS) defines the Xreview rule set (the S line) which contains
a single rule that looks for a value that is the literal word YES. If that header??™s
value is YES, the message is quarantined with the reason shown. If that header is
missing, or if it has any other value, this quarantine step is skipped.
Note that rule sets can detect whether a message has already been quarantined by
checking the ${quarantine} sendmail macro (?§21.9.80 on page 841). If that macro
has a value, the message was already quarantined.
11.10.2.7 Log quarantined messages
Whenever a message is quarantined, the fact that it was quarantined and the reason for
doing so are logged using syslog(3). One log line is produced to record the quarantine
event.
Pages:
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795