[Mailman-Users] Bug report

[Mark Sapiro]

PeteBell wrote:
>
>I have just gone live with my email list, and this is the first time  
>anyone has reported a problem to me, so here it is for your comments.  
>(First let me remind you that I do *not* have access to the Mailman  
>installation, and I do *NOT* speak Python - apart from the "Monty"  
>version!)....
>
>
>> I tried to subscribe using the 3-c.coop address, but it wouldn't  
>> let me say I didn't want to receive the emails, so I clicked  
>> cancel. Then I got this:
>>
>> "Bug in Mailman version 2.1.5p1
>>
>> We're sorry, we hit a bug!
>>
>> If you would like to help us identify the problem, please email a  
>> copy of this page to the webmaster for this site with a description  
>> of what happened. Thanks!
>> Traceback:
>>
>> Traceback (most recent call last):
>>   File "/usr/local/cpanel/3rdparty/mailman/scripts/driver", line  
>> 87, in run_main
>>     main()
>>   File "/usr/local/cpanel/3rdparty/mailman/Mailman/Cgi/confirm.py",  
>> line 114, in main
>>     subscription_cancel(mlist, doc, cookie)
>>   File "/usr/local/cpanel/3rdparty/mailman/Mailman/Cgi/confirm.py",  
>> line 312, in subscription_cancel
>>     userdesc = mlist.pend_confirm(cookie)[1]
>>   File "/usr/local/cpanel/3rdparty/mailman/Mailman/Pending.py",  
>> line 141, in pend_confirm
>>     assert self.Locked()
>> AssertionError"

First, see FAQ article 6.11

Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

That said, this is not a cPanel problem per se. It has been fixed in
Mailman 2.1.6.

As far as your user's not wanting to subscribe if she/he can't supress
e-mail, the user needs to subscribe first and then disable mail
delivery on his/her options page. See
http://www.list.org/mailman-member/node20.html (or the whole manual at
http://www.list.org/mailman-member/mailman-member.html)

--
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan