From noreply at sourceforge.net Sun Jan 1 00:04:08 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 31 Dec 2005 15:04:08 -0800 Subject: [ mailman-Feature Requests-1394592 ] Allow any registered member to be a moderator Message-ID: Feature Requests item #1394592, was opened at 2005-12-31 18:04 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=1394592&group_id=103 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: Rocky Bernstein (rockyb) Assigned to: Nobody/Anonymous (nobody) Summary: Allow any registered member to be a moderator Initial Comment: A number of bug, info, or help mailing list are the target of spam, viruses and hoaxes. So often they have to be public but be moderated for non-subscribers even if they have spam or virus checking. The sad part about moderation is that it is usually an additional burden on the relatively fewer developers who are more skilled rather than the relatively larger folks who requesting services who are less skilled. So it might be nice to have a box or flag for such a mailing list that allows anyone who is registered in the mailing list have the pleasure of doing email moderation. After all, what's needed here is someone to be able to detect spam from a legitimate post and most people are capable of doing that. I suppose this could be subject for abuse too (discard valid posts and accept spam), but I have a feeling that to first order approximaton this would be a big help. And doesn't mailman already have ways of watching users or moderators, and revoking moderation by the administrator or whatnot? Thanks for considering this. -- worn down developer/administrator of GPL projects ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1394592&group_id=103 From noreply at sourceforge.net Sun Jan 1 06:44:09 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 31 Dec 2005 21:44:09 -0800 Subject: [ mailman-Bugs-1394696 ] "ValueError: day of year out of range" on Dec 31? Message-ID: Bugs item #1394696, was opened at 2006-01-01 06:44 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=1394696&group_id=103 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: Open Resolution: None 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 at 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 at one /var/mailman]# time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range [root at one /var/mailman]# date Sat Dec 31 23:39:23 CST 2005 [root at one /var/mailman]# bin/version Using Mailman version: 2.1.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_id=103 From noreply at sourceforge.net Sun Jan 1 19:01:29 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 01 Jan 2006 10:01:29 -0800 Subject: [ mailman-Bugs-1394892 ] Unable to set default header filter (new style) Message-ID: Bugs item #1394892, was opened at 2006-01-01 19:01 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=1394892&group_id=103 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: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Magnus Danielson (magdan) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to set default header filter (new style) Initial Comment: As I am working on setting up a multilist/multidomain setup using Mailman 2.1.6, I encountered the need that I wanted to be able to set the default header filter rules so that the lists I create will all have the same basic rule (since we concluded we want one as default). It proved to be a fairly small hack, so I thought I contribute it to you. diff MailList.py.orig MailList.py 342c342,343 < self.header_filter_rules = [] --- > self.header_filter_rules = \ > mm_cfg.DEFAULT_HEADER_FILTER_RULES diff Defaults.py.orig Defaults.py 908a909,918 > # New style SPAM Privacy header filtering > # Mailman can match the patterns of header content and decide upon different > # actions (Defer, Hold, Reject Discard and Accept). These properties is > # configured per list, and here can the list default be set. > # A list of rules where each entry contains the matching string, the action > # code and an empty flag (set False). > # Example (discard mails marked by SpamAssassin): > #DEFAULT_HEADER_FILTER_RULES = [('X-Spam-Status: Yes', DISCARD, False)] > DEFAULT_HEADER_FILTER_RULES = [] > OK, it certainly could be cleaned up in the aspect of comments/documentation, but it should be the trivia part for you guys. It has been tested to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394892&group_id=103 From noreply at sourceforge.net Sun Jan 1 19:48:39 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 01 Jan 2006 10:48:39 -0800 Subject: [ mailman-Bugs-1394914 ] Unable to set default header filter (new style) Message-ID: Bugs item #1394914, was opened at 2006-01-01 19:48 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=1394914&group_id=103 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: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Magnus Danielson (magdan) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to set default header filter (new style) Initial Comment: As I am working on setting up a multilist/multidomain setup using Mailman 2.1.6, I encountered the need that I wanted to be able to set the default header filter rules so that the lists I create will all have the same basic rule (since we concluded we want one as default). It proved to be a fairly small hack, so I thought I contribute it to you. diff MailList.py.orig MailList.py 342c342,343 < self.header_filter_rules = [] --- > self.header_filter_rules = \ > mm_cfg.DEFAULT_HEADER_FILTER_RULES diff Defaults.py.orig Defaults.py 908a909,918 > # New style SPAM Privacy header filtering > # Mailman can match the patterns of header content and decide upon different > # actions (Defer, Hold, Reject Discard and Accept). These properties is > # configured per list, and here can the list default be set. > # A list of rules where each entry contains the matching string, the action > # code and an empty flag (set False). > # Example (discard mails marked by SpamAssassin): > #DEFAULT_HEADER_FILTER_RULES = [('X-Spam-Status: Yes', DISCARD, False)] > DEFAULT_HEADER_FILTER_RULES = [] > OK, it certainly could be cleaned up in the aspect of comments/documentation, but it should be the trivia part for you guys. It has been tested to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394914&group_id=103 From noreply at sourceforge.net Sun Jan 1 21:29:34 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 01 Jan 2006 12:29:34 -0800 Subject: [ mailman-Patches-1394949 ] held message expiration Message-ID: Patches item #1394949, was opened at 2006-01-01 15:29 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=1394949&group_id=103 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: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Robby Griffin (alierak) Assigned to: Nobody/Anonymous (nobody) Summary: held message expiration Initial Comment: This patch against 2.1.4 includes an enhanced version of bin/discard and a trivial shell script that rejects held messages older than 10 days, to keep moderator queues relatively clean and to let users know when the moderator is asleep at the wheel. Note that bin/checkdbs in newer versions of Mailman can already discard held messages according to the max_days_to_hold per-list config parameter. Changes to bin/discard include: - support for --approve, --reject, and --comment= for rejection comments (compare to patch #992621). - sane error handling when a specified held message belongs to a nonexistent / invalid listname It's advisable to schedule the expire-heldmsgs cron job to happen before daily admin reminders, so that moderators don't see lists of messages that are gone by the time they visit the admin page. If anyone wants to do further work in this area, they should probably look into extending the expiration capability of 2.1.7 to support approval / rejection with optional comment of expired held posts. I would also suggest that deleting a list should cause its held messages to be expired immediately. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1394949&group_id=103 From noreply at sourceforge.net Sun Jan 1 21:39:21 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 01 Jan 2006 12:39:21 -0800 Subject: [ mailman-Patches-1394949 ] held message expiration Message-ID: Patches item #1394949, was opened at 2006-01-01 15:29 Message generated for change (Comment added) made by alierak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1394949&group_id=103 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: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Robby Griffin (alierak) Assigned to: Nobody/Anonymous (nobody) Summary: held message expiration Initial Comment: This patch against 2.1.4 includes an enhanced version of bin/discard and a trivial shell script that rejects held messages older than 10 days, to keep moderator queues relatively clean and to let users know when the moderator is asleep at the wheel. Note that bin/checkdbs in newer versions of Mailman can already discard held messages according to the max_days_to_hold per-list config parameter. Changes to bin/discard include: - support for --approve, --reject, and --comment= for rejection comments (compare to patch #992621). - sane error handling when a specified held message belongs to a nonexistent / invalid listname It's advisable to schedule the expire-heldmsgs cron job to happen before daily admin reminders, so that moderators don't see lists of messages that are gone by the time they visit the admin page. If anyone wants to do further work in this area, they should probably look into extending the expiration capability of 2.1.7 to support approval / rejection with optional comment of expired held posts. I would also suggest that deleting a list should cause its held messages to be expired immediately. ---------------------------------------------------------------------- >Comment By: Robby Griffin (alierak) Date: 2006-01-01 15:39 Message: Logged In: YES user_id=83996 The discard patch applies equally well to 2.1.7, for what it's worth. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1394949&group_id=103 From noreply at sourceforge.net Mon Jan 2 22:34:41 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 02 Jan 2006 13:34:41 -0800 Subject: [ mailman-Feature Requests-1395591 ] Forced user setup adjustment notification Message-ID: Feature Requests item #1395591, was opened at 2006-01-02 22:34 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=1395591&group_id=103 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: STanda Opichal (opichals) Assigned to: Nobody/Anonymous (nobody) Summary: Forced user setup adjustment notification Initial Comment: Hi! For example when the user's email is bouncing frequently mailman switches the user profile to the 'disabled' state. The use has however no chance to get any notification about this happened. I would propose to allow use to specify another email address to be notified at when something was automatically chaged because of a problem found during operation. Best Regards Standa ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1395591&group_id=103 From noreply at sourceforge.net Tue Jan 3 02:12:54 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 02 Jan 2006 17:12:54 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: Bugs item #1395683, was opened at 2006-01-02 17:12 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=1395683&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) 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) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103 From noreply at sourceforge.net Tue Jan 3 02:54:27 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 02 Jan 2006 17:54:27 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) 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: Mark Sapiro (msapiro) Date: 2006-01-02 17: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_id=103 From noreply at sourceforge.net Tue Jan 3 06:21:17 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 02 Jan 2006 21:21:17 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) 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: Mark Sapiro (msapiro) Date: 2006-01-02 21: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-02 17: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_id=103 From noreply at sourceforge.net Tue Jan 3 18:28:48 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 03 Jan 2006 09:28:48 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) 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: Mark Sapiro (msapiro) Date: 2006-01-03 09: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-02 21: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-02 17: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_id=103 From noreply at sourceforge.net Tue Jan 3 19:20:06 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 03 Jan 2006 10:20:06 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) 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: Mark Sapiro (msapiro) Date: 2006-01-03 10: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 09: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-02 21: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-02 17: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_id=103 From noreply at sourceforge.net Wed Jan 4 21:53:02 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 04 Jan 2006 12:53:02 -0800 Subject: [ mailman-Bugs-1397214 ] Cron DeprecationWarning with Python 2.4 Message-ID: Bugs item #1397214, was opened at 2006-01-04 21:53 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=1397214&group_id=103 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: Schoinobates Volans (schoinobates) Assigned to: Nobody/Anonymous (nobody) Summary: Cron DeprecationWarning with Python 2.4 Initial Comment: This is Debian bug #341699: http://bugs.debian.org/341699 The cron script senddigests spews: DeprecationWarning: get_type() deprecated; use get_content_type() ctype = part.get_type(part.get_default_type()) Here's a patch that shuts up the warning, as you want to keep Python 2.1 compatibility (get_content_type() appeared in Python 2.2.2). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1397214&group_id=103 From noreply at sourceforge.net Thu Jan 5 03:50:29 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 04 Jan 2006 18:50:29 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: 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_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) 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-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_id=103 From noreply at sourceforge.net Thu Jan 5 08:35:38 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 04 Jan 2006 23:35:38 -0800 Subject: [ mailman-Patches-1365282 ] Add New Langauge Punjabi (pa) to mailman Message-ID: Patches item #1365282, was opened at 2005-11-24 05:19 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_id=103 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: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Amanpreet Singh Alam (aalam) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Add New Langauge Punjabi (pa) to mailman Initial Comment: Hello I translate mailman to Punajbi and Want to include in mailman. As per direction from Barry, I m attaching file here! following is info about Language "Punjabi" ISO Code = "pa" Coding = Unicode (UTF-8) Can u please include those files for Punjabi to Mailman? thanks AP Singh Alam http://punlinux.sf.net ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-05 07:35 Message: Logged In: YES user_id=67709 Sorry for the delayed response but what is your output from 'bin/transcheck pa' ? ---------------------------------------------------------------------- Comment By: Amanpreet Singh Alam (aalam) Date: 2005-11-28 05:45 Message: Logged In: YES user_id=1200839 I buid on Fedora and it was ready can u please help me to send the errors? thanks AP Singh ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-11-26 06:32 Message: Logged In: YES user_id=67709 Hi, I tested your translation and get error. Will you please test your translation by yourself before submitting to the patch tracker? You should add your language in templates/Makefile.in, messages/Makefile.in and Mailman/Defaults.py.in then do the configure/make install. bin/transcheck should help debugging. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_id=103 From noreply at sourceforge.net Thu Jan 5 16:34:08 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 05 Jan 2006 07:34:08 -0800 Subject: [ mailman-Bugs-1305881 ] Problem creating list via web Message-ID: Bugs item #1305881, was opened at 2005-09-27 08:49 Message generated for change (Comment added) made by echoism You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 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: Open Resolution: None Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) 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 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster at mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- Comment By: echoism (echoism) Date: 2006-01-05 10:34 Message: Logged In: YES user_id=1420107 I had this same problem. It is a permission issue, because the webserver doesn't have access to create a file in /usr/local/mailman/archives/private. This directory has permissions of 750, owned by the mailman user. The webserver, however, runs cgi scripts as nobody, not mailman. You can confirm this, by checking your /usr/local/mailman/lists directory, the list you tried to create should have a directory there, owned by nobody (or, whatever account your webserver uses), as the permissions for the lists directory permit write access. ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 09:44 Message: Logged In: YES user_id=1352490 #/usr/local/mailman>/usr/local/mailman/bin/check_perms No problems found #/usr/local/mailman> ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 09:32 Message: Logged In: YES user_id=1352490 Thanks but it doesn't still work. I have done: /usr/local/mailman/bin/check_perms -f and fixed all the problems, but it still doesn't work. :o( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-27 09:21 Message: Logged In: YES user_id=12800 Run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 From noreply at sourceforge.net Fri Jan 6 06:43:36 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 05 Jan 2006 21:43:36 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: Bugs item #1395683, was opened at 2006-01-02 17:12 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) 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: Mark Sapiro (msapiro) Date: 2006-01-05 21: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-04 18: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 10: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 09: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-02 21: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-02 17: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_id=103 From noreply at sourceforge.net Sat Jan 7 06:05:15 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 06 Jan 2006 21:05:15 -0800 Subject: [ mailman-Bugs-1399021 ] newlist creates archive placeholder with bad link Message-ID: Bugs item #1399021, was opened at 2006-01-06 22:05 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=1399021&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Crusoe (khedron) Assigned to: Nobody/Anonymous (nobody) Summary: newlist creates archive placeholder with bad link Initial Comment: The placeholder for the archive includes a bad link to the signup page. Example @: http://lopsa.org/pipermail/creationtest/ bad link: http://lopsa.org/cgi-bin/mailmanlistinfo/creationtest Presumed correct link: http://lopsa.org/cgi-bin/mailman/listinfo/creationtest Thanks for reviewing this bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1399021&group_id=103 From noreply at sourceforge.net Sat Jan 7 07:40:12 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 06 Jan 2006 22:40:12 -0800 Subject: [ mailman-Bugs-1399021 ] newlist creates archive placeholder with bad link Message-ID: Bugs item #1399021, was opened at 2006-01-06 21:05 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1399021&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Crusoe (khedron) Assigned to: Nobody/Anonymous (nobody) Summary: newlist creates archive placeholder with bad link Initial Comment: The placeholder for the archive includes a bad link to the signup page. Example @: http://lopsa.org/pipermail/creationtest/ bad link: http://lopsa.org/cgi-bin/mailmanlistinfo/creationtest Presumed correct link: http://lopsa.org/cgi-bin/mailman/listinfo/creationtest Thanks for reviewing this bug. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-06 22:40 Message: Logged In: YES user_id=1123998 It appears you have changed (overridden) DEFAULT_URL_PATTERN in mm_cfg.py and left off the trailing slash. You first need to fix that and then run fix_url to fix the existing lists. Run bin/fix_url.py for instructions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1399021&group_id=103 From noreply at sourceforge.net Sat Jan 7 08:33:59 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 06 Jan 2006 23:33:59 -0800 Subject: [ mailman-Patches-1399065 ] link in approval request emails directly to the held message Message-ID: Patches item #1399065, was opened at 2006-01-07 02:33 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=1399065&group_id=103 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: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Miller (justdave72) Assigned to: Nobody/Anonymous (nobody) Summary: link in approval request emails directly to the held message Initial Comment: The emails currently sent to a list moderator include a URL you can click to go visit the moderation queue. But it loads the entire queue. If you get a lot of spam, you probably have a habit of just ignoring the approval requests if they're spam. This can make the size of your queue pretty large after a while (even if you're using a cron job to expire old requests), and make it difficult to find the message you want to approve when you get one worth approving. Include in the email is an attached email with a 40-digit token which you can reply to and send a password in order to approve the message. Trying to remember a list password when I moderate 85 lists is nuts (that's what my browser's password autofill is for), and I don't like the idea of mailing my site password around in cleartext. The admindb interface on the Web UI already has the ability to display a single message (when you click the [1] or [2] in front of the subject line). So why not use it, and have the moderator approval request mails list link directly to that? This patch modifies admindb in the web interface to accept a confirmation token in the msgid parameter, in addition to the sequence ID within the queue. It decides which it got by checking the length (if it's 40 digits, it's a token), and if it's a token, it looks up the sequence number and feeds that to the existing single-message display code. It also modifies the held message handler to add the cookie to the variables passed to the message template, and modifies the postauth.txt template to add that cookie to the URL included in the email. With this patch applied, clicking the link in the email takes you to the single-message view in the request queue, where you can do what you want with just that message. I wrote this patch against 2.1.5 (that's what ships with RHEL4), but it appears to apply cleanly to 2.1.7 also. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1399065&group_id=103 From noreply at sourceforge.net Sat Jan 7 08:39:04 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 06 Jan 2006 23:39:04 -0800 Subject: [ mailman-Patches-1399065 ] link in approval request emails directly to the held message Message-ID: Patches item #1399065, was opened at 2006-01-07 02:33 Message generated for change (Comment added) made by justdave72 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1399065&group_id=103 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: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Miller (justdave72) Assigned to: Nobody/Anonymous (nobody) Summary: link in approval request emails directly to the held message Initial Comment: The emails currently sent to a list moderator include a URL you can click to go visit the moderation queue. But it loads the entire queue. If you get a lot of spam, you probably have a habit of just ignoring the approval requests if they're spam. This can make the size of your queue pretty large after a while (even if you're using a cron job to expire old requests), and make it difficult to find the message you want to approve when you get one worth approving. Include in the email is an attached email with a 40-digit token which you can reply to and send a password in order to approve the message. Trying to remember a list password when I moderate 85 lists is nuts (that's what my browser's password autofill is for), and I don't like the idea of mailing my site password around in cleartext. The admindb interface on the Web UI already has the ability to display a single message (when you click the [1] or [2] in front of the subject line). So why not use it, and have the moderator approval request mails list link directly to that? This patch modifies admindb in the web interface to accept a confirmation token in the msgid parameter, in addition to the sequence ID within the queue. It decides which it got by checking the length (if it's 40 digits, it's a token), and if it's a token, it looks up the sequence number and feeds that to the existing single-message display code. It also modifies the held message handler to add the cookie to the variables passed to the message template, and modifies the postauth.txt template to add that cookie to the URL included in the email. With this patch applied, clicking the link in the email takes you to the single-message view in the request queue, where you can do what you want with just that message. I wrote this patch against 2.1.5 (that's what ships with RHEL4), but it appears to apply cleanly to 2.1.7 also. ---------------------------------------------------------------------- >Comment By: David Miller (justdave72) Date: 2006-01-07 02:39 Message: Logged In: YES user_id=648592 Also of note, I only modified the English template... if you use other languages (or if this gets taken for a release) the same modification will need to be made to the postauth.txt template in the other language directories as well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1399065&group_id=103 From noreply at sourceforge.net Sat Jan 7 09:32:20 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 07 Jan 2006 00:32:20 -0800 Subject: [ mailman-Patches-1399065 ] link in approval request emails directly to the held message Message-ID: Patches item #1399065, was opened at 2006-01-07 02:33 Message generated for change (Comment added) made by justdave72 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1399065&group_id=103 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: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Miller (justdave72) Assigned to: Nobody/Anonymous (nobody) Summary: link in approval request emails directly to the held message Initial Comment: The emails currently sent to a list moderator include a URL you can click to go visit the moderation queue. But it loads the entire queue. If you get a lot of spam, you probably have a habit of just ignoring the approval requests if they're spam. This can make the size of your queue pretty large after a while (even if you're using a cron job to expire old requests), and make it difficult to find the message you want to approve when you get one worth approving. Include in the email is an attached email with a 40-digit token which you can reply to and send a password in order to approve the message. Trying to remember a list password when I moderate 85 lists is nuts (that's what my browser's password autofill is for), and I don't like the idea of mailing my site password around in cleartext. The admindb interface on the Web UI already has the ability to display a single message (when you click the [1] or [2] in front of the subject line). So why not use it, and have the moderator approval request mails list link directly to that? This patch modifies admindb in the web interface to accept a confirmation token in the msgid parameter, in addition to the sequence ID within the queue. It decides which it got by checking the length (if it's 40 digits, it's a token), and if it's a token, it looks up the sequence number and feeds that to the existing single-message display code. It also modifies the held message handler to add the cookie to the variables passed to the message template, and modifies the postauth.txt template to add that cookie to the URL included in the email. With this patch applied, clicking the link in the email takes you to the single-message view in the request queue, where you can do what you want with just that message. I wrote this patch against 2.1.5 (that's what ships with RHEL4), but it appears to apply cleanly to 2.1.7 also. ---------------------------------------------------------------------- >Comment By: David Miller (justdave72) Date: 2006-01-07 03:32 Message: Logged In: YES user_id=648592 OK, after discussion on IRC, I've modified the patch a bit... In order to avoid modifying localized templates, it now modifies the admindb_url variable before passing it to the template. Also cleaned up some leftover debugging messages. ---------------------------------------------------------------------- Comment By: David Miller (justdave72) Date: 2006-01-07 02:39 Message: Logged In: YES user_id=648592 Also of note, I only modified the English template... if you use other languages (or if this gets taken for a release) the same modification will need to be made to the postauth.txt template in the other language directories as well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1399065&group_id=103 From noreply at sourceforge.net Mon Jan 9 07:13:31 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 08 Jan 2006 22:13:31 -0800 Subject: [ mailman-Bugs-1400128 ] edithtml.py missing import Message-ID: Bugs item #1400128, was opened at 2006-01-08 22:13 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=1400128&group_id=103 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: Cliff Wells (cliffwells18) Assigned to: Nobody/Anonymous (nobody) Summary: edithtml.py missing import Initial Comment: You can't save edited pages because edithtml.py fails to import the re module. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1400128&group_id=103 From noreply at sourceforge.net Mon Jan 9 07:50:14 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 08 Jan 2006 22:50:14 -0800 Subject: [ mailman-Bugs-1400128 ] edithtml.py missing import Message-ID: 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_id=103 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: Cliff Wells (cliffwells18) Assigned to: Nobody/Anonymous (nobody) 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-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_id=103 From noreply at sourceforge.net Mon Jan 9 08:41:20 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 08 Jan 2006 23:41:20 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: 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_id=103 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: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Michael Wallis (kf6spf) Assigned to: Nobody/Anonymous (nobody) 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-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_id=103 From noreply at sourceforge.net Mon Jan 9 08:44:40 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 08 Jan 2006 23:44:40 -0800 Subject: [ mailman-Bugs-1400128 ] edithtml.py missing import Message-ID: 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_id=103 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: Closed >Resolution: Fixed Priority: 5 Submitted By: Cliff Wells (cliffwells18) Assigned to: Nobody/Anonymous (nobody) 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-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_id=103 From noreply at sourceforge.net Tue Jan 10 07:08:07 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 09 Jan 2006 22:08:07 -0800 Subject: [ mailman-Bugs-1399021 ] newlist creates archive placeholder with bad link Message-ID: Bugs item #1399021, was opened at 2006-01-06 22:05 Message generated for change (Comment added) made by khedron You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1399021&group_id=103 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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Crusoe (khedron) Assigned to: Nobody/Anonymous (nobody) Summary: newlist creates archive placeholder with bad link Initial Comment: The placeholder for the archive includes a bad link to the signup page. Example @: http://lopsa.org/pipermail/creationtest/ bad link: http://lopsa.org/cgi-bin/mailmanlistinfo/creationtest Presumed correct link: http://lopsa.org/cgi-bin/mailman/listinfo/creationtest Thanks for reviewing this bug. ---------------------------------------------------------------------- >Comment By: Michael Crusoe (khedron) Date: 2006-01-09 23:08 Message: Logged In: YES user_id=59618 Thanks for the response! It appears that this was the default from Debian. /usr/share/docs/mailman/examples/mm_cfg.py contains the line: DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman' I used the bin/fix_url.py program, but that doesn't regenerate the static HTML in the archive. I'm having a hard time finding documentation for pipermail. Any more pointers? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-06 23:40 Message: Logged In: YES user_id=1123998 It appears you have changed (overridden) DEFAULT_URL_PATTERN in mm_cfg.py and left off the trailing slash. You first need to fix that and then run fix_url to fix the existing lists. Run bin/fix_url.py for instructions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1399021&group_id=103 From noreply at sourceforge.net Tue Jan 10 13:54:18 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Jan 2006 04:54:18 -0800 Subject: [ mailman-Bugs-1399021 ] newlist creates archive placeholder with bad link Message-ID: Bugs item #1399021, was opened at 2006-01-07 00:05 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1399021&group_id=103 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: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Michael Crusoe (khedron) Assigned to: Nobody/Anonymous (nobody) Summary: newlist creates archive placeholder with bad link Initial Comment: The placeholder for the archive includes a bad link to the signup page. Example @: http://lopsa.org/pipermail/creationtest/ bad link: http://lopsa.org/cgi-bin/mailmanlistinfo/creationtest Presumed correct link: http://lopsa.org/cgi-bin/mailman/listinfo/creationtest Thanks for reviewing this bug. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-01-10 07:54 Message: Logged In: YES user_id=12800 Use the bin/arch program to regenerate the archives. ---------------------------------------------------------------------- Comment By: Michael Crusoe (khedron) Date: 2006-01-10 01:08 Message: Logged In: YES user_id=59618 Thanks for the response! It appears that this was the default from Debian. /usr/share/docs/mailman/examples/mm_cfg.py contains the line: DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman' I used the bin/fix_url.py program, but that doesn't regenerate the static HTML in the archive. I'm having a hard time finding documentation for pipermail. Any more pointers? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-07 01:40 Message: Logged In: YES user_id=1123998 It appears you have changed (overridden) DEFAULT_URL_PATTERN in mm_cfg.py and left off the trailing slash. You first need to fix that and then run fix_url to fix the existing lists. Run bin/fix_url.py for instructions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1399021&group_id=103 From noreply at sourceforge.net Tue Jan 10 22:31:52 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Jan 2006 13:31:52 -0800 Subject: [ mailman-Bugs-1400128 ] edithtml.py missing import Message-ID: Bugs item #1400128, was opened at 2006-01-09 06:13 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1400128&group_id=103 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: Open 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-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_id=103 From noreply at sourceforge.net Tue Jan 10 22:34:16 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Jan 2006 13:34:16 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: Bugs item #1395683, was opened at 2006-01-03 01:12 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103 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: Open 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-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_id=103 From noreply at sourceforge.net Tue Jan 10 22:37:46 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Jan 2006 13:37:46 -0800 Subject: [ mailman-Bugs-1394696 ] "ValueError: day of year out of range" on Dec 31? Message-ID: Bugs item #1394696, was opened at 2006-01-01 05:44 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_id=103 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: Open >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 at 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 at one /var/mailman]# time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range [root at one /var/mailman]# date Sat Dec 31 23:39:23 CST 2005 [root at one /var/mailman]# bin/version Using Mailman version: 2.1.4 ---------------------------------------------------------------------- >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_id=103 From noreply at sourceforge.net Wed Jan 11 03:49:41 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Jan 2006 18:49:41 -0800 Subject: [ mailman-Bugs-1400128 ] edithtml.py missing import Message-ID: Bugs item #1400128, was opened at 2006-01-09 01:13 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1400128&group_id=103 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: Open 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: Barry A. Warsaw (bwarsaw) Date: 2006-01-10 21: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 16: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 02:44 Message: Logged In: YES user_id=67709 It was fixed it in the CVS. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-09 01: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_id=103 From noreply at sourceforge.net Wed Jan 11 04:37:35 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Jan 2006 19:37:35 -0800 Subject: [ mailman-Bugs-1394696 ] "ValueError: day of year out of range" on Dec 31? Message-ID: Bugs item #1394696, was opened at 2006-01-01 00:44 Message generated for change (Comment added) made by n8wilson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_id=103 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: Open 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 at 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 at one /var/mailman]# time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range [root at one /var/mailman]# date Sat Dec 31 23:39:23 CST 2005 [root at one /var/mailman]# bin/version Using Mailman version: 2.1.4 ---------------------------------------------------------------------- Comment By: Nate (n8wilson) Date: 2006-01-10 22: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 at 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 at gttx nwilson]# exit exit [nwilson at gttx ~]$ date Tue Jan 10 22:35:01 EST 2006 You have new mail in /var/spool/mail/nwilson [nwilson at gttx ~]$ /usr/lib/mailman/bin/version Using Mailman version: 2.1.5 [nwilson at gttx ~]$ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-10 16: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_id=103 From noreply at sourceforge.net Wed Jan 11 05:33:24 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Jan 2006 20:33:24 -0800 Subject: [ mailman-Bugs-1394696 ] "ValueError: day of year out of range" on Dec 31? Message-ID: Bugs item #1394696, was opened at 2005-12-31 21:44 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_id=103 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: Open 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 at 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 at one /var/mailman]# time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range [root at one /var/mailman]# date Sat Dec 31 23:39:23 CST 2005 [root at one /var/mailman]# bin/version Using Mailman version: 2.1.4 ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-10 20: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 And yes, disabling bounce processing will avoid the error. ---------------------------------------------------------------------- Comment By: Nate (n8wilson) Date: 2006-01-10 19: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 at 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 at gttx nwilson]# exit exit [nwilson at gttx ~]$ date Tue Jan 10 22:35:01 EST 2006 You have new mail in /var/spool/mail/nwilson [nwilson at gttx ~]$ /usr/lib/mailman/bin/version Using Mailman version: 2.1.5 [nwilson at gttx ~]$ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-01-10 13: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_id=103 From noreply at sourceforge.net Wed Jan 11 05:58:06 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Jan 2006 20:58:06 -0800 Subject: [ mailman-Bugs-1194419 ] Lose Topics when go directly to topics URL Message-ID: Bugs item #1194419, was opened at 2005-05-03 22:29 Message generated for change (Comment added) made by zenzen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1194419&group_id=103 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: Open Resolution: None 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/) 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: Stuart Bishop (zenzen) Date: 2006-01-11 15: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_id=103 From noreply at sourceforge.net Sat Jan 14 04:41:40 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 13 Jan 2006 19:41:40 -0800 Subject: [ mailman-Bugs-1194419 ] Lose Topics when go directly to topics URL Message-ID: Bugs item #1194419, was opened at 2005-05-03 05:29 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1194419&group_id=103 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: Open Resolution: None 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/) 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: Mark Sapiro (msapiro) Date: 2006-01-13 19: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-10 20: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_id=103 From noreply at sourceforge.net Sat Jan 14 14:07:25 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 14 Jan 2006 05:07:25 -0800 Subject: [ mailman-Patches-1405790 ] Mailman 2.1.7 multiple patch Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Sat Jan 14 14:10:28 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 14 Jan 2006 05:10:28 -0800 Subject: [ mailman-Bugs-1400128 ] edithtml.py missing import Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Sat Jan 14 14:11:56 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 14 Jan 2006 05:11:56 -0800 Subject: [ mailman-Bugs-1395683 ] UnicodeError running arch Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Sat Jan 14 14:16:36 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 14 Jan 2006 05:16:36 -0800 Subject: [ mailman-Bugs-1194419 ] Lose Topics when go directly to topics URL Message-ID: 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_id=103 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/) 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_id=103 From noreply at sourceforge.net Sat Jan 14 14:20:40 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 14 Jan 2006 05:20:40 -0800 Subject: [ mailman-Bugs-1394696 ] "ValueError: day of year out of range" on Dec 31? Message-ID: 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_id=103 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 at 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 at one /var/mailman]# time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range [root at one /var/mailman]# date Sat Dec 31 23:39:23 CST 2005 [root at 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 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 at 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 at gttx nwilson]# exit exit [nwilson at gttx ~]$ date Tue Jan 10 22:35:01 EST 2006 You have new mail in /var/spool/mail/nwilson [nwilson at gttx ~]$ /usr/lib/mailman/bin/version Using Mailman version: 2.1.5 [nwilson at 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_id=103 From noreply at sourceforge.net Mon Jan 16 20:08:01 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 16 Jan 2006 11:08:01 -0800 Subject: [ mailman-Bugs-1152800 ] Footer is Added in Plaintext to baes64 encoded mails Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Mon Jan 16 20:09:06 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 16 Jan 2006 11:09:06 -0800 Subject: [ mailman-Bugs-1218827 ] please do not put the list footer in attachment if possible Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Tue Jan 17 20:56:43 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Jan 2006 11:56:43 -0800 Subject: [ mailman-Bugs-1408435 ] Build python extensions when building mailman, not install Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Tue Jan 17 23:59:28 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Jan 2006 14:59:28 -0800 Subject: [ mailman-Patches-1408586 ] localize Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Wed Jan 18 08:22:54 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Jan 2006 23:22:54 -0800 Subject: [ mailman-Bugs-1408801 ] mail with special characters not archived on pipermail Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Wed Jan 18 16:10:19 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 18 Jan 2006 07:10:19 -0800 Subject: [ mailman-Bugs-1408801 ] mail with special characters not archived on pipermail Message-ID: Bugs item #1408801, was opened at 2006-01-17 23:22 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1408801&group_id=103 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 ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-18 07:10 Message: Logged In: YES user_id=1123998 There is a bug in this area in the 2.1.7 release, but it will log an error and shunt the message (1395683) I suggest you get the 2.1.7 final release and apply the cumulative patch (1405790) or update to the latest CVS and see if the problem still exists. Also note that if it is bug 1395683, an htmlized message would have been created at archives/private/LIST_NAME/yyyy-Month/nnnnnn.html, but it would not be linked from any of the html index files. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1408801&group_id=103 From noreply at sourceforge.net Thu Jan 19 20:32:48 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 19 Jan 2006 11:32:48 -0800 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 13:17 Message generated for change (Comment added) made by ssrjazz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 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: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 9 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Jeff Schoby (ssrjazz) Date: 2006-01-19 13:32 Message: Logged In: YES user_id=198250 Does anyone have any idea why when I run ~mailman/bin/arch it will generate the rss.xml file, but when new emails come in to said list it doesn't do ANYTHING with the xml file? I'd like for the rss feed to update itself every time a new post comes into a list. Right now it isn't doing that. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-12-06 12:01 Message: Logged In: YES user_id=75166 The following is based on the July 2003 version of the patch file posted on sourceforge. The RSS patch adds the RSS() function as member function of the HyperArchive class defined in HyperArch.py. It has been reported that the following statement in RSS(): date, msgid = self.database.dateIndex.first() may generate an AttributeError exception: AttributeError: HyperDatabase instance has no attribute 'dateIndex' The RSS patch appears to make the assumption that whenever the RSS() function is called from the write_TOC() member function of the HyperArchive class the __openIndices() function has already been called on the latest period archive associated with the list, whose TOC page is being generated by write_TOC(), and that no intervening call to __closeIndices() has been made. If the assumption were correct then whenever the RSS() function was called on a HyperArchive instance, the xxxxxIndices attributes of the HyperDatabase instance "owned" by the HyperArchive instance would be pointing to valid instance of DumbBTree. Unfortunately, this assumption is not correct. In order to do its work, write_TOC() does not itself need to perform any call to the __openIndices() function for the list/archive/database whose TOC page is to be recreated. It just happens that in some circumstances, some of the code which might call write_TOC may have called the __openIndices() function at some prior point and left the HyperDatabase instance with a valid set of xxxxxIndices attributes in place when write_TOC() is called. For the RSS patch to be work reliably the code in the RSS() function has to be changed so that it ensures that the conditions it wants prevail when it executes the statement giving the problem. The following is an untested code change but if part of the RSS() function's code definition in HyperArch.py is modified from: # Get the most recent messages. The only index operation # we can count on is traversal by increasing date, so # we end up traversing all of the entries and remembering the last # N of them. Sigh. items = [] try: date, msgid = self.database.dateIndex.first() items.append(msgid) except KeyError: pass while 1: try: to read: # Get the most recent messages. The only index operation # we can count on is traversal by increasing date, so # we end up traversing all of the entries and remembering the last # N of them. Sigh. items = [] got_first = 0 try: msgid = self.database.first(self.archives[0], 'date') if msgid: items.append(msgid) got_first = 1 except KeyError: pass while got_first and 1: try: this should fix the exception problem. ---------------------------------------------------------------------- Comment By: Roy M. Silvernail (codewhacker) Date: 2003-12-23 13:35 Message: Logged In: YES user_id=670974 I'm trying to enrich the RSS output by adding a proper [description] and a [content:encoded] module, but I am having the devil's own time locating the raw message text. Be happy to contribute a patch if you can point me to the raw content (without the italics markup for quoting). Thanks! ---------------------------------------------------------------------- Comment By: Michael Weber (wookiew) Date: 2003-09-10 11:29 Message: Logged In: YES user_id=863445 So far the patch is included (by the way: i hope that Defaults.py.in in the patch *means* Defaults.py ) and mailman get a restart. Hopefully i add the two lines in listinfo.html ( /de/ because we have german speaking lists) and take a look for the xml file). After search the whole device (only to be sure) i can say: There is no file like this. Is another patch need before? Another setup to make? I cant find any hint here... so i have to ask. But the idea is great... if it work on my lists its genious... regards, Michael running version 2.1.1 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-01 23:15 Message: Logged In: YES user_id=12800 Bumping priority. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 13:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 20:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 19:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 10:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan <danbri at w3.org> ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 06:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 06:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 17:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 15:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 19:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 13:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 13:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 13:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Sat Jan 21 20:23:13 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 21 Jan 2006 11:23:13 -0800 Subject: [ mailman-Bugs-1411656 ] 2.1.7 not available from gnu or list.org Message-ID: Bugs item #1411656, was opened at 2006-01-21 19:23 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=1411656&group_id=103 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: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.7 not available from gnu or list.org Initial Comment: list.org/download.html has links to retrieve the latest release from "GNU" and "list.org", but neither of these are up to date. ftp.gnu.org has only 2.1.5, and the list.org mailman.tar.gz unpacked into 2.1.6. Best, Karl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1411656&group_id=103 From noreply at sourceforge.net Thu Jan 26 02:55:05 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 25 Jan 2006 17:55:05 -0800 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 20:14 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 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: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- >Comment By: Brad Knowles (shub) Date: 2006-01-26 01:55 Message: Logged In: YES user_id=18417 Folks, Okay, I just uploaded version 0.0.15, which addresses the most recent comments here from Mark and Tom, and makes a few additional tweaks as well. See the version comments at the top of the script. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-06 18:25 Message: Logged In: YES user_id=1123998 The vette log summary lists posts held for moderation individually under "Other Errors:". The following patch (watch out for wrapped lines) summarizes them by list instead. --- mmdsr 2005-09-29 21:31:33.000000000 -0700 +++ mmdsrx 2005-11-06 08:20:58.835895418 -0800 @@ -415,10 +415,15 @@ echo "------------------------------" >> $TMP $GREP -i 'Posting to a moderated newsgroup' $TMPLOG | $AWK '{ print $6 }' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + echo "" >> $TMP + echo "Post to moderated list (by list):" >> $TMP + echo "------------------------------" >> $TMP + $GREP -i 'Post to moderated list' $TMPLOG | $AWK '{ print $6 }' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + echo "" >> $TMP echo "Other Errors:" >> $TMP echo "------------------------------" >> $TMP - $EGREP -vi '(Post by non-member|suspicious header|message approved|Discarded posting|bulk message discarded|junk message discarded|Message has implicit destination|Posting to a moderated newsgroup|Message discarded, msgid)' $TMPLOG | $SED 's/^.* ([0-9]*) //' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + $EGREP -vi '(Post by non-member|suspicious header|message approved|Discarded posting|bulk message discarded|junk message discarded|Message has implicit destination|Posting to a moderated newsgroup|Post to moderated list|Message discarded, msgid)' $TMPLOG | $SED 's/^.* ([0-9]*) //' | $SORT | $UNIQ -c | $SORT -nr >> $TMP else ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-10-19 08:23 Message: Logged In: YES user_id=1159458 ps output on solaris is full of whitespace but a further echo get's rid of it. The lines in the smtp log are sometimes broken up by a newline (right before the msgid) which throws of the summary. Piping it through sed first will rejoin the broken lines. Use $AWK instead of awk. Patch inserted below: --- mmdsr.orig 2005-10-19 09:42:30.000000000 +0200 +++ mmdsr 2005-10-19 09:44:23.000000000 +0200 @@ -203,7 +203,8 @@ # there is an easier cross-platform way to do it, please let me know. ############################################################################### -MYUID=`$PS -o user -p $$ | $TAIL -1` +GRABUID=`$PS -o user -p $$ | $TAIL -1` +MYUID=`echo $GRABUID` RUNAS="mailman" ############################################################################### @@ -254,7 +255,7 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG + $SED -e :a -e '$!N;s/\n //;ta' -e 'P;D' $LOGDIR/$LOG | $GREP -si "^$DAY [0-9][0-9:]* $YEAR" >> $TMPLOG if [ -f "$LOGDIR/${LOG}" ] ; then @@ -264,7 +265,7 @@ echo "Hourly Summary of Posts" >> $TMP echo "-----------------------" >> $TMP - $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.*$//' $TMPLOG | $UNIQ -c | $SORT -n +1 | awk '{ printf( "%8d %02d:00-%02d :59\n", $1, $2, $2 ) }' >> $TMP + $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.*$//' $TMPLOG | $UNIQ -c | $SORT -n +1 | $AWK '{ printf( "%8d %02d:00-%02 d:59\n", $1, $2, $2 ) }' >> $TMP echo "" >> $TMP echo "Post Count by List" >> $TMP @@ -295,7 +296,7 @@ echo "" >> $TMP echo "Hourly Summary of Messages Sent" >> $TMP echo "-------------------------------" >> $TMP - $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.* for / /' -e 's/ recips,.*$//' $TMPLOG | awk '{ val=int($1); sum[val]+=$2 } END { for (i=0; i<24; i++) { printf "%8d %02d:00-%02d:59\n", sum[i], i, i } }' >> $TMP + $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.* for / /' -e 's/ recips,.*$//' $TMPLOG | $AWK '{ val=int($1); sum[val]+=$ 2 } END { for (i=0; i<24; i++) { printf "%8d %02d:00-%02d:59\n", sum[i], i, i } }' >> $TMP else ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-22 23:17 Message: Logged In: YES user_id=18417 Okay, I took Mark's comments and incorporated them. Adrian Wells also pointed out a log file difference between Mailman 2.1.5 and 2.1.6 that caused the summary of the "smtp" log to be munged. I've now fixed these bugs, deleted the old file, and uploaded the new one (version 0.0.12). Thanks! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-11 02:22 Message: Logged In: YES user_id=1123998 Oooops! I mistakenly thought I could add the mmdsr.patch as a downloadable file, but I can't so here it is. Watch out for wrapped lines ... --- mmdsr.orig 2005-09-06 20:37:53.000000000 -0700 +++ mmdsr 2005-09-10 18:33:14.532393572 -0700 @@ -132,6 +132,7 @@ MMDIR="/usr/local/mailman" TMPDIR="/tmp" +LOGDIR="/var/log/mailman" ############################################################################### # Maximum number of subdirectory entries to display in report @@ -234,9 +235,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "post" ] ; then @@ -304,9 +305,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "error" ] ; then @@ -453,4 +454,4 @@ $CAT $TMP fi -$RM $TMP +$RM -f $TMP $TMPLOG ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-11 02:16 Message: Logged In: YES user_id=1123998 I tried the script and other than the expected site specific changes, I found two issues which are both addressed by the patch in the mmdsr.patch file. 1) Mailman's log files are not necessarily in $var_prefix/logs/ - they can be in any directory. The patch adds a LOGDIR directory independant of MMDIR. 2) The $TMPLOG file is not removed at completion. The patch removes it. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-06 14:06 Message: Logged In: YES user_id=18417 Okay, I've deleted the old version of the mmdsr script that was attached, and uploaded the latest version. This is what we're currently using to monitor the lists on python.org, and we have found it very useful. Any comments you may have will be appreciated. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-02-22 20:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 15:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 08:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Thu Jan 26 12:37:43 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 26 Jan 2006 03:37:43 -0800 Subject: [ mailman-Feature Requests-1182014 ] forum like interface to mailman Message-ID: Feature Requests item #1182014, was opened at 2005-04-12 22:40 Message generated for change (Comment added) made by mapopa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1182014&group_id=103 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: mariuz (mapopa) Assigned to: Nobody/Anonymous (nobody) Summary: forum like interface to mailman Initial Comment: one long term item would be creating an forum like interface for archives / mail The idea came to me after some users on mono list requested a forum for mono http://lists.ximian.com/mailman/listinfo/mono-list the basic forum interface (there are many others) http://www.gotmono.com/cgi-bin/yabb/YaBB.pl?board=ASPX ---------------------------------------------------------------------- >Comment By: mariuz (mapopa) Date: 2006-01-26 02:37 Message: Logged In: YES user_id=85089 Arioch /BDV/ wrote to me an email "I do not have my SF's password here, so i cannot comment ont bug-tracker yet. Can i ask You to add the following links tou You feature request ? F.Req: http://sourceforge.net/tracker/index.php?func=detail&aid=1182014&group_id=103&atid=350103 1) www.FudForum.org - PHP-based WWW-forum, who claims of a feature to be a front-end for nntp and maillist's 2) http://comments.gmane.org/gmane.discuss/7911 This is my long-standing dream, it was even registered on SourceForge's bug-tracker. Alas, later removed. Perhaps this can be achived using "external membership sources", but other from root page of mailman.sf.net i could not find any reference|description what it is. If it ws implemented, i guess Mailman, Sourceforge and Gmane were in benefit all :) " ---------------------------------------------------------------------- Comment By: mariuz (mapopa) Date: 2005-08-30 00:24 Message: Logged In: YES user_id=85089 On ubuntuforums.org they have two way between mailman and vbulletin Here is the example http://ubuntuforums.org/showthread.php?t=60843 ---------------------------------------------------------------------- Comment By: Fred H Olson (fholson) Date: 2005-08-24 00:57 Message: Logged In: YES user_id=1334022 There is an open source development project similar to this: GroupServer is a GPL open source collaboration server. It supports many-to-many interaction in groups and communities via email and an integrated web forum interface. See http://groupserver.org/ How much do mailman and groupserver developers communicate? Has collaboration of some sort been considered? Fred Olson http://justcomm.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1182014&group_id=103 From noreply at sourceforge.net Fri Jan 27 04:23:28 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 26 Jan 2006 19:23:28 -0800 Subject: [ mailman-Patches-1415956 ] Sitewide headers/footers & XHTML Compliant Web UI Message-ID: Patches item #1415956, was opened at 2006-01-26 22:23 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=1415956&group_id=103 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 UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: Sitewide headers/footers & XHTML Compliant Web UI Initial Comment: This patch was borne out of a request I received to make the Mailman UI fit the look of the web site. This patch allows you to set a site wide header and footer. This allows you to pretty much make the MM UI look like any other site. While I was at it I also made the web UI XHTML compliant. Once you patch your source and install it, all you need to do is edit the html files in the templates/en directory. Most of the pages will get the header and footers from the site-header.html and site-footer.html files, but some of the HTML files already contain theor own header/footer so you will need ot edit some of these files as well. Since this also adds XHTML compliance, this superceeds patch #116035 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_id=103 From noreply at sourceforge.net Fri Jan 27 04:27:36 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 26 Jan 2006 19:27:36 -0800 Subject: [ mailman-Patches-1415956 ] Sitewide headers/footers & XHTML Compliant Web UI Message-ID: Patches item #1415956, was opened at 2006-01-26 22:23 Message generated for change (Comment added) made by carbonnb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_id=103 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 UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: Sitewide headers/footers & XHTML Compliant Web UI Initial Comment: This patch was borne out of a request I received to make the Mailman UI fit the look of the web site. This patch allows you to set a site wide header and footer. This allows you to pretty much make the MM UI look like any other site. While I was at it I also made the web UI XHTML compliant. Once you patch your source and install it, all you need to do is edit the html files in the templates/en directory. Most of the pages will get the header and footers from the site-header.html and site-footer.html files, but some of the HTML files already contain theor own header/footer so you will need ot edit some of these files as well. Since this also adds XHTML compliance, this superceeds patch #116035 ---------------------------------------------------------------------- >Comment By: Bryan Carbonnell (carbonnb) Date: 2006-01-26 22:27 Message: Logged In: YES user_id=449953 I have only tested this with the english pages. I'm not sure how to deal with i18n yet, but I'm reading and I will update this patch as soon as I figure out how to deal with it. To apply this patch for MM2.1.7, you will need to apply patch #1405790 (Mailman 2.1.7 multiple patch) first. to apply this patch use this command from your mailman source directory: patch -p1 Patches item #1415956, was opened at 2006-01-26 22:23 Message generated for change (Comment added) made by carbonnb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_id=103 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 UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: Sitewide headers/footers & XHTML Compliant Web UI Initial Comment: This patch was borne out of a request I received to make the Mailman UI fit the look of the web site. This patch allows you to set a site wide header and footer. This allows you to pretty much make the MM UI look like any other site. While I was at it I also made the web UI XHTML compliant. Once you patch your source and install it, all you need to do is edit the html files in the templates/en directory. Most of the pages will get the header and footers from the site-header.html and site-footer.html files, but some of the HTML files already contain theor own header/footer so you will need ot edit some of these files as well. Since this also adds XHTML compliance, this superceeds patch #116035 ---------------------------------------------------------------------- >Comment By: Bryan Carbonnell (carbonnb) Date: 2006-01-26 22:31 Message: Logged In: YES user_id=449953 I am also uploading a second version of this patch. This second version will add the sitewide headers/footer to source that has been patched with the ht://dig integration patches. At the time I posted this, the official ht://dig integration patches were not released, but the MM2.1.6 patches appear to work with MM 2.1.7, so they are what were used. to apply this patch use this command from your mailman source directory: patch -p1 Patches item #1415961, was opened at 2006-01-26 22:41 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=1415961&group_id=103 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: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: List bandwidth monitor Initial Comment: I needed a way to monitor the bandwidth usage for a specific list that I administer. Since there is no way in mailman to do this, I wrote a Python script to parse the POST log and take the size of the posts to a specific list and then multiply that by the number of active subscribers at the time this script was run. This gets the "stats" from the day before the script is run. These stats are only approximates, since digest users are counted as receiving the mail on the day that it was sent, even though it may not have. There are some constants at the top of the file that you will need to modify to uit your installation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415961&group_id=103 From noreply at sourceforge.net Fri Jan 27 11:12:45 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 27 Jan 2006 02:12:45 -0800 Subject: [ mailman-Bugs-1305881 ] Problem creating list via web Message-ID: Bugs item #1305881, was opened at 2005-09-27 15:49 Message generated for change (Comment added) made by jontek You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 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: Open Resolution: None Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) 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 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster at mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- >Comment By: Jon (jontek) Date: 2006-01-27 11:12 Message: Logged In: YES user_id=1352490 Well, all the perms in both directories are mailman:mailman I have been create (check_perms says "all OK" but it isn't) the three directories: 1. #/usr/local/mailman/lists>mkdir listname 2. #/usr/local/mailman/archives/private>mkdir listname 3. #/usr/local/mailman/archives/private>mkdir listname.mbox 4. chown www (to the three) Will I change the directory owner to www? May that destroy or corrupt other lists? Thank you again. JOn ---------------------------------------------------------------------- Comment By: echoism (echoism) Date: 2006-01-05 16:34 Message: Logged In: YES user_id=1420107 I had this same problem. It is a permission issue, because the webserver doesn't have access to create a file in /usr/local/mailman/archives/private. This directory has permissions of 750, owned by the mailman user. The webserver, however, runs cgi scripts as nobody, not mailman. You can confirm this, by checking your /usr/local/mailman/lists directory, the list you tried to create should have a directory there, owned by nobody (or, whatever account your webserver uses), as the permissions for the lists directory permit write access. ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 16:44 Message: Logged In: YES user_id=1352490 #/usr/local/mailman>/usr/local/mailman/bin/check_perms No problems found #/usr/local/mailman> ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 16:32 Message: Logged In: YES user_id=1352490 Thanks but it doesn't still work. I have done: /usr/local/mailman/bin/check_perms -f and fixed all the problems, but it still doesn't work. :o( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-27 16:21 Message: Logged In: YES user_id=12800 Run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 From noreply at sourceforge.net Fri Jan 27 21:05:41 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 27 Jan 2006 12:05:41 -0800 Subject: [ mailman-Bugs-1416853 ] Jan 14 change to Handlers/SpamDetect.py is incomplete Message-ID: Bugs item #1416853, was opened at 2006-01-27 15:05 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=1416853&group_id=103 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: security/privacy Group: None Status: Open Resolution: None Priority: 5 Submitted By: Dan Astoorian (djast) Assigned to: Nobody/Anonymous (nobody) Summary: Jan 14 change to Handlers/SpamDetect.py is incomplete Initial Comment: tkikuchi's patch to Handlers/SpamDetect.py to avoid an infinite loop when administrivia messages are caught by spam filters fails to fix a related problem; a different approach should perhaps be considered. Specifically: it is (IMHO) probably incorrect to apply the "Hold" action to messages which were not submitted to the list address. For example, a message sent to "listname-owner" and matched by a "Hold" header_filter_rule should not be held for approval (irrespective of whether the message was administrivia or not). (It is not clear to the end user whether approving such a held message would cause the message to be delivered to the original "listname-owner" address, or whether it would be sent to the list itself.) I suspect (but have not verified) that similar issues may exist for other mail paths (e.g., -request, -admin, -(un)subscribe). Probably the most sensible thing to do with messages that match a "Hold" rule would be to hold the message only if the "tolist" key is set; otherwise, do one of the following: a) continue on to the next rule, as though the "Hold" rule failed to match the message; b) accept the message; or c) discard the message. It's not clear to me which of these options makes the most sense. Discarding the message is probably unwise, as a "hold" rule in the first place suggests that the administrator does not consider all mail that matches the rule to be expendable. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1416853&group_id=103 From noreply at sourceforge.net Sun Jan 29 00:56:54 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 28 Jan 2006 15:56:54 -0800 Subject: [ mailman-Bugs-1417678 ] Dutch translation wrong Message-ID: Bugs item #1417678, was opened at 2006-01-28 23: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=1417678&group_id=103 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: (un)subscribing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Koen Martens (gmc2000) Assigned to: Nobody/Anonymous (nobody) Summary: Dutch translation wrong Initial Comment: On some versions i've seen 'Uw bent' in the dutch translation of certain messages, this should be 'U bent' (uw is possesive): # grep "Uw bent" * -r messages/nl/LC_MESSAGES/mailman.po:"Uw bent op deze lijst aangemeld met het adres met niet te wijzigen You are " messages/nl/LC_MESSAGES/mailman.po:msgstr "Uw bent afgemeld van de %(realname)s maillijst" Binary file messages/nl/LC_MESSAGES/mailman.mo matches Solution is simple: just s/Uw bent/U bent/g ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1417678&group_id=103 From noreply at sourceforge.net Sun Jan 29 05:07:15 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 28 Jan 2006 20:07:15 -0800 Subject: [ mailman-Patches-1415956 ] Sitewide headers/footers & XHTML Compliant Web UI Message-ID: Patches item #1415956, was opened at 2006-01-26 22:23 Message generated for change (Comment added) made by carbonnb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_id=103 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 UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: Sitewide headers/footers & XHTML Compliant Web UI Initial Comment: This patch was borne out of a request I received to make the Mailman UI fit the look of the web site. This patch allows you to set a site wide header and footer. This allows you to pretty much make the MM UI look like any other site. While I was at it I also made the web UI XHTML compliant. Once you patch your source and install it, all you need to do is edit the html files in the templates/en directory. Most of the pages will get the header and footers from the site-header.html and site-footer.html files, but some of the HTML files already contain theor own header/footer so you will need ot edit some of these files as well. Since this also adds XHTML compliance, this superceeds patch #116035 ---------------------------------------------------------------------- >Comment By: Bryan Carbonnell (carbonnb) Date: 2006-01-28 23:07 Message: Logged In: YES user_id=449953 Updated both patches to remove some of my site specific HTML coding. ---------------------------------------------------------------------- Comment By: Bryan Carbonnell (carbonnb) Date: 2006-01-26 22:31 Message: Logged In: YES user_id=449953 I am also uploading a second version of this patch. This second version will add the sitewide headers/footer to source that has been patched with the ht://dig integration patches. At the time I posted this, the official ht://dig integration patches were not released, but the MM2.1.6 patches appear to work with MM 2.1.7, so they are what were used. to apply this patch use this command from your mailman source directory: patch -p1 Patches item #1418016, was opened at 2006-01-29 17:04 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=1418016&group_id=103 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: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Schoinobates Volans (schoinobates) Assigned to: Nobody/Anonymous (nobody) Summary: Dutch translation update Initial Comment: A Debian user, Luc Stroobant, has contributed this update to the Dutch translation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1418016&group_id=103 From noreply at sourceforge.net Mon Jan 30 15:48:11 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 30 Jan 2006 06:48:11 -0800 Subject: [ mailman-Bugs-1000699 ] moderator page with details misses a submit button Message-ID: Bugs item #1000699, was opened at 2004-07-30 09:30 Message generated for change (Comment added) made by djast You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1000699&group_id=103 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: Open Resolution: None Priority: 5 Submitted By: Stepan Kasal (kasal) Assigned to: Nobody/Anonymous (nobody) Summary: moderator page with details misses a submit button Initial Comment: Working with version 2.1.5. I moderate a few lists. When I go from summary page to "wiev the detail of individual postings", I get a page which has a submit button at the bottom. Similar button should be on the top, as with the Summary page. Besides being an inconvenience, this can also be confusing: I checked "Discard all msgs marked as deferred" on the top, then moved to the end and pressed the button there. Of course the upper checkbox had no influence. Btw: I hope that the "discard all deferred" checkbox discards only the messages from that dispayed page, not the messages that might have arrived while themoderator was staring at the page. That would be nasty if it weren't this way. ---------------------------------------------------------------------- Comment By: Dan Astoorian (djast) Date: 2006-01-30 09:48 Message: Logged In: YES user_id=1437943 The scope of the problem is greater than that: "Discard all msgs marked as deferred" does not appear to work at all from the "details" page, as far as I can tell. In the summary page, each group of items on which an action is to be taken is identified with a set of radio buttons with 'INPUT name="senderaction-SENDER"' tags, and the "senderaction-" prefix is used by the code in Cgi/admindb.py which processes the "Discard all msgs marked as deferred" checkbox. However, the details page uses only the request-id in the field names, e.g., 'INPUT name="10112"', so they aren't processed by the same code. I can't find anywhere else in the code (Mailman 2.1.7) where the discardalldefersp field is processed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1000699&group_id=103 From noreply at sourceforge.net Mon Jan 30 15:51:29 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 30 Jan 2006 06:51:29 -0800 Subject: [ mailman-Bugs-1418670 ] Problems with lists named like languages Message-ID: Bugs item #1418670, was opened at 2006-01-30 15:51 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=1418670&group_id=103 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: 6 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Problems with lists named like languages Initial Comment: "update" has fatal problems with lists named like a language. Create some lists named "it" (Italian) or "de" (German) an update will crash: Updating mailing list: de Updating the held requests database. - updating old private mbox file looks like you have a really recent CVS installation... you're either one brave soul, or you already ran me - updating old public mbox file looks like you have a really recent CVS installation... you're either one brave soul, or you already ran me - This list looks like it might have <= b4 list templates around Traceback (most recent call last): File "bin/update", line 789, in ? errors = main() File "bin/update", line 679, in main errors = errors + dolist(listname) File "bin/update", line 357, in dolist os.rename(o_tmpl, n_tmpl) OSError: [Errno 2] No such file or directory make: *** [update] Error 1 (Btw: update crashs if there`s no pending.pck. That should not happen!) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1418670&group_id=103 From noreply at sourceforge.net Mon Jan 30 16:21:02 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 30 Jan 2006 07:21:02 -0800 Subject: [ mailman-Bugs-1000699 ] moderator page with details misses a submit button Message-ID: Bugs item #1000699, was opened at 2004-07-30 06:30 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1000699&group_id=103 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: 5 Submitted By: Stepan Kasal (kasal) Assigned to: Nobody/Anonymous (nobody) Summary: moderator page with details misses a submit button Initial Comment: Working with version 2.1.5. I moderate a few lists. When I go from summary page to "wiev the detail of individual postings", I get a page which has a submit button at the bottom. Similar button should be on the top, as with the Summary page. Besides being an inconvenience, this can also be confusing: I checked "Discard all msgs marked as deferred" on the top, then moved to the end and pressed the button there. Of course the upper checkbox had no influence. Btw: I hope that the "discard all deferred" checkbox discards only the messages from that dispayed page, not the messages that might have arrived while themoderator was staring at the page. That would be nasty if it weren't this way. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-30 07:21 Message: Logged In: YES user_id=1123998 I am marking this closed/fixed because the "discard all deferred" checkbox was intended to work only on the summary page. It's appearance on the detail pages was a mistake that was fixed in 2.1.6. So yes, in 2.1.5 neither "discard all deferred" checkbox works on the detail pages, and BTW, you can check the box at the top of the summary page and click the button at the bottom or vice versa and it works. In 2.1.6 and above, the checkboxes appear only on the summary page and they only cause messages on that page marked 'defer' to be discarded even if there are other messages not rendered on that page. Also, there are submit buttons at both the top and bottom of both the 'all messages from' detail and the individual message detail. If you really want a "discard all messages marked defer" box that works on the "view all messages from" page, that is now a feature request (RFE) and should be resubmitted as such. ---------------------------------------------------------------------- Comment By: Dan Astoorian (djast) Date: 2006-01-30 06:48 Message: Logged In: YES user_id=1437943 The scope of the problem is greater than that: "Discard all msgs marked as deferred" does not appear to work at all from the "details" page, as far as I can tell. In the summary page, each group of items on which an action is to be taken is identified with a set of radio buttons with 'INPUT name="senderaction-SENDER"' tags, and the "senderaction-" prefix is used by the code in Cgi/admindb.py which processes the "Discard all msgs marked as deferred" checkbox. However, the details page uses only the request-id in the field names, e.g., 'INPUT name="10112"', so they aren't processed by the same code. I can't find anywhere else in the code (Mailman 2.1.7) where the discardalldefersp field is processed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1000699&group_id=103 From noreply at sourceforge.net Mon Jan 30 16:54:22 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 30 Jan 2006 07:54:22 -0800 Subject: [ mailman-Bugs-1000699 ] moderator page with details misses a submit button Message-ID: Bugs item #1000699, was opened at 2004-07-30 09:30 Message generated for change (Comment added) made by djast You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1000699&group_id=103 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: 5 Submitted By: Stepan Kasal (kasal) Assigned to: Nobody/Anonymous (nobody) Summary: moderator page with details misses a submit button Initial Comment: Working with version 2.1.5. I moderate a few lists. When I go from summary page to "wiev the detail of individual postings", I get a page which has a submit button at the bottom. Similar button should be on the top, as with the Summary page. Besides being an inconvenience, this can also be confusing: I checked "Discard all msgs marked as deferred" on the top, then moved to the end and pressed the button there. Of course the upper checkbox had no influence. Btw: I hope that the "discard all deferred" checkbox discards only the messages from that dispayed page, not the messages that might have arrived while themoderator was staring at the page. That would be nasty if it weren't this way. ---------------------------------------------------------------------- Comment By: Dan Astoorian (djast) Date: 2006-01-30 10:54 Message: Logged In: YES user_id=1437943 Apologies for being unclear: the "details" page I was referring to in my followup is the "?details=all" page (following the "you can also view the details of all held postings" link at the top of the summary page), not the details page for an individual sender or message id. The "discard all deferred" checkbox still does appear (but fails to work) on the "?details=all" page, as of 2.1.7. The test for whether to supply the button is "if not (sender or msgid):"; if the button is not supposed to appear on the "?details=all" page, perhaps the test should be changed to something like "if not (details or sender or msgid)"? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-01-30 10:21 Message: Logged In: YES user_id=1123998 I am marking this closed/fixed because the "discard all deferred" checkbox was intended to work only on the summary page. It's appearance on the detail pages was a mistake that was fixed in 2.1.6. So yes, in 2.1.5 neither "discard all deferred" checkbox works on the detail pages, and BTW, you can check the box at the top of the summary page and click the button at the bottom or vice versa and it works. In 2.1.6 and above, the checkboxes appear only on the summary page and they only cause messages on that page marked 'defer' to be discarded even if there are other messages not rendered on that page. Also, there are submit buttons at both the top and bottom of both the 'all messages from' detail and the individual message detail. If you really want a "discard all messages marked defer" box that works on the "view all messages from" page, that is now a feature request (RFE) and should be resubmitted as such. ---------------------------------------------------------------------- Comment By: Dan Astoorian (djast) Date: 2006-01-30 09:48 Message: Logged In: YES user_id=1437943 The scope of the problem is greater than that: "Discard all msgs marked as deferred" does not appear to work at all from the "details" page, as far as I can tell. In the summary page, each group of items on which an action is to be taken is identified with a set of radio buttons with 'INPUT name="senderaction-SENDER"' tags, and the "senderaction-" prefix is used by the code in Cgi/admindb.py which processes the "Discard all msgs marked as deferred" checkbox. However, the details page uses only the request-id in the field names, e.g., 'INPUT name="10112"', so they aren't processed by the same code. I can't find anywhere else in the code (Mailman 2.1.7) where the discardalldefersp field is processed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1000699&group_id=103 From noreply at sourceforge.net Tue Jan 31 02:21:02 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 30 Jan 2006 17:21:02 -0800 Subject: [ mailman-Patches-1419490 ] email.Utils.parsedate can return bogus date Message-ID: Patches item #1419490, was opened at 2006-01-31 01:21 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=1419490&group_id=103 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: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Tokio Kikuchi (tkikuchi) Summary: email.Utils.parsedate can return bogus date Initial Comment: While the CVE entry of CVE-2005-4153 (see http://www.securityfocus.com/bid/16248/info) is not vulnerable for mailman-2.1.7 and newer, we should fix the date parsing bug in email package. In the meantime of the package renewal, this patch may be used to workaround the bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1419490&group_id=103