Mailman 3 August 2008 - Mailman-coders

[ mailman-Patches-943827 ] true virtual hosting patch for 2.1
by SourceForge.net 07 Aug '08

07 Aug '08

Patches item #943827, was opened at 2004-04-28 12:57 Message generated for change (Comment added) made by selsky You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i… 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 Private: No Submitted By: The Anarcat (anarcat) Assigned to: Nobody/Anonymous (nobody) Summary: true virtual hosting patch for 2.1 Initial Comment: [copy of the mail sent to -developpers@] We developped a reliable solution for running lists with the same name on different domains on the same Mailman installation. I implemented that on top of the Mailman 2.1.1-5.1 Debian stable package. All that is needed is to patch 2 files (bin/newlist, Mailman/MailList.py) in the mailman install, and here is the patch: http://bugs.koumbit.net/file_download.php?file_id=3&type=bug There's only one caveat right now: Mailman/Cgi/create.py might need to get patched too, but I haven't got around looking at it yet, and it "just works", for now. I don't know what's the current status of virtual hosting support on Mailman, but this patch is a simple hack that should bring joy in the homes of all Mailman admins around the world. :) I got my inspiration and part of the code from: http://mithrandr.moria.org/blog/139.html All it does is to add the domain to the internal_name() of a list. The real_name is kept as is, and the getListAddress() does the Right Thing. This makes Mailman generate aliases like: list-example.com: "|/var/lib/mailman/mail/mailman post list-example.com" Care will have to be taken on the MTA side to map those list-example.com to list(a)example.com. We are using alternc.org to manage our server, so we are using LDAP, so everything went pretty smoothly. :) But I guess it will require some magic on the Postfix side or something... Cheers, A. PS: for those wanting to see more, you can come to our Wiki: http://koumbit.net/wiki/VirtualMailman You'll probably have a little trouble finding your way if you don't read french though. :) Babelfish might help, haven't tried. ---------------------------------------------------------------------- Comment By: Matt Selsky (selsky) Date: 2008-08-07 15:12 Message: Logged In: YES user_id=324866 Originator: NO Is this forward compatible with Mailman 3? ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2008-04-16 13:26 Message: Logged In: YES user_id=246797 Originator: YES The patch is online in our wiki: http://wiki.koumbit.net/VirtualMailman Note that the v3 of mailman now supports this out of the box, although it's in alpha, as far as I understand. ---------------------------------------------------------------------- Comment By: Graham Leggett (minfrin) Date: 2008-04-16 13:09 Message: Logged In: YES user_id=129704 Originator: NO The site http://nix.lauft.net/mailman/ is now down - does anyone have a copy of the mailman-vh-2.1.7.patch anywhere? ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2007-03-01 17:57 Message: Logged In: YES user_id=87909 Originator: NO Grab mailman-vh-2.1.7.patch from http://nix.lauft.net/mailman/, it applies fine to 2.1.9. ---------------------------------------------------------------------- Comment By: GILLIG (fgillig) Date: 2007-03-01 06:18 Message: Logged In: YES user_id=1463624 Originator: NO I search this patch for mailman 2.1.9 ... (fc5). Anyone can help ? ---------------------------------------------------------------------- Comment By: Pedro Algarvio (s0undt3ch) Date: 2006-10-12 21:05 Message: Logged In: YES user_id=927681 +1 for this patch ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2006-04-22 07:48 Message: Logged In: YES user_id=87909 Crud, wrapping... The changes are all on one line. ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2006-04-22 07:47 Message: Logged In: YES user_id=87909 minfrin, create it as listname-domain or try this patch: diff -urNad mailman-2.1.5/Mailman/Cgi/create.py /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py --- mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22 20:58:10.324872941 +1000 +++ /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22 21:13:31.596133649 +1000 @@ -184,7 +184,7 @@ oldmask = os.umask(002) try: try: - mlist.Create(listname, owner, pw, langs, emailhost) + mlist.Create("%s@%s" % (listname,hostname), owner, pw, langs, emailhost) finally: os.umask(oldmask) except Errors.EmailAddressError, s: Which will add the '@domain' to the listname before passing it to mlist.Create, which the patch changes to deal with '@' the way we want. ---------------------------------------------------------------------- Comment By: Graham Leggett (minfrin) Date: 2006-03-17 15:39 Message: Logged In: YES user_id=129704 I tried the patch at http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch and it applied cleanly to mailman as provided by RHEL4. I tried to create a list called "list(a)domain1.com", but this failed with the error "Error: List name must not include "@"". Does this patch have any sort of instructions anywhere? ---------------------------------------------------------------------- Comment By: Arnaud Lavrard (arnaudlavrard) Date: 2005-07-20 09:52 Message: Logged In: YES user_id=1315788 I ported the patch to mailman 2.1.5 : http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2005-03-16 15:40 Message: Logged In: YES user_id=246797 I have ported the patch to 2.1.4, no news on 2.1.5 yet. I have also put the patch in a seperate CVS server. Fetch all the goods there: http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-vi… http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-vi… I've also updated the 2.1.1 patch to fix the list-id, so I delete the attachment, fetch the patch straight from our CVS for the latest fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i…

