Mailman 3 November 2002 - Mailman-Developers

I finally released an editing header/body patch for MM 2.1
by anser＠pobox.com 26 Nov '02

26 Nov '02

A lot of people were asking me for a 2.1 version of my "edit held message headers/bodies" patch, but I held off because I wasn't sure if 2.1 was gonna change under me and make me repeat the work. It seems pretty stable, now so here we go. This is the quick and dirty version, no frills, but it works for me. I like a lot of the new functionality in MM2.1, and now I can actually use it to run clean lists. Let me know if you encounter any problems. https://sourceforge.net/tracker/index.php?func=detail&aid=644129&group_id=1 03&atid=300103

1 0

[ mailman-Patches-644129 ] Edit held message header/body
by noreply＠sourceforge.net 26 Nov '02

26 Nov '02

Patches item #644129, was opened at 2002-11-26 14:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: Edit held message header/body Initial Comment: Here is my preliminary (brute force) patch to allow full editing of headers and bodies of messages being held for approval in Mailman 2.1 (as of beta 5). I have released versions of this for 1.x and 2.0.x but wanted to wait until 2.1 was fairly stable before releasing this one. You must set HOLD_MESSAGES_AS_PICKLES = 0 in your installation's mm_cfg.py for this to work. I may support pickles in a future version. Personally I don't see that much performance difference anyway, not on the held stuff... Also note that if you had HOLD_MESSAGES_AS_PICKLES = 1 (the default) when you created a list, you must recreate it after changing that variable. (Learned the hard way) This patch overrides the ADMINDB_PAGE_TEXT_LIMIT setting, so if you have megabyte messages being held, be ready to wait. Also - this version doesn't change the request database, so if you change the Subject: header you won't see the change reflected in the summary list (but it will be sent out your way when you Approve). Happy mailmanning! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_i…

1 0

How to lose friends and alienate people
by Greg Ward 26 Nov '02

26 Nov '02

