aboutsummaryrefslogtreecommitdiffstats
path: root/Mailman/Handlers/CookHeaders.py (unfollow)
Commit message (Collapse)AuthorFilesLines
2015-09-16Subject prefixing could fail to collapse multiple 'Re:' in an incommingMark Sapiro1-1/+7
message if they all came after the list's subject_prefix.
2015-06-07Fixed an issue with shunted messages on a list where the charset forMark Sapiro1-1/+6
the list's preferred_language had been changed from iso-8859-1 to utf-8 without recoding the list's description.
2015-01-11Due to a prior change, From: header munging would unnecessarily add theMark Sapiro1-4/+13
original From: to Cc: when was already in an original Reply-To:. Fixed.
2015-01-04Add some explanitory comments for why we defer some Munge From changesMark Sapiro1-0/+5
to WrapMessage. Correct a misplaced item in NEWS.
2015-01-03When applying DMARC mitigations, CookHeaders now adds the original From:Mark Sapiro1-10/+44
to Cc: rather than Reply-To: in some cases to make MUA 'reply' and 'reply all' more consistent with the non-DMARC cases.
2014-05-11Enhance the fix for (LP: #1318025)Mark Sapiro1-0/+2
2014-05-09Handle missing From: header addresses for DMARC mitigation actions.Mark Sapiro1-3/+10
(LP: #1318025)
2014-05-04Sender: headers are no longer removed in from_is_list Munge FromMark Sapiro1-3/+0
actions. (LP: #1315970)
2014-05-02Updated CookHeaders to always add the poster's From: address to Reply-To:Mark Sapiro1-8/+2
when applying from_is_list transformations.
2014-04-25Changed from_is_list actions to insert the list address in Cc: if theMark Sapiro1-12/+20
list is fully personalized. Otherwise, the list address is only in From: and Reply-To: overrides it. (LP: #1312970)
2014-04-23Fixed the Munge From action to not actually Munge the From: or Reply-To:Mark Sapiro1-11/+15
until after the message has been sent to the archive, digest and usenet gateway.
2014-04-08Enhanced fix for LP: #1304511 to use member's real name if available.Mark Sapiro1-1/+4
2014-04-08For from_is_list feature, use email address from original From: ifMark Sapiro1-0/+2
original From: has no display name and strip domain part from resultant names that look like email addresses. (LP: #1304511)
2014-04-06For from_is_list, if no real name in From, use email address.Mark Sapiro1-0/+2
2014-03-14Cleaned up a couple of comments missed in the author_is_list toMark Sapiro1-1/+1
from_is_list change.
2014-02-16- The from_is_list header munging feature introduced in Mailman 2.1.16 isMark Sapiro1-3/+6
no longer erroneously applied to Mailman generated notices.
2013-09-28Renamed author_is_list to from_is_list.Mark Sapiro1-6/+6
2013-09-27Made author_is_list a 3-way with an option to wrap the message.Mark Sapiro1-18/+47
2013-07-19Second cut at the author_is_list feature.Mark Sapiro1-1/+2
2013-07-18First cut at the author_is_list feature.Mark Sapiro1-3/+4
2012-06-20Fixed a typo in the UPGRADING doc - bin/upgrade -> bin/update.Mark Sapiro1-0/+0
2012-03-24Stopped removing the trailing slash from the List-Archive: header URL.Mark Sapiro1-2/+0
(LP: #964190)
2011-11-22Changed subject prefixing to allow for possible whitespace between anMark Sapiro1-2/+2
'Re' and the following colon when determining how to add the prefix. Bug #893290.
2008-06-20Fixed CookHeaders.py which in some cases with new style prefixingMark Sapiro1-1/+4
would insert an extra space between the prefix and the subject.
2008-03-06CookHeaders.py - Changed the first URL in the RFC 2369 List-Unsubscribe:Mark Sapiro1-2/+3
header to go to the options login page instead of the listinfo page. options.py - Changed to only issue the "No address given" error if coming from the page itself so we don't get the error when linking from another page or the List-Unsubscribe: header. - Changed to remember the user's language selection when redisplaying the page after an error.
2006-02-17ch_oneline(): Input string variable is overwritten. Also use listtkikuchi1-8/+4
comprehension where appropriate.
2006-01-01process(): Fix a comment.bwarsaw1-4/+3
2005-12-30A cleansing pass, almost entirely cosmetic. Such things as whitespacebwarsaw1-11/+13
normalization, removal of tabs, copyright year updates to changed files, docstring and comment fixes, and usage of True/False. I also made a pass through the NEWS file. One import was reordered, and after this commit I will move the mmdsr.readme file to README.mmdsr. From my perspective, after that we're ready to go. I will port these changes forward to the trunk.
2005-12-26Python interpreter has evolved to be strict on ascii charset range.tkikuchi1-20/+13
Subject manipulation should be done in unicode string mode.
2005-11-04Port from MAIN. Finnish Re: dialect.tkikuchi1-1/+1
2005-08-27FSF office has moved to 51 Franklin Street.tkikuchi1-1/+1
2005-05-13I finally find out why re.escape() doesn't work properly. '%' should nottkikuchi1-8/+8
be escaped for it is the insert directive. It was my trial and error in the comments in previous version. Well, I didn't think of '++' ...
2005-05-13prefix_subject(): Don't double escape the prefix_pattern.bwarsaw1-3/+0
2005-05-13strip_subject() in HyperArch.pybwarsaw1-8/+7
prefix_subject() in CookHeaders.py When calling re.sub() to substitute the subject prefix, you have to escape the pattern, otherwise prefixes like [C++] cause "multiple repeat" exceptions in re. Also, whitespace normalization and copyright years updates.
2005-02-12Request from Brad Knowles. We need subject prefix strippedtkikuchi1-0/+11
from the posts from mailling list for gatewaying to nntp.
2005-02-11bumping 2.1.6b3tkikuchi1-1/+4
2005-01-25Fix in pipermail to use Unicode for indexing (sort fails for ascii 8bit)tkikuchi1-1/+1
with some code clean up. Also, include SV (danish/swedish) Re: like pattern.
2005-01-22Introduce old_style in CookHeaders.py and OLD_STYLE_PREFIXING in Defaults.py.tkikuchi1-5/+29
Now the default behavior of prefixing is "Re: [prefix] subject". Variations like "Re[2]:" and German style "AW:" is now replaced by "Re:".
2004-10-09[ 601117 ] add sequencial number in subject prefixtkikuchi1-52/+117
Here is my major patch. It was postponed to 2.2 but since 2.2 is so late...
2003-12-18Fix commentbwarsaw1-2/+1
2003-12-18uheader(): Added default argument for maxlinelen.bwarsaw1-11/+12
process(): Reworked the way we calculate the List-Id header in the face of i18n descriptions which may need to be quoted (if ASCII and containing RFC 2822 special chars). What we do now is RFC 2047 encode just the description part, if there is one, then use formataddr() to combine that with the email address-like list identification.
2003-12-13process(): Quote the description when adding it to the List-ID header,bwarsaw1-1/+1
in case there are any special characters (in the RFC 2822) in the description.
2003-09-22Backporting from the HEAD -- updated handlersbwarsaw1-1/+1
2003-03-31Backporting from trunkbwarsaw1-2/+2
2003-02-08Backporting from the trunk.bwarsaw1-5/+14