1 0

[ mailman-Bugs-2037414 ] Subscriber "disappears" after subscription
by SourceForge.net 06 Aug '08

06 Aug '08

Bugs item #2037414, was opened at 2008-08-04 00:59 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2037414&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: Accepted Priority: 5 Private: No Submitted By: Massimo Lanfranconi (mlanfranconi) >Assigned to: Mark Sapiro (msapiro) Summary: Subscriber "disappears" after subscription Initial Comment: Mailman 2.1.11 Python 2.4.4 OS Solaris 2.11 Hi, I have been able to reproduce this bug consistently by running the replicate_bug script: replicate _bug is the following: #!/bin/sh /usr/local/mailman/bin/rmlist testlist1 /usr/local/mailman/bin/rmlist testlist2 /usr/local/mailman/bin/rmlist testlist3 /usr/local/mailman/bin/rmlist testlist4 /usr/local/mailman/bin/rmlist testlist5 /usr/local/mailman/bin/rmlist testlist6 /usr/local/mailman/bin/newlist -q -e url.domain.com testlist1 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist2 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist3 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist4 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist5 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist6 list-admin(a)domain.com testpwd echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist6 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist6 After a short wait the following output is received: Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com foo(a)bar.com receives 6 confirmation emails, as boo(a)foo.com does. So far so good. At this point testlist1-6 each should contain 2 subscribers: foo(a)bar.com and boo(a)foo.com BUT /usr/local/mailman/bin/list_members testlist1 /usr/local/mailman/bin/list_members testlist2 /usr/local/mailman/bin/list_members testlist3 /usr/local/mailman/bin/list_members testlist4 /usr/local/mailman/bin/list_members testlist5 /usr/local/mailman/bin/list_members testlist6 invariably produce some random combination in which one or more of the subscribers are missing: for example: boo(a)foo.com foo(a)bar.com foo(a)bar.com boo(a)foo.com foo(a)bar.com foo(a)bar.com foo(a)bar.com boo(a)foo.com foo(a)bar.com in which three instances of boo(a)foo.com are missing... No Errors in any Mailman log. Thanks in advance for your help. Please let me know if you need additional details. Regards, Max ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-05 17:08 Message: Logged In: YES user_id=1123998 Originator: NO Thanks for the script. It was helpful in finding the problem. The analysis of the cause of the problem and potential fix is at <http://mail.python.org/pipermail/mailman-developers/2008-August/020330.html>. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2037414&group_…

1 0

[ mailman-Bugs-2039241 ] teach firefox that different lists may have different passwo
by SourceForge.net 06 Aug '08

06 Aug '08

