Mailman 3 January 2006 - Mailman-coders

[ mailman-Bugs-1408801 ] mail with special characters not archived on pipermail
by SourceForge.net 18 Jan '06

18 Jan '06

Bugs item #1408801, was opened at 2006-01-18 07:22 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=1408801&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Jericho (jericho001) Assigned to: Nobody/Anonymous (nobody) Summary: mail with special characters not archived on pipermail Initial Comment: Mail with the following text: MÃ¥ns ÃhrstrÃ¶m Will not be archived on the list archive (via Pipermail). No warning or errors are generated, nothing in the logs to show the failure (that I could see). Converting the special chars to the approximate letters "Mans Ohrstrom" allowed the mail to reach the archive. Delivered by Mailman version 2.1.7rc1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1408801&group_…

1 0

[ mailman-Patches-1408586 ] localize
by SourceForge.net 17 Jan '06

17 Jan '06

Patches item #1408586, was opened at 2006-01-17 23:59 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=1408586&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Giuseppe Scrivano (rocky_10_balboa) Assigned to: Nobody/Anonymous (nobody) Summary: localize Initial Comment: Hi, We wrote this little patch as we needed the possibility to change the default language for a virtual host (we use the same mailman instance for multiple sites). By default this is not possible, you can configure only one language for the entire installation and change it only for mailing lists but you get always the same language for listinfo, add list page and admin initial pages. We hope it can be useful for others too. Regards, Domenico Chierico Alessandro Iurlano Giuseppe Scrivano ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1408586&group_…

1 0

[ mailman-Bugs-1408435 ] Build python extensions when building mailman, not install
by SourceForge.net 17 Jan '06

17 Jan '06

Bugs item #1408435, was opened at 2006-01-17 13:56 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=1408435&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Build python extensions when building mailman, not install Initial Comment: The python extensions that are included with Mailman are installed when you do 'make install' on the mailman distribution. Wouldn't make sense to have those extensions built when you just do 'make' so any build errors on the extensions can be dealt with before you try to actually install? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1408435&group_…

1 0

[ mailman-Bugs-1218827 ] please do not put the list footer in attachment if possible
by SourceForge.net 16 Jan '06

16 Jan '06

Bugs item #1218827, was opened at 2005-06-11 16:27 Message generated for change (Comment added) made by suso You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1218827&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nagy Gábor Péter (bagoy) Assigned to: Nobody/Anonymous (nobody) Summary: please do not put the list footer in attachment if possible Initial Comment: I manage a list, for a long time it was running on mailman 2.0.11, now it was upgraded to 2.1.5 I was happy to see that I could set the list language to our language, but soon people started to complain because of the list footer. The old version has just added the footer at the bottom of every message, and we never had a problem with that. The new one tries to be smart, and from time to time it puts the footer in another mime part, with different encoding. While I realize that this is good in certain cases, most of the time it is useless. Our list footer contains ascii characters only. Those ascii characters could be simply added at the end of any latin1, latin2, or utf8 messages without any problem. Now it seems that even though I did not put any 8 bit characters in the footer, mailman always kept the footer latin2. (because of the list language). Now I have set the list language to english, so we have the same footer, but this time it is (correctly) us-ascii. Still, sometimes I receive emails, where the us-ascii footer was not added at the end of an email. Today for example there was a utf8 mail on the list, and the footer came as an attachment. Please try to find a way to recognize the possible combinations, and try to avoid creating a new attachment. It seems that most of the list members use some microsoft email clients, and all but one m$ clients don't show the footer inline. And all the clients (opera and netscape too, I was told) shows the attachment sign for all these messages, and people don't know which mails have "real" attachments, and which ones have only the footer attached. Cheers, Gabor ---------------------------------------------------------------------- Comment By: Suso Banderas (suso) Date: 2006-01-16 19:09 Message: Logged In: YES user_id=155277 This bug has been open for a while now. I just wanted to let everyone know that you can fix this issue by not using the % escape sequences in your footer. That may not be ideal, but if fixes the problem for now if you'd rather not have attached footers than have dynamic footers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1218827&group_…