After upgrading our only large, busy, high-profile list to MM 2.1 a few days ago, we've already got our first customer feedback: """ You've got some nerve quarantining my messages when all I've ever done on your forum is attempt to provide specific help to people who have requested it. Don't worry about my participation in the future. """ Ouch. This, of course, is in response to the standard response to posts to a moderated list: """ The reason it is being held: Posts by member are currently quarantined for moderation """ Ironically, I did notice the change when I was installing MM 2.1, decided I did not like it, but did not do anything about it. I have now, with a simple-stupid patch to Mailman/Handlers/Moderate.py: --- Mailman/Handlers/Moderate.py.orig Mon Oct 28 10:24:28 2002 +++ Mailman/Handlers/Moderate.py Mon Nov 25 22:03:29 2002 @@ -34,3 +34,3 @@ class ModeratedMemberPost(Hold.ModeratedPost): - reason = _('Posts by member are currently quarantined for moderation') + reason = _('Post to moderated list') This will at least keep the wolves, err users, at bay for a while. May I suggest the following: * on a traditional moderated list, where all users are moderated, telling individuals that *their* post is quarantined is likely to cause confusion at best, offense at worst (see above) * on a list with mixed moderation, you might not want to reveal to users who are moderated that there is something "special" about them ...both of which argue for making my little patch permanent. Greg -- Greg Ward - software developer gward(a)mems-exchange.org MEMS Exchange http://www.mems-exchange.org

2 1

[ mailman-Bugs-644005 ] sync_members: problems with u umlaut
by noreply＠sourceforge.net 26 Nov '02

26 Nov '02

Bugs item #644005, was opened at 2002-11-26 09:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_i… Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members: problems with u umlaut Initial Comment: Running sync_members -n, I get this error, when a member with an umlaut-u in it's real name gets removed. Traceback (most recent call last): File "/usr/sbin/sync_members", line 283, in ? main() File "/usr/sbin/sync_members", line 275, in main print _('Removed: <%(addr)30s> %(name)s') UnicodeError: ASCII encoding error: ordinal not in range(128) Changing the ü in the web-frontend to ue, and then running again sync_members "fixes" the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_i…

1 0

[ mailman-Bugs-643762 ] Uncaught runner exception/Attribute erro
by noreply＠sourceforge.net 26 Nov '02

26 Nov '02

Bugs item #643762, was opened at 2002-11-25 21:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 6 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception/Attribute erro Initial Comment: Hi. I have just upgraded from 2.0.11 to 2.1b5. Now, for every mail sent to mailman, I get an error in logs/error (included below). My Python version is 2.2.2. If you have further questions, I would be glad to answer them and to provide additional information. Regards, Matthias Nov 25 21:46:32 2002 (1371) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 25 21:46:33 2002 (1371) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/home/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- >Comment By: Matthias Juchem (brightice) Date: 2002-11-25 22:15 Message: Logged In: YES user_id=60479 Argh, please forget the comment about archiving... ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2002-11-25 21:58 Message: Logged In: YES user_id=60479 Uops, I forgot to say that archiving is broken. I do not know if this related to the reported error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_i…

1 0

[ mailman-Bugs-643762 ] Uncaught runner exception/Attribute erro
by noreply＠sourceforge.net 26 Nov '02

26 Nov '02

Bugs item #643762, was opened at 2002-11-25 21:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None >Priority: 6 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception/Attribute erro Initial Comment: Hi. I have just upgraded from 2.0.11 to 2.1b5. Now, for every mail sent to mailman, I get an error in logs/error (included below). My Python version is 2.2.2. If you have further questions, I would be glad to answer them and to provide additional information. Regards, Matthias Nov 25 21:46:32 2002 (1371) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 25 21:46:33 2002 (1371) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/home/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- >Comment By: Matthias Juchem (brightice) Date: 2002-11-25 21:58 Message: Logged In: YES user_id=60479 Uops, I forgot to say that archiving is broken. I do not know if this related to the reported error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_i…

1 0

[ mailman-Bugs-643762 ] Uncaught runner exception/Attribute erro
by noreply＠sourceforge.net 26 Nov '02

26 Nov '02

Bugs item #643762, was opened at 2002-11-25 21:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception/Attribute erro Initial Comment: Hi. I have just upgraded from 2.0.11 to 2.1b5. Now, for every mail sent to mailman, I get an error in logs/error (included below). My Python version is 2.2.2. If you have further questions, I would be glad to answer them and to provide additional information. Regards, Matthias Nov 25 21:46:32 2002 (1371) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 25 21:46:33 2002 (1371) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/home/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/home/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/home/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/home/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/home/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/home/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643762&group_i…

1 0

UTF8 problem with Microsoft Exchange and Mailman 2.1b4
by PieterB 26 Nov '02

26 Nov '02

Hi, I have a problem with UTF8-encoded e-mails from a Microsoft Exchange 2000 server which are sent to a Mailman 2.1b4 mailinglist server. Exchange uses "utf8" characterset, so that the users will get an extra "attachement" with every mailinglist message (charset "utf-8" is used for the body, and charset "us-ascii" is used for the signature of the mailinglist). An example of the headers and body is included, below. Is there a way to change the filtering in Mailman, so that these messages are converted to a more common charset, such as: us-ascii or iso-8859-1 For more information see: http://www.microsoft.com/exchange/techinfo/tips/Mail_utf8.asp (Mailbox Tip: Allow Non-UTF-8 Mail Clients To View Messages Sent from Exchange). I tried to get the Exchange server changed, but didn't get any response of the local administrator. ;( Regards, Pieter 8<-------------------------------------------- X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C29496.DF565EF8" Date: Mon, 25 Nov 2002 16:25:23 +0100 X-MS-TNEF-Correlator: <D5DF62311578B6438DC9703240E4FC6F179F4B(a)foo.bar> Thread-Topic: foo.bar Thread-Index: AcKUlojItUqNGxBLS1mNvYY31kEXygAACufy X-Content-Filtered-By: Mailman/MimeDel 2.1b4 X-Mailman-Version: 2.1b4 This is a multi-part message in MIME format. ------_=_NextPart_001_01C29496.DF565EF8 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 [base64 attachement removed] ------_=_NextPart_001_01C29496.DF565EF8 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit -- footer of the mailinglist ------_=_NextPart_001_01C29496.DF565EF8--

1 0

[ mailman-Bugs-643605 ] RFC2882 and / in subscriber address
by noreply＠sourceforge.net 25 Nov '02

25 Nov '02

Bugs item #643605, was opened at 2002-11-25 09:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_i… Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: RFC2882 and / in subscriber address Initial Comment: Reproduced from the mailman-users list. Thanks to Bill for the followup. --chris [][][][][][] Majordomo would tell you the same thing but I agree that it is a legal address (we use similar addresses internally at work) and should be accepted. RFC2822 (http://www.faqs.org/rfcs/rfc2822.html) clearly allows it in the local-part (Section 3.4.1) as a dot-atom. This should be fixed but in the mean time I don't think you are going to get it into mailman. Bill W. At 09:31 AM 11/25/2002 -0600, Christopher Kolar wrote: Hello. I am trying to add a person to a mail list and having some problems. Their organization runs some sort of bestial mail system where the addresses are of the form: schmoe.j/bhs(a)dns.u99.k12.il.us When I try to drop the address in through the mass subscribe screen I get the following message from Mailman: * Joe Schmoe -- Hostile address (illegal characters) My guess is that the / is getting parsed by Mm as an attempt to reference a file (a la majordomo). Is there a way to force the address onto the subscriber list? It is an actual valid address for delivery. Thanks in advance, --chris ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_i…

1 0

RELEASED Mailman 2.1 beta 5
by barry＠python.org 25 Nov '02

25 Nov '02

I've released Mailman 2.1 beta 5, and upgraded the python.org server to run this version, so with this announcement you are seeing its effects. :) Everything seems to be cruising along smoothly, so hopefully we'll have better luck with this version than with 2.1b4. See below for a list of changes since 2.1b4. Lots of bug fixes, u/i tweaks, and added support for Estonian. Be sure to read the IMPORTANT note in the change file below. If you're seeing horrible performance with Pipermail archives under 2.1b4, there is a fix available but you will have to take some manual steps. Enjoy, -Barry -------------------- snip snip -------------------- 2.1 beta 5 (19-Nov-2002) As is typical for a late beta release, this one includes the usual bug fixes, tweaks, and massive new features (just kidding). IMPORTANT: If you are using Pipermail, and you have any archives that were created or added to in 2.1b4, you will need to run bin/b4b5-archfix, followed by bin/check_perms to fix some serious performance problems. From you install directory, run "bin/b4b5-archfix --help" for details. - The personalization options have been tweaked to provide more control over mail header and decoration personalizations. In 2.1b4, when personalization was enabled, the To and Cc headers were always overwritten. But that's usually not appropriate for anything but announce lists, so now these headers aren't changed unless "Full personalization" is enabled. - You now need to go to the General category to enable emergency moderation. - The order of the hold modules in the GLOBAL_PIPELINE has changed, again. Now Moderate comes before Hold. - Estonian language support has been added. - All posted messages should now get decorated with headers and footers in a MIME-safe way. Previously, some MIME type messages didn't get decorated at all. - bin/arch grew a -q/--quiet option - bin/list_lists grew a -b/--bare option

12 14