[ mailman-Bugs-2037414 ] Subscriber "disappears" after subscription

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_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: 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@domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist2 list-admin@domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist3 list-admin@domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist4 list-admin@domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist5 list-admin@domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist6 list-admin@domain.com testpwd echo "foo@bar.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "foo@bar.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "foo@bar.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "foo@bar.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "foo@bar.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "foo@bar.com" | /usr/local/mailman/bin/add_members -r - testlist6 echo "boo@foo.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "boo@foo.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "boo@foo.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "boo@foo.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "boo@foo.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "boo@foo.com" | /usr/local/mailman/bin/add_members -r - testlist6 After a short wait the following output is received: Subscribed: foo@bar.com Subscribed: foo@bar.com Subscribed: foo@bar.com Subscribed: foo@bar.com Subscribed: foo@bar.com Subscribed: foo@bar.com Subscribed: boo@foo.com Subscribed: boo@foo.com Subscribed: boo@foo.com Subscribed: boo@foo.com Subscribed: boo@foo.com Subscribed: boo@foo.com foo@bar.com receives 6 confirmation emails, as boo@foo.com does. So far so good. At this point testlist1-6 each should contain 2 subscribers: foo@bar.com and boo@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@foo.com foo@bar.com foo@bar.com boo@foo.com foo@bar.com foo@bar.com foo@bar.com boo@foo.com foo@bar.com in which three instances of boo@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_id=103
participants (1)
-
SourceForge.net