1 0

[ mailman-Bugs-1152800 ] Footer is Added in Plaintext to baes64 encoded mails
by SourceForge.net 16 Jan '06

16 Jan '06

Bugs item #1152800, was opened at 2005-02-27 08:36 Message generated for change (Comment added) made by suso You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152800&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: James (james_tis) Assigned to: Nobody/Anonymous (nobody) Summary: Footer is Added in Plaintext to baes64 encoded mails Initial Comment: When a user sends an email to the list with the following headers: Content-Type: text/plain Content-Transfer-Encoding: base64 The mailman software attaches the list footer to the body part of the message in plain text. When users receive the message, they see a string of garbage characters at the bottom, where their mail client software tried to base64 decode the plaintext footer. Mailman should instead check the Content-Transfer-Encoding header and either: (1) append the footer encoded in the appropriate encoding (2) change the Content-Type header to multipart/text and add the footer as a separate body part (3) do not add the footer ---------------------------------------------------------------------- Comment By: Suso Banderas (suso) Date: 2006-01-16 19:08 Message: Logged In: YES user_id=155277 This bug has been open for a while now. I just wanted to let everyone know that you can fix this issue by not using the % escape sequences in your footer. That may not be ideal, but if fixes the problem for now if you'd rather not have attached footers than have dynamic footers. ---------------------------------------------------------------------- Comment By: James (james_tis) Date: 2005-02-27 09:28 Message: Logged In: YES user_id=1228458 I'll try upgrading and see if that helps... ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-27 08:46 Message: Logged In: YES user_id=67709 What is the version of your mailman? I believe I fixed this in mailman-2.1.6(b4). The latest version should decode base64 before appending the footer (and re-encode appropriately according to the charset). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152800&group_…

1 0

[ mailman-Bugs-1394696 ] "ValueError: day of year out of range" on Dec 31?
by SourceForge.net 14 Jan '06

14 Jan '06

Bugs item #1394696, was opened at 2006-01-01 05:44 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) >Status: Closed Resolution: Out of Date Priority: 5 Submitted By: quinn comendant (quinncom) Assigned to: Nobody/Anonymous (nobody) Summary: "ValueError: day of year out of range" on Dec 31? Initial Comment: I haven't checked closely but I'm guessing the following error is because [root@one /var/mailman]# /etc/init.d/mailman stop Traceback (most recent call last): File "/var/mailman/bin/qrunner", line 270, in ? main() File "/var/mailman/bin/qrunner", line 230, in main qrunner.run() File "/var/mailman/Mailman/Queue/Runner.py", line 82, in run self._cleanup() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 139, in _cleanup self._register_bounces() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 129, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/var/mailman/Mailman/Bouncer.py", line 131, in registerBounce [root@one /var/mailman]# time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range [root@one /var/mailman]# date Sat Dec 31 23:39:23 CST 2005 [root@one /var/mailman]# bin/version Using Mailman version: 2.1.4 ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-11 04:33 Message: Logged In: YES user_id=1123998 As Tokio says, this is a known incompatability between Mailman 2.1.5 and earlier and Python 2.4 and later. It has nothing to do with specific dates. It occurs whenever a second or subsequent bounce is received for the same user in the same day. It is fixed by upgrading to Mailman 2.1.6 or later or by changing time.strftime('%d-%b-%Y', day + (0,)*6)) in line 131 of Mailman/Bouncer.py to time.strftime('%d-%b-%Y', day + (0,0,0,0,1,0))) See <http://mail.python.org/pipermail/mailman-users/2005-March/043640.html> And yes, disabling bounce processing will avoid the error. ---------------------------------------------------------------------- Comment By: Nate (n8wilson) Date: 2006-01-11 03:37 Message: Logged In: YES user_id=1271889 I got a similar/same error on Jan 10th - Mailman seems to run for a while and spontaneaously do this - or maybe when it gets a bounced message. I disabled bounce-detection in hopes of it not occurring. ------- [root@gttx nwilson]# Traceback (most recent call last): File "/usr/lib/mailman/bin/qrunner", line 270, in ? main() File "/usr/lib/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 87, in run self._cleanup() File "/usr/lib/mailman/Mailman/Queue/OutgoingRunner.py", line 134, in _cleanup BounceMixin._cleanup(self) File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py", line 132, in _cleanup self._register_bounces() File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py", line 120, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/usr/lib/mailman/Mailman/Bouncer.py", line 131, in registerBounce time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range Traceback (most recent call last): File "/usr/lib/mailman/bin/qrunner", line 270, in ? main() File "/usr/lib/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 87, in run self._cleanup() File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py", line 220, in _cleanup BounceMixin._cleanup(self) File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py", line 132, in _cleanup self._register_bounces() File "/usr/lib/mailman/Mailman/Queue/BounceRunner.py", line 120, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/usr/lib/mailman/Mailman/Bouncer.py", line 131, in registerBounce time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range [root@gttx nwilson]# exit exit [nwilson@gttx ~]$ date Tue Jan 10 22:35:01 EST 2006 You have new mail in /var/spool/mail/nwilson [nwilson@gttx ~]$ /usr/lib/mailman/bin/version Using Mailman version: 2.1.5 [nwilson@gttx ~]$ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-10 21:37 Message: Logged In: YES user_id=67709 time.strftime('%d-%b-%Y',day + (0,)*6)) caused error in Python 2.4 and this was fixed in Mailman 2.1.6. Please upgrade your mailman to the latest version. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_…

