summaryrefslogtreecommitdiff
path: root/src/mailman/rules/docs
diff options
context:
space:
mode:
authorBarry Warsaw2015-10-20 22:48:59 -0400
committerBarry Warsaw2015-10-20 22:48:59 -0400
commit5f917c8aec735608cb85195e691fb68fbb835af7 (patch)
tree2a963a102f7610a118cd211711c4df90aada94cd /src/mailman/rules/docs
parentadb9e3164ee1e19802a4373e76b42b1435d1e687 (diff)
downloadmailman-5f917c8aec735608cb85195e691fb68fbb835af7.tar.gz
mailman-5f917c8aec735608cb85195e691fb68fbb835af7.tar.zst
mailman-5f917c8aec735608cb85195e691fb68fbb835af7.zip
Diffstat (limited to 'src/mailman/rules/docs')
-rw-r--r--src/mailman/rules/docs/header-matching.rst16
1 files changed, 8 insertions, 8 deletions
diff --git a/src/mailman/rules/docs/header-matching.rst b/src/mailman/rules/docs/header-matching.rst
index 05d01efb2..2eb8d9bdf 100644
--- a/src/mailman/rules/docs/header-matching.rst
+++ b/src/mailman/rules/docs/header-matching.rst
@@ -120,11 +120,11 @@ List-specific header matching
Each mailing list can also be configured with a set of header matching regular
expression rules. These can be used to impose list-specific header filtering
-with the same semantics as the global `[antispam]` section, or to have a
+with the same semantics as the global ``[antispam]`` section, or to have a
different action.
To follow the global antispam action, the header match rule must not specify a
-`chain` to jump to. If the default antispam action is changed in the
+``chain`` to jump to. If the default antispam action is changed in the
configuration file and Mailman is restarted, those rules will get the new jump
action.
@@ -147,8 +147,8 @@ A message with a spam score of two pluses does not match.
x-spam-score: [+]{3,}
But a message with a spam score of three pluses does match. Because a message
-with the previous Message-Id is already in the moderation queue, we need to
-give this message a new Message-Id.
+with the previous ``Message-Id`` is already in the moderation queue, we need
+to give this message a new ``Message-Id``.
>>> msgdata = {}
>>> del msg['x-spam-score']
@@ -174,8 +174,8 @@ As does a message with a spam score of four pluses.
x-spam-score: [+]{3,}
No rules missed
-Now, the list administrator wants to match on three plus signs, but wants those
-emails to be discarded instead of held.
+Now, the list administrator wants to match on three plus signs, but wants
+those emails to be discarded instead of held.
>>> header_matches.remove('x-spam-score', '[+]{3,}')
>>> header_matches.add('x-spam-score', '[+]{3,}', 'discard')
@@ -187,10 +187,10 @@ will be discarded.
>>> del msg['x-spam-score']
>>> msg['X-Spam-Score'] = '+++'
>>> del msg['message-id']
- >>> msg['Message-Id'] = '<dee>'
+ >>> msg['Message-Id'] = '<dog>'
>>> with event_subscribers(handler):
... process(mlist, msg, msgdata, 'header-match')
- DiscardEvent discard <dee>
+ DiscardEvent discard <dog>
>>> hits_and_misses(msgdata)
Rule hits:
x-spam-score: [+]{3,}