Bugs item #2039241, was opened at 2008-08-05 12:55 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2039241&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: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Robert Collins (rbcollins) Assigned to: Nobody/Anonymous (nobody) Summary: teach firefox that different lists may have different passwo Initial Comment: given two lists on a mailman instance, foo and bar, each with a list passsword the same as the name. login to one, save the password in firefox, go to the other's admindb and it will fail - wrong password. login and ask firefox to remember it and it resets the password saved for the list foo. This is annoying :) I suspect you are using the same field and form names - while I don't know what the heuristic ff uses for html auth field detection, its certainly assuming its the *same* password. One hack that might be elegant and work would be a hidden field called username set to the list name :) Another would be just changing things to ff thinks its a different password and stores it differently. I'd *really* love a fix that can be backported to 2.1.8 which our list servers are running. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-05 15:08 Message: Logged In: YES user_id=1123998 Originator: NO The template for the pages is admlogin.html. See <http://wiki.list.org/x/jYA9> for ways to make an edited version of this template. The string %(listname)s will be replaced with the list name. You could implement your first suggestion by changing the line <TD><INPUT TYPE="password" NAME="adminpw" SIZE="30"></TD> to <TD><INPUT TYPE="HIDDEN" NAME="userid" VALUE="%(listname)s"> <INPUT TYPE="password" NAME="adminpw" SIZE="30"></TD> Changing the name "adminpw" to something list specific as in your second suggestion would require several code changes to identify the password. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2039241&group_…

1 0

[ mailman-Bugs-2039241 ] teach firefox that different lists may have different passwo
by SourceForge.net 05 Aug '08

05 Aug '08

Bugs item #2039241, was opened at 2008-08-06 05:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2039241&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: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Robert Collins (rbcollins) Assigned to: Nobody/Anonymous (nobody) Summary: teach firefox that different lists may have different passwo Initial Comment: given two lists on a mailman instance, foo and bar, each with a list passsword the same as the name. login to one, save the password in firefox, go to the other's admindb and it will fail - wrong password. login and ask firefox to remember it and it resets the password saved for the list foo. This is annoying :) I suspect you are using the same field and form names - while I don't know what the heuristic ff uses for html auth field detection, its certainly assuming its the *same* password. One hack that might be elegant and work would be a hidden field called username set to the list name :) Another would be just changing things to ff thinks its a different password and stores it differently. I'd *really* love a fix that can be backported to 2.1.8 which our list servers are running. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2039241&group_…

1 0

[ mailman-Bugs-2037414 ] Subscriber "disappears" after subscription
by SourceForge.net 04 Aug '08

04 Aug '08

Bugs item #2037414, was opened at 2008-08-04 00:59 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=2037414&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 Private: No Submitted By: Massimo Lanfranconi (mlanfranconi) Assigned to: Nobody/Anonymous (nobody) Summary: Subscriber "disappears" after subscription Initial Comment: Mailman 2.1.11 Python 2.4.4 OS Solaris 2.11 Hi, I have been able to reproduce this bug consistently by running the replicate_bug script: replicate _bug is the following: #!/bin/sh /usr/local/mailman/bin/rmlist testlist1 /usr/local/mailman/bin/rmlist testlist2 /usr/local/mailman/bin/rmlist testlist3 /usr/local/mailman/bin/rmlist testlist4 /usr/local/mailman/bin/rmlist testlist5 /usr/local/mailman/bin/rmlist testlist6 /usr/local/mailman/bin/newlist -q -e url.domain.com testlist1 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist2 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist3 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist4 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist5 list-admin(a)domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist6 list-admin(a)domain.com testpwd echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "foo(a)bar.com" | /usr/local/mailman/bin/add_members -r - testlist6 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "boo(a)foo.com" | /usr/local/mailman/bin/add_members -r - testlist6 After a short wait the following output is received: Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: foo(a)bar.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com Subscribed: boo(a)foo.com foo(a)bar.com receives 6 confirmation emails, as boo(a)foo.com does. So far so good. At this point testlist1-6 each should contain 2 subscribers: foo(a)bar.com and boo(a)foo.com BUT /usr/local/mailman/bin/list_members testlist1 /usr/local/mailman/bin/list_members testlist2 /usr/local/mailman/bin/list_members testlist3 /usr/local/mailman/bin/list_members testlist4 /usr/local/mailman/bin/list_members testlist5 /usr/local/mailman/bin/list_members testlist6 invariably produce some random combination in which one or more of the subscribers are missing: for example: boo(a)foo.com foo(a)bar.com foo(a)bar.com boo(a)foo.com foo(a)bar.com foo(a)bar.com foo(a)bar.com boo(a)foo.com foo(a)bar.com in which three instances of boo(a)foo.com are missing... No Errors in any Mailman log. Thanks in advance for your help. Please let me know if you need additional details. Regards, Max ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2037414&group_…

1 0

Mailman-coders August 2008