1 0

[ mailman-Bugs-1194419 ] Lose Topics when go directly to topics URL
by SourceForge.net 14 Jan '06

14 Jan '06

Bugs item #1194419, was opened at 2005-05-03 12:29 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1194419&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Jeff Peterson (jeffpeterson) Assigned to: Nobody/Anonymous (nobody) Summary: Lose Topics when go directly to topics URL Initial Comment: If I go directly to my list's Topics URL (http://my.site.com/mailman/admin/scan/topics) the first time I bring up my web browser, I get the List's (Scan) Administrator Authentication page. After signing in, I am redirected to the Admin List's (Scan) Topics page, but all my topics are gone for my list. I looked in the list's directory (mailman/lists/<list name>) and the config.pck file has been changed and no longer contains my configurations. Luckily, I had a backup copy of my config.pck file. Is this a known bug? The losing of the configuration/topics information only occurs if I am not currently logged in as administrator and am redirected to the Admin login page. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-14 13:16 Message: Logged In: YES user_id=67709 fixed in CVS and opened a patch tracker. Thank you Mark! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-14 03:41 Message: Logged In: YES user_id=1123998 Try the attached patch. I believe it will fix the problem. It should apply as is for 2.1.5 through 2.1.7, and with a change in line number, back to 2.1.1. ---------------------------------------------------------------------- Comment By: Stuart Bishop (zenzen) Date: 2006-01-11 04:58 Message: Logged In: YES user_id=46639 This just bit me too. It also of course affects people if the authentication gets triggered in other ways when visiting that page. I just logged into the front page, clicked on 'topics', got prompted for auth information again and discovered all my topics were gone. An assert to ensure that the topic list is only shrinking by a maximum of one would be a nice temporary fix - there is no web ui for growing or shrinking the list dramatically so this case would indicate a dataloss bug is about to trigger. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1194419&group_…

1 0

[ mailman-Bugs-1395683 ] UnicodeError running arch
by SourceForge.net 14 Jan '06

14 Jan '06

