From noreply at sourceforge.net Tue Aug 1 00:13:49 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 31 Jul 2006 15:13:49 -0700 Subject: [ mailman-Feature Requests-403066 ] Auto Approval of subscriptions for certain domains Message-ID: Feature Requests item #403066, was opened at 2001-01-01 09:27 Message generated for change (Comment added) made by jimpop You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&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: Closed Resolution: Accepted Priority: 3 Submitted By: Mark Tearle (mtearle) Assigned to: Mark Sapiro (msapiro) Summary: Auto Approval of subscriptions for certain domains Initial Comment: A patch to enable automatic approval for certain domains, eg people in the example.com are automatically approved all others have to wait for the moderator ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-07-31 18:13 Message: Logged In: YES user_id=3142 New feature request for this patch, seeking feedback. Most of my lists automatically moderate new subscribers, in addition some require admin approval for subsciption, except for domains listed in subscribe_auto_approval. A nice addition to this patch would be to not moderate subscribers whose domains are listed in subscribe_auto_approval. ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2006-03-25 22:21 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-03-12 22:12 Message: Logged In: YES user_id=3142 I've successfully applied this against a v2.1.8 system and it works well. Thanks!! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-03-11 13:36 Message: Logged In: YES user_id=1123998 The attached patch is against a 2.1.8a1 installed base (installed because it patches Defaults.py and not Defaults.py.in). It is a modification and extension of the original patch. It implements a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. It implements the original intent if one just uses regexps that match domains. This will go in Mailman 2.2, but it would be nice to get some feedback from people who are interested in this feature and are willing to try the patch. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 08:31 Message: Logged In: YES user_id=34209 Is this still necessary with Mailman 2.1, which has more 'automatic' options (as well as 'memberadaptors') ? In any case, the patch is likely heavily out of date by now, I'm moving this to Feature Requests for now. Feel free to respond if you (still) have a need. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_id=103 From noreply at sourceforge.net Tue Aug 1 01:04:47 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 31 Jul 2006 16:04:47 -0700 Subject: [ mailman-Patches-1532081 ] with long lists, findmember option got forgotten Message-ID: Patches item #1532081, was opened at 2006-08-01 01:04 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1532081&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: RISKO Gergely (errge) Assigned to: Nobody/Anonymous (nobody) Summary: with long lists, findmember option got forgotten Initial Comment: After the admin do a filtering on members, the generated first letter based URLs don't inherit the filter regex. This patch fixes that bug. Reported in debian as #359721. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1532081&group_id=103 From noreply at sourceforge.net Tue Aug 1 03:51:45 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 31 Jul 2006 18:51:45 -0700 Subject: [ mailman-Bugs-1531675 ] ARCHIVE_TO_MBOX=1 broken Message-ID: Bugs item #1531675, was opened at 2006-07-31 04:23 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1531675&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: Closed >Resolution: Fixed Priority: 5 Submitted By: Ross Golder (rossigee) Assigned to: Nobody/Anonymous (nobody) Summary: ARCHIVE_TO_MBOX=1 broken Initial Comment: While looking into an archiving problem on mail.gnome.org, where we use our own external archiver (ARCHIVE_TO_MBOX was set to 1), Owen Taylor discovered the following bug causing it to ignore this setting: >From /usr/lib/mailman/Mailman/Defaults.py: # ARCHIVE_TO_MBOX #-1 - do not do any archiving # 0 - do not archive to mbox, use builtin mailman html archiving only # 1 - archive to mbox to use an external archiving mechanism only # 2 - archive to both mbox and builtin mailman html archiving - # use this to make both external archiving mechanism work and # mailman's builtin html archiving. the flat mail file can be # useful for searching, external archivers, etc. ARCHIVE_TO_MBOX = 2 Now, while that's not particularly clear, I can certainly see why one might assume that we wanted a setting, of '1', but if you look at the code we see: if mm_cfg.ARCHIVE_TO_MBOX in (1, 2): self.__archive_to_mbox(msg) if mm_cfg.ARCHIVE_TO_MBOX == 1: # Archive to mbox only. return txt = str(msg) # should we use the internal or external archiver? [...] So, ARCHIVE_TO_MBOX=1 skips both the internal *and* external archivers, and archives only to the MBOX files. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-07-31 18:51 Message: Logged In: YES user_id=1123998 This really isn't a bug. It is a case of things changing and the documentation not keeping pace. (What's the difference between a bug and an error? - A bug is fixed by changing the code; an error is fixed by changing the documentation.) The misleading part is: # 1 - archive to mbox to use an external archiving mechanism only. This should really say: # 1 - archive to mbox only The PUBLIC_EXTERNAL_ARCHIVER and PRIVATE_EXTERNAL_ARCHIVER settings were added significantly after the ARCHIVE_TO_MBOX setting. Prior to this, 'external archivers' had to read the .mbox file which is why the setting of '1' was described as it was. I've changed the descriptions in the Subversion trunk. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1531675&group_id=103 From noreply at sourceforge.net Tue Aug 1 20:40:42 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 01 Aug 2006 11:40:42 -0700 Subject: [ mailman-Bugs-1532638 ] can't unsub addr with double-at Message-ID: Bugs item #1532638, was opened at 2006-08-01 11:40 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=1532638&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: Cameron (thenoob2) Assigned to: Nobody/Anonymous (nobody) Summary: can't unsub addr with double-at Initial Comment: Mailman version 2.1.8. Python 2.4.1 as shipped in Mandriva 2006. One of our list owners mass-subscribed an address with the at-sign doubled. fubar@@example.net. That pattern should be added to whatever input sanitization mass-subscribe uses. Once it was in there, he tried to mass unsubscribe it. Which failed, and caused a nightly error mailed to the mailman user. Traceback (most recent call last): File "bin/remove_members", line 186, in ? main() File "bin/remove_members", line 176, in main admin_notif, userack) File "/u/m/mcal/run/Mailman/MailList.py", line 1014, in ApprovedDeleteMember self.removeMember(emailaddr) File "/u/m/mcal/run/Mailman/OldStyleMemberships.py", line 220, in removeMember self.__assertIsMember(member) File "/u/m/mcal/run/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: fubar@ The bad address shows up in Membership Management but you can't do anything with it. Its mail gets disabled for excessive bouncing. Not knowing how to drive bin/config_list, my workaround was Perl edit in place on the pickle. perl -pi -e 's/fubar\@\@/fubar\@x/g' list/config.pck and then I could remove fubar at xexample.net with bin/remove_members. Ugly, eh? I wonder if this is the same bug as 551730. Thanks for working on this, Cameron ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1532638&group_id=103 From noreply at sourceforge.net Tue Aug 1 23:19:50 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 01 Aug 2006 14:19:50 -0700 Subject: [ mailman-Bugs-1532638 ] can't unsub addr with double-at Message-ID: Bugs item #1532638, was opened at 2006-08-01 11:40 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1532638&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: Cameron (thenoob2) Assigned to: Nobody/Anonymous (nobody) Summary: can't unsub addr with double-at Initial Comment: Mailman version 2.1.8. Python 2.4.1 as shipped in Mandriva 2006. One of our list owners mass-subscribed an address with the at-sign doubled. fubar@@example.net. That pattern should be added to whatever input sanitization mass-subscribe uses. Once it was in there, he tried to mass unsubscribe it. Which failed, and caused a nightly error mailed to the mailman user. Traceback (most recent call last): File "bin/remove_members", line 186, in ? main() File "bin/remove_members", line 176, in main admin_notif, userack) File "/u/m/mcal/run/Mailman/MailList.py", line 1014, in ApprovedDeleteMember self.removeMember(emailaddr) File "/u/m/mcal/run/Mailman/OldStyleMemberships.py", line 220, in removeMember self.__assertIsMember(member) File "/u/m/mcal/run/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: fubar@ The bad address shows up in Membership Management but you can't do anything with it. Its mail gets disabled for excessive bouncing. Not knowing how to drive bin/config_list, my workaround was Perl edit in place on the pickle. perl -pi -e 's/fubar\@\@/fubar\@x/g' list/config.pck and then I could remove fubar at xexample.net with bin/remove_members. Ugly, eh? I wonder if this is the same bug as 551730. Thanks for working on this, Cameron ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-08-01 14:19 Message: Logged In: YES user_id=1123998 Have you tried checking 'unsub' on the admin membership list and 'Submit Your Changes'? If that doesn't work, see http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.013.htp for the 'withlist' method. For what it's worth, I tried mass subscribing msapiro@@value.net with both the distribution 2.1.5 and my 2.1.8+ working copy and I get "Bad/Invalid email address". Are you sure this is how the subscribe was done? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1532638&group_id=103 From noreply at sourceforge.net Wed Aug 2 06:21:41 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 01 Aug 2006 21:21:41 -0700 Subject: [ mailman-Bugs-1532638 ] can't unsub addr with double-at Message-ID: Bugs item #1532638, was opened at 2006-08-01 11:40 Message generated for change (Comment added) made by thenoob2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1532638&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: Cameron (thenoob2) Assigned to: Nobody/Anonymous (nobody) Summary: can't unsub addr with double-at Initial Comment: Mailman version 2.1.8. Python 2.4.1 as shipped in Mandriva 2006. One of our list owners mass-subscribed an address with the at-sign doubled. fubar@@example.net. That pattern should be added to whatever input sanitization mass-subscribe uses. Once it was in there, he tried to mass unsubscribe it. Which failed, and caused a nightly error mailed to the mailman user. Traceback (most recent call last): File "bin/remove_members", line 186, in ? main() File "bin/remove_members", line 176, in main admin_notif, userack) File "/u/m/mcal/run/Mailman/MailList.py", line 1014, in ApprovedDeleteMember self.removeMember(emailaddr) File "/u/m/mcal/run/Mailman/OldStyleMemberships.py", line 220, in removeMember self.__assertIsMember(member) File "/u/m/mcal/run/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: fubar@ The bad address shows up in Membership Management but you can't do anything with it. Its mail gets disabled for excessive bouncing. Not knowing how to drive bin/config_list, my workaround was Perl edit in place on the pickle. perl -pi -e 's/fubar\@\@/fubar\@x/g' list/config.pck and then I could remove fubar at xexample.net with bin/remove_members. Ugly, eh? I wonder if this is the same bug as 551730. Thanks for working on this, Cameron ---------------------------------------------------------------------- >Comment By: Cameron (thenoob2) Date: 2006-08-01 21:21 Message: Logged In: YES user_id=1207635 It's possible the bad address has been in there since before we upgraded from 2.1.6 to 2.1.8. I don't know how it got subscribed. These are very small lists (25 subscribers on this one) and most subscriptions are by the list owner through the Web interface. But the system was installed at 2.1.6. >Have you tried checking 'unsub' on the admin >membership list and 'Submit Your Changes'? Yes that is the second thing I tried, after bin/remove_members (as the mailman user) threw the error shown. Result was a red error message at the top of the new form, something like can't mass unsubscribe a non-subscribed address. I've used bin/withlist to move a list from one virtual domain to another. That procedure is documented in the comments at the top of bin/fix_url.py. I'll try it next time I have a broken list. Thanks. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-08-01 14:19 Message: Logged In: YES user_id=1123998 Have you tried checking 'unsub' on the admin membership list and 'Submit Your Changes'? If that doesn't work, see http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.013.htp for the 'withlist' method. For what it's worth, I tried mass subscribing msapiro@@value.net with both the distribution 2.1.5 and my 2.1.8+ working copy and I get "Bad/Invalid email address". Are you sure this is how the subscribe was done? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1532638&group_id=103 From noreply at sourceforge.net Wed Aug 2 13:11:57 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 02 Aug 2006 04:11:57 -0700 Subject: [ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File Message-ID: Bugs item #1533058, was opened at 2006-08-02 13:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&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: chris-taylor (chris-taylor) Assigned to: Nobody/Anonymous (nobody) Summary: Duplicate Entries in Aliases/Virtual-Mailman File Initial Comment: Hello, we are using mailman-2.1.7 in cooperation with the postfix mta. While fiddling around with pipe transport we recovered the following problem: Create a mailing list named: students Create a mailing list named: students-request Result: A duplicated entry for students-request in the alias file and in the virtual-mailman file. Shouldn't there be a check for avoiding duplicate entries? The postalias command reports this duplicate entry.... BTW: The postfix-to-mailman.py script also is not able to handle the duplicate entries.... Regards Christian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&group_id=103 From noreply at sourceforge.net Wed Aug 2 14:15:24 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 02 Aug 2006 05:15:24 -0700 Subject: [ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File Message-ID: Bugs item #1533058, was opened at 2006-08-02 07:11 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&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: chris-taylor (chris-taylor) Assigned to: Nobody/Anonymous (nobody) Summary: Duplicate Entries in Aliases/Virtual-Mailman File Initial Comment: Hello, we are using mailman-2.1.7 in cooperation with the postfix mta. While fiddling around with pipe transport we recovered the following problem: Create a mailing list named: students Create a mailing list named: students-request Result: A duplicated entry for students-request in the alias file and in the virtual-mailman file. Shouldn't there be a check for avoiding duplicate entries? The postalias command reports this duplicate entry.... BTW: The postfix-to-mailman.py script also is not able to handle the duplicate entries.... Regards Christian ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-02 08:15 Message: Logged In: YES user_id=12800 Because each mailing list really consists of a number of aliases, of which -request is one, you cannot create a mailing list witht he same basename and -request. While this won't change, perhaps Mailman should refuse to create such -request mailing lists (and -owner, -bounces, etc.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&group_id=103 From noreply at sourceforge.net Wed Aug 2 15:36:45 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 02 Aug 2006 06:36:45 -0700 Subject: [ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File Message-ID: Bugs item #1533058, was opened at 2006-08-02 13:11 Message generated for change (Comment added) made by chris-taylor You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&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: chris-taylor (chris-taylor) Assigned to: Nobody/Anonymous (nobody) Summary: Duplicate Entries in Aliases/Virtual-Mailman File Initial Comment: Hello, we are using mailman-2.1.7 in cooperation with the postfix mta. While fiddling around with pipe transport we recovered the following problem: Create a mailing list named: students Create a mailing list named: students-request Result: A duplicated entry for students-request in the alias file and in the virtual-mailman file. Shouldn't there be a check for avoiding duplicate entries? The postalias command reports this duplicate entry.... BTW: The postfix-to-mailman.py script also is not able to handle the duplicate entries.... Regards Christian ---------------------------------------------------------------------- >Comment By: chris-taylor (chris-taylor) Date: 2006-08-02 15:36 Message: Logged In: YES user_id=994602 The refusal of listnames ending with the "administrative extensions" (like -bounces etc.) sounds good to me. But maybe other users schould comment if this restriction is viable for them..... Because there might be users who want to create lists like: house-owner feature-request etc. This is no problem as long as there are no lists named house or feature.... Thank you for this good piece of software Christian ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-02 14:15 Message: Logged In: YES user_id=12800 Because each mailing list really consists of a number of aliases, of which -request is one, you cannot create a mailing list witht he same basename and -request. While this won't change, perhaps Mailman should refuse to create such -request mailing lists (and -owner, -bounces, etc.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&group_id=103 From noreply at sourceforge.net Wed Aug 2 15:38:36 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 02 Aug 2006 06:38:36 -0700 Subject: [ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File Message-ID: Bugs item #1533058, was opened at 2006-08-02 13:11 Message generated for change (Comment added) made by chris-taylor You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&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: chris-taylor (chris-taylor) Assigned to: Nobody/Anonymous (nobody) Summary: Duplicate Entries in Aliases/Virtual-Mailman File Initial Comment: Hello, we are using mailman-2.1.7 in cooperation with the postfix mta. While fiddling around with pipe transport we recovered the following problem: Create a mailing list named: students Create a mailing list named: students-request Result: A duplicated entry for students-request in the alias file and in the virtual-mailman file. Shouldn't there be a check for avoiding duplicate entries? The postalias command reports this duplicate entry.... BTW: The postfix-to-mailman.py script also is not able to handle the duplicate entries.... Regards Christian ---------------------------------------------------------------------- >Comment By: chris-taylor (chris-taylor) Date: 2006-08-02 15:38 Message: Logged In: YES user_id=994602 The refusal of listnames ending with the "administrative extensions" (like -bounces etc.) sounds good to me. But maybe other users schould comment if this restriction is viable for them..... Because there might be users who want to create lists like: house-owner feature-request etc. This is no problem as long as there are no lists named house or feature.... Thank you for this good piece of software Christian ---------------------------------------------------------------------- Comment By: chris-taylor (chris-taylor) Date: 2006-08-02 15:36 Message: Logged In: YES user_id=994602 The refusal of listnames ending with the "administrative extensions" (like -bounces etc.) sounds good to me. But maybe other users schould comment if this restriction is viable for them..... Because there might be users who want to create lists like: house-owner feature-request etc. This is no problem as long as there are no lists named house or feature.... Thank you for this good piece of software Christian ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-02 14:15 Message: Logged In: YES user_id=12800 Because each mailing list really consists of a number of aliases, of which -request is one, you cannot create a mailing list witht he same basename and -request. While this won't change, perhaps Mailman should refuse to create such -request mailing lists (and -owner, -bounces, etc.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&group_id=103 From noreply at sourceforge.net Wed Aug 2 15:40:13 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 02 Aug 2006 06:40:13 -0700 Subject: [ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File Message-ID: Bugs item #1533058, was opened at 2006-08-02 13:11 Message generated for change (Comment added) made by chris-taylor You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&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: chris-taylor (chris-taylor) Assigned to: Nobody/Anonymous (nobody) Summary: Duplicate Entries in Aliases/Virtual-Mailman File Initial Comment: Hello, we are using mailman-2.1.7 in cooperation with the postfix mta. While fiddling around with pipe transport we recovered the following problem: Create a mailing list named: students Create a mailing list named: students-request Result: A duplicated entry for students-request in the alias file and in the virtual-mailman file. Shouldn't there be a check for avoiding duplicate entries? The postalias command reports this duplicate entry.... BTW: The postfix-to-mailman.py script also is not able to handle the duplicate entries.... Regards Christian ---------------------------------------------------------------------- >Comment By: chris-taylor (chris-taylor) Date: 2006-08-02 15:40 Message: Logged In: YES user_id=994602 The refusal of listnames ending with the "administrative extensions" (like -bounces etc.) sounds good to me. But maybe other users schould comment if this restriction is viable for them..... Because there might be users who want to create lists like: house-owner feature-request etc. This is no problem as long as there are no lists named house or feature.... Thank you for this good piece of software Christian ---------------------------------------------------------------------- Comment By: chris-taylor (chris-taylor) Date: 2006-08-02 15:38 Message: Logged In: YES user_id=994602 The refusal of listnames ending with the "administrative extensions" (like -bounces etc.) sounds good to me. But maybe other users schould comment if this restriction is viable for them..... Because there might be users who want to create lists like: house-owner feature-request etc. This is no problem as long as there are no lists named house or feature.... Thank you for this good piece of software Christian ---------------------------------------------------------------------- Comment By: chris-taylor (chris-taylor) Date: 2006-08-02 15:36 Message: Logged In: YES user_id=994602 The refusal of listnames ending with the "administrative extensions" (like -bounces etc.) sounds good to me. But maybe other users schould comment if this restriction is viable for them..... Because there might be users who want to create lists like: house-owner feature-request etc. This is no problem as long as there are no lists named house or feature.... Thank you for this good piece of software Christian ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-02 14:15 Message: Logged In: YES user_id=12800 Because each mailing list really consists of a number of aliases, of which -request is one, you cannot create a mailing list witht he same basename and -request. While this won't change, perhaps Mailman should refuse to create such -request mailing lists (and -owner, -bounces, etc.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&group_id=103 From noreply at sourceforge.net Wed Aug 2 19:27:07 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 02 Aug 2006 10:27:07 -0700 Subject: [ mailman-Feature Requests-1533331 ] support moving lists to another mailman instance Message-ID: Feature Requests item #1533331, was opened at 2006-08-02 17:27 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=1533331&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: Eric S. Raymond (esr) Assigned to: Nobody/Anonymous (nobody) Summary: support moving lists to another mailman instance Initial Comment: I'm having to move a project off a hosting site that uses Mailman, and have discovered to my shock that there is no easy way to capture a snapshot of the list state and re-instantiate it on another Mailman instance. While this remains the case, Mailman is a prison for my data. The only way I could get even the subscriber list was by tedious screen-scraping of the membership management CGI, made more tedious because the interface only wants to show me the subscriber list in small chunks. Breaking up the list archives by month is all very well but I want to be able to get all of the traffic -- and I want to be able to upload it into another Mailman instance. I gave up on metadata such as hide and digest bits entirely; there's no equivalent of mass subscribe that would let me set those, I'd have to patch them in by hand per each subscriber address in the new list instance. The *correct* design would be to allow me to download one file that's an XML document containing subscriber list, metadata such as digest and hide bits, and the traffic. That blob should be uploadable to another Mailman instance in a way that simply re-instantiates the list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1533331&group_id=103 From noreply at sourceforge.net Wed Aug 2 19:39:10 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 02 Aug 2006 10:39:10 -0700 Subject: [ mailman-Feature Requests-1533331 ] support moving lists to another mailman instance Message-ID: Feature Requests item #1533331, was opened at 2006-08-02 13:27 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1533331&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: Eric S. Raymond (esr) Assigned to: Nobody/Anonymous (nobody) Summary: support moving lists to another mailman instance Initial Comment: I'm having to move a project off a hosting site that uses Mailman, and have discovered to my shock that there is no easy way to capture a snapshot of the list state and re-instantiate it on another Mailman instance. While this remains the case, Mailman is a prison for my data. The only way I could get even the subscriber list was by tedious screen-scraping of the membership management CGI, made more tedious because the interface only wants to show me the subscriber list in small chunks. Breaking up the list archives by month is all very well but I want to be able to get all of the traffic -- and I want to be able to upload it into another Mailman instance. I gave up on metadata such as hide and digest bits entirely; there's no equivalent of mass subscribe that would let me set those, I'd have to patch them in by hand per each subscriber address in the new list instance. The *correct* design would be to allow me to download one file that's an XML document containing subscriber list, metadata such as digest and hide bits, and the traffic. That blob should be uploadable to another Mailman instance in a way that simply re-instantiates the list. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-02 13:39 Message: Logged In: YES user_id=12800 FWIW, It's very easy to move a list if you have shell access to the server Mailman is running on. There are many security implications to allowing access to all that data via the web. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1533331&group_id=103 From noreply at sourceforge.net Wed Aug 2 19:58:56 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 02 Aug 2006 10:58:56 -0700 Subject: [ mailman-Feature Requests-1533331 ] support moving lists to another mailman instance Message-ID: Feature Requests item #1533331, was opened at 2006-08-02 17:27 Message generated for change (Comment added) made by esr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1533331&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: Eric S. Raymond (esr) Assigned to: Nobody/Anonymous (nobody) Summary: support moving lists to another mailman instance Initial Comment: I'm having to move a project off a hosting site that uses Mailman, and have discovered to my shock that there is no easy way to capture a snapshot of the list state and re-instantiate it on another Mailman instance. While this remains the case, Mailman is a prison for my data. The only way I could get even the subscriber list was by tedious screen-scraping of the membership management CGI, made more tedious because the interface only wants to show me the subscriber list in small chunks. Breaking up the list archives by month is all very well but I want to be able to get all of the traffic -- and I want to be able to upload it into another Mailman instance. I gave up on metadata such as hide and digest bits entirely; there's no equivalent of mass subscribe that would let me set those, I'd have to patch them in by hand per each subscriber address in the new list instance. The *correct* design would be to allow me to download one file that's an XML document containing subscriber list, metadata such as digest and hide bits, and the traffic. That blob should be uploadable to another Mailman instance in a way that simply re-instantiates the list. ---------------------------------------------------------------------- >Comment By: Eric S. Raymond (esr) Date: 2006-08-02 17:58 Message: Logged In: YES user_id=3060 First, that "if you have shell access" is a big if. I do not in fact have shell access to the list server, and it's a bad thing if the Mailman design assumes I do. Second, AFAIK the "easy" procedure is not documented. Third, I don't see any (additional) security implications. All the pieces of state are already available through the administration interface, they're just a royal pain in the ass to extract by hand. Finally, you should support moveable list snapshots because it gives Mailman users the guarantee that they can have *all* their data back in a transparent form whenever they need it. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-02 17:39 Message: Logged In: YES user_id=12800 FWIW, It's very easy to move a list if you have shell access to the server Mailman is running on. There are many security implications to allowing access to all that data via the web. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1533331&group_id=103 From noreply at sourceforge.net Mon Aug 7 02:02:34 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 06 Aug 2006 17:02:34 -0700 Subject: [ mailman-Feature Requests-1533331 ] support moving lists to another mailman instance Message-ID: Feature Requests item #1533331, was opened at 2006-08-02 13:27 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1533331&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: Eric S. Raymond (esr) Assigned to: Nobody/Anonymous (nobody) Summary: support moving lists to another mailman instance Initial Comment: I'm having to move a project off a hosting site that uses Mailman, and have discovered to my shock that there is no easy way to capture a snapshot of the list state and re-instantiate it on another Mailman instance. While this remains the case, Mailman is a prison for my data. The only way I could get even the subscriber list was by tedious screen-scraping of the membership management CGI, made more tedious because the interface only wants to show me the subscriber list in small chunks. Breaking up the list archives by month is all very well but I want to be able to get all of the traffic -- and I want to be able to upload it into another Mailman instance. I gave up on metadata such as hide and digest bits entirely; there's no equivalent of mass subscribe that would let me set those, I'd have to patch them in by hand per each subscriber address in the new list instance. The *correct* design would be to allow me to download one file that's an XML document containing subscriber list, metadata such as digest and hide bits, and the traffic. That blob should be uploadable to another Mailman instance in a way that simply re-instantiates the list. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-06 20:02 Message: Logged In: YES user_id=12800 Here's the procedure for moving a list with shell access: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.004.htp As for security, should the XML output include user passwords? If you're exporting via the web, probably not. If you're exporting via the shell, probably so. Also, not every installation will want to allow list owners to move their lists (e.g. python.org probably wouldn't). If I had to guess I'd say that if list owners can delete their lists, they can probably move them. See what I mean about there being issues? It's a good idea though so I've added it as a possible item for MM2.2: http://wiki.list.org/x/IQ It probably needs more discussion on mailman-developers though. ---------------------------------------------------------------------- Comment By: Eric S. Raymond (esr) Date: 2006-08-02 13:58 Message: Logged In: YES user_id=3060 First, that "if you have shell access" is a big if. I do not in fact have shell access to the list server, and it's a bad thing if the Mailman design assumes I do. Second, AFAIK the "easy" procedure is not documented. Third, I don't see any (additional) security implications. All the pieces of state are already available through the administration interface, they're just a royal pain in the ass to extract by hand. Finally, you should support moveable list snapshots because it gives Mailman users the guarantee that they can have *all* their data back in a transparent form whenever they need it. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-02 13:39 Message: Logged In: YES user_id=12800 FWIW, It's very easy to move a list if you have shell access to the server Mailman is running on. There are many security implications to allowing access to all that data via the web. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1533331&group_id=103 From noreply at sourceforge.net Tue Aug 8 11:40:28 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Aug 2006 02:40:28 -0700 Subject: [ mailman-Bugs-1536532 ] digest mails: RFC2046 non-compliance Message-ID: Bugs item #1536532, was opened at 2006-08-08 11:40 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=1536532&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: Colin Leroy (colinleroy) Assigned to: Nobody/Anonymous (nobody) Summary: digest mails: RFC2046 non-compliance Initial Comment: Hi, Mailman 2.1.6 does not respect RFC2046 when sending out digests: the end boundary of the last inner digested mail is not separated from the separator boundary between the multipart/digest main part and footer part, as described on http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/show_bug.cgi?id=998 See the attachments (broken email, hand-fixed email and diff between the two). The relevant part of RFC2046 is: RFC 2046 - page 19: NOTE: The CRLF preceding the boundary delimiter line is conceptually attached to the boundary so that it is possible to have a part that does not end with a CRLF (line break). Body parts that must be considered to end with line breaks, therefore, must have two CRLFs preceding the boundary delimiter line, the first of which is part of the preceding body part, and the second of which is part of the encapsulation boundary. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1536532&group_id=103 From noreply at sourceforge.net Wed Aug 9 08:34:28 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Aug 2006 23:34:28 -0700 Subject: [ mailman-Bugs-1536532 ] digest mails: RFC2046 non-compliance Message-ID: Bugs item #1536532, was opened at 2006-08-08 11:40 Message generated for change (Settings changed) made by colinleroy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1536532&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: Closed Resolution: None Priority: 5 Submitted By: Colin Leroy (colinleroy) Assigned to: Nobody/Anonymous (nobody) Summary: digest mails: RFC2046 non-compliance Initial Comment: Hi, Mailman 2.1.6 does not respect RFC2046 when sending out digests: the end boundary of the last inner digested mail is not separated from the separator boundary between the multipart/digest main part and footer part, as described on http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/show_bug.cgi?id=998 See the attachments (broken email, hand-fixed email and diff between the two). The relevant part of RFC2046 is: RFC 2046 - page 19: NOTE: The CRLF preceding the boundary delimiter line is conceptually attached to the boundary so that it is possible to have a part that does not end with a CRLF (line break). Body parts that must be considered to end with line breaks, therefore, must have two CRLFs preceding the boundary delimiter line, the first of which is part of the preceding body part, and the second of which is part of the encapsulation boundary. ---------------------------------------------------------------------- >Comment By: Colin Leroy (colinleroy) Date: 2006-08-09 08:34 Message: Logged In: YES user_id=460566 Sorry. After more reading of the RFC, I found out that I was wrong and this double-separator isn't needed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1536532&group_id=103 From noreply at sourceforge.net Wed Aug 9 13:15:09 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 09 Aug 2006 04:15:09 -0700 Subject: [ mailman-Bugs-1537308 ] Error in 'de' translation: "Membership exposure" Message-ID: Bugs item #1537308, was opened at 2006-08-09 13:15 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=1537308&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: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Error in 'de' translation: "Membership exposure" Initial Comment: Hello, In Debian we got the following bug report: > In German "Membership exposure" becomes "Mitgliedschaft > abgelaufen" which means "Membership expired". It was suggested to me that "Mitglieder anzeigen" would be the right translation. Thanks, Thijs Kinkhorst ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1537308&group_id=103 From noreply at sourceforge.net Wed Aug 9 13:18:48 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 09 Aug 2006 04:18:48 -0700 Subject: [ mailman-Bugs-1537312 ] Typo in comment Message-ID: Bugs item #1537312, was opened at 2006-08-09 13:18 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=1537312&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: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Typo in comment Initial Comment: Hello, A Debian user found it necessary to report a typo in a comment :) Well, better forward it to you guys then... here it is: > Tiny typo: > > /usr/lib/mailman/Mailman/Utils.py > > def ValidateEmail(s): > """Verify that the an email address isn't grossly evil.""" > ^^^^^^ Thanks, Thijs Kinkhorst ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1537312&group_id=103 From noreply at sourceforge.net Wed Aug 9 13:19:42 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 09 Aug 2006 04:19:42 -0700 Subject: [ mailman-Bugs-1537312 ] Typo in comment Message-ID: Bugs item #1537312, was opened at 2006-08-09 13:18 Message generated for change (Settings changed) made by kink You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1537312&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: 1 Submitted By: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Typo in comment Initial Comment: Hello, A Debian user found it necessary to report a typo in a comment :) Well, better forward it to you guys then... here it is: > Tiny typo: > > /usr/lib/mailman/Mailman/Utils.py > > def ValidateEmail(s): > """Verify that the an email address isn't grossly evil.""" > ^^^^^^ Thanks, Thijs Kinkhorst ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1537312&group_id=103 From noreply at sourceforge.net Wed Aug 9 14:53:40 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 09 Aug 2006 05:53:40 -0700 Subject: [ mailman-Bugs-1537308 ] Error in 'de' translation: "Membership exposure" Message-ID: Bugs item #1537308, was opened at 2006-08-09 07:15 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1537308&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: None Priority: 5 Submitted By: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Error in 'de' translation: "Membership exposure" Initial Comment: Hello, In Debian we got the following bug report: > In German "Membership exposure" becomes "Mitgliedschaft > abgelaufen" which means "Membership expired". It was suggested to me that "Mitglieder anzeigen" would be the right translation. Thanks, Thijs Kinkhorst ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-09 08:53 Message: Logged In: YES user_id=12800 Please contact the German translation team: http://wiki.list.org/display/DEV/Languages ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1537308&group_id=103 From noreply at sourceforge.net Wed Aug 9 14:55:05 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 09 Aug 2006 05:55:05 -0700 Subject: [ mailman-Bugs-1537312 ] Typo in comment Message-ID: Bugs item #1537312, was opened at 2006-08-09 07:18 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1537312&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: Fixed Priority: 1 Submitted By: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Typo in comment Initial Comment: Hello, A Debian user found it necessary to report a typo in a comment :) Well, better forward it to you guys then... here it is: > Tiny typo: > > /usr/lib/mailman/Mailman/Utils.py > > def ValidateEmail(s): > """Verify that the an email address isn't grossly evil.""" > ^^^^^^ Thanks, Thijs Kinkhorst ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-08-09 08:55 Message: Logged In: YES user_id=12800 Thanks! I like the easy ones. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1537312&group_id=103 From noreply at sourceforge.net Wed Aug 9 15:26:44 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 09 Aug 2006 06:26:44 -0700 Subject: [ mailman-Patches-1537368 ] Report only bad emails in emaillistex Message-ID: Patches item #1537368, was opened at 2006-08-09 15:26 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=1537368&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: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Report only bad emails in emaillistex Initial Comment: Hello, I got the following report and patch from Paul Wise: "When you have bad emails in an emaillistex in the admin interface (such as privacy/sender/discard_these_nonmembers), the error lists all the email addresses instead of just the bad ones. This is annoying when you have heaps of addresses (including a few bad ones) that were added from the admindb interface with the "Add foo at bar.com to one of these sender filters:" option (which doesn't seem to check if the email is valid). The attached patch applies to mailman 2.1.7, and makes mailman only report the bad addresses instead of all of the addresses." Will you consider applying this? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1537368&group_id=103 From noreply at sourceforge.net Wed Aug 9 16:17:36 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 09 Aug 2006 07:17:36 -0700 Subject: [ mailman-Patches-1537408 ] Log error on screwed-up template Message-ID: Patches item #1537408, was opened at 2006-08-09 16:17 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=1537408&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Log error on screwed-up template Initial Comment: Hello! Bob Tanner supplied us with the following patch to add logging to the code that handles really "screwed up templates" so the admin can more easily see what has gone wrong. Please consider, thanks! Thijs --- HyperArch.py 2003-12-26 14:41:30.000000000 -0600 +++ HyperArch.py-bob 2005-11-23 03:19:13.000000000 -0600 @@ -217,8 +217,9 @@ Utils.GetCharSet(lang), 'replace') text = sdict.interpolate(utemplate) - except (TypeError, ValueError): + except (TypeError, ValueError), e: # The template is really screwed up + syslog('error', 'The template is really screwed up: %s\n', e) pass # Make sure the text is in the given character set, or html-ify any # bogus # characters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1537408&group_id=103 From noreply at sourceforge.net Fri Aug 18 09:53:10 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 18 Aug 2006 00:53:10 -0700 Subject: [ mailman-Patches-1542456 ] Mail address obscurification via tags Message-ID: Patches item #1542456, was opened at 2006-08-18 09:53 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=1542456&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: Raimo Niskanen (raimo_niskanen) Assigned to: Nobody/Anonymous (nobody) Summary: Mail address obscurification via tags Initial Comment: While replacing majordomo + mhonarc with mailman we had (at www.erlang.org) an own email address obscurification that created .png file for all email addresses and inserted tags in the mhonarc HTML archives. I have now reimplemented that for pipermail in mailman using the Python Imaging Library (http:/www.pytonware.com/products/pil). The patch is for mailman 2.1.6 in OpenBSD 3.8. I have introduced mm_cfg.ARCHIVER_OBSCURES_EMAILADDRS_FONT that if not False is a path to a .pil font activating email address obscurification by tags. The email addresses are stored in /var/spool/mailman/archives/private/%(listname)s/emailaddrs/ as files named %06s.png. Handling of this directory should probably be moved to Archiver/HyperDatabase.py, but I wanted to concentrate my changes to one file. pipermail.pck contains a dictionary to map email address to image index number. If this makes the file to large, the dictionary should perhaps be moved to a file in the database/ directory but OTOH that directory contains only files per archive period. The patch needs improvement regarding i18n. Perhaps it is enough to be able to select obscurification font per list, or maybe font variant should be automatically selected depending on encoding. I have virtually no previous experience of i18n issues. The patch also removes the domain name for all email addresses in the downloadable text archive, like mhonarc does in . All this because i am convinced the rewriting is too easy to harvest. This patch works for me, and I am sure others would benefit from it or something equivalent. / Raimo Niskanen, Ericsson AB, Erlang/OTP ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1542456&group_id=103 From noreply at sourceforge.net Wed Aug 23 17:23:51 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Aug 2006 08:23:51 -0700 Subject: [ mailman-Bugs-1545373 ] Change of user information by administrator can cause error Message-ID: Bugs item #1545373, was opened at 2006-08-23 10:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1545373&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Wojciech Komornicki (wnkltd) Assigned to: Nobody/Anonymous (nobody) Summary: Change of user information by administrator can cause error Initial Comment: As adminstrator of a list I changed the subscription address of a user. The user responded immediately before I clicked on the "LOG OUT" button. When I did so, I received the following message. Bug in Mailman version 2.1.8 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Below is the traceback info from the error log: Wojciech Komornicki wnk at wnk.hamline.edu admin(3123): File "/usr/local/mailman/scripts/driver", line 101, in run_main admin(3123): main() admin(3123): File "/usr/local/mailman/Mailman/Cgi/options.py", line 262, in main admin(3123): print mlist.ZapCookie (mm_cfg.AuthUser, user) admin(3123): File "/usr/local/mailman/Mailman/SecurityManager.py", line 254, in ZapCookie admin(3123): key, secret = self.AuthContextInfo (authcontext, user) admin(3123): File "/usr/local/mailman/Mailman/SecurityManager.py", line 106, in AuthContextInfo admin(3123): secret = self.getMemberPassword(user) admin(3123): File "/usr/local/mailman/Mailman/OldStyleMemberships.py ", line 102, in getMemberPassword admin(3123): raise Errors.NotAMemberError, member admin(3123): NotAMemberError: wnk at euclid.hamline.edu admin(3123): [----- Python Information -----] admin(3123): sys.version = 2.4.3 (#1, Jun 13 2006, 16:41:18) [GCC 4.0.2 20051125 (Red Hat 4.0.2-8)] admin(3123): sys.executable = /usr/bin/python admin(3123): sys.prefix = /usr admin(3123): sys.exec_prefix = /usr admin(3123): sys.path = /usr admin(3123): sys.platform = linux2 admin(3123): [----- Environment Variables -----] admin(3123): HTTP_COOKIE: esl+admin=2802000000698065ec447328000000646533393034383 0663762643238393665303361346162386430$ admin(3123): SERVER_SOFTWARE: Apache/2.2.0 (Unix) admin(3123): SCRIPT_NAME: /mailman/options admin(3123): SERVER_SIGNATURE:
Apache/2.2.0 (Unix) Server at wnk.hamline.edu Port 80
admin(3123): admin(3123): REQUEST_METHOD: POST admin(3123): PATH_INFO: /esl/wnk at euclid.hamline.edu admin(3123): SERVER_PROTOCOL: HTTP/1.1 admin(3123): QUERY_STRING: admin(3123): CONTENT_LENGTH: 14 admin(3123): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) admin(3123): HTTP_CONNECTION: Keep-Alive admin(3123): HTTP_REFERER: http://wnk.hamline.edu/mailman/options/esl/wnk at euclid.h amline.edu admin(3123): SERVER_NAME: wnk.hamline.edu admin(3123): REMOTE_ADDR: 24.118.123.243 admin(3123): PATH_TRANSLATED: /usr/local/apache2/htdocs/esl/wnk at eucl id.hamline.edu admin(3123): SERVER_PORT: 80 admin(3123): SERVER_ADDR: 138.192.24.100 admin(3123): DOCUMENT_ROOT: /usr/local/apache2/htdocs admin(3123): PYTHONPATH: /usr/local/mailman admin(3123): SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/options admin(3123): SERVER_ADMIN: wnk at hamline.edu admin(3123): HTTP_HOST: wnk.hamline.edu admin(3123): HTTP_CACHE_CONTROL: no-cache admin(3123): REQUEST_URI: /mailman/options/esl/wnk at euclid.hamline.ed u admin(3123): HTTP_ACCEPT: image/gif, image/x- xbitmap, image/jpeg, image/pjpeg, application/vnd.ms- powerpoint, applicat$ admin(3123): GATEWAY_INTERFACE: CGI/1.1 admin(3123): REMOTE_PORT: 1182 admin(3123): HTTP_ACCEPT_LANGUAGE: en-us admin(3123): CONTENT_TYPE: application/x-www-form- urlencoded admin(3123): HTTP_ACCEPT_ENCODING: gzip, deflate ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1545373&group_id=103 From noreply at sourceforge.net Tue Aug 29 06:00:37 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 28 Aug 2006 21:00:37 -0700 Subject: [ mailman-Bugs-1548312 ] cmd line works but website doesn't Message-ID: Bugs item #1548312, was opened at 2006-08-28 21: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=1548312&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: M. D. Parker (gaparkerm) Assigned to: Nobody/Anonymous (nobody) Summary: cmd line works but website doesn't Initial Comment: I have performed a fresh install of FC5 with mailman 2.1.8 package on a second server. I have made appropriate adjustments on my sendmail configurations to accomodate mailman. OK, now I copy the contents of the /var/mailman/ {data,lists,archive} on the old server to the location /var/lib/mailman/... on the new server. I configure a virtual host to host the mailman interface portion. Like the old server All seems ok. Sendmail redirection work GREAT. Using the commandline /usr/lib/mailman/bin/list_lists confirms that there are (in my case) 9 lists. GREAT. However, I use the website interface URI: http://www.xxx.com/mailman/listinfo and get the message that there are no lists out there. Interesting as when (as the apache user), I execute: /usr/lib/mailman/cgi-bin/listinfo I see the appropriate HTML output with all 9 websites. Further, if I use the following on a group that I know is ok: http://www.xxx.com/mailman/admin/known-list I get that the list is not present. The check_perms program reports NO errors. PROBLEM: How do I get the website to work correctly and display the lists and such as it should and did on the old server. HELP Thanks.... Mike Parker parkerm at ga.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1548312&group_id=103 From noreply at sourceforge.net Tue Aug 29 06:01:48 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 28 Aug 2006 21:01:48 -0700 Subject: [ mailman-Bugs-1548312 ] cmd line works but website doesn't Message-ID: Bugs item #1548312, was opened at 2006-08-28 21:00 Message generated for change (Settings changed) made by gaparkerm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1548312&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: M. D. Parker (gaparkerm) Assigned to: Nobody/Anonymous (nobody) Summary: cmd line works but website doesn't Initial Comment: I have performed a fresh install of FC5 with mailman 2.1.8 package on a second server. I have made appropriate adjustments on my sendmail configurations to accomodate mailman. OK, now I copy the contents of the /var/mailman/ {data,lists,archive} on the old server to the location /var/lib/mailman/... on the new server. I configure a virtual host to host the mailman interface portion. Like the old server All seems ok. Sendmail redirection work GREAT. Using the commandline /usr/lib/mailman/bin/list_lists confirms that there are (in my case) 9 lists. GREAT. However, I use the website interface URI: http://www.xxx.com/mailman/listinfo and get the message that there are no lists out there. Interesting as when (as the apache user), I execute: /usr/lib/mailman/cgi-bin/listinfo I see the appropriate HTML output with all 9 websites. Further, if I use the following on a group that I know is ok: http://www.xxx.com/mailman/admin/known-list I get that the list is not present. The check_perms program reports NO errors. PROBLEM: How do I get the website to work correctly and display the lists and such as it should and did on the old server. HELP Thanks.... Mike Parker parkerm at ga.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1548312&group_id=103 From noreply at sourceforge.net Tue Aug 29 06:22:02 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 28 Aug 2006 21:22:02 -0700 Subject: [ mailman-Bugs-1548312 ] cmd line works but website doesn't Message-ID: Bugs item #1548312, was opened at 2006-08-28 21:00 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1548312&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: M. D. Parker (gaparkerm) Assigned to: Nobody/Anonymous (nobody) Summary: cmd line works but website doesn't Initial Comment: I have performed a fresh install of FC5 with mailman 2.1.8 package on a second server. I have made appropriate adjustments on my sendmail configurations to accomodate mailman. OK, now I copy the contents of the /var/mailman/ {data,lists,archive} on the old server to the location /var/lib/mailman/... on the new server. I configure a virtual host to host the mailman interface portion. Like the old server All seems ok. Sendmail redirection work GREAT. Using the commandline /usr/lib/mailman/bin/list_lists confirms that there are (in my case) 9 lists. GREAT. However, I use the website interface URI: http://www.xxx.com/mailman/listinfo and get the message that there are no lists out there. Interesting as when (as the apache user), I execute: /usr/lib/mailman/cgi-bin/listinfo I see the appropriate HTML output with all 9 websites. Further, if I use the following on a group that I know is ok: http://www.xxx.com/mailman/admin/known-list I get that the list is not present. The check_perms program reports NO errors. PROBLEM: How do I get the website to work correctly and display the lists and such as it should and did on the old server. HELP Thanks.... Mike Parker parkerm at ga.com ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-08-28 21:22 Message: Logged In: YES user_id=1123998 Please see FAQ 4.62 at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.062.htp and perhaps other FAQ entries. If that doesn't help, please follow up on mailman-users at python.org. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1548312&group_id=103 From noreply at sourceforge.net Tue Aug 29 18:03:15 2006 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 29 Aug 2006 09:03:15 -0700 Subject: [ mailman-Bugs-1548312 ] cmd line works but website doesn't Message-ID: Bugs item #1548312, was opened at 2006-08-28 23:00 Message generated for change (Comment added) made by wnkltd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1548312&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: M. D. Parker (gaparkerm) Assigned to: Nobody/Anonymous (nobody) Summary: cmd line works but website doesn't Initial Comment: I have performed a fresh install of FC5 with mailman 2.1.8 package on a second server. I have made appropriate adjustments on my sendmail configurations to accomodate mailman. OK, now I copy the contents of the /var/mailman/ {data,lists,archive} on the old server to the location /var/lib/mailman/... on the new server. I configure a virtual host to host the mailman interface portion. Like the old server All seems ok. Sendmail redirection work GREAT. Using the commandline /usr/lib/mailman/bin/list_lists confirms that there are (in my case) 9 lists. GREAT. However, I use the website interface URI: http://www.xxx.com/mailman/listinfo and get the message that there are no lists out there. Interesting as when (as the apache user), I execute: /usr/lib/mailman/cgi-bin/listinfo I see the appropriate HTML output with all 9 websites. Further, if I use the following on a group that I know is ok: http://www.xxx.com/mailman/admin/known-list I get that the list is not present. The check_perms program reports NO errors. PROBLEM: How do I get the website to work correctly and display the lists and such as it should and did on the old server. HELP Thanks.... Mike Parker parkerm at ga.com ---------------------------------------------------------------------- Comment By: Wojciech Komornicki (wnkltd) Date: 2006-08-29 11:03 Message: Logged In: YES user_id=1582277 I recently upgraded from 2.1.5 to 2.1.8. When I merely updated the package with yum I lost all of my lists. Doing a make install from the mailman distribution tar file causes the databases to be rebuilt. I think (am I correct?) that the database format has changed in 2.1.8. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-08-28 23:22 Message: Logged In: YES user_id=1123998 Please see FAQ 4.62 at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.062.htp and perhaps other FAQ entries. If that doesn't help, please follow up on mailman-users at python.org. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1548312&group_id=103