1 files changed, 9 insertions, 9 deletions

diff --git a/src/mailman/rules/docs/loop.txt b/src/mailman/rules/docs/loop.txt
index bb6da364b..d6be10f8a 100644
--- a/src/mailman/rules/docs/loop.txt
+++ b/src/mailman/rules/docs/loop.txt
@@ -3,7 +3,7 @@ Posting loops
 =============
 
 To avoid a posting loop, Mailman has a rule to check for the existence of an
-X-BeenThere header with the value of the list's posting address.
+RFC 2369 List-Post header with the value of the list's posting address.
 
     >>> mlist = create_list('_xtest@example.com')
     >>> rule = config.rules['loop']
@@ -22,26 +22,26 @@ The header could be missing, in which case the rule does not match.
 
 The header could be present, but not match the list's posting address.
 
-    >>> msg['X-BeenThere'] = 'not-this-list@example.com'
+    >>> msg['List-Post'] = 'not-this-list@example.com'
     >>> rule.check(mlist, msg, {})
     False
 
 If the header is present and does match the posting address, the rule
 matches.
 
-    >>> del msg['x-beenthere']
-    >>> msg['X-BeenThere'] = mlist.posting_address
+    >>> del msg['list-post']
+    >>> msg['List-Post'] = mlist.posting_address
     >>> rule.check(mlist, msg, {})
     True
 
-Even if there are multiple X-BeenThere headers, as long as one with the
-posting address exists, the rule matches.
+Even if there are multiple List-Post headers, as long as one with the posting
+address exists, the rule matches.
 
     >>> msg = message_from_string("""\
     ... From: aperson@example.com
-    ... X-BeenThere: not-this-list@example.com
-    ... X-BeenThere: _xtest@example.com
-    ... X-BeenThere: foo@example.com
+    ... List-Post: not-this-list@example.com
+    ... List-Post: _xtest@example.com
+    ... List-Post: foo@example.com
     ...
     ... An important message.
     ... """)