From noreply at sourceforge.net Fri Sep 2 03:23:15 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 01 Sep 2005 18:23:15 -0700 Subject: [ mailman-Bugs-1015709 ] change subs. address while logged in - error on logout Message-ID: Bugs item #1015709, was opened at 2004-08-25 01:11 Message generated for change (Comment added) made by unavco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015709&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: Matt Crawford (crawdad) Assigned to: Nobody/Anonymous (nobody) Summary: change subs. address while logged in - error on logout Initial Comment: A user used the web interface to change his email address for all lists, and replied to the confirmation email. Then he logged out of the web interface, eliciting this error traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/var/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/var/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/var/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/var/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: HIS at OLD.EMAIL.ADDRESS.HERE ---------------------------------------------------------------------- Comment By: unavco (unavco) Date: 2005-09-02 01:23 Message: Logged In: YES user_id=1338757 I just experienced this on v2.1.4. I did notice in my error traceback output that there is an environment variable (PATH_TRANSLATED) that has a value that is invalid. This value appears to be a concatenation of our web server's doc root (/doc/root/path/) and a mailman path (/listname/email at address.com) which gives us /doc/root/path/listname/email at address.com Is this environment variable assigned an invalid value? Or is it possible that mailman is misconfigured and it has the httpd doc root entered as a value where it should not be? Anyone know of a fix for this? v2.1.6? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015709&group_id=103 From noreply at sourceforge.net Tue Sep 6 16:06:37 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 06 Sep 2005 07:06:37 -0700 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 20:14 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- >Comment By: Brad Knowles (shub) Date: 2005-09-06 14:06 Message: Logged In: YES user_id=18417 Okay, I've deleted the old version of the mmdsr script that was attached, and uploaded the latest version. This is what we're currently using to monitor the lists on python.org, and we have found it very useful. Any comments you may have will be appreciated. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-02-22 20:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 15:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 08:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Thu Sep 8 14:08:24 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 08 Sep 2005 05:08:24 -0700 Subject: [ mailman-Bugs-1284832 ] Error while editiing general list information page Message-ID: Bugs item #1284832, was opened at 2005-09-08 14:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1284832&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Eivind (eivind_nordby) Assigned to: Nobody/Anonymous (nobody) Summary: Error while editiing general list information page Initial Comment: I got the error message enclosed when I save the general list information page for the list davd11 after some editing. Actually, I just have to open the page http://www.cs.kau.se/mailman/edithtml/davd11/listinfo.ht ml and klick submit changes (without doing any changes) for the error page to appear. Enclosed: error page, error log (zipped) Fick bifogade meddelande n?r jag ville redigera n?gra html-koder i presentationssidan f?r davd11-listan. Det r?cker att spara den sidan som redan anv?nds (som jag har redigerat tidigare). Nu genererar den detta felmeddelande. Kan kanske skickas vidare till mailman eller n?t. Det ?r inte kritiskt f?r mig, jag klarar mig. Eivind ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1284832&group_id=103 From noreply at sourceforge.net Thu Sep 8 18:47:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 08 Sep 2005 09:47:36 -0700 Subject: [ mailman-Feature Requests-1285097 ] option index for lists Message-ID: Feature Requests item #1285097, was opened at 2005-09-08 12: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=1285097&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: Mark A. Mandel (mamandel) Assigned to: Nobody/Anonymous (nobody) Summary: option index for lists Initial Comment: An option index, implemented within Mailman, for each and every list. (The wording is due to Brad Knowles; my thanks to him. I wrote to mailman-users at python.org as below, and he suggested I enter this RFE.) (My post:) I've noticed that a fair number of the questions and answers on this list follow the pattern Q: How do I do X? A: Look in .... Q: Aha! Thanks, I didn't know it was there. And as an owner of a number of lists, though not a sysadmin, I've fairly often had the experience of "Now, where the heck was that feature the last time I used it? ... Not there... it's not there either... OK, let's go through the option pages one by one. ... ... ... Oh, THERE you are, you little devil!" One way to solve this problem would be an index. Another would be a wiki. (Brad Knowles replied:) That's a good idea -- An option index, implemented within Mailman, for each and every list. We do have the Mailman FAQ Wizard (see ), which works much like many wikis, but that is obviously not enough. Nor is the other online documentation linked under . Sigh.... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1285097&group_id=103 From noreply at sourceforge.net Fri Sep 9 22:23:34 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 09 Sep 2005 13:23:34 -0700 Subject: [ mailman-Feature Requests-1286298 ] Feature Request: Admin change subscriber's e-mail Message-ID: Feature Requests item #1286298, was opened at 2005-09-09 15:23 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=1286298&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: Dennis Behrens (djbehrens) Assigned to: Nobody/Anonymous (nobody) Summary: Feature Request: Admin change subscriber's e-mail Initial Comment: I would like to be able to go into Membership Management and be able to change a subscriber's e-mail address without sending a confirmation to the user. I'd rather not have to unsubscribe and resubscribe them with a different e-mail address. In my case, I'm taking an old listproc list and moving the user list wholesale into mailman, and then cleaning up the resulting mess. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1286298&group_id=103 From noreply at sourceforge.net Fri Sep 9 22:25:56 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 09 Sep 2005 13:25:56 -0700 Subject: [ mailman-Feature Requests-1286301 ] Feature Request: Mass Subscribe in Digest mode Message-ID: Feature Requests item #1286301, was opened at 2005-09-09 15:25 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=1286301&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: Dennis Behrens (djbehrens) Assigned to: Nobody/Anonymous (nobody) Summary: Feature Request: Mass Subscribe in Digest mode Initial Comment: I'd like to be able to do a mass subscribe to a mailman list and have all users in that mass subscribe to be placed into digest mode--especially if the list's default is set to individual messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1286301&group_id=103 From noreply at sourceforge.net Sun Sep 11 04:16:20 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 10 Sep 2005 19:16:20 -0700 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 12:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-10 19:16 Message: Logged In: YES user_id=1123998 I tried the script and other than the expected site specific changes, I found two issues which are both addressed by the patch in the mmdsr.patch file. 1) Mailman's log files are not necessarily in $var_prefix/logs/ - they can be in any directory. The patch adds a LOGDIR directory independant of MMDIR. 2) The $TMPLOG file is not removed at completion. The patch removes it. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-06 07:06 Message: Logged In: YES user_id=18417 Okay, I've deleted the old version of the mmdsr script that was attached, and uploaded the latest version. This is what we're currently using to monitor the lists on python.org, and we have found it very useful. Any comments you may have will be appreciated. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-02-22 12:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 07:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 00:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Sun Sep 11 04:22:25 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 10 Sep 2005 19:22:25 -0700 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 12:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-10 19:22 Message: Logged In: YES user_id=1123998 Oooops! I mistakenly thought I could add the mmdsr.patch as a downloadable file, but I can't so here it is. Watch out for wrapped lines ... --- mmdsr.orig 2005-09-06 20:37:53.000000000 -0700 +++ mmdsr 2005-09-10 18:33:14.532393572 -0700 @@ -132,6 +132,7 @@ MMDIR="/usr/local/mailman" TMPDIR="/tmp" +LOGDIR="/var/log/mailman" ############################################################################### # Maximum number of subdirectory entries to display in report @@ -234,9 +235,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "post" ] ; then @@ -304,9 +305,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "error" ] ; then @@ -453,4 +454,4 @@ $CAT $TMP fi -$RM $TMP +$RM -f $TMP $TMPLOG ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-10 19:16 Message: Logged In: YES user_id=1123998 I tried the script and other than the expected site specific changes, I found two issues which are both addressed by the patch in the mmdsr.patch file. 1) Mailman's log files are not necessarily in $var_prefix/logs/ - they can be in any directory. The patch adds a LOGDIR directory independant of MMDIR. 2) The $TMPLOG file is not removed at completion. The patch removes it. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-06 07:06 Message: Logged In: YES user_id=18417 Okay, I've deleted the old version of the mmdsr script that was attached, and uploaded the latest version. This is what we're currently using to monitor the lists on python.org, and we have found it very useful. Any comments you may have will be appreciated. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-02-22 12:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 07:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 00:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Sun Sep 11 09:08:18 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 11 Sep 2005 00:08:18 -0700 Subject: [ mailman-Patches-1287546 ] Remove DomainKeys (and similar) header lines Message-ID: Patches item #1287546, was opened at 2005-09-11 01:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) Summary: Remove DomainKeys (and similar) header lines Initial Comment: This simple patch removes the header lines containing keys used in DomainKeys (Yahoo) and DKIM. The keys, if left in the header, will make the email seem forged or altered to the recipient, since Mailman alters header/body info. If the keys are removed, the MTA will generate new keys (if this is installed on the host). -Joe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&group_id=103 From noreply at sourceforge.net Sun Sep 11 09:09:22 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 11 Sep 2005 00:09:22 -0700 Subject: [ mailman-Patches-1287546 ] Remove DomainKeys (and similar) header lines Message-ID: Patches item #1287546, was opened at 2005-09-11 01:08 Message generated for change (Comment added) made by skyrush You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) Summary: Remove DomainKeys (and similar) header lines Initial Comment: This simple patch removes the header lines containing keys used in DomainKeys (Yahoo) and DKIM. The keys, if left in the header, will make the email seem forged or altered to the recipient, since Mailman alters header/body info. If the keys are removed, the MTA will generate new keys (if this is installed on the host). -Joe ---------------------------------------------------------------------- >Comment By: Joe Peterson (skyrush) Date: 2005-09-11 01:09 Message: Logged In: YES user_id=738814 Attached is the patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&group_id=103 From noreply at sourceforge.net Sun Sep 11 20:00:02 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 11 Sep 2005 11:00:02 -0700 Subject: [ mailman-Patches-1287921 ] post log entries show envelope sender, not From: Message-ID: Patches item #1287921, was opened at 2005-09-11 11:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287921&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: post log entries show envelope sender, not From: Initial Comment: The interpolation dictionary used with the SMTPDirect.py log messages includes 'sender' which is obtained with the Message.get_sender() method. If mm_cfg.USE_ENVELOPE_SENDER is Yes, this method returns the envelope sender which, since this is an outgoing message, is always the listname-bounces address. Since 'listname' is already in the dictionary, this is redundant. It would be more useful, at least for lists which aren't anonymous, to override this behavior and get the sender with get_sender(use_envelope=0) which would return the From: address. The patch makes this change. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287921&group_id=103 From noreply at sourceforge.net Mon Sep 12 20:21:02 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 12 Sep 2005 11:21:02 -0700 Subject: [ mailman-Feature Requests-1286301 ] Feature Request: Mass Subscribe in Digest mode Message-ID: Feature Requests item #1286301, was opened at 2005-09-09 13:25 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1286301&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: Dennis Behrens (djbehrens) Assigned to: Nobody/Anonymous (nobody) Summary: Feature Request: Mass Subscribe in Digest mode Initial Comment: I'd like to be able to do a mass subscribe to a mailman list and have all users in that mass subscribe to be placed into digest mode--especially if the list's default is set to individual messages. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-12 11:21 Message: Logged In: YES user_id=1123998 I agree that an additional radio selection for Regular/Digest (if the list allows both) on the Mass Subscribe page would be useful and convenient. Currently, whatever the setting is for digest_is_default, if you want to mass subscribe users for the other delivery mode, you have to change the digest_is_default setting, submit the mass subscribe and then change it back. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1286301&group_id=103 From noreply at sourceforge.net Mon Sep 12 23:59:03 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 12 Sep 2005 14:59:03 -0700 Subject: [ mailman-Patches-1287546 ] Remove DomainKeys (and similar) header lines Message-ID: Patches item #1287546, was opened at 2005-09-11 03:08 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) Summary: Remove DomainKeys (and similar) header lines Initial Comment: This simple patch removes the header lines containing keys used in DomainKeys (Yahoo) and DKIM. The keys, if left in the header, will make the email seem forged or altered to the recipient, since Mailman alters header/body info. If the keys are removed, the MTA will generate new keys (if this is installed on the host). -Joe ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-12 17:59 Message: Logged In: YES user_id=12800 Applied to both Mailman 2.1 branch and trunk (2.2) ---------------------------------------------------------------------- Comment By: Joe Peterson (skyrush) Date: 2005-09-11 03:09 Message: Logged In: YES user_id=738814 Attached is the patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&group_id=103 From noreply at sourceforge.net Tue Sep 13 19:37:15 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 13 Sep 2005 10:37:15 -0700 Subject: [ mailman-Patches-1290317 ] add date field to the mail list archive index page Message-ID: Patches item #1290317, was opened at 2005-09-13 13:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1290317&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: Matt Ryanczak (ryanczak) Assigned to: Nobody/Anonymous (nobody) Summary: add date field to the mail list archive index page Initial Comment: I was asked to make the date for each message in a mailman archive be visible in the index for that month. This required that I modify HyperArch.py and the template file archidxentry.html. I thought others might find this useful so here is the relevant patch for the mailman-2.1.6 source tree. Apply the following patch to your mailman-2.1.6 source tree and build as usual. patch -p0 < date-in-archive-index.patch. This patch will modify the following files: mailman-2.1.6/Mailman/Archiver/HyperArch.py mailman-2.1.6/templates/ca/archidxentry.html mailman-2.1.6/templates/en/archidxentry.html mailman-2.1.6/templates/es/archidxentry.html mailman-2.1.6/templates/eu/archidxentry.html mailman-2.1.6/templates/fr/archidxentry.html mailman-2.1.6/templates/hr/archidxentry.html mailman-2.1.6/templates/hu/archidxentry.html mailman-2.1.6/templates/it/archidxentry.html mailman-2.1.6/templates/ja/archidxentry.html mailman-2.1.6/templates/lt/archidxentry.html mailman-2.1.6/templates/pl/archidxentry.html mailman-2.1.6/templates/pt/archidxentry.html mailman-2.1.6/templates/pt_BR/archidxentry.html mailman-2.1.6/templates/ro/archidxentry.html mailman-2.1.6/templates/ru/archidxentry.html mailman-2.1.6/templates/sl/archidxentry.html mailman-2.1.6/templates/sr/archidxentry.html mailman-2.1.6/templates/tr/archidxentry.html mailman-2.1.6/templates/uk/archidxentry.html mailman-2.1.6/templates/zh_CN/archidxentry.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1290317&group_id=103 From noreply at sourceforge.net Tue Sep 13 19:46:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 13 Sep 2005 10:46:36 -0700 Subject: [ mailman-Feature Requests-843141 ] No date in archive overview Message-ID: Feature Requests item #843141, was opened at 2003-11-16 08:28 Message generated for change (Comment added) made by ryanczak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=843141&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: Bernhard Kuemel (darsie) Assigned to: Nobody/Anonymous (nobody) Summary: No date in archive overview Initial Comment: There is no date displayed for each message in the archive overview: http://rainbow.bksys.at/pipermail/test/2003-July/thread.html It may be argued if that's a bug or a feature - I prefer to see the dates. Bernhard ---------------------------------------------------------------------- Comment By: Matt Ryanczak (ryanczak) Date: 2005-09-13 13:46 Message: Logged In: YES user_id=1343484 Bernhard, I wrote a patch for mailman 2.1.6 that adds this functionality. It can be found here: http://sourceforge.net/tracker/index.php?func=detail&aid=1290317&group_id=103&atid=300103 Regards, Matt ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-11-24 16:42 Message: Logged In: YES user_id=12800 This is a feature request. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=843141&group_id=103 From noreply at sourceforge.net Wed Sep 14 21:32:17 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 14 Sep 2005 12:32:17 -0700 Subject: [ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1 Message-ID: Patches item #839386, was opened at 2003-11-10 13:04 Message generated for change (Comment added) made by adrianwi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&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: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Kev Green (kyrian) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL MemberAdaptor for Mailman 2.1 Initial Comment: A MemberAdaptor "plugin" which should allow Mailman list members to be loaded from a MySQL database, rather than just a Mailman "pickle" file. Provided as-is, and without warranty, this "plugin" may destroy your server, soul, scalp, house, and life. Please use it with caution. Kev Green, oRe Net. http://www.orenet.co.uk/ ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-09-14 14:32 Message: Logged In: YES user_id=1175103 Thank you for developing this adaptor! So far it's working well with the limited testing I've done. There seems to be a minor bug in the addNewMember method of this adaptor (version 1.61). At lines 579-584, there are SQL statements which add a new row in the MySQL database for a new member. In those statements, the column 'delivery_status' is given the value of MemberAdaptor.UNKNOWN. MemberAdaptor.py defines: # Delivery statuses ENABLED = 0 # enabled UNKNOWN = 1 # legacy disabled BYUSER = 2 # disabled by user choice BYADMIN = 3 # disabled by admin choice BYBOUNCE = 4 # disabled by bounces So, it appears that the SQL statements should be changed to use the value of MemberAdaptor.ENABLED instead of MemberAdaptor.UNKNOWN (which is "legacy disabled"). Making this change prevents "nomail [reason]" ? from being set in the user's options for new members (as seen in the web interface). This was tested with Mailman 2.1.6. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-07-27 07:38 Message: Logged In: YES user_id=99923 Folks, For my own sanity I have decided to create a dedicated area of my business website for various opensource projects, and put this project among others under there, so please refer to this location for updates to this patch in future: http://www.orenet.co.uk/opensource/ I will still be reading bug reports via sourceforge, but if nothing else, their user interface is much more fiddly and time consuming to publish files than a quick tar -czvf and an scp, so I'll be using my own environment to host the files at least for the time being. The latest version at this time is 1.61, I belive it still requires substantial testing which I'll get around to one of these days. K. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-05-31 13:57 Message: Logged In: YES user_id=99923 Folks, Well, I've finally gotten around to releasing an update to this thing, after a phone conversation with the client who are using it, and I've incorporated a couple of cosmetic fixes, fairly substantial changes to make the bounce processing work properly (the ability to set people to NOMAIL now exists, and real world testing is commencing soon), and incorporated the flat vs. wide table archivecture types with various bugfixes. Main notes: * It would be a good idea to change all your delivery_status fields from VARCHAR(255) to INT(10) or similar, so that they will work properly, and not bomb out on this new version (they should be okay I think, but I'd advise the change). * The missing-'AND' typo has been rectified. Any suggestions and bugs should be sent to my sourceforge account address, which ends up in the right place. K. ---------------------------------------------------------------------- Comment By: Gergely EGERVARY (egervary) Date: 2005-04-09 05:14 Message: Logged In: YES user_id=1255996 Thank you for your good work. FYI: there's a missing "AND" in MysqlMemberships.py in line 494. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 18:22 Message: Logged In: YES user_id=1226150 excellent. can you please give me a list of the files modified from the original distro? grep sees six that grep have msyql in them. thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-03-11 17:56 Message: Logged In: YES user_id=99923 The flat file databases are unused when you put the MySQL adaptor in place, and they are untouched (and indeed not deleted) by it, the MySQL adaptor only queries the MySQL tables for membership information, without trying to force you into using it fulltime by deleting anything, etc. Once you unconfigure the MySQL adaptor, Mailman should revert back to your existing flat file databases. Of course, I could have missed something, etc. so do back up your flat file databases before installing the MySQL adaptor, and then you can just migrate back to them by restoring the backups. Either way, you have come up with a good question for an FAQ on the SQL adaptor :-) K. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 17:42 Message: Logged In: YES user_id=1226150 neat. just what i was looking for. i have a couple of live lists running on version version 2.1.5. i am a bit leary about unzipping this distrobution over the top of my working mailman as i am not sure how to backup the existing flat file databases. i would prefer to experiment with dropping the adapter into my existing installation. any pointers as to where to start? thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 13:34 Message: Logged In: YES user_id=99923 Oh, btw. v1.57 hasn't been tested yet, so it might kill your server, eat your dog, and stick your wife in the oven. Be careful using it! ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 13:33 Message: Logged In: YES user_id=99923 Version 1.57: 2004/12/13 * Merge in Daniel Shriver patch/code for a flat table architecture. [ Suggested by Kevin McCann , but I hadn't found time to do it myself... ] * Add bugfix information from Jinhyok Heo * Add in mksqlmailman script from TheSin * Follow Barry Warsaw's suggestion on delivery status timestamp. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-01-08 06:38 Message: Logged In: YES user_id=99923 Latest version incorporates automated generation of the necessary tables, cleaner error reporting, and updated documentation. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2003-11-11 06:14 Message: Logged In: YES user_id=99923 Bit of an oops in version 1.49, 1.50 now uploaded, which should fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_id=103 From noreply at sourceforge.net Fri Sep 16 23:00:14 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 16 Sep 2005 14:00:14 -0700 Subject: [ mailman-Bugs-1293267 ] Errno 36: filename too long -- stops mail delivery Message-ID: Bugs item #1293267, was opened at 2005-09-16 17:00 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=1293267&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: Andy Riebs (ariebs) Assigned to: Nobody/Anonymous (nobody) Summary: Errno 36: filename too long -- stops mail delivery Initial Comment: A user sent a Bugzilla page with an auto-generated filename (basically, the query used to generate the page) as an attachment. Unfortunately, this filename is long enough to overwhelm the pathname limit on Linux ext3 file systems. (See below.) This, in turn, prevents subsequent mail from being delivered. Version info: mailman-2.1.4-2.3.100mdk as distributed with Mandrake Linux release 10.0 (Official) for i586 For example, $ /usr/bin/python -S /usr/lib/mailman/cron/senddigests Traceback (most recent call last): File "/usr/lib/mailman/cron/senddigests", line 94, in ? main() File "/usr/lib/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 227, in process url = save_attachment(mlist, part, dir, filter_html=False) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 445, in save_attachment fp = open(path, 'w') IOError: [Errno 36] File name too long: '/var/lib/mailman/archives/private/xx/attachments/20050915/6cfa4267/buglist.cgiquery_formatadvancedshort_desc_typeallwordssubstrshort_desccomponentXXlong_desc_typesubstringlong_descbug_file_loc_typeallwordssubstrbug_file_locbug_statusNEWbug_statusASSIGNEDbug_statusREOPENEDemailtype1substringemail1emailassigned_to21emailreporter21emailcc21emailtype2substringemail2bugidtypeincludebug_idvoteschfieldfromchfieldtoNowchfieldvaluefield0-0-0nooptype0-0-0noopvalue0-0-0orderbugs.html' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1293267&group_id=103 From noreply at sourceforge.net Sat Sep 17 18:58:54 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 17 Sep 2005 09:58:54 -0700 Subject: [ mailman-Patches-1293919 ] Streamlined mail approval interface Message-ID: Patches item #1293919, was opened at 2005-09-17 11:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1293919&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: None Status: Open Resolution: None Priority: 5 Submitted By: Skip Montanaro (montanaro) Assigned to: Nobody/Anonymous (nobody) Summary: Streamlined mail approval interface Initial Comment: (Brad asked that I submit this.) I manage 10-15 mailing lists and needed a more efficient way to plow through mail held for review. Attached is the Python script I wrote (mmfold.py). It presents the messages one per line, just the subjects, and makes the default action "discard". (I wrote this around the same time, but somewhat before, the "discard defers" checkbox was added to Mailman.) I drive it with a simple shell function: function mmcheck { for url in http://mail.python.org/mailman/admindb/python-mode http://mail.python.org/mailman/admindb/pydotorg http://mail.python.org/mailman/admindb/python-dev do python ~/tmp/mmfold.py $url done } and execute the front-end script a couple times a week. Use it in good health. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1293919&group_id=103 From noreply at sourceforge.net Sun Sep 18 00:02:26 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 17 Sep 2005 15:02:26 -0700 Subject: [ mailman-Bugs-1293267 ] Errno 36: filename too long -- stops mail delivery Message-ID: Bugs item #1293267, was opened at 2005-09-16 21:00 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1293267&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: Andy Riebs (ariebs) Assigned to: Nobody/Anonymous (nobody) Summary: Errno 36: filename too long -- stops mail delivery Initial Comment: A user sent a Bugzilla page with an auto-generated filename (basically, the query used to generate the page) as an attachment. Unfortunately, this filename is long enough to overwhelm the pathname limit on Linux ext3 file systems. (See below.) This, in turn, prevents subsequent mail from being delivered. Version info: mailman-2.1.4-2.3.100mdk as distributed with Mandrake Linux release 10.0 (Official) for i586 For example, $ /usr/bin/python -S /usr/lib/mailman/cron/senddigests Traceback (most recent call last): File "/usr/lib/mailman/cron/senddigests", line 94, in ? main() File "/usr/lib/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 227, in process url = save_attachment(mlist, part, dir, filter_html=False) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 445, in save_attachment fp = open(path, 'w') IOError: [Errno 36] File name too long: '/var/lib/mailman/archives/private/xx/attachments/20050915/6cfa4267/buglist.cgiquery_formatadvancedshort_desc_typeallwordssubstrshort_desccomponentXXlong_desc_typesubstringlong_descbug_file_loc_typeallwordssubstrbug_file_locbug_statusNEWbug_statusASSIGNEDbug_statusREOPENEDemailtype1substringemail1emailassigned_to21emailreporter21emailcc21emailtype2substringemail2bugidtypeincludebug_idvoteschfieldfromchfieldtoNowchfieldvaluefield0-0-0nooptype0-0-0noopvalue0-0-0orderbugs.html' ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2005-09-17 22:02 Message: Logged In: YES user_id=75166 Upgrading to MM 2.1.6 and setting the configuration variable mm_cfg.SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = True might avoid this problem ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1293267&group_id=103 From noreply at sourceforge.net Tue Sep 20 14:56:21 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 20 Sep 2005 05:56:21 -0700 Subject: [ mailman-Bugs-1296367 ] can't subscribe - does not like recipient Message-ID: Bugs item #1296367, was opened at 2005-09-20 14:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1296367&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: None Status: Open Resolution: None Priority: 5 Submitted By: troels knak-nielsen (swaxi) Assigned to: Nobody/Anonymous (nobody) Summary: can't subscribe - does not like recipient Initial Comment: I have a general problem subscribing to lists at sourceforge. I get the confirmation-mail, which tells me to reply. When I do, I recieve a failure-notice from my mail-agent. Appearently sourceforge doesn't like me. How's that ? Copy of failurenotice below : Return-Path: <> Delivered-To: troels at kyberfabrikken.dk Received: (qmail 17352 invoked for bounce); 20 Sep 2005 12:40:39 -0000 Date: 20 Sep 2005 12:40:39 -0000 From: MAILER-DAEMON at freja.yanet.dk To: troels at kyberfabrikken.dk Subject: failure notice X-UM-Flags: \SEEN Hi. This is the qmail-send program at freja.yanet.dk. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : 66.35.250.206 does not like recipient. Remote host said: 550-Verification failed for 550-Called: 81.7.136.34 550-Sent: RCPT TO: 550-Response: 553 sorry, your envelope sender has been denied (#5.7.1) 550 Sender verify failed Giving up on 66.35.250.206. --- Below this line is a copy of the message. Return-Path: Received: (qmail 17341 invoked by uid 613); 20 Sep 2005 12:40:32 -0000 Received: from localhost (HELO Yanetdkwebmail) (127.0.0.1) by localhost with SMTP; 20 Sep 2005 12:40:32 -0000 Received: from client 212.242.176.101 for UebiMiau2.7 (webmail client); Tue, 20 Sep 2005 14:40:32 +0100 Date: Tue, 20 Sep 2005 14:40:32 +0100 From: "Troels Knak-Nielsen" To: simpletest-support-request at lists.sourceforge.net Reply-to: "Troels Knak-Nielsen" Subject: SV: Simpletest-support -- confirmation of subscription -- request 766612 X-Priority: 3 X-Mailer: Yanet.dk - webmail X-Original-IP: 212.242.176.101 Content-Transfer-Encoding: 8bit Return-Path: troels at kyberfabrikken.dk X-MSMail-Priority: Medium Importance: Medium Content-Type: text/plain; charset="iso-8859-1"; MIME-Version: 1.0 -- mvh troels www.kyberfabrikken.dk --------- Original Besked -------- fra: simpletest-support-request at lists.sourceforge.net Til: troels at kyberfabrikken.dk Emne: Simpletest-support -- confirmation of subscription -- request 766612 Dato: 20/09/05 13:40 > > Simpletest-support -- confirmation of subscription -- request 766612 > > We have received a request from 212.242.176.101 for subscription of > your email address, <troels at kyberfabrikken.dk>, to the > simpletest-support at lists.sourceforge.net mailing list. To confirm the > request, please send a message to > simpletest-support-request at lists.sourceforge.net, and either: > > - maintain the subject line as is (the reply's additional "Re:" is > ok), > > - or include the following line - and only the following line - in the > message body: > > confirm 766612 > > (Simply sending a 'reply' to this message should work from most email > interfaces, since that usually leaves the subject line in the right > form.) > > If you do not wish to subscribe to this list, please simply disregard > this message. Send questions to > simpletest-support-admin at lists.sourceforge.net. > > > > > ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1296367&group_id=103 From noreply at sourceforge.net Wed Sep 21 06:30:05 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 20 Sep 2005 21:30:05 -0700 Subject: [ mailman-Bugs-1230865 ] spam filters get removed when changing other privacy pages Message-ID: Bugs item #1230865, was opened at 2005-07-01 10:51 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1230865&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Alex (ams001) Assigned to: Nobody/Anonymous (nobody) Summary: spam filters get removed when changing other privacy pages Initial Comment: Originally reported in 1020013 http://sourceforge.net/tracker/?group_id=103&atid=100103&func=detail&aid=1020013 This problem still very annoyingly ocurrs in the 2.1.6 release which appears not to include the patch submitted. I have updated the patch against 2.1.6 and included it below. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-09-21 04:30 Message: Logged In: YES user_id=67709 Fixed in CVS. (2.2.0a0) ---------------------------------------------------------------------- Comment By: Alex (ams001) Date: 2005-07-08 17:29 Message: Logged In: YES user_id=1156173 Unfortunately this patch does not fix all occurances of the problem. I can reliably "lose" all spam filters entered by going directly to the spam filter section after logging out. To reproduce: 1. Login as list admin 2. Goto Privacy / Spam filters and create a spam filter 3. Logout 4. Modify logout URL from ...//logout to ...//privacy/spam 5. Enter password and observe absense of Spam filter. The worrying thing is that it appears to be the login through the privacy/spam script that kills the spam filter. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1230865&group_id=103 From noreply at sourceforge.net Wed Sep 21 18:03:03 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 21 Sep 2005 09:03:03 -0700 Subject: [ mailman-Bugs-1059637 ] Leave choice on obfuscation method to sysadmin Message-ID: Bugs item #1059637, was opened at 2004-11-03 12:14 Message generated for change (Comment added) made by magicfab You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alster (alster) Assigned to: Nobody/Anonymous (nobody) Summary: Leave choice on obfuscation method to sysadmin Initial Comment: As far as I know, currently the way pipermail obfuscates email addresses is hardcoded to "user at domain.com". This is really easy to harvest. It may be a better idea to leave the method of obfuscation to the mailman (sys)admin (not list admin). This will result in increased diversity of obfuscation methods on the several pipermail setups and thus to decreased harvesting. ---------------------------------------------------------------------- Comment By: Fabi?n A. Rodr?guez S. (magicfab) Date: 2005-09-21 12:03 Message: Logged In: YES user_id=92045 I agree this should be addressed as more and more bots & agents harvest public lists for this information. Even private lists that are not tuning 2.1.6 may be vulnerable to this harvesting method. I'd like to suggest to use a random obfuscation method *for each message* . ---------------------------------------------------------------------- Comment By: Jean Delvare (khali) Date: 2005-07-18 06:15 Message: Logged In: YES user_id=66405 I would second this request. The current obfuscation scheme is next to useless. I understand that it would make little sense hardcoding a more complex obfuscation scheme, as it could easily be reverse-engineered. However, if the obfuscation method was left to the administrator, there would be virtually as many different obfuscation schemes as sites, so reverse-engineering would be much more difficult, if impossible. As a side note, I wonder why there is no option in mailman to plain discard the e-mail addresses from the Archive. This should be even more simple to implement, and sufficient at least for my own needs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_id=103 From noreply at sourceforge.net Wed Sep 21 18:21:55 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 21 Sep 2005 09:21:55 -0700 Subject: [ mailman-Bugs-1059637 ] Leave choice on obfuscation method to sysadmin Message-ID: Bugs item #1059637, was opened at 2004-11-03 12:14 Message generated for change (Comment added) made by magicfab You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alster (alster) Assigned to: Nobody/Anonymous (nobody) Summary: Leave choice on obfuscation method to sysadmin Initial Comment: As far as I know, currently the way pipermail obfuscates email addresses is hardcoded to "user at domain.com". This is really easy to harvest. It may be a better idea to leave the method of obfuscation to the mailman (sys)admin (not list admin). This will result in increased diversity of obfuscation methods on the several pipermail setups and thus to decreased harvesting. ---------------------------------------------------------------------- Comment By: Fabi?n A. Rodr?guez S. (magicfab) Date: 2005-09-21 12:21 Message: Logged In: YES user_id=92045 This would also affect messages that are already archived or the existing methods for archival of messages. See this in the Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.034.htp Some docs on making your lists less vulnerable to harvesting: http://www.list.org/mailman-member/node40.html Other related threads: http://mail.python.org/pipermail/mailman-developers/2004-February/016569.html http://zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanProblems ---------------------------------------------------------------------- Comment By: Fabi?n A. Rodr?guez S. (magicfab) Date: 2005-09-21 12:03 Message: Logged In: YES user_id=92045 I agree this should be addressed as more and more bots & agents harvest public lists for this information. Even private lists that are not tuning 2.1.6 may be vulnerable to this harvesting method. I'd like to suggest to use a random obfuscation method *for each message* . ---------------------------------------------------------------------- Comment By: Jean Delvare (khali) Date: 2005-07-18 06:15 Message: Logged In: YES user_id=66405 I would second this request. The current obfuscation scheme is next to useless. I understand that it would make little sense hardcoding a more complex obfuscation scheme, as it could easily be reverse-engineered. However, if the obfuscation method was left to the administrator, there would be virtually as many different obfuscation schemes as sites, so reverse-engineering would be much more difficult, if impossible. As a side note, I wonder why there is no option in mailman to plain discard the e-mail addresses from the Archive. This should be even more simple to implement, and sufficient at least for my own needs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_id=103 From noreply at sourceforge.net Thu Sep 22 07:29:30 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 21 Sep 2005 22:29:30 -0700 Subject: [ mailman-Patches-1298355 ] Select language(s) when install Message-ID: Patches item #1298355, was opened at 2005-09-22 05:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&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: configure/install Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Select language(s) when install Initial Comment: While the number of translated languages is growing, most users are using only a few languages. With this patch, the site admin can select his/her required languages by an option to the configure script by `--with-languages' and can considerably reduce the install size. This patch is for 2.2.0a0 (most recent CVS as of writing) but also applicable to 2.1.6 except that you may have to regenerate configure script by invoing autoconf command. Patch usage: % cd mailman (src directory) % patch -p0 < /path/to/install_selected_language.patch.txt Configure usage: % ./configure --with-languages="ja fr" ... en+ja+fr % ./configure --with-languages="" ... all available languages % ./configure .... all available languages % ./configure --with-languages="none" ... English only Japanese and Korean codecs are no longer installed by `make install' but availability is checked during the configure run and urge to install if they are absent when CJK languages are included in the language list. I hope skilled developers can review this patch before I check in to the CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&group_id=103 From noreply at sourceforge.net Thu Sep 22 07:35:37 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 21 Sep 2005 22:35:37 -0700 Subject: [ mailman-Patches-1298355 ] Select language(s) when install Message-ID: Patches item #1298355, was opened at 2005-09-22 05:29 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&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: configure/install Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Select language(s) when install Initial Comment: While the number of translated languages is growing, most users are using only a few languages. With this patch, the site admin can select his/her required languages by an option to the configure script by `--with-languages' and can considerably reduce the install size. This patch is for 2.2.0a0 (most recent CVS as of writing) but also applicable to 2.1.6 except that you may have to regenerate configure script by invoing autoconf command. Patch usage: % cd mailman (src directory) % patch -p0 < /path/to/install_selected_language.patch.txt Configure usage: % ./configure --with-languages="ja fr" ... en+ja+fr % ./configure --with-languages="" ... all available languages % ./configure .... all available languages % ./configure --with-languages="none" ... English only Japanese and Korean codecs are no longer installed by `make install' but availability is checked during the configure run and urge to install if they are absent when CJK languages are included in the language list. I hope skilled developers can review this patch before I check in to the CVS. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-09-22 05:35 Message: Logged In: YES user_id=67709 Oops, I forgot to check `Upload and Attach a File'. ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&group_id=103 From noreply at sourceforge.net Thu Sep 22 17:17:47 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 22 Sep 2005 08:17:47 -0700 Subject: [ mailman-Bugs-1298841 ] withlist locks with -l and -a switches Message-ID: Bugs item #1298841, was opened at 2005-09-22 10:17 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=1298841&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: adrianwi (adrianwi) Assigned to: Nobody/Anonymous (nobody) Summary: withlist locks with -l and -a switches Initial Comment: The following is from Thanks to Mark for the reply and explaniation. This probably belongs in both the command line scripts and documentation category. >customchange.py is located at the root installation directory >of Mailman. >It contains: > ># Python function to make custom changes >def customchange(m): > curlist = m.real_name > curlist = curlist.lower() > print 'Current list is: ' + curlist > if curlist.startswith('apples'): > print 'Starts with apples! Current host_name is: ' + m.host_name > print 'Changing hostname now...' > m.host_name = 'lists.newlistname.org' > m.Save() > > >This script is then run with withlist: > >./withlist -a -l -r customchange > > >After preforming this, I noticed that the web interface for lists >are not accessible and that the locks directory contains at >least two lock files for every list. This probably should be considered a bug in withlist or at least a documentation deficiency. The problem is when running withlist with -l and -a switches, only the last list is unlocked by withlist. Thus you need to unlock the lists in your script. In your example you could do this two ways 1) make sure you unlock every list, processed or not. # Python function to make custom changes def customchange(m): curlist = m.real_name curlist = curlist.lower() print 'Current list is: ' + curlist if curlist.startswith('apples'): print 'Starts with apples! Current host_name is: ' + m.host_name print 'Changing hostname now...' m.host_name = 'lists.newlistname.org' m.Save() m.Unlock() 2) run withlist with -a but without -l and only lock the lists you're changing. # Python function to make custom changes def customchange(m): curlist = m.real_name curlist = curlist.lower() print 'Current list is: ' + curlist if curlist.startswith('apples'): m.Lock() print 'Starts with apples! Current host_name is: ' + m.host_name print 'Changing hostname now...' m.host_name = 'lists.newlistname.org' m.Save() m.Unlock() 3) Safer still is like 2) with the addition of try: finally: # Python function to make custom changes def customchange(m): curlist = m.real_name curlist = curlist.lower() print 'Current list is: ' + curlist if curlist.startswith('apples'): try: m.Lock() print 'Starts with apples! Current host_name is: ' + m.host_name print 'Changing hostname now...' m.host_name = 'lists.newlistname.org' m.Save() finally: m.Unlock() -- Mark Sapiro ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1298841&group_id=103 From noreply at sourceforge.net Fri Sep 23 01:17:40 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 22 Sep 2005 16:17:40 -0700 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 20:14 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- >Comment By: Brad Knowles (shub) Date: 2005-09-22 23:17 Message: Logged In: YES user_id=18417 Okay, I took Mark's comments and incorporated them. Adrian Wells also pointed out a log file difference between Mailman 2.1.5 and 2.1.6 that caused the summary of the "smtp" log to be munged. I've now fixed these bugs, deleted the old file, and uploaded the new one (version 0.0.12). Thanks! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-11 02:22 Message: Logged In: YES user_id=1123998 Oooops! I mistakenly thought I could add the mmdsr.patch as a downloadable file, but I can't so here it is. Watch out for wrapped lines ... --- mmdsr.orig 2005-09-06 20:37:53.000000000 -0700 +++ mmdsr 2005-09-10 18:33:14.532393572 -0700 @@ -132,6 +132,7 @@ MMDIR="/usr/local/mailman" TMPDIR="/tmp" +LOGDIR="/var/log/mailman" ############################################################################### # Maximum number of subdirectory entries to display in report @@ -234,9 +235,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "post" ] ; then @@ -304,9 +305,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "error" ] ; then @@ -453,4 +454,4 @@ $CAT $TMP fi -$RM $TMP +$RM -f $TMP $TMPLOG ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-11 02:16 Message: Logged In: YES user_id=1123998 I tried the script and other than the expected site specific changes, I found two issues which are both addressed by the patch in the mmdsr.patch file. 1) Mailman's log files are not necessarily in $var_prefix/logs/ - they can be in any directory. The patch adds a LOGDIR directory independant of MMDIR. 2) The $TMPLOG file is not removed at completion. The patch removes it. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-06 14:06 Message: Logged In: YES user_id=18417 Okay, I've deleted the old version of the mmdsr script that was attached, and uploaded the latest version. This is what we're currently using to monitor the lists on python.org, and we have found it very useful. Any comments you may have will be appreciated. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-02-22 20:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 15:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 08:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Fri Sep 23 22:00:06 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 23 Sep 2005 13:00:06 -0700 Subject: [ mailman-Patches-1301983 ] Fix for lack of date header in new list notification emails Message-ID: Patches item #1301983, was opened at 2005-09-23 20:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1301983&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: Bjorn-Erik Townsend (eriktown) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for lack of date header in new list notification emails Initial Comment: This is a fix for Bug 1212066, where the notification email sent to the Mailman site owner after a new list is created using the Web UI does not include a Date header as required by RFC 2822. The underlying issue appears to be that the notification email is being sent with an outdated or incorrect method (outq.enqueue instead of msg.send). I simply took the same code that is used in the newlist script to do this and added it here, along with the code that it ensures that the header uses the site owner list's preferred language. This patch also includes a fix for a bug that has not been reported, in which notification emails sent upon list removal experience the same issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1301983&group_id=103 From noreply at sourceforge.net Fri Sep 23 23:45:33 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 23 Sep 2005 14:45:33 -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-09-23 21:45 Message: Logged In: YES user_id=75166 mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of $prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the problem was not present in patches for previous MM versions. In some circumstances, after running $prefix/bin/arch --wipe, subsequent post to a list my be generated using the wrong archiver. Examining index pages in the archives of a list will show if this problem has affected that list. Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe should resolve the problem. ---------------------------------------------------------------------- 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 Sat Sep 24 06:34:23 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 23 Sep 2005 21:34:23 -0700 Subject: [ mailman-Bugs-1212066 ] 2.1.6rc4 mailing list creation mail has no Date: header Message-ID: Bugs item #1212066, was opened at 2005-05-31 15:08 Message generated for change (Comment added) made by eriktown You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1212066&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Anton R. Ivanov (arivanov) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.6rc4 mailing list creation mail has no Date: header Initial Comment: This is cosmetic (mostly) The mail with a subject: Mailing list creation request for list LISTNAME is sent without a Date: header which makes Mozilla and other mail clients display it as sent on 1/01/1970 A. ---------------------------------------------------------------------- Comment By: Bjorn-Erik Townsend (eriktown) Date: 2005-09-24 04:34 Message: Logged In: YES user_id=73240 I submitted a patch for this: https://sourceforge.net/tracker/index.php?func=detail&aid=1301983&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1212066&group_id=103 From noreply at sourceforge.net Sun Sep 25 05:11:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 24 Sep 2005 20:11:36 -0700 Subject: [ mailman-Bugs-1212066 ] 2.1.6rc4 mailing list creation mail has no Date: header Message-ID: Bugs item #1212066, was opened at 2005-05-31 15:08 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1212066&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Anton R. Ivanov (arivanov) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.6rc4 mailing list creation mail has no Date: header Initial Comment: This is cosmetic (mostly) The mail with a subject: Mailing list creation request for list LISTNAME is sent without a Date: header which makes Mozilla and other mail clients display it as sent on 1/01/1970 A. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-09-25 03:11 Message: Logged In: YES user_id=67709 Fixed in CVS (Mailman/MTA/Manual.py) ---------------------------------------------------------------------- Comment By: Bjorn-Erik Townsend (eriktown) Date: 2005-09-24 04:34 Message: Logged In: YES user_id=73240 I submitted a patch for this: https://sourceforge.net/tracker/index.php?func=detail&aid=1301983&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1212066&group_id=103 From noreply at sourceforge.net Sun Sep 25 05:14:00 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 24 Sep 2005 20:14:00 -0700 Subject: [ mailman-Patches-1301983 ] Fix for lack of date header in new list notification emails Message-ID: Patches item #1301983, was opened at 2005-09-23 20:00 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1301983&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: Closed >Resolution: Fixed Priority: 5 Submitted By: Bjorn-Erik Townsend (eriktown) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for lack of date header in new list notification emails Initial Comment: This is a fix for Bug 1212066, where the notification email sent to the Mailman site owner after a new list is created using the Web UI does not include a Date header as required by RFC 2822. The underlying issue appears to be that the notification email is being sent with an outdated or incorrect method (outq.enqueue instead of msg.send). I simply took the same code that is used in the newlist script to do this and added it here, along with the code that it ensures that the header uses the site owner list's preferred language. This patch also includes a fix for a bug that has not been reported, in which notification emails sent upon list removal experience the same issue. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-09-25 03:13 Message: Logged In: YES user_id=67709 Fixed it in a slightly different way. Thanks anyway for the direction of where to fix. See CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1301983&group_id=103 From noreply at sourceforge.net Mon Sep 26 13:31:09 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 26 Sep 2005 04:31:09 -0700 Subject: [ mailman-Bugs-1304742 ] templates/ru/userpass.txt typo Message-ID: Bugs item #1304742, was opened at 2005-09-26 15:31 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=1304742&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ilya Pizik (polzun) Assigned to: Nobody/Anonymous (nobody) Summary: templates/ru/userpass.txt typo Initial Comment: $(fqdn_lname) should be changed to %(fqdn_lname) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1304742&group_id=103 From noreply at sourceforge.net Tue Sep 27 15:49:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Sep 2005 06:49:48 -0700 Subject: [ mailman-Bugs-1305881 ] Problem creating list via web Message-ID: Bugs item #1305881, was opened at 2005-09-27 15:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster at mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 From noreply at sourceforge.net Tue Sep 27 16:21:21 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Sep 2005 07:21:21 -0700 Subject: [ mailman-Bugs-1305881 ] Problem creating list via web Message-ID: Bugs item #1305881, was opened at 2005-09-27 09:49 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster at mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-27 10:21 Message: Logged In: YES user_id=12800 Run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 From noreply at sourceforge.net Tue Sep 27 16:32:26 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Sep 2005 07:32:26 -0700 Subject: [ mailman-Bugs-1305881 ] Problem creating list via web Message-ID: Bugs item #1305881, was opened at 2005-09-27 15:49 Message generated for change (Comment added) made by jontek You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) Status: Closed Resolution: Invalid Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster at mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- >Comment By: Jon (jontek) Date: 2005-09-27 16:32 Message: Logged In: YES user_id=1352490 Thanks but it doesn't still work. I have done: /usr/local/mailman/bin/check_perms -f and fixed all the problems, but it still doesn't work. :o( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-27 16:21 Message: Logged In: YES user_id=12800 Run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 From noreply at sourceforge.net Tue Sep 27 16:39:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Sep 2005 07:39:48 -0700 Subject: [ mailman-Bugs-1305881 ] Problem creating list via web Message-ID: Bugs item #1305881, was opened at 2005-09-27 09:49 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) >Status: Open >Resolution: None Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster at mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 10:32 Message: Logged In: YES user_id=1352490 Thanks but it doesn't still work. I have done: /usr/local/mailman/bin/check_perms -f and fixed all the problems, but it still doesn't work. :o( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-27 10:21 Message: Logged In: YES user_id=12800 Run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 From noreply at sourceforge.net Tue Sep 27 16:44:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Sep 2005 07:44:10 -0700 Subject: [ mailman-Bugs-1305881 ] Problem creating list via web Message-ID: Bugs item #1305881, was opened at 2005-09-27 15:49 Message generated for change (Comment added) made by jontek You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster at mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- >Comment By: Jon (jontek) Date: 2005-09-27 16:44 Message: Logged In: YES user_id=1352490 #/usr/local/mailman>/usr/local/mailman/bin/check_perms No problems found #/usr/local/mailman> ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 16:32 Message: Logged In: YES user_id=1352490 Thanks but it doesn't still work. I have done: /usr/local/mailman/bin/check_perms -f and fixed all the problems, but it still doesn't work. :o( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-27 16:21 Message: Logged In: YES user_id=12800 Run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_id=103