[Mailman-Users] Help - Subscribe/unsubscribe broken

[Mark Sapiro]

On 03/27/2018 07:01 AM, Jeff Polasek via Mailman-Users wrote:
> Howdy,
> I recently updated from mailman 2.1.? to 2.1.26.  After this update users can not subscribe or unsubscribe.  Here is the error from the mailman log.  Any ideas what I need to fix?  It may be a database problem?
> Thanks
> Jeff
> 
> Mar 27 08:57:49 2018 admin(21493): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
> 
> admin(21493): [----- Mailman Version: 2.1.26 -----] 
> 
> admin(21493): [----- Traceback ------] 
> 
> admin(21493): Traceback (most recent call last):
> 
> admin(21493):   File "/var/lib/mailman/scripts/driver", line 117, in run_main
> 
> admin(21493):     main()
> 
> admin(21493):   File "/var/lib/mailman/Mailman/Cgi/subscribe.py", line 113, in main
> 
> admin(21493):     process_form(mlist, doc, cgidata, language)
> 
> admin(21493):   File "/var/lib/mailman/Mailman/Cgi/subscribe.py", line 248, in process_form
> 
> admin(21493):     mlist.AddMember(userdesc, remote)
> 
> admin(21493):   File "/var/lib/mailman/Mailman/MailList.py", line 923, in AddMember
> 
> admin(21493):     cookie = self.pend_new(Pending.SUBSCRIPTION, userdesc)
> 
> admin(21493):   File "/var/lib/mailman/Mailman/Pending.py", line 85, in pend_new
> 
> admin(21493):     evictions = db.setdefault('evictions', {})
> 
> admin(21493): AttributeError: Message instance has no attribute 'setdefault'


This is very strange. It is saying that in the statement

        evictions = db.setdefault('evictions', {})

in Pending.py, db is a Message object. I think the only way this could
happen is if the lists/LISTNAME/pending.pck file is a pickled Message
object rather than a pending database. How that would happen, I don't know.

You could dump this file with Mailman's bin/dumpdb and see what it is,
but the simple fix is just remove the file.

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