[Mailman-Users] Mailman 2.1.7rc1 (was Re: Released: Mailman 2.1.7b1)
Oops, Sorry for the typo in the message title. I mean Released: Mailman 2.1.7rc1 Release Candidate Tokio Kikuchi wrote: > Hi all, > > I've just released Mailman 2.1.7rc1 Release Candidate. I'm sorry for > the violation of file name extension convention because I made a small > mistake when tagging the release number. I will be releasing 2.1.7 > final by December 31 if there is no problem. > > Please download it from SF or: > http://mm.tkikuchi.net/mailman-2.1.7rc1.tar.gz > > Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] Released: Mailman 2.1.7b1
Hi all, I've just released Mailman 2.1.7rc1 Release Candidate. I'm sorry for the violation of file name extension convention because I made a small mistake when tagging the release number. I will be releasing 2.1.7 final by December 31 if there is no problem. Please download it from SF or: http://mm.tkikuchi.net/mailman-2.1.7rc1.tar.gz Cheers, Tokio --- 2.1.7rc1 (24-Dec-2005) Security - The fix for CAN-2005-0202 has been enhanced to issue an appropriate message instead of just quietly dropping ./ and ../ from URLs. - A note on CVE-2005-3573: Although the RFC2231 bug example in the CVE has been solved in mailman-2.1.6, there may be more cases where ToDigest.send_digests() can block regular delivery. We put the send_digests() calling part in try - except clause and leave a message in the error log if something happened in send_digests(). Daily call of cron/senddigests will notify more detail to the site administrator. - List administrators can no longer change the user's option/subscription globally. Site admin can change these only if mm_cfg.ALLOW_SITE_ADMIN_COOKIES is set to Yes. - Script tag is disallowd in edithtml script. - Since probe message for the disabled users may reach unexpected persons, the password was excluded from sendProbe() and probe.txt. Note that the default value of VERP_PROBE has been set to `No' from 2.1.6., thus this change doesn't change the default behavior. New Features - Always remove DomainKey (and similar) headers (1287546) from messages sent to the list. - List owners can customize content filter behavior as not to collapse multipart/alternative to its first content. This allows HTML part to pass through after other content filtering is done. Internationalization - New language: Interlingua. Bug fixes and other patches - Defaults.py.in: SCRUBBER_DONT_USE_ATTACHMENT_FILENAME is set to True for safer operation. - Fix Scrubber.py mungs quoted-printable bug with introducing 'X-Mailman-Scrubbed' header for marking that the payload is scrubber-munged. The flag is referenced in ToDigest.py, ToArchive.py, Decorate.py and Archiver. Similar problem in ToDigest.py where the plain digest is generated is also fixed. - Fix Syslog.py to write quopri encoded message when it fail to write 8-bit characters. - Fix MTA/Postfix.py to check aliases group permission in check_perms and fix mailman-install document on this matter (1378270). - Fix private.py to go to the original URL after authorization (1080943). - Fix bounce log score messages to be more consistent. - Fix bin/remove_members to accept no arguments when both --fromall and --file= options are specified. - Change cgi-bin and mail wrapper "group not found" error message to be more descriptive of the actual problem. - Apply the list's ban_list to address changes and admin mass subscribe and invite and to confirmations/approvals of address changes, subscriptions and invitations. - Decode quoted-printable and base64 encoded parts before passing to HTML_TO_PLAIN_TEXT_COMMAND (1367783). - Remove Approve: header from post - treat as Approved: (1355707). - Stop removing line following Approve(d): line in body of post (1318883). - Remove Approve(d): from all text/* parts in addition the initial text/plain part. It still must be the first non-blank line in the first text/plain part or it won't be found or removed at all (1181161). - Log post in post log with true sender, not listname-bounces (1287921). - Correctly initialize and remember the list's default_member_moderation attribute in the web list creation page (1263213). - Add PEP263 charset in config_list output (1343100). - header_filter_rules get lost if accessed directly and needed authenti- cation by login page (1230865). - Obscure email when the poster doesn't set full name in 'From:' header. - Take preambles and epilogues into account when calculating message sizes for holding purposes (Mark Sapiro). - Logging/Logger.py unicode transform option (1235567). - bin/update crashes with bogus files (949117). - Bugs and patches: 1212066/1301983 (Date header in create/remove notice) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi
Re: [Mailman-Users] [Mailman-Developers] filename too long error - stopping list
On Fri, 2005-12-23 at 09:22 +0900, Tokio Kikuchi wrote: > May be we should set this default in Defaults.py.in in the next release > of 2.1.7. Thoughts? It's probably a good idea, but also as Stephen says, it might be a good idea to shorten the filename (keeping the extension) even when this value is left as False. -Barry signature.asc Description: This is a digitally signed message part -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Failed Upgrade: System now down for 2.5 days HELP
mcnutt wrote: > >I foolishly tried to upgrade from mailman 2.0.x to Mailman 2.1.6, and I >heartily repent of my sin. I have attempted to restore back to my working >version, but its still not running. Can anyone help me? > - Transcript of session follows - >Traceback (most recent call last): > File "/usr/local/mailman/scripts/post", line 94, in ? >main() > File "/usr/local/mailman/scripts/post", line 73, in main >mlist = MailList.MailList(listname, lock=0) > File "/usr/local/mailman/Mailman/MailList.py", line 79, in __init__ >self.Load() > File "/usr/local/mailman/Mailman/MailList.py", line 892, in Load >dict, e = self.__load(dbfile) > File "/usr/local/mailman/Mailman/MailList.py", line 869, in __load >fp = open(dbfile) >IOError: [Errno 13] Permission denied: >'/usr/local/mailman/lists/cls-news/config.db' >554 5.3.0 unknown mailer error 1 This trace is not from Mailman 2.1.6 so I assume it is from your old 2.0.x version. You have a permissions problem. Have you run bin/check_perms since restoring back? It seems that the process of upgrading and restoring back may have left some things with the wrong group ownership or without SETGID. In particular, the post wrapper is either not SETGID or its group doesn't have permission to write '/usr/local/mailman/lists/cls-news/config.db' -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] Failed Upgrade: System now down for 2.5 days HELP
I foolishly tried to upgrade from mailman 2.0.x to Mailman 2.1.6, and I heartily repent of my sin. I have attempted to restore back to my working version, but its still not running. Can anyone help me? Bill McNutt IT Administrator, UT Center for Literacy Studies http://cls.coe.utk.edu -Original Message- From: Mail Delivery Subsystem [mailto:[EMAIL PROTECTED] Sent: Friday, December 23, 2005 11:59 AM To: [EMAIL PROTECTED] Subject: Returned mail: see transcript for details The original message was received at Fri, 23 Dec 2005 11:58:36 -0500 (EST) from utk-cls.ra.utk.edu [160.36.208.91] - The following addresses had permanent fatal errors - "|/usr/local/mailman/mail/wrapper post cls-news" (reason: 1) (expanded from: <[EMAIL PROTECTED]>) - Transcript of session follows - Traceback (most recent call last): File "/usr/local/mailman/scripts/post", line 94, in ? main() File "/usr/local/mailman/scripts/post", line 73, in main mlist = MailList.MailList(listname, lock=0) File "/usr/local/mailman/Mailman/MailList.py", line 79, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 892, in Load dict, e = self.__load(dbfile) File "/usr/local/mailman/Mailman/MailList.py", line 869, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/usr/local/mailman/lists/cls-news/config.db' 554 5.3.0 unknown mailer error 1 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Mailman under Cygwin - won't add list
Stephen J. Turnbull wrote: >> "Ben" == Ben Discoe <[EMAIL PROTECTED]> writes: > >Ben> Wow. I had no idea at all that it was possible to run Apache >Ben> _inside_ Cygwin. The Apache website directs Windows people >Ben> to just install and run, so the alternate route is not well >Ben> known. > >You might want to just take a look at the list of stuff that Cygwin's >setup.exe supports. I imagine Apache (some version) is on the list. Absolutely. I run Cygwin Apache 1.3.29, and 1.3.33 and 2.0.54 are also available. As I said earlier, this is only for testing and only accessible locally. I don't think I'd want to run any MS-Windows server exposed to the world, Cygwin or native. >>> Maybe the solution is to run Apache under Cygwin or run a >>> mailman only version of Apache under Cygwin that listens on a >>> different port. > >Ben> Arrgh, it's hard to imagine that moving _closer_ to Cygwin is >Ben> the right direction, when all the trouble seems to stem from >Ben> Cygwin itself. > >No, the trouble stems from mixing different models of security and >other OS services. While Cygwin is a big PIMA, too, there's no doubt >in my mind that people who are using Cygwin for one app are better off >using it for apps that cooperate with the first, too. I do know of a >few exceptions, but they are all out-and-out bugs in the helper >applications. I totally agree with Stephen here. I'm surprised that Windows Apache can even execute the Cygwin compiled cgi-bin wrappers and Python at all. If I try to run a Cygwin compiled and linked program of any sort from a Windows command shell or even directly from Start->run, I get a fatal error dialog "The procedure entry point __getreent could not be located in the dynamic link library cygwin1.dll." Anyway, that part seems to work in your case, surprising or not. As Stephen says, mixing different security/protection models in one system is asking for trouble. Mailman is designed to run in a POSIX compliant or similar environment. Cygwin has its problems, but it is the closest thing to that environment that exists on Windows. Further, the only successful (albeit, perhaps limited) installations of Mailman on windows that we know of are under Cygwin. It may be possible to get Mailman to run in a Windows environment without Cygwin, and it may be valuable to you (Ben) and to others, but you're on your own in uncharted waters. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Mailman under Cygwin - won't add list
> "Ben" == Ben Discoe <[EMAIL PROTECTED]> writes: Ben> Wow. I had no idea at all that it was possible to run Apache Ben> _inside_ Cygwin. The Apache website directs Windows people Ben> to just install and run, so the alternate route is not well Ben> known. You might want to just take a look at the list of stuff that Cygwin's setup.exe supports. I imagine Apache (some version) is on the list. >> Maybe the solution is to run Apache under Cygwin or run a >> mailman only version of Apache under Cygwin that listens on a >> different port. Ben> Arrgh, it's hard to imagine that moving _closer_ to Cygwin is Ben> the right direction, when all the trouble seems to stem from Ben> Cygwin itself. No, the trouble stems from mixing different models of security and other OS services. While Cygwin is a big PIMA, too, there's no doubt in my mind that people who are using Cygwin for one app are better off using it for apps that cooperate with the first, too. I do know of a few exceptions, but they are all out-and-out bugs in the helper applications. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
