From noreply at sourceforge.net Mon Aug 1 16:10:15 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 01 Aug 2005 07:10:15 -0700 Subject: [ mailman-Patches-1244799 ] XML-RPC interface to Mailman Message-ID: Patches item #1244799, was opened at 2005-07-25 21:29 Message generated for change (Comment added) made by jtate You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1244799&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: Joseph Tate (jtate) Assigned to: Nobody/Anonymous (nobody) Summary: XML-RPC interface to Mailman Initial Comment: This patch adds an XML-RPC public interface to Mailman 2.1.6. The functionality is very basic but includes interfaces for adding and deleting lists, setting list settings, and adding/removing/listing subscribers. There are also some changes made to a few Cgi and command line interfaces to break functionality away from output generation so that they could be more easily reused. ---------------------------------------------------------------------- >Comment By: Joseph Tate (jtate) Date: 2005-08-01 14:10 Message: Logged In: YES user_id=55276 I've updated the patch. There were some problems in the way that I was doing some things. This version of the patch will remain static for the forseeable future. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1244799&group_id=103 From shay_bm at netvision.net.il Mon Aug 1 23:35:55 2005 From: shay_bm at netvision.net.il (shay ben michael) Date: Mon, 01 Aug 2005 23:35:55 +0200 Subject: problem with regular expression Message-ID: <003f01c596e1$03fa23e0$1e9f84d9@9q0wmwmn62szk9s> hello I have a regular expression run on a massive text. the results are fed into an iteraton (by finditer). for some reason I can't iterate it. (the program is stucked ). what is the reason (may the reason be there are non ASCII characters) how can I solve that. in case you are not able to answer can you give me please a link of a good forum desperatly waiting for answer thank in advance shay -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-coders/attachments/20050801/f5e69bc4/attachment.htm From noreply at sourceforge.net Wed Aug 3 01:12:18 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 02 Aug 2005 16:12:18 -0700 Subject: [ mailman-Bugs-1250657 ] header_filter_rules should use multiline mode Message-ID: Bugs item #1250657, was opened at 2005-08-02 23: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=1250657&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: Iain Pople (iainpople) Assigned to: Nobody/Anonymous (nobody) Summary: header_filter_rules should use multiline mode Initial Comment: I have noticed some unexpected behaviour with header_filter_rules. I wanted to reject messages with an empty subject line so i came up with the following regex: ^subject:\s*$ However it wasn't working as desired. After delving around in the SpamDetect.py code i noticed that the re.search call is not using MULTILINE mode. So the headers are treated as one long string and ^ would only match the beginning of the string. Is this the desired behaviour? To me it makes more sense that it should use multiline mode. i.e.: --- SpamDetect.py.bak 2005-08-02 15:56:42.083270000 +1000 +++ SpamDetect.py 2005-08-02 17:33:59.698226000 +1000 @@ -127,7 +127,7 @@ for pattern in patterns.splitlines(): if pattern.startswith('#'): continue - if re.search(pattern, headers, re.IGNORECASE): + if re.search(pattern, headers, re.IGNORECASE| re.MULTILINE): if action == mm_cfg.DISCARD: raise Errors.DiscardMessage if action == mm_cfg.REJECT: @@ -137,3 +137,4 @@ hold_for_approval(mlist, msg, msgdata, HeaderMatchHold) if action == mm_cfg.ACCEPT: return ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1250657&group_id=103 From noreply at sourceforge.net Wed Aug 3 17:25:43 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 03 Aug 2005 08:25:43 -0700 Subject: [ mailman-Bugs-1251101 ] cgi generated pages do not produce valid html Message-ID: Bugs item #1251101, was opened at 2005-08-03 17:25 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=1251101&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: skripi (skripi) Assigned to: Nobody/Anonymous (nobody) Summary: cgi generated pages do not produce valid html Initial Comment: Hi, i ran 'http://www.htmlhelp.com/cgi-bin/validate.cgi? url=http%3A%2F%2Fv1837.vanager. de&warnings=yes&input=yes&spider=yes&hidevalid=yes " against my local mailman installation and noticed: - the cgi's do not produce a proper doctype - the mailinglist templates are no longer html conform. Possible solution: prepend to all generated pages a DOCTYPE: --- --- or ---- --- I would prefer strict and move presentation related stuff to css.. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1251101&group_id=103 From noreply at sourceforge.net Wed Aug 3 17:32:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 03 Aug 2005 08:32:39 -0700 Subject: [ mailman-Feature Requests-1251109 ] use css for presentation of content Message-ID: Feature Requests item #1251109, was opened at 2005-08-03 17:32 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=1251109&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: skripi (skripi) Assigned to: Nobody/Anonymous (nobody) Summary: use css for presentation of content Initial Comment: Hi, i tried to customize the mailman templates and noticed that a lot of presenation is hard-coded into the html-code. I was wondering if it would be possible to split the structure and the representation by using css. As while using css, the pages could more easily be changed in their representation. Maybe you could give it a thought. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1251109&group_id=103 From noreply at sourceforge.net Wed Aug 3 17:58:01 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 03 Aug 2005 08:58:01 -0700 Subject: [ mailman-Patches-1244799 ] XML-RPC interface to Mailman Message-ID: Patches item #1244799, was opened at 2005-07-25 21:29 Message generated for change (Comment added) made by jtate You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1244799&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: Joseph Tate (jtate) Assigned to: Nobody/Anonymous (nobody) Summary: XML-RPC interface to Mailman Initial Comment: This patch adds an XML-RPC public interface to Mailman 2.1.6. The functionality is very basic but includes interfaces for adding and deleting lists, setting list settings, and adding/removing/listing subscribers. There are also some changes made to a few Cgi and command line interfaces to break functionality away from output generation so that they could be more easily reused. ---------------------------------------------------------------------- >Comment By: Joseph Tate (jtate) Date: 2005-08-03 15:58 Message: Logged In: YES user_id=55276 Fix a bug in the Cgi/create.py script. Complete patch attached. ---------------------------------------------------------------------- Comment By: Joseph Tate (jtate) Date: 2005-08-01 14:10 Message: Logged In: YES user_id=55276 I've updated the patch. There were some problems in the way that I was doing some things. This version of the patch will remain static for the forseeable future. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1244799&group_id=103 From noreply at sourceforge.net Thu Aug 4 06:10:54 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 03 Aug 2005 21:10:54 -0700 Subject: [ mailman-Bugs-1250657 ] header_filter_rules should use multiline mode Message-ID: Bugs item #1250657, was opened at 2005-08-02 23:12 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1250657&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: Closed >Resolution: Fixed Priority: 5 Submitted By: Iain Pople (iainpople) Assigned to: Nobody/Anonymous (nobody) Summary: header_filter_rules should use multiline mode Initial Comment: I have noticed some unexpected behaviour with header_filter_rules. I wanted to reject messages with an empty subject line so i came up with the following regex: ^subject:\s*$ However it wasn't working as desired. After delving around in the SpamDetect.py code i noticed that the re.search call is not using MULTILINE mode. So the headers are treated as one long string and ^ would only match the beginning of the string. Is this the desired behaviour? To me it makes more sense that it should use multiline mode. i.e.: --- SpamDetect.py.bak 2005-08-02 15:56:42.083270000 +1000 +++ SpamDetect.py 2005-08-02 17:33:59.698226000 +1000 @@ -127,7 +127,7 @@ for pattern in patterns.splitlines(): if pattern.startswith('#'): continue - if re.search(pattern, headers, re.IGNORECASE): + if re.search(pattern, headers, re.IGNORECASE| re.MULTILINE): if action == mm_cfg.DISCARD: raise Errors.DiscardMessage if action == mm_cfg.REJECT: @@ -137,3 +137,4 @@ hold_for_approval(mlist, msg, msgdata, HeaderMatchHold) if action == mm_cfg.ACCEPT: return ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-08-04 04:10 Message: Logged In: YES user_id=67709 Thank you! This was fixed in CVS. There may be some incompatibilities with this fix but my trivial example (in the Mailman FAQ Wizard 3.51) passed a test. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1250657&group_id=103 From noreply at sourceforge.net Sun Aug 7 15:47:52 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 07 Aug 2005 06:47:52 -0700 Subject: [ mailman-Feature Requests-1253550 ] Pls add red colour background with oversized messages Message-ID: Feature Requests item #1253550, was opened at 2005-08-07 15:47 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=1253550&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: Loek Jehee (loekjehe) Assigned to: Nobody/Anonymous (nobody) Summary: Pls add red colour background with oversized messages Initial Comment: Hello, I use MailMan 2.1.6 for a Buddhist moderated mailinglist of 1440 subscribers. I am the moderator of the list and all posts have to be approved by me. I have put the maximum length of a message body in the General Options to 120 KB because I receive many complaints when too large messages are placed on the list. Unfortunately, MailMan in some cases does not give me a warning if a message is too large, e.g. if the message is done by a non-member of the list. In such cases these warnings seem to overrule the "too large" warning. It then is very easy for me to overlook the fact that a certain message is too large (>120 KB). I must then really read the Size field very well and that is an easy thing to forget. If I then by accident approve such message, this approval overrules the 120 KB setting in the General Options and the message thus is sent to the list (causing much irritation with some subscribers). That is why I would like to suggest to add in a future release of MailMan the feature, that all messages that are over the size as indicated in the General Options, show up in the "pending moderator requests" window with a light red coloured background. This should not be a difficult addition and it would be extremely beneficial for me to protect me against accidently approving oversized messages! It would also help if you give messages from non-members a yellow colour, etc. there are more possibilities there. But the red warning is crucial! Thank you and keep up the good work! Loek ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1253550&group_id=103 From noreply at sourceforge.net Wed Aug 10 09:27:26 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 10 Aug 2005 00:27:26 -0700 Subject: [ mailman-Bugs-1255548 ] Corrupt address -> message stuck in queue (endless loop) Message-ID: Bugs item #1255548, was opened at 2005-08-10 09:27 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=1255548&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: bounce detection Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: mpellissetti (mpellissetti) Assigned to: Nobody/Anonymous (nobody) Summary: Corrupt address -> message stuck in queue (endless loop) Initial Comment: Version: mailman-2.0.8-1, on Red Hat Linux 7.2 We transferred email adresses from a Windows-based program (Filemaker), by exporting them in an ASCII file (Addresses.txt) and importing them to the mailman list with: /var/mailman/bin/remove_members -a Listname; /var/mailman/bin/add_members -n Addresses.txt Listname The file Addresses.txt contained one corrupt email address of the form: user1 at host.domain^Kpers: user2 at host.domain Viewing the file content with od showed the following exact character sequence (separate characters with one blank for better viewing): u s e r 1 @ h o s t . d o m a i n \v p e r s : u s e r 2 @ h o s t . d o m a i n Note: The corrupt address was not detected by mailman when it was imported! Sending an email to this mailing list caused the message to be stuck in /var/mailman/qfiles. Since qrunner is specified in /var/mailman/cron/crontab.in to be executed every minute, the message was sent out repeatedly (18 times mailman was killed manually) basically to the addresses preceding the corrupt one. The sender of the message received the following error message per email: ... ----- The following addresses had permanent fatal errors ----- pers: ----- Transcript of session follows ----- 553 5.1.3 pers:... List:; syntax illegal for recipient addresses ... Note: This bug is reproducible. This behavior denotes poor fault tolerance, I strongly hope that newer versions behave differently in such a case. It is always possible that a corrupt address is being entered, but the consequences (in the described case) are catastrophic! (Fortunately one of the approx. 500 recipients replied quite immediately, so "only" 18 copies of the message were sent out!) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1255548&group_id=103 From noreply at sourceforge.net Wed Aug 10 09:35:12 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 10 Aug 2005 00:35:12 -0700 Subject: [ mailman-Bugs-1255548 ] Corrupt address -> message stuck in queue (endless loop) Message-ID: Bugs item #1255548, was opened at 2005-08-10 09:27 Message generated for change (Comment added) made by mpellissetti You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1255548&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: bounce detection Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: mpellissetti (mpellissetti) Assigned to: Nobody/Anonymous (nobody) Summary: Corrupt address -> message stuck in queue (endless loop) Initial Comment: Version: mailman-2.0.8-1, on Red Hat Linux 7.2 We transferred email adresses from a Windows-based program (Filemaker), by exporting them in an ASCII file (Addresses.txt) and importing them to the mailman list with: /var/mailman/bin/remove_members -a Listname; /var/mailman/bin/add_members -n Addresses.txt Listname The file Addresses.txt contained one corrupt email address of the form: user1 at host.domain^Kpers: user2 at host.domain Viewing the file content with od showed the following exact character sequence (separate characters with one blank for better viewing): u s e r 1 @ h o s t . d o m a i n \v p e r s : u s e r 2 @ h o s t . d o m a i n Note: The corrupt address was not detected by mailman when it was imported! Sending an email to this mailing list caused the message to be stuck in /var/mailman/qfiles. Since qrunner is specified in /var/mailman/cron/crontab.in to be executed every minute, the message was sent out repeatedly (18 times mailman was killed manually) basically to the addresses preceding the corrupt one. The sender of the message received the following error message per email: ... ----- The following addresses had permanent fatal errors ----- pers: ----- Transcript of session follows ----- 553 5.1.3 pers:... List:; syntax illegal for recipient addresses ... Note: This bug is reproducible. This behavior denotes poor fault tolerance, I strongly hope that newer versions behave differently in such a case. It is always possible that a corrupt address is being entered, but the consequences (in the described case) are catastrophic! (Fortunately one of the approx. 500 recipients replied quite immediately, so "only" 18 copies of the message were sent out!) ---------------------------------------------------------------------- >Comment By: mpellissetti (mpellissetti) Date: 2005-08-10 09:35 Message: Logged In: YES user_id=1326612 Rectification: After the message got stuck in /var/mailman/qfiles, the message was sent out repeatedly (18 times until mailman was killed manually), basically to the addresses FOLLOWING the corrupt one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1255548&group_id=103 From noreply at sourceforge.net Wed Aug 10 14:04:04 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 10 Aug 2005 05:04:04 -0700 Subject: [ mailman-Bugs-1255548 ] Corrupt address -> message stuck in queue (endless loop) Message-ID: Bugs item #1255548, was opened at 2005-08-10 03:27 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1255548&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: bounce detection Group: 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: mpellissetti (mpellissetti) Assigned to: Nobody/Anonymous (nobody) Summary: Corrupt address -> message stuck in queue (endless loop) Initial Comment: Version: mailman-2.0.8-1, on Red Hat Linux 7.2 We transferred email adresses from a Windows-based program (Filemaker), by exporting them in an ASCII file (Addresses.txt) and importing them to the mailman list with: /var/mailman/bin/remove_members -a Listname; /var/mailman/bin/add_members -n Addresses.txt Listname The file Addresses.txt contained one corrupt email address of the form: user1 at host.domain^Kpers: user2 at host.domain Viewing the file content with od showed the following exact character sequence (separate characters with one blank for better viewing): u s e r 1 @ h o s t . d o m a i n \v p e r s : u s e r 2 @ h o s t . d o m a i n Note: The corrupt address was not detected by mailman when it was imported! Sending an email to this mailing list caused the message to be stuck in /var/mailman/qfiles. Since qrunner is specified in /var/mailman/cron/crontab.in to be executed every minute, the message was sent out repeatedly (18 times mailman was killed manually) basically to the addresses preceding the corrupt one. The sender of the message received the following error message per email: ... ----- The following addresses had permanent fatal errors ----- pers: ----- Transcript of session follows ----- 553 5.1.3 pers:... List:; syntax illegal for recipient addresses ... Note: This bug is reproducible. This behavior denotes poor fault tolerance, I strongly hope that newer versions behave differently in such a case. It is always possible that a corrupt address is being entered, but the consequences (in the described case) are catastrophic! (Fortunately one of the approx. 500 recipients replied quite immediately, so "only" 18 copies of the message were sent out!) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-08-10 08:04 Message: Logged In: YES user_id=12800 Mailman 2.0.8 is extremely old and no longer supported. If you upgrade to Mailman 2.1.6 (the current release of the 2.1 branch) and the problem persists, then feel free to open a new bug report, but please try to include the content of the offending message so that we can debug it. ---------------------------------------------------------------------- Comment By: mpellissetti (mpellissetti) Date: 2005-08-10 03:35 Message: Logged In: YES user_id=1326612 Rectification: After the message got stuck in /var/mailman/qfiles, the message was sent out repeatedly (18 times until mailman was killed manually), basically to the addresses FOLLOWING the corrupt one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1255548&group_id=103 From noreply at sourceforge.net Thu Aug 11 01:47:55 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 10 Aug 2005 16:47:55 -0700 Subject: [ mailman-Bugs-1256272 ] NNTP gatewaying trashes Message-IDs Message-ID: Bugs item #1256272, was opened at 2005-08-11 00:47 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=1256272&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: nntp/news Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kate Turner (kateturner) Assigned to: Nobody/Anonymous (nobody) Summary: NNTP gatewaying trashes Message-IDs Initial Comment: when a message is relayed to NNTP, the NewsRunner unconditionally replaces the existing Message-ID with its own. this breaking threading when reading a list via news, and when an NNTP user replies to a list message. a better solution would be either: 1) do not rewrite the message-id unless the NNTP server reports an error when posting it (duplicate ID); or 2) optionally, always rewrite posters' message-ids into a mailman-generated ID, and use this ID for both mail and news. i have implemented the former at our site and it appears to work, but it's so ugly i'd not feel comfortable submitting a patch for it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256272&group_id=103 From noreply at sourceforge.net Thu Aug 11 18:44:51 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 11 Aug 2005 09:44:51 -0700 Subject: [ mailman-Bugs-1256879 ] Bug report: hanging message (shunting) Message-ID: Bugs item #1256879, was opened at 2005-08-11 18: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=1256879&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: None Status: Open Resolution: None Priority: 5 Submitted By: Loek Jehee (loekjehe) Assigned to: Nobody/Anonymous (nobody) Summary: Bug report: hanging message (shunting) Initial Comment: Hello, I repeatedly have a shunted message when it is a message made in Eudora 6.2 (on Mac OS X) that contains a so-called "in-line" image (like jpg). When I send such message to the list (and I approve it as a moderator), then the message gets "shunted" and manually has to be put in the normal queue. I consider this a bug in MailMan which I would like to inform you of. I don't know if this list is the right place to post such bug report but I thought it might be interesting also for other users to know that such thing can happen. Maybe someone has a solution for me for this type of messages containing in-line pictures. The bug recently happens always when I send such message so it is a reproducible error. Below is the error log for your information. Best regards, Loek Jehee -------- Hi Loek, if you report this to mailman-users mailing list, here is the error log. It is for the default installation of version 2.1.6. Aug 10 19:29:19 2005 (30334) Uncaught runner exception: [Errno 5] Input/output error Aug 10 19:29:19 2005 (30334) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 92, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 315, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 286, in process payload = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 223, in get_payload uu.decode(StringIO(payload+'\n'), sfp) File "/usr/lib/python2.4/uu.py", line 139, in decode sys.stderr.write("Warning: %s\n" % str(v)) File "/usr/local/mailman/Mailman/Logging/MultiLogger.py", line 45, in write _logexc(logger, msg) File "/usr/local/mailman/Mailman/Logging/Utils.py", line 22, in _logexc sys.__stderr__.write('Logging error: %s\n' % logger) IOError: [Errno 5] Input/output error Aug 10 19:29:19 2005 (30334) SHUNTING: 1123691170.7004039+8fe48db8d809846344debd6eddb21ddcfb95ffca "Shunting" means putting the message into the deferred queue. "Unshunting" means pulling the message out into the normal queue, so it is sent out. Another piece of info that might help is the output of bin/unshunt: Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256879&group_id=103 From noreply at sourceforge.net Fri Aug 12 07:23:18 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 11 Aug 2005 22:23:18 -0700 Subject: [ mailman-Bugs-1257306 ] Email is discarded when the subject is in Unicode (Chinese) Message-ID: Bugs item #1257306, was opened at 2005-08-12 05: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=1257306&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: gamelover (gamelover9001) Assigned to: Nobody/Anonymous (nobody) Summary: Email is discarded when the subject is in Unicode (Chinese) Initial Comment: If you send an email with the subject in unicode (e.g., Chinese) to a mailing list, the email will be discarded. The Mailman does not give any information to the sender. So both senders and recipients will not know anything about what is going on about the email. This is a bug for 2.1.5. I am not sure if the bug is still there for 2.1.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1257306&group_id=103 From noreply at sourceforge.net Fri Aug 12 19:40:07 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 12 Aug 2005 10:40:07 -0700 Subject: [ mailman-Feature Requests-1041100 ] moderation approval should send email notification Message-ID: Feature Requests item #1041100, was opened at 2004-10-05 17:35 Message generated for change (Comment added) made by kiwimonster You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1041100&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: Kirsten Petersen (kiwimonster) Assigned to: Nobody/Anonymous (nobody) Summary: moderation approval should send email notification Initial Comment: When a non-member attempts to post to a moderated list, they receive an email informing them that their message is pending moderation. However, when the moderator has approved the message, they receive no follow-up to let them know this has happened. Since the non-member is not on the list, they have no way of knowing whether their post was successful. It would be nice to have a checkbox that allowed the moderator to notify the poster when their message has been approved. Or, to have notification sent by default. ---------------------------------------------------------------------- >Comment By: Kirsten Petersen (kiwimonster) Date: 2005-08-12 10:40 Message: Logged In: YES user_id=1122614 Okay, so it's a feature request. Is there any chance that this functionality will be added to Mailman? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-10-13 06:10 Message: Logged In: YES user_id=67709 This is more a feature request than a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1041100&group_id=103 From noreply at sourceforge.net Thu Aug 18 18:50:37 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 18 Aug 2005 09:50:37 -0700 Subject: [ mailman-Bugs-1263213 ] checkbox "Send list created" not saved if failure Message-ID: Bugs item #1263213, was opened at 2005-08-18 16:50 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=1263213&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: checkbox "Send list created" not saved if failure Initial Comment: On the list creation page (/mailman/create), if we check the "Send list created e-mail to list owner" button to 'yes' and that we put a wrong password by submitting the form, the checkbox will come back to 'no'. This is not the case with the other checkboxes or the text, everything else comes back to the previously chosen values. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263213&group_id=103 From noreply at sourceforge.net Thu Aug 18 18:57:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 18 Aug 2005 09:57:42 -0700 Subject: [ mailman-Bugs-1263219 ] Link of the 'admin' page not updated if config change Message-ID: Bugs item #1263219, was opened at 2005-08-18 16:57 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=1263219&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Link of the 'admin' page not updated if config change Initial Comment: If I change the mailman url on the server, the link displayed on the admin page that shows the 'mailing list overview page' is not updated in consequence. I have put the followings in mm_cfg.py: DEFAULT_URL_HOST = 'https://www.mysite.com/mailman' (secure connection), and we can see on the admin page that the link is on the http:// page and not https://. It should also be the same for the other pages. BTW it would be good if we could also change the pages ourselves. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263219&group_id=103 From noreply at sourceforge.net Thu Aug 18 19:25:43 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 18 Aug 2005 10:25:43 -0700 Subject: [ mailman-Bugs-1263239 ] Mailman on SSL sends passwords in plain text Message-ID: Bugs item #1263239, was opened at 2005-08-18 17:25 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=1263239&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman on SSL sends passwords in plain text Initial Comment: I have tried putting Mailman on a secure path of my server on an https url. It seemed to work approximately when adding the following directive in apache: RewriteCond %{HTTPS} !=on RewriteRule /mailman/(.*) https://www\.mysite\.com/mailman/$1 [R] However, I have sniffed the TCP/HTTP traffic during a list creation and I have seen that all the form is posted IN CLEAR. This is normal in fact as we send that to the http link first (see Bug Request #1263219). Therefore the whole test is sent in clear and only afterwards the client receives back the document move to https from apache to redirect to the proper page. I think that this could be solved if all links of the mailman binaries (admin, create and so forth) are taking dynamically the link specified in the mm_cfg.py, in the DEFAULT_URL_HOST tag. However maybe there is another clean way of putting that on a secure url. If so I would be interested in how to do that because I didn't find anything about that subject appart people doing all like I did. Thanks, Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&group_id=103 From noreply at sourceforge.net Thu Aug 18 19:28:47 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 18 Aug 2005 10:28:47 -0700 Subject: [ mailman-Bugs-1263239 ] Mailman on SSL sends passwords in plain text Message-ID: Bugs item #1263239, was opened at 2005-08-18 17:25 Message generated for change (Settings changed) made by doolyo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&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: None Status: Open Resolution: None >Priority: 8 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman on SSL sends passwords in plain text Initial Comment: I have tried putting Mailman on a secure path of my server on an https url. It seemed to work approximately when adding the following directive in apache: RewriteCond %{HTTPS} !=on RewriteRule /mailman/(.*) https://www\.mysite\.com/mailman/$1 [R] However, I have sniffed the TCP/HTTP traffic during a list creation and I have seen that all the form is posted IN CLEAR. This is normal in fact as we send that to the http link first (see Bug Request #1263219). Therefore the whole test is sent in clear and only afterwards the client receives back the document move to https from apache to redirect to the proper page. I think that this could be solved if all links of the mailman binaries (admin, create and so forth) are taking dynamically the link specified in the mm_cfg.py, in the DEFAULT_URL_HOST tag. However maybe there is another clean way of putting that on a secure url. If so I would be interested in how to do that because I didn't find anything about that subject appart people doing all like I did. Thanks, Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&group_id=103 From noreply at sourceforge.net Thu Aug 18 20:09:13 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 18 Aug 2005 11:09:13 -0700 Subject: [ mailman-Bugs-1263239 ] Mailman on SSL sends passwords in plain text Message-ID: Bugs item #1263239, was opened at 2005-08-18 17:25 Message generated for change (Comment added) made by doolyo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&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: None Status: Open Resolution: None Priority: 8 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman on SSL sends passwords in plain text Initial Comment: I have tried putting Mailman on a secure path of my server on an https url. It seemed to work approximately when adding the following directive in apache: RewriteCond %{HTTPS} !=on RewriteRule /mailman/(.*) https://www\.mysite\.com/mailman/$1 [R] However, I have sniffed the TCP/HTTP traffic during a list creation and I have seen that all the form is posted IN CLEAR. This is normal in fact as we send that to the http link first (see Bug Request #1263219). Therefore the whole test is sent in clear and only afterwards the client receives back the document move to https from apache to redirect to the proper page. I think that this could be solved if all links of the mailman binaries (admin, create and so forth) are taking dynamically the link specified in the mm_cfg.py, in the DEFAULT_URL_HOST tag. However maybe there is another clean way of putting that on a secure url. If so I would be interested in how to do that because I didn't find anything about that subject appart people doing all like I did. Thanks, Daniel ---------------------------------------------------------------------- >Comment By: Daniel (doolyo) Date: 2005-08-18 18:09 Message: Logged In: YES user_id=1320890 P.S.: I have seen that we can use fix_url.py to fix the URL for a specific list. However, it does not seem to fix the links of /mailman/create and the others and thus does not solve the problem, as I want to have the SSL on that page. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&group_id=103 From noreply at sourceforge.net Thu Aug 18 20:49:00 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 18 Aug 2005 11:49:00 -0700 Subject: [ mailman-Bugs-1263213 ] checkbox "Send list created" not saved if failure Message-ID: Bugs item #1263213, was opened at 2005-08-18 16:50 Message generated for change (Comment added) made by doolyo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263213&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: checkbox "Send list created" not saved if failure Initial Comment: On the list creation page (/mailman/create), if we check the "Send list created e-mail to list owner" button to 'yes' and that we put a wrong password by submitting the form, the checkbox will come back to 'no'. This is not the case with the other checkboxes or the text, everything else comes back to the previously chosen values. ---------------------------------------------------------------------- >Comment By: Daniel (doolyo) Date: 2005-08-18 18:49 Message: Logged In: YES user_id=1320890 Oops, sorry. It is not the correct checkbox. It is the other, called 'Should new members be quarantined before they are allowed to post unmoderated to this list?'. The rest is true for the fact that it looses it's 'yes' value. Thanks, Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263213&group_id=103 From noreply at sourceforge.net Sat Aug 20 19:44:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 20 Aug 2005 10:44:42 -0700 Subject: [ mailman-Feature Requests-1264981 ] Option to determine what member is allowed to post Message-ID: Feature Requests item #1264981, was opened at 2005-08-20 17:44 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=1264981&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: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Option to determine what member is allowed to post Initial Comment: Using Sympa mailing list program, you can determine who is allowed to post to the mailing list, by still keeping the e-mail on hold. This is very handy when we have to create a list of members that can only receive e- mails and are forbidden to post. It also adds some security, and avoids to have to check all member's requests to post which are pending. If a member is disallowed then he just receives the forbidden message already in use. It is a clean way to proceed. Thus I recommend adding a field that would contain a list of members allowed to post. Else we could add a column in the member list wich a checkbox that determines who is allowed to post. This would be the best. We would choose a tag name for the default setting and the administrator of the list would be able to choose who can post on this list. I just add that we can do that already, but what I want is to allow only one member to post, and the mail being put on hold, and NOT sent directly. The moderator would still have to accept his post manually. The others are just notfied that they are not allowed to post or discarded. Thank you. Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1264981&group_id=103 From noreply at sourceforge.net Tue Aug 23 04:57:55 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 22 Aug 2005 19:57:55 -0700 Subject: [ mailman-Bugs-1266729 ] Default list signature blocks do not follow good netiquette Message-ID: Bugs item #1266729, was opened at 2005-08-22 21:57 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=1266729&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: More Information Needed Status: Open Resolution: None Priority: 5 Submitted By: Patrick W. Barnes (nman64) Assigned to: Nobody/Anonymous (nobody) Summary: Default list signature blocks do not follow good netiquette Initial Comment: I recently noticed on a mailing list to which I am a member that the signature blocks did not comply with good netiquette guidelines. After discussing this with one of the list maintainers, and getting those lists corrected, he informed me that the faulty blocks were the default under mailman. If this is not the case, I apologize. Basically, a signature block should begin with two hyphens and a space, followed by a newline. Currently, the default blocks begin with the two hyphens and a newline, without the space. For more information, please see: http://en.wikipedia.org/wiki/Signature_block For the curious, the lists that we dealt with were the Fedora Project mailing lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1266729&group_id=103 From noreply at sourceforge.net Tue Aug 23 12:33:53 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Aug 2005 03:33:53 -0700 Subject: [ mailman-Bugs-1266969 ] Extra HR line after headers Message-ID: Bugs item #1266969, was opened at 2005-08-23 06:33 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=1266969&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: StockCarGazette (stockcargazette) Assigned to: Nobody/Anonymous (nobody) Summary: Extra HR line after headers Initial Comment: My site provider just upgraded my Mailman installation to 2.1.6. I normally send out strictly text-based newsletters using Mailman. I am now getting a HTML HR line after the header and before the actual content of my e-zine. Any ideas why this is happening, and how I can get rid of it? Thanks, Mike Mike at MotorSportsNews.Net http://MotorSportsNews.Net Home of the FREE Stock Car Gazette E-zine ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1266969&group_id=103 From noreply at sourceforge.net Tue Aug 23 16:39:08 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Aug 2005 07:39:08 -0700 Subject: [ mailman-Feature Requests-669056 ] Archive URL in Email Message-ID: Feature Requests item #669056, was opened at 2003-01-16 14:12 Message generated for change (Comment added) made by decibel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669056&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: Grant Bowman (grantbow) Assigned to: Nobody/Anonymous (nobody) Summary: Archive URL in Email Initial Comment: When an email goes out, it should have the assigned URL in the header. This requires you to know what it is as you send it out which can be tricky. I don't know if Mailman is designed to handle such a feature. I hope it is! ---------------------------------------------------------------------- Comment By: Jim C. Nasby (decibel) Date: 2005-08-23 14:39 Message: Logged In: YES user_id=457856 I agree this would be extremely handy. I'd post the URL to a thread about it on mailman-users, but I'm too lazy to find it in the archive. Of course if there was a URL in the emails... FWIW, Brad Knowles posted that right now this isn't possible to do because the archives use a sequence number. If instead they used a hash of the email, then doing this would be easy. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669056&group_id=103 From noreply at sourceforge.net Tue Aug 23 17:24:50 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Aug 2005 08:24:50 -0700 Subject: [ mailman-Feature Requests-669056 ] Archive URL in Email Message-ID: Feature Requests item #669056, was opened at 2003-01-16 09:12 Message generated for change (Comment added) made by fehwalker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669056&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: Grant Bowman (grantbow) Assigned to: Nobody/Anonymous (nobody) Summary: Archive URL in Email Initial Comment: When an email goes out, it should have the assigned URL in the header. This requires you to know what it is as you send it out which can be tricky. I don't know if Mailman is designed to handle such a feature. I hope it is! ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2005-08-23 11:24 Message: Logged In: YES user_id=660772 Some sort of unique identifier (a hash, or some other permanent ID tag inserted as a header in the .mbox file) for each message would be very useful if the archive is later modified and rebuilt. Currently if a message is removed or added and the archive rebuilt, search engines must reindex the entire archive to get the updated URL for each message based on the new sequence numbers. For large archives this is non-trivial. +1 for a unique and permanent URL per message, +0 for having the message URL included in the message/headers. ---------------------------------------------------------------------- Comment By: Jim C. Nasby (decibel) Date: 2005-08-23 10:39 Message: Logged In: YES user_id=457856 I agree this would be extremely handy. I'd post the URL to a thread about it on mailman-users, but I'm too lazy to find it in the archive. Of course if there was a URL in the emails... FWIW, Brad Knowles posted that right now this isn't possible to do because the archives use a sequence number. If instead they used a hash of the email, then doing this would be easy. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669056&group_id=103 From noreply at sourceforge.net Tue Aug 23 19:36:04 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Aug 2005 10:36:04 -0700 Subject: [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&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: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2005-08-23 17:36 Message: Logged In: YES user_id=75166 indexing-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-08-03 09:39 Message: Logged In: YES user_id=75166 indexing-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-03 09:20 Message: Logged In: YES user_id=75166 indexing-2.1.4-0.1.patch is a MM 2.1.4 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:10 Message: Logged In: YES user_id=75166 indexing-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:37 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz no longer needs patch #661138 to be applied as that patch was incorporated in the MM 2.1.2 release ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:34 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz is revised for MM 2.1.2 compatibility. Before applying thisversion of the patch you must also apply Bug fix patch #728836 to the source distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:49 Message: Logged In: YES user_id=75166 indexing-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:05 Message: Logged In: YES user_id=75166 indexing-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1. Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:55 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:53 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:52 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:40 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:39 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:23 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply at sourceforge.net Tue Aug 23 19:38:53 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Aug 2005 10:38:53 -0700 Subject: [ mailman-Patches-444884 ] Integration of Mailman and htdig for archiving Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&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: Unofficial 2.0 patch Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) >Summary: Integration of Mailman and htdig for archiving Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2005-08-23 17:38 Message: Logged In: YES user_id=75166 htdig-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-08-03 09:45 Message: Logged In: YES user_id=75166 htdig-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-03 09:16 Message: Logged In: YES user_id=75166 htdig-2.1.4-0.1.patch is a MM 2.1.4 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-12-15 16:13 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.5.patch modifies htdig.py and private.py; the security changes introduced by htdig-2.1.3-0.2 patch to these scripts incorrectly blocked access to the listname.mbox/listname.mbox file. The 0.5 revision of the patch corrects this error. This problem and a suggested fix were pointed out to me in a private email by Stephan Berndts stb-mm at spline.de ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 14:55 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.4.patch provides minor improvements in handling of HTTP request handled by htidg.py which lead to the user receiving an authentication challenge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-19 21:13 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.3.patch.gz add minor private archive security improvements to the patch for MM 2.1.3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:14 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:47 Message: Logged In: YES user_id=75166 last comment should have read: htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:45 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 19:00 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz adds some minor performance improvement in template handling in MM 2.1.2 You should consider also applying this bug-fis patch: [ 730769 ] template access hierarchy is broken http://sourceforge.net/tracker/index.php? func=detail&aid=730769&group_id=103&atid=100103 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 15:44 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.2.patch.gz corrects error in file uploaded as htdig-2.1.2-0.1.patch.gz. Sorry for any inconvenience. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:46 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.1.patch.gz is a revised version for MM 2.1.2 compatibility. It also incoporates a previosuly unpublished change to overcome a potential problem with htdig excluced urls - see the INSTALL.htdig-mm file for more information ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 18:29 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.4.patch.gz fixes a problem with mmsearch handling multi-page search results from htsearch. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 17:54 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.3.patch.gz fixes a fault when mmsearch.py is rasing an excpetion because it has had a problem running htsearch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-20 14:10 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.2.patch.gz close a security exploit which allows leakage of information held in htdig's per-list search indexes to users not authorized to view private list archives. Read file INSTALL.htdig-mm installed by this patch for details and instructions for upgrading MM installations using earlier versions of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:50 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-05 18:12 Message: Logged In: YES user_id=75166 It seems it is possible, if this patch is installed, for a list's htdig conf file and the list specific htdig index db files to be read directly through the web interface for list archives. Even if this patch isn't installed it seems a list's pipermail.pck file can also be read directly through the web interface for list archives. This seems to be true for accesses via /pipermail for public lists and via /mailman/private for private lists. The problem does not occur for htdig search results accessed via /mailman/htdig as the htdig.py script is more protective than private.py Broadly speaking the data affected is availble to a user in normal operation which is why I do not consider the issue to be a security breach as such. Adding the following RewriteRule to Apache's httpd.conf prevents the situation, assuming you got the RewriteEngine On: RewriteRule ^(/pipermail/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.html [F] RewriteRule ^(/mailman/private/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.htm l [F] You could, of course, substitute an R flag for the F flag on the RewriteRules and be more hacker friendly. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-22 14:20 Message: Logged In: YES user_id=75166 htdig-2.1-0.3.patch corrects yet another bug in htdig.py. Hope that all of them! Stops use of obsolete config variable DEFAULT_HOST in several files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:18 Message: Logged In: YES user_id=75166 htdig-2.1-0.2.patch corrects a bug in htdig.py and deals with an adverse interaction between htdig.py and a bug in $prefix/scripts/driver (see #668685 for a patch to fix this). It also improves the content type and security handling by htdig.py for MM 2.1 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:14 Message: Logged In: YES user_id=75166 Uploaded wrong file mailer-2.0.13-0.4.patch on last attempt. Should have been htdig-2.0.13-0.4.patch which improves the content type and security handling by htdig.py for MM 2.0.13 version of patch. Please ignore mailer-2.0.13-0.4.patch file ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:09 Message: Logged In: YES user_id=75166 mailer-2.0.13-0.4.patch improves the content type and security handling by htdig.py for MM 2.0.13 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:07 Message: Logged In: YES user_id=75166 htdig-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:48 Message: Logged In: YES user_id=75166 htdig-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-04 10:53 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.3.patch corrects a minor typo in text appearing in the list TOC after the patch is applied. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:24 Message: Logged In: YES user_id=75166 htdig-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:43 Message: Logged In: YES user_id=75166 htdig-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-14 11:50 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.3.patch removes use of the file() function, used instead of the open() function, in three cron scripts added by the patch. Use of the file() function created an unnecessary dependency on Python 2.2 ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-12 16:51 Message: Logged In: YES user_id=624179 Got a workaround! The line referred to in the traceback: file(rundig_run_file, 'w').close() is used to create a 'rundig_last_run' file of lenght 0 bytes Creating this manually (or copying it) means the line isn't called and everything seems to work. Either file() is not a valid function call or my python is broken - I'm not literate enough in python to know the answer though! ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-06 14:18 Message: Logged In: YES user_id=624179 Just rebuilt MM as 2.1b3 with htdig. Upgraded lists which had htdig before work fine New lists give the obvious error: Unable to read word database file Did you run htmerge? Running the cronjob doesn't fix as it used to, message is: Output from command /usr/bin/python - S /usr/local/mailman/cron/nightly_htdig .. Traceback (most recent call last): File "/usr/local/mailman/cron/nightly_htdig", line 153, in ? main() File "/usr/local/mailman/cron/nightly_htdig", line 118, in main file(rundig_run_file, 'w').close() NameError: global name 'file' is not defined The archive/htdig folder only contains the xx.conf file, but no db.xx files If I copy in db.xx files from another list then the problem goes away (except I've now got an invalid set of references!) Is this my elementary error or is it more sinister?! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-15 11:02 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig- 2.1b3-0.1.patch which will typically show up as logged errors in the operation of the ArchRunner qrunner at line 721 of HyperArch.py ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:51 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 16:33 Message: Logged In: YES user_id=12800 I've sent Richard some comments off-line about this patch. Meta comments: the 2.0.x patches can't be officially supported, but I'm going to create an unofficial patches page off the wiki for where the 2.0 patches can be migrated. I think this patch set is too big for MM2.1, but if it's cleaned up as per my private message, let's re-evaluate it for MM2.2 (or 3.0). ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:11 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:35 Message: Logged In: YES user_id=75166 htdig-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:25 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 15:07 Message: Logged In: YES user_id=75166 Do not use htdig-2.0.12-0.1.patch there is an error in it. Use htdig-2.0.12-0.2.patch instead ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:10 Message: Logged In: YES user_id=75166 htdig-2.0.12-0.1.patch is a revised version of the patch that applies without complaint to MM 2.0.12. It also add a facility for adding site wide htdig configuration attributes to all list specific htdig configuration files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:59 Message: Logged In: YES user_id=75166 htdig-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 This version removes an incompatibility with Python 2.2 which caused warning messages to be generated when any of the family cron/nightly_htdig scripts were run. Some guidance on file access permissions for some htdig database files needed by rundig have been added to installation notes. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:59 Message: Logged In: YES user_id=75166 htdig-2.0.10-0.1.patch is a revised version of the patch that is compatible with MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:46 Message: Logged In: YES user_id=75166 htdig-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:22 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002 Known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:56 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:58 Message: Logged In: YES user_id=75166 htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 17:33 Message: Logged In: YES user_id=75166 The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the web_page_url for a list uses other than the http addressing (some folks want to use https). While specified as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If you do not have the requirement for using other than http addressing in you lists web_page_urls it probably isn't worth the trouble of upgrading to this patch level. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:08 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:00 Message: Logged In: YES user_id=75166 This patch should also apply without problems to Mm 2.0.7 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-09 11:54 Message: Logged In: YES user_id=75166 The htdig-2.0.6-03.patch version of the patch makes some previously hard-coded things configurable and enhances the capability to run the htdig searches and indexing on a different machine to the one delivering Mailman and Mailman's web UI. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 From noreply at sourceforge.net Tue Aug 23 19:41:41 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Aug 2005 10:41:41 -0700 Subject: [ mailman-Patches-760567 ] moderation request message content Message-ID: Patches item #760567, was opened at 2003-06-25 15:25 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&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: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: moderation request message content Initial Comment: This patch makes per-list configurable the inclusion of the body of messages that require moderation in the request messages sent to list moderators. This patch has similar objectives to those of patch #593674 but is a simpler implementation. This adds one list attribute, which can be set or unset via the web admin GUI, and which controls whether the moderated message body is included in the moderator request. Apply the attached patch file with the MM build directory as the current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2005-08-23 17:41 Message: Logged In: YES user_id=75166 modinc-2.1.6-0.1.patch is a MM 2.1.6 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-08-03 10:02 Message: Logged In: YES user_id=75166 modinc-2.1.5-0.1.patch is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:28 Message: Logged In: YES user_id=75166 modinc-2.1.4-0.1.patch is a MM 2.1.4 compatible veriosn of this patch ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-24 17:29 Message: Logged In: YES user_id=12800 I'm going to defer this one until 2.1.5 since I don't want to add any new list attributes at this late date. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:43 Message: Logged In: YES user_id=75166 modinc-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-25 17:21 Message: Logged In: YES user_id=75166 Missed one changed file from initial patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 From noreply at sourceforge.net Tue Aug 23 19:43:25 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Aug 2005 10:43:25 -0700 Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch Message-ID: Patches item #820723, was opened at 2003-10-09 16:19 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&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.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman/pipermail/MHonArc integration patch Initial Comment: This patch tightly integrates the MHonArc mail-to-HTML convertor with Mailman and its internal pipermail archiving code. The purpose of the patch is to produce a fusion of (hopefully) the best features of pipermail and MHonArc for handling Mailman mailing list archives. For more detail see patch content or http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2005-08-23 17:43 Message: Logged In: YES user_id=75166 mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch ---------------------------------------------------------------------- Comment By: dfragos (dfragos) Date: 2005-07-21 15:24 Message: Logged In: YES user_id=1310569 what about MM 2.1.6? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-08-03 10:04 Message: Logged In: YES user_id=75166 mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-19 23:53 Message: Logged In: YES user_id=696559 I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it works great for me. Would someone apply to offcial cvs tree? Thanks. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 14:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.3-0.6.patch better supports the use of MHonArc -saveresources option. Also fixes minor HTML syntax error in mhonarc.mrc and author.mrc that affected generated date and author index pages. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-14 05:49 Message: Logged In: YES user_id=75166 With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself defined in Defaults.py is the empty string and, until this is changed, the option to select MHonArc instead of pipermail for per-list archiving is not offered on the web admin GUI. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-10 17:51 Message: Logged In: YES user_id=75166 Under some circumstances, when a single message is passed to MHonArc for archiving via a pipe, MHonArc may finish its processing and exit, closing its STDIN before the Mailman process that invoked it has finished output of the message to the pipe. Mistakenly, the patched pipermail code treated this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103 From noreply at sourceforge.net Tue Aug 23 19:46:21 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Aug 2005 10:46:21 -0700 Subject: [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&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.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2005-08-23 17:46 Message: Logged In: YES user_id=75166 exitstatus-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-08-03 09:56 Message: Logged In: YES user_id=75166 exitstatus-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:14 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:39 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:40 Message: Logged In: YES user_id=75166 exitstatus-2.1.2-0.1.patch is a revision of the patch for MM 2.1.2 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:42 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:30 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 03:29 Message: Logged In: YES user_id=12800 Sorry Richard, I have to defer this one. It's too much for me to think about for MM2.1. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:58 Message: Logged In: YES user_id=75166 exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 2.1b6 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 From noreply at sourceforge.net Wed Aug 24 10:08:33 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 24 Aug 2005 01:08:33 -0700 Subject: [ mailman-Feature Requests-791928 ] digest filter options Message-ID: Feature Requests item #791928, was opened at 2003-08-20 09:10 Message generated for change (Comment added) made by fholson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=791928&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: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: digest filter options Initial Comment: Add an option on the *digest* settings page to automatically discard, bounce to the sender (with an explanatory message), or hold for moderator approval all messages with a subject that matches the list-created subject used on the outgoing digest. That way when you setup your digest options, you can easily select from several common methods of how listmanagers often want their list to handle replies from digest subscribers. Link to this setting from the page that has the other incoming message filtering options, so that when you are looking at your incoming message filtering options you notice/remember that you also have special filters relating to digests. ---------------------------------------------------------------------- Comment By: Fred H Olson (fholson) Date: 2005-08-24 03:08 Message: Logged In: YES user_id=1334022 This is a feature that I and others have long desired. On one list I currently have a low size limit (8K) to catch quoted digests which typically accompany "digest replies" ... It helps. Fred http://justcomm.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=791928&group_id=103 From noreply at sourceforge.net Wed Aug 24 10:36:38 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 24 Aug 2005 01:36:38 -0700 Subject: [ mailman-Feature Requests-1267807 ] Digest header / masthead.txt changes Message-ID: Feature Requests item #1267807, was opened at 2005-08-24 03:36 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=1267807&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: Fred H Olson (fholson) Assigned to: Nobody/Anonymous (nobody) Summary: Digest header / masthead.txt changes Initial Comment: Mailman digests get (potentially) two blocks of text at the top: The contents of a file called masthead.txt currently about 13 lines which I summarize as: Send ... submissions to ... To subscribe or unsubscribe ... You can reach the person managing the list at .... When replying, please edit your Subject line ... In addition list admins can add a digest_header (which defaults to nothing) that follows the masthead. Two other requests suggest allowing the the masthead be moved to the bottom of the list because a significant number of people in my estimation find this repetitive block of text rather verbose and a nuisance. See feature requests: 1220821 Option to move "cruft" ("boilerplate") to bottom of digest 1059834 daily digest new setting: mail body change Note that the masthead.txt does not seem to change for announcement lists for which the "submissions" and "when replying" portions are inappropriate. REQUEST: Allow "masthead" text to be changeable by listowners I would like to see the text supplied currently by masthead be changeable by list owners. It seems like this could be done similar to footers - with default contents (preferably smarter) to the digest_header form which already exists. Fred H Olson who manages lists as http://justcomm.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1267807&group_id=103 From noreply at sourceforge.net Wed Aug 24 10:50:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 24 Aug 2005 01:50:42 -0700 Subject: [ mailman-Feature Requests-1198375 ] edit moderated messages directly on admindb page Message-ID: Feature Requests item #1198375, was opened at 2005-05-09 11:01 Message generated for change (Comment added) made by fholson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1198375&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: rst (r_st) Assigned to: Nobody/Anonymous (nobody) Summary: edit moderated messages directly on admindb page Initial Comment: When viewing held messages on the administrative database page, owners/moderators should be able to edit those messages without having to forward the messages to themselves. This will allow for easy editing as well as maintaining the original headers. ---------------------------------------------------------------------- Comment By: Fred H Olson (fholson) Date: 2005-08-24 03:50 Message: Logged In: YES user_id=1334022 I agree this would be useful tho I suppose some indicator that a message has been edited should be added. It would be nice to be able to edit subject lines at least. All those "digest reply" subject lines. And deleting all the excessive quoting - particularly on "top replies" Some options for doing the latter automatically would be great. Fred H Olson http://justcomm.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1198375&group_id=103 From noreply at sourceforge.net Wed Aug 24 10:57:15 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 24 Aug 2005 01:57:15 -0700 Subject: [ mailman-Feature Requests-1182014 ] forum like interface to mailman Message-ID: Feature Requests item #1182014, was opened at 2005-04-13 01:40 Message generated for change (Comment added) made by fholson 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: Fred H Olson (fholson) Date: 2005-08-24 03: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 Wed Aug 24 21:11:55 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 24 Aug 2005 12:11:55 -0700 Subject: [ mailman-Bugs-1268939 ] host_name tag doesn't allow IP addresses Message-ID: Bugs item #1268939, was opened at 2005-08-24 19:11 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=1268939&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: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: host_name tag doesn't allow IP addresses Initial Comment: Hello. I have realised that we cannot put an IP address in the 'host_name' tag. Normally, we can send an e-mail from a client to a server that doesn't have a domain name by just putting it's IP address into square brackets like this: john@[142.56.2.72] This works, especially if you have put the same IP address on the destination server in your /etc/mail/local- host-names file on one line (for Sendmail): [142.56.2.72] Now the problem is that if we specify the IP address into square brackets in the 'host_name' tag, then the resolved hostname is returned in the e-mail address instead of this square brackets IP address. I have tried several backslashes like '', [], "", %5B and % 5D but nothing does. Square brackets are still correct to the standard, so I think that this is a bug. Regards, Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1268939&group_id=103 From noreply at sourceforge.net Wed Aug 24 22:09:56 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 24 Aug 2005 13:09:56 -0700 Subject: [ mailman-Bugs-1269067 ] e-mail command confirmations should be optional Message-ID: Bugs item #1269067, was opened at 2005-08-24 20:09 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=1269067&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: e-mail command confirmations should be optional Initial Comment: When we send an e-mail to change the member's options with a command (e.g. to subscribe/unsubscribe members), the confirmation of the commands should be optionnal. This is useful particularly if we do a php script that sends the commands automatically from a post field. Then the member doesn't need to see all those e-mail commands. This should be an optional command that would disable these confirmations for the whole list and all commands. www.Sympa.org mailing list does this very well. Thank you. Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1269067&group_id=103 From noreply at sourceforge.net Wed Aug 24 21:55:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 24 Aug 2005 12:55:39 -0700 Subject: [ mailman-Bugs-1269025 ] unsubscribe removal confirmation should be optional Message-ID: Bugs item #1269025, was opened at 2005-08-24 19:55 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=1269025&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: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: unsubscribe removal confirmation should be optional Initial Comment: We should be able to choose if we want the members that unsubscribe by e-mail to receive a 'removal confirmation' e-mail. I need the user to not receive this notice and just remove him without him knowing it. However, we should still be able to sent him the good_bye message when he left if we want it, like it's the case currently. The removal notice is not really necessary if people receive an e-mail telling that they have been removed. They can submit again if they want and report the abuse. This option should just be an added tag that would be valid for the whole list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1269025&group_id=103 From noreply at sourceforge.net Mon Aug 29 19:26:17 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 29 Aug 2005 10:26:17 -0700 Subject: [ mailman-Bugs-1275856 ] Utils.get_domain() wrong if VIRTUAL_HOST_OVERVIEW off Message-ID: Bugs item #1275856, was opened at 2005-08-29 10:26 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=1275856&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: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Utils.get_domain() wrong if VIRTUAL_HOST_OVERVIEW off Initial Comment: Part of the code in get_domain() in Utils.py is: if mm_cfg.VIRTUAL_HOST_OVERVIEW and host: return host.lower() else: # See the note in Defaults.py concerning DEFAULT_HOST_NAME # vs. DEFAULT_EMAIL_HOST. hostname = mm_cfg.DEFAULT_HOST_NAME or mm_cfg.DEFAULT_EMAIL_HOST return hostname.lower() It is clear that get_domain() should return the web host, not the e-mail host. This code should be: if mm_cfg.VIRTUAL_HOST_OVERVIEW and host: return host.lower() else: # See the note in Defaults.py concerning DEFAULT_URL # vs. DEFAULT_URL_HOST. hostname = mm_cfg.DEFAULT_URL or mm_cfg.DEFAULT_URL_HOST return hostname.lower() ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1275856&group_id=103 From noreply at sourceforge.net Tue Aug 30 10:24:17 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 30 Aug 2005 01:24:17 -0700 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: 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