summaryrefslogtreecommitdiff
path: root/src/mailman/rules/docs/suspicious.txt
diff options
context:
space:
mode:
Diffstat (limited to 'src/mailman/rules/docs/suspicious.txt')
-rw-r--r--src/mailman/rules/docs/suspicious.txt35
1 files changed, 35 insertions, 0 deletions
diff --git a/src/mailman/rules/docs/suspicious.txt b/src/mailman/rules/docs/suspicious.txt
new file mode 100644
index 000000000..190a34aca
--- /dev/null
+++ b/src/mailman/rules/docs/suspicious.txt
@@ -0,0 +1,35 @@
+Suspicious headers
+==================
+
+Suspicious headers are a way for Mailman to hold messages that match a
+particular regular expression. This mostly historical feature is fairly
+confusing to users, and the list attribute that controls this is misnamed.
+
+ >>> mlist = config.db.list_manager.create(u'_xtest@example.com')
+ >>> rule = config.rules['suspicious-header']
+ >>> print rule.name
+ suspicious-header
+
+Set the so-called suspicious header configuration variable.
+
+ >>> mlist.bounce_matching_headers = u'From: .*person@(blah.)?example.com'
+ >>> msg = message_from_string("""\
+ ... From: aperson@example.com
+ ... To: _xtest@example.com
+ ... Subject: An implicit message
+ ...
+ ... """)
+ >>> rule.check(mlist, msg, {})
+ True
+
+But if the header doesn't match the regular expression, the rule won't match.
+This one comes from a .org address.
+
+ >>> msg = message_from_string("""\
+ ... From: aperson@example.org
+ ... To: _xtest@example.com
+ ... Subject: An implicit message
+ ...
+ ... """)
+ >>> rule.check(mlist, msg, {})
+ False