From c170b01eae9958bc6d0892e8227d2726f60362b7 Mon Sep 17 00:00:00 2001 From: Mark Sapiro Date: Sun, 4 Jan 2015 19:03:40 -0800 Subject: Add some explanitory comments for why we defer some Munge From changes to WrapMessage. Correct a misplaced item in NEWS. --- Mailman/Handlers/CookHeaders.py | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'Mailman/Handlers/CookHeaders.py') diff --git a/Mailman/Handlers/CookHeaders.py b/Mailman/Handlers/CookHeaders.py index 0139f3c3..30e05655 100755 --- a/Mailman/Handlers/CookHeaders.py +++ b/Mailman/Handlers/CookHeaders.py @@ -72,6 +72,11 @@ def change_header(name, value, mlist, msg, msgdata, delete=True, repl=True): (msgdata.get('from_is_list') == 0 and mlist.from_is_list == 2)) and not msgdata.get('_fasttrack') ) or name.lower() in ('from', 'reply-to', 'cc'): + # The or name.lower() in ... above is because when we are munging + # the From:, we want to defer the resultant changes to From:, + # Reply-To:, and/or Cc: until after the message passes through + # ToDigest, ToArchive and ToUsenet. Thus, we put them in + # msgdata[add_header] here and apply them in WrapMessage. msgdata.setdefault('add_header', {})[name] = value elif repl or not msg.has_key(name): if delete: -- cgit v1.2.3