Mailman 3 August 2006 - Mailman-coders

[ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File
by SourceForge.net Aug. 2, 2006

Aug. 2, 2006

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_… 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 <listname>-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_…

1 0

[ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File
by SourceForge.net Aug. 2, 2006

Aug. 2, 2006

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_… 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 <listname>-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_…

1 0

[ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File
by SourceForge.net Aug. 2, 2006

Aug. 2, 2006

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_… 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 <listname>-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_…

1 0

[ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File
by SourceForge.net Aug. 2, 2006

Aug. 2, 2006

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_… 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 <listname>-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_…

1 0

[ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File
by SourceForge.net Aug. 2, 2006

Aug. 2, 2006

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_… 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_…

1 0

[ mailman-Bugs-1532638 ] can't unsub addr with double-at
by SourceForge.net Aug. 2, 2006

Aug. 2, 2006

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_… 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(a)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_…

1 0

[ mailman-Bugs-1532638 ] can't unsub addr with double-at
by SourceForge.net Aug. 1, 2006

Aug. 1, 2006

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_… 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(a)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_…

1 0

[ mailman-Bugs-1532638 ] can't unsub addr with double-at
by SourceForge.net Aug. 1, 2006

Aug. 1, 2006

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_… 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(a)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_…

1 0

[ mailman-Bugs-1531675 ] ARCHIVE_TO_MBOX=1 broken
by SourceForge.net Aug. 1, 2006

Aug. 1, 2006

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_… 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_…

1 0