aboutsummaryrefslogtreecommitdiffstats
path: root/Mailman (unfollow)
Commit message (Collapse)AuthorFilesLines
2003-12-27show_helds_overview(), show_post_requests(): Another part of TK'sbwarsaw1-2/+13
patch # 865661. Encode the subject header in the list's preferred character set and make sure it is all on one line.
2003-12-26hold_for_approval(): Another part of TK's patch # 865661. Encode thebwarsaw1-2/+7
subject header in the list's preferred character set and make sure it is all on one line, when sent back to the original author.
2003-12-26oneline(): Another part of TK's patch # 865661. This one adds abwarsaw1-0/+15
utility function that returns a header in an i18n-safe way such that it is guaranteed to span exactly one line.
2003-12-26Article.__init__(): Provide a default charset if the message doesn'tbwarsaw1-3/+7
have one. Part of TK's patch #865661. __processbody_URLquote(): One chunk of TK's patch # 865661 for improving the i18n of the 'at' substitutions for archives.
2003-12-26Authenticate(): When authenticating AuthUser, wrap thebwarsaw1-35/+40
self.authenticateMember() call in a try/except catching and ignoring NotAMemberErrors. The effect of this is that other authcontexts being check will then proceed as normal. This fixes admin login to the private archives, and non-public rosters. Under the old code, if you tried to get into the private archives w/o entering an email address, but using the admin password, you'd be denied access. WebAuthenticate(): Removed the wrapping of .Authenticate() in try/except catching of NotAMemberError, since this should never percolate out now. Also, use True/False everywhere it's appropriate (but not in the cookie code). Original bug and patch by Stephan Berndts. Closes SF bug # 864676 and SF patch # 864674.
2003-12-24Update version numbers (2.1.4 is definitely going out before the endbwarsaw1-3/+3
of the year).
2003-12-24adminy_overview(): Richard Barrett's patch # 828811 to reduce listinfobwarsaw1-5/+6
and admin cgi process size by not keeping the entire mlist object alive through a reference in the advertised list. Only the information used in the overview is kept.
2003-12-24listinfo_overview(): Richard Barrett's patch # 828811 to reducebwarsaw1-5/+6
listinfo and admin cgi process size by not keeping the entire mlist object alive through a reference in the advertised list. Only the information used in the overview is kept.
2003-12-24finished_update_article(): Richard Barrett's fix to reduce Pipermailbwarsaw1-0/+9
archive bloat by deleting the html_body attribute on Article objects. Closes SF bug #835332. This is a stub in the base class. _update_thread_index(): Call finished_update_article() when done. store_article(): squirrel away the html_body value when pickling the article. This only reduces bloat on new articles. See bin/rb-archfix to clean up older archives.
2003-12-24finished_update_article(): Richard Barrett's fix to reduce Pipermailbwarsaw1-0/+6
archive bloat by deleting the html_body attribute on Article objects. Closes SF bug #835332. This only reduces bloat on new articles. See bin/rb-archfix to clean up older archives.
2003-12-22Comment repair.bwarsaw1-1/+1
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-16send_i18n_digests(): Configurations can change between the time abwarsaw1-1/+6
message is originally received and the time the digest is sent. If the configuration changes by setting ARCHIVE_HTML_SANITIZER to 0, a DiscardMessage exception can occur during the scrubbing. Catch this error. Closes SF #860135 with basic solution by Martin Pool.
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-12-13Romanian is iso-8859-2bwarsaw1-1/+1
2003-12-13handleForm(): Close some cross-site scripting holes found by Dirkbwarsaw2-4/+5
Mueller.
2003-12-01process(): Update a few email package calls.bwarsaw1-5/+11
2003-12-01Results.__init__(): It's possible for the Header functions to raise abwarsaw1-4/+9
HeaderParseError, so if that happens just ignore the Subject header for command purposes.
2003-12-01Fix a small comment bug.bwarsaw1-1/+1
2003-12-01process(): The implementation of extended header filters viabwarsaw1-4/+79
header_filter_rules.
2003-12-01True/False where appropriate.bwarsaw1-1/+1
process(): When we encode the text, catch ValueError along with UnicodeError and LookupError. The ValueError can be raised if the charset is the empty string. Closes SF bug # 834486.
2003-12-01True/False where appropriate.bwarsaw1-15/+23
process(): When we encode the text, catch ValueError along with UnicodeError and LookupError. The ValueError can be raised if the charset is the empty string. Closes SF bug # 834486.
2003-12-01True/False where appropriate.bwarsaw1-1/+7
2003-12-01True/False where appropriate.bwarsaw1-18/+19
handleForm(): Close a very minor, potential CSS hole.
2003-12-01GetConfigInfo(), handleForm(): Added header_filter_rules, a new variable whichbwarsaw1-2/+114
collects regular expression rules to match against the message's outer headers, along with the action to take when a match occurs.
2003-12-01_getValidValue(): Basically ignore HeaderFilter widgets. They'll be handledbwarsaw1-0/+2
in the Privacy.py file.
2003-12-01process(): Catch MMBadPasswordError which gets thrown by ProcessConfirmation()bwarsaw1-0/+3
when the wrong admin password is given in a confirmation message.
2003-12-01subscription_prompt(): Make text and submit button have consistent text.bwarsaw1-2/+2
Closes SF bug # 816410.
2003-12-01get_item_gui_value(): Added a new widget HeaderFilter and associated code tobwarsaw1-2/+72
build the interface from header_filter_rules. Here you can specify a set of regular expressions to test against a message's (outer) headers. You can also specify the action to take when a rule matches. These are available on Privacy->Spam Filters page.
2003-12-01html_TOC(): If PUBLIC_MBOX is false, use archtocnombox.html which doesn't havebwarsaw1-5/+6
a link to the mbox file.
2003-12-01makelink(), breaklink(): Some coding updates.bwarsaw1-14/+23
InitVars(): Fix the permissions on the empty archive index. Fixes SF bug #835012. CheckHTMLArchiveDir(): Only make the mbox link public if PUBLIC_MBOX is true.
2003-12-01NewVars(): Add header_filter_rules if missing.bwarsaw1-0/+1
2003-12-01Bump version to 2.1.4a0.bwarsaw1-4/+4
Also bump DATA_FILE_VERSION to pick up the new header_filter_rules variable.
2003-12-01True/False where appropriate.bwarsaw1-1/+1
2003-12-01True/False wehre appropriate.bwarsaw1-2/+8
2003-12-01repend(): An interface for putting request data back into the requestbwarsaw1-4/+19
database.
2003-12-01InitVars(): Added header_filter_rules for support of the expanded spambwarsaw1-14/+27
filters. ProcessConfirmation(): A fix for bug # 833384, where the incorrect admin password given in a the response to a hold message's confirm attachment would end up discarding the message. Now, an error message is returned to the sender and the held message is re-pended.
2003-12-01RejectMessage.__init__(): Since the notice message is put into the body of thebwarsaw1-0/+6
rejection message, make sure it ends with at least two newlines.
2003-12-01New variable PUBLIC_MBOX which allows the site administrator to disable publicbwarsaw1-30/+35
access to all list mbox files (this is not a per-list configuration). HeaderFilter: a new widget type to support the expanded spam filtering.
2003-11-27GetAvailableLanguages(): Strip out any language codes that aren't inbwarsaw1-1/+3
LC_DESCRIPTIONS. This is mostly useful for debugging since I occasionally add languages for testing and then disable them.
2003-11-27Added Romanian support by Stefaniu Criste.bwarsaw1-0/+2
(Note that Croatian is added but not yet supported. I'm still waiting for Nino Katic to give me a blessed translation.)
2003-11-27Typosbwarsaw1-2/+2
2003-11-27bulkdeliver(): Include the Message-ID in the log message.bwarsaw1-4/+6
2003-11-26bulkdeliver(): Rework the SMTP error handling to fix a problembwarsaw1-10/+21
described here: http://mail.python.org/pipermail/mailman-developers/2003-November/016119.html The issue is that if we get an SMTPResponseException with a permanent error code, we don't want to add all the recipients to the failures dict, otherwise they'll all score a bounce. That's not appropriate because the message is being rejected by the local smtpd for reasons having to do with the content of the message, not because there's some delivery problem to the recipient. Log all problems now to logs/smtp-failure.
2003-11-25ApprovedChangeMemberAddress(): When someone requests to change theirbwarsaw1-2/+12
address globally, it is possible the new address is already a member of this (or one of the other) lists. In that case, the old address is removed. Closes SF # 835036.
2003-11-24Create(): Take an optional emailhost name and use that to calculatebwarsaw1-2/+5
the valid postingaddr. If not given (the default), use DEFAULT_EMAIL_HOST as before.
2003-11-24process_request(): In response to SF bug # 835870, we now check thebwarsaw1-5/+12
calculated host name, and if VIRTUAL_HOST_OVERVIEW is true, that host name must match one of our known virtual hosts. Otherwise we'll refuse to create the list. If VIRTUAL_HOST_OVERVIEW is false, we'll do no checking (meaning the old behavior of being able to create a list with a non-fqdn hostname still exists). Also, pass the email host name into the MailList.Create() call.
2003-11-21copyright years.bwarsaw1-1/+1
2003-11-21_BounceInfo.__init__(), registerBounce(), disableBouncingMember(): Abwarsaw1-6/+7
fix for SF bug # 846681, where the confirmation cookie emailed in a bounce disabled notification was always out of date. The problem was that we created the cookie at the time of the first bounce. This is very likely more than three days before the time of the last bounce, which is when we should have (and now do) create the cookie.