Mailman 3 April 2005 - Mailman-coders

[ mailman-Bugs-1179789 ] error in documentation?
by SourceForge.net 09 Apr '05

09 Apr '05

Bugs item #1179789, was opened at 2005-04-09 11:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1179789&group_… Category: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: regis (rmd1023) Assigned to: Nobody/Anonymous (nobody) Summary: error in documentation? Initial Comment: in the online documentation at http://www.gnu.org/software/mailman/mailman-install/node43.html it says the following: "You should check the values for DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in Defaults.py. Make any necessary changes in the mm_cfg.py file, not in the mm_cfg.py file." I assume the second "mm_cfg.py" should actually be "Defaults.py" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1179789&group_…

1 0

[ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
by SourceForge.net 09 Apr '05

09 Apr '05

Patches item #839386, was opened at 2003-11-10 19:04 Message generated for change (Comment added) made by egervary You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i… Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Kev Green (kyrian) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL MemberAdaptor for Mailman 2.1 Initial Comment: A MemberAdaptor "plugin" which should allow Mailman list members to be loaded from a MySQL database, rather than just a Mailman "pickle" file. Provided as-is, and without warranty, this "plugin" may destroy your server, soul, scalp, house, and life. Please use it with caution. Kev Green, oRe Net. http://www.orenet.co.uk/ ---------------------------------------------------------------------- Comment By: Gergely EGERVARY (egervary) Date: 2005-04-09 12:14 Message: Logged In: YES user_id=1255996 Thank you for your good work. FYI: there's a missing "AND" in MysqlMemberships.py in line 494. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-12 00:22 Message: Logged In: YES user_id=1226150 excellent. can you please give me a list of the files modified from the original distro? grep sees six that grep have msyql in them. thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-03-11 23:56 Message: Logged In: YES user_id=99923 The flat file databases are unused when you put the MySQL adaptor in place, and they are untouched (and indeed not deleted) by it, the MySQL adaptor only queries the MySQL tables for membership information, without trying to force you into using it fulltime by deleting anything, etc. Once you unconfigure the MySQL adaptor, Mailman should revert back to your existing flat file databases. Of course, I could have missed something, etc. so do back up your flat file databases before installing the MySQL adaptor, and then you can just migrate back to them by restoring the backups. Either way, you have come up with a good question for an FAQ on the SQL adaptor :-) K. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 23:42 Message: Logged In: YES user_id=1226150 neat. just what i was looking for. i have a couple of live lists running on version version 2.1.5. i am a bit leary about unzipping this distrobution over the top of my working mailman as i am not sure how to backup the existing flat file databases. i would prefer to experiment with dropping the adapter into my existing installation. any pointers as to where to start? thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 19:34 Message: Logged In: YES user_id=99923 Oh, btw. v1.57 hasn't been tested yet, so it might kill your server, eat your dog, and stick your wife in the oven. Be careful using it! ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 19:33 Message: Logged In: YES user_id=99923 Version 1.57: 2004/12/13 * Merge in Daniel Shriver patch/code for a flat table architecture. [ Suggested by Kevin McCann <kmccann(at)bellanet.org>, but I hadn't found time to do it myself... ] * Add bugfix information from Jinhyok Heo <novembre(a)NOSPAM.ournature.org> * Add in mksqlmailman script from TheSin <thesin(a)SPAMNOTHANKS.southofheaven.org> * Follow Barry Warsaw's suggestion on delivery status timestamp. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-01-08 12:38 Message: Logged In: YES user_id=99923 Latest version incorporates automated generation of the necessary tables, cleaner error reporting, and updated documentation. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2003-11-11 12:14 Message: Logged In: YES user_id=99923 Bit of an oops in version 1.49, 1.50 now uploaded, which should fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i…

1 0

[ mailman-Bugs-1179487 ] denial of service security bug
by SourceForge.net 08 Apr '05

08 Apr '05

Bugs item #1179487, was opened at 2005-04-08 14:46 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1179487&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Crispin (mrcrispin) Assigned to: Nobody/Anonymous (nobody) Summary: denial of service security bug Initial Comment: We've had multiple incidents of this problem. If a digest gets a message containing an attachment using an RFC 2231 encoded parameter has a character set that is unknown to Python (in this case, "X- UNKNOWN"), then routine get_filename() in email/Message.py (not to be confused with Mailman/Message.py) calls unicode() without any error trap. The result is that digest delivery for that entire mailing list is suspended until that message is manually removed. It appears that passing an "ignore" as the errors parameter to unicode() won't stop Python from generating this error. I'm not sure as to the best way to fix this. I haven't worked much with Python at all, and Mailman support was just dumped on my lap. I can see that there are lots of unicode() calls throughout the Mailman source that don't have any error protection. I don't know which ones are also vulnerable to this attack. Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_n ow ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in sen d_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in sen d_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 268, in pro cess url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 362, in sav e_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 731, in get_f ilename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1179487&group_…

1 0

[ mailman-Feature Requests-1178486 ] Configurable default for Defer Accept Reject Discard options
by SourceForge.net 07 Apr '05

07 Apr '05

Feature Requests item #1178486, was opened at 2005-04-07 12:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1178486&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rodger Copp (rodger_copp) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable default for Defer Accept Reject Discard options Initial Comment: One particular user from our organization regularly sends several emails to several moderated mailman lists. It is sufficient to simply see who the message is from and then "Accept" it. We have to approve each one separately and we have to change the "Defer" tick each time. It's becoming a pain and it would be nice not to make those extra mouse movements. Is it possible to have the Accept selection ticked by default instead of Defer for Mailman's Moderator Administration page? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1178486&group_…

1 0

[ mailman-Bugs-1178453 ] allow setting max# or autoexpire pending administration
by SourceForge.net 07 Apr '05

07 Apr '05

Bugs item #1178453, was opened at 2005-04-07 11:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1178453&group_… Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ken Yee (kenyee) Assigned to: Nobody/Anonymous (nobody) Summary: allow setting max# or autoexpire pending administration Initial Comment: Some mailing lists gets spammed a lot, so the "tend to pending administration work" gets huge after a few weeks, especially if you forget about it for a while :-) I'd suggest one of two things: 1) set a max# of pending admin items and autodelete the ones that are oldest 2) set an automatic purge of items older than N days I have a list I'm on where I can't even load the "tend to pending admin work" page any more because it's so huge. The browser just sits there and spins while the server tries to send everything down. Of course, I've neglected deleting spam (it's a list where only list members can post) for a few months.... ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1178453&group_…

1 0

[ mailman-Bugs-969613 ] double-quotes handled inconsistent for list's description
by SourceForge.net 07 Apr '05

07 Apr '05

Bugs item #969613, was opened at 2004-06-09 15:54 Message generated for change (Comment added) made by windl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=969613&group_i… >Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: Ulrich Windl (windl) Assigned to: Nobody/Anonymous (nobody) >Summary: double-quotes handled inconsistent for list's description Initial Comment: (I'll use a double exclamation mark (!!) instead of a double-quote here, because it seems the double-quotes are converted to """ here by mistake) If I enter a short description like the following line for a mailing list: List about !!something interesting!! mailman-2.1.4 cunnecessarily converts the double quotes (!!) to " in EMail header values. Example: List-Id: !!List about "something interesting" !! <mailbox(a)domain.org> I think that the quoting in font of an EMail address enclosed by anglr brackets (<...>) is not necessary, and using HTML is wron and not portable. I might work with some broken clients however. ---------------------------------------------------------------------- >Comment By: Ulrich Windl (windl) Date: 2005-04-07 12:45 Message: Logged In: YES user_id=181779 I've learned that "&quit;" is stored in mailman's list configuration file like this: description = 'Talking about "this"' where description = 'Talking about "this"' would work. Actually when using config_list to make that change, it tuns out that the Web interface can't handle that, producing just 'Talking about '. list_lists however would print the correct strings. Summary: This is not just a problem in mail headers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=969613&group_i…

1 0

[ mailman-Bugs-1178199 ] 2.1.6B4: encode_ascii_prefixes error
by SourceForge.net 06 Apr '05

06 Apr '05

Bugs item #1178199, was opened at 2005-04-07 02:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1178199&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.6B4: encode_ascii_prefixes error Initial Comment: Hi! Mailman seems not to encode the subject prefix correctly. Options: Language: german (iso-8859-1) encode_ascii_prefixes: Always Prefix: ÄÖÜ my mailsubject: äöü result: =?utf-8?b?W8OEw7bDnF0=?= =?iso-8859-1?q? =E4=F6=FC?= my Mailsubject: test result: =?utf-8?b?W8OEw7bDnF0=?= test Mailman seems to convert always in utf regardless of which language is chosen. The result is a subject-line with two different encodings if you have special chars in prefix and the subject-line. A lot of mailcleints do not support this so that in the display (not in the mailheader) the subject after the prefix is lost. And the space between prefix and subject will be lost because it is not encoded. This problem we did not have before using mailman version 2.2a. The MTA is postfix. I dont know if postfix is doing this encoding to utf or mailman. In this case mailman fails to convert the prefix. If I choose encode_ascii_prefixes: Needed I get the same result. If I choose encode_ascii_prefixes: Never I get the same result. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1178199&group_…

1 0

[ mailman-Bugs-1176706 ] error when doing bin/newlist mailman
by SourceForge.net 04 Apr '05

04 Apr '05

Bugs item #1176706, was opened at 2005-04-05 02:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1176706&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: BuGoFf (bugoff) Assigned to: Nobody/Anonymous (nobody) Summary: error when doing bin/newlist mailman Initial Comment: I installed mailman like it is said in the INSTALL file but when i have to make the newlist it gives an error: mailman@bleu_top:~$ ./bin/newlist mailman Enter the email of the person running the list: admin(a)blue-top.be Initial mailman password: Traceback (most recent call last): File "./bin/newlist", line 219, in ? main() File "./bin/newlist", line 160, in main mlist.Create(listname, owner_mail, pw) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 296, in InitVars self.web_page_url = ( TypeError: not all arguments converted during string formatting Is there a solution for this problem? Thanks in advance for your help Bram ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1176706&group_…

1 0

[ mailman-Patches-1176278 ] HeaderParseError
by SourceForge.net 04 Apr '05

04 Apr '05

Patches item #1176278, was opened at 2005-04-04 13:47 Message generated for change (Comment added) made by interra You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1176278&group_… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Myroslav Opyr (interra) Assigned to: Nobody/Anonymous (nobody) Summary: HeaderParseError Initial Comment: Hi, The error was reported several times at maillists (Users and Developers). It look like email library started producing this Exception and Mailman never got to handle it in addition to LookupError, and UnicodeError. In my case the problem was in ugly headers. I was with Email 2.5.5 and 3.0. ---------------------------------------------------------------------- >Comment By: Myroslav Opyr (interra) Date: 2005-04-04 14:02 Message: Logged In: YES user_id=327208 Forgot to attach :( it should be automagically turned on when I fill the upload box! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1176278&group_…

1 0

[ mailman-Patches-1176284 ] CommandRunner-UnicodeDecodeError
by SourceForge.net 04 Apr '05

04 Apr '05

Patches item #1176284, was opened at 2005-04-04 14:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1176284&group_… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Myroslav Opyr (interra) Assigned to: Nobody/Anonymous (nobody) Summary: CommandRunner-UnicodeDecodeError Initial Comment: Another two messages got stuck in my shunt folder: Apr 04 13:48:45 2005 (31466) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 224, in _dispose res = Results(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 78, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/lib/python2.3/site-packages/email/Header.py", line 124, in make_header h.append(s, charset) File "/usr/local/lib/python2.3/site-packages/email/Header.py", line 252, in append ustr = unicode(s, incodec, errors) UnicodeDecodeError: 'ascii' codec can't decode byte 0xd5 in position 0: ordinal not in range(128) Attached patch pushed them. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1176284&group_…

1 0