aboutsummaryrefslogtreecommitdiffstats
path: root/Mailman/Handlers/CookHeaders.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Improvements in subject prefixing with encoded prefixes.Mark Sapiro2017-05-121-6/+8
|
* Properly RFC 2047 encode the display name in DMARC munged From:.Mark Sapiro2016-11-241-5/+36
|
* Acknowledge option will now be honored for posts to anonymous listsMark Sapiro2016-02-171-1/+3
|
* Fixed garbled From: with DMARC mitigations and non-ascii display name.Mark Sapiro2016-01-211-2/+5
|
* Ensure white space following subject_prefix.Mark Sapiro2015-12-141-0/+5
|
* hanged CookHeaders to default to using space rather than tab asMark Sapiro2015-10-141-3/+3
| | | continuation_ws when folding headers.
* Subject prefixing could fail to collapse multiple 'Re:' in an incommingMark Sapiro2015-09-161-1/+7
| | | message if they all came after the list's subject_prefix.
* Fixed an issue with shunted messages on a list where the charset forMark Sapiro2015-06-071-1/+6
| | | | the list's preferred_language had been changed from iso-8859-1 to utf-8 without recoding the list's description.
* Due to a prior change, From: header munging would unnecessarily add theMark Sapiro2015-01-111-4/+13
| | | | original From: to Cc: when was already in an original Reply-To:. Fixed.
* Add some explanitory comments for why we defer some Munge From changesMark Sapiro2015-01-041-0/+5
| | | | to WrapMessage. Correct a misplaced item in NEWS.
* When applying DMARC mitigations, CookHeaders now adds the original From:Mark Sapiro2015-01-031-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.
* Enhance the fix for (LP: #1318025)Mark Sapiro2014-05-111-0/+2
|
* Handle missing From: header addresses for DMARC mitigation actions.Mark Sapiro2014-05-091-3/+10
| | | | (LP: #1318025)
* Sender: headers are no longer removed in from_is_list Munge FromMark Sapiro2014-05-041-3/+0
| | | | actions. (LP: #1315970)
* Updated CookHeaders to always add the poster's From: address to Reply-To:Mark Sapiro2014-05-021-8/+2
| | | | when applying from_is_list transformations.
* Changed from_is_list actions to insert the list address in Cc: if theMark Sapiro2014-04-251-12/+20
| | | | | list is fully personalized. Otherwise, the list address is only in From: and Reply-To: overrides it. (LP: #1312970)
* Fixed the Munge From action to not actually Munge the From: or Reply-To:Mark Sapiro2014-04-231-11/+15
| | | | | until after the message has been sent to the archive, digest and usenet gateway.
* Added and modified various options regarding DMARC. See the NEWS file.Mark Sapiro2014-04-151-5/+5
|\
* | Enhanced fix for LP: #1304511 to use member's real name if available.Mark Sapiro2014-04-081-1/+4
| |
* | For from_is_list feature, use email address from original From: ifMark Sapiro2014-04-081-0/+2
| | | | | | | | | | original From: has no display name and strip domain part from resultant names that look like email addresses. (LP: #1304511)
* | For from_is_list, if no real name in From, use email address.Mark Sapiro2014-04-061-0/+2
| |
* | Cleaned up a couple of comments missed in the author_is_list toMark Sapiro2014-03-141-1/+1
| | | | | | from_is_list change.
* | - The from_is_list header munging feature introduced in Mailman 2.1.16 isMark Sapiro2014-02-161-3/+6
|/ | | | no longer erroneously applied to Mailman generated notices.
* Renamed author_is_list to from_is_list.Mark Sapiro2013-09-281-6/+6
|
* Made author_is_list a 3-way with an option to wrap the message.Mark Sapiro2013-09-271-18/+47
|
* Second cut at the author_is_list feature.Mark Sapiro2013-07-191-1/+2
|
* First cut at the author_is_list feature.Mark Sapiro2013-07-181-3/+4
|
* Fixed a typo in the UPGRADING doc - bin/upgrade -> bin/update.Mark Sapiro2012-06-201-0/+0
|
* Stopped removing the trailing slash from the List-Archive: header URL.Mark Sapiro2012-03-241-2/+0
| | | | (LP: #964190)
* Changed subject prefixing to allow for possible whitespace between anMark Sapiro2011-11-221-2/+2
| | | | | 'Re' and the following colon when determining how to add the prefix. Bug #893290.
* Fixed CookHeaders.py which in some cases with new style prefixingMark Sapiro2008-06-201-1/+4
| | | | | would insert an extra space between the prefix and the subject.
* CookHeaders.py - Changed the first URL in the RFC 2369 List-Unsubscribe:Mark Sapiro2008-03-061-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.
* ch_oneline(): Input string variable is overwritten. Also use listtkikuchi2006-02-171-8/+4
| | | | comprehension where appropriate.
* process(): Fix a comment.bwarsaw2006-01-011-4/+3
|
* A cleansing pass, almost entirely cosmetic. Such things as whitespacebwarsaw2005-12-301-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.
* Python interpreter has evolved to be strict on ascii charset range.tkikuchi2005-12-261-20/+13
| | | | Subject manipulation should be done in unicode string mode.
* Port from MAIN. Finnish Re: dialect.tkikuchi2005-11-041-1/+1
|
* FSF office has moved to 51 Franklin Street.tkikuchi2005-08-271-1/+1
|
* I finally find out why re.escape() doesn't work properly. '%' should nottkikuchi2005-05-131-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 '++' ...
* prefix_subject(): Don't double escape the prefix_pattern.bwarsaw2005-05-131-3/+0
|
* strip_subject() in HyperArch.pybwarsaw2005-05-131-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.
* Request from Brad Knowles. We need subject prefix strippedtkikuchi2005-02-121-0/+11
| | | | from the posts from mailling list for gatewaying to nntp.
* bumping 2.1.6b3tkikuchi2005-02-111-1/+4
|
* Fix in pipermail to use Unicode for indexing (sort fails for ascii 8bit)tkikuchi2005-01-251-1/+1
| | | | with some code clean up. Also, include SV (danish/swedish) Re: like pattern.
* Introduce old_style in CookHeaders.py and OLD_STYLE_PREFIXING in Defaults.py.tkikuchi2005-01-221-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:".
* [ 601117 ] add sequencial number in subject prefixtkikuchi2004-10-091-52/+117
| | | | Here is my major patch. It was postponed to 2.2 but since 2.2 is so late...
* Fix commentbwarsaw2003-12-181-2/+1
|
* uheader(): Added default argument for maxlinelen.bwarsaw2003-12-181-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.
* process(): Quote the description when adding it to the List-ID header,bwarsaw2003-12-131-1/+1
| | | | | in case there are any special characters (in the RFC 2822) in the description.
* Backporting from the HEAD -- updated handlersbwarsaw2003-09-221-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-28 22:33:15 +0000