Bugs item #1395683, was opened at 2006-01-03 01:12 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 (stable) >Status: Closed Resolution: Fixed Priority: 7 Submitted By: Michael Wallis (kf6spf) Assigned to: Tokio Kikuchi (tkikuchi) Summary: UnicodeError running arch Initial Comment: I just deployed the latest release (2.1.7 stable) and decided to rebuild an archive. I'm getting the following error trace caused by it hitting high-order byte characters. These were not a problem when I first built the archive from 2.1.6 so something may have changed. Pickling archive state into /usr/local/mailman/archives/private/basfa/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 585, in processUnixMailbox self.add_article(a) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 626, in add_article filename)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1116, in write_article f.write(article.as_text()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in as_text '\g<1>' + _(' at ') + '\g<2>', body) File "/usr/lib/python2.2/sre.py", line 143, in sub return _compile(pattern, 0).sub(repl, string, count) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-14 13:11 Message: Logged In: YES user_id=67709 Closing now bcause this is included in a new patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-10 21:34 Message: Logged In: YES user_id=67709 Re-open for visitors can find this. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-09 07:41 Message: Logged In: YES user_id=67709 Hi, I've just committed this patch in the CVS. I'll be releasing 2.1.8 but, in the meantime, please use this patch. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-06 05:43 Message: Logged In: YES user_id=1123998 I have deleted my patch # 161995 to avoid confusion as patch # 162200 is the correct one. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-05 02:50 Message: Logged In: YES user_id=67709 Here is a revised patch to incorporate non-ascii '_at_' replacement. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 18:20 Message: Logged In: YES user_id=1123998 One other followup note on this. The problem can also occur when archiving an individual post to a list. In this case, the HTML file for the post will be written but not indexed; the post will not be added to the .txt file; the error will be logged in the 'error' log, and the message will be shunted. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 17:28 Message: Logged In: YES user_id=1123998 The previous patch wasn't effective in all circumstances. I have replaced it again. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 05:21 Message: Logged In: YES user_id=1123998 I've developed a new patch which I've attached here in place of the previous one. I think the new patch actually fixes the problem. Please try it and report. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-03 01:54 Message: Logged In: YES user_id=1123998 I also observed this problem. It will be properly fixed. In the mean time, I have attached a patch - HyperArch.patch - which will allow you to rebuild the full archive. The patch is not a real fix for the problem however, as the problem messages will not have email addresses obscured in the body of the message in the monthly .txt files. The HTML archive will be OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_…

1 0

[ mailman-Bugs-1400128 ] edithtml.py missing import
by SourceForge.net 14 Jan '06

14 Jan '06

Bugs item #1400128, was opened at 2006-01-09 06:13 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1400128&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: Fixed Priority: 7 Submitted By: Cliff Wells (cliffwells18) Assigned to: Tokio Kikuchi (tkikuchi) Summary: edithtml.py missing import Initial Comment: You can't save edited pages because edithtml.py fails to import the re module. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-14 13:10 Message: Logged In: YES user_id=67709 Closing now because this is included in the mailman-2.1-patch-200601014.txt. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-01-11 02:49 Message: Logged In: YES user_id=12800 I'm not sure I understand the motivation for keeping resolved issues open. I think it's better to close them when it's fixed in CVS. I know the SF tracker searching sucks, but if we really need to keep tabs on resolved issues, I think there are other ways to do this, such as starting a page on the web site. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-10 21:31 Message: Logged In: YES user_id=67709 Re-open it for new visitors can find it. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-09 07:44 Message: Logged In: YES user_id=67709 It was fixed it in the CVS. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-09 06:50 Message: Logged In: YES user_id=67709 Please add import re line in the first part of edithtml.py file. Sorry for the inconvenience. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1400128&group_…

1 0

[ mailman-Patches-1405790 ] Mailman 2.1.7 multiple patch
by SourceForge.net 14 Jan '06

14 Jan '06

Patches item #1405790, was opened at 2006-01-14 13:07 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=1405790&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Mailman 2.1.7 multiple patch Initial Comment: After the release of Mailman 2.1.7, a few bugs are found in a couple of weeks. We are planning to release 2.1.8 near future, but in the mean time, please apply this patch. It fixes bugs 1400128, 1395683, 1194419, http://mail.python.org/pipermail/mailman-users/2006-January/048573.html (SpamDetect loop) and few others. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1405790&group_…

1 0