[Mailman-Users] OldStyleMemberships Error
msapiro at value.net
Sun Oct 31 17:31:06 CET 2004
Speedy Gonzalis wrote:
>Since upgrading to Mailman 2.1.4 from v2.0.8 I have been getting the below errors in the log whenever a non-member tries to access a non existing account. They are also presented with the "we've hit a bug" screen which also displays the below information.
>Is there some process that I can run to convert all of the "old style memberships" to whatever Mailman wants to stop this and have the person just get a screen that says he's not subscribed?
>admin(19326): File "/var/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo
>admin(19326): secret = self.getMemberPassword(user)
>admin(19326): File "/var/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword
>admin(19326): raise Errors.NotAMemberError, member
>admin(19326): NotAMemberError: xxxxx at sbcglobal.net
I see these and similar error traces occasionally in a "new" Mailman
2.1.4 installation. I don't know if they occur in 2.1.5 or not, but I
think it is a real bug in 2.1.4. It has nothing to do with "old style
memberships". According to comments at least in
OldStyleMemberships.py, it is used for 2.1.x memberships, and my
installation has no pre-2.1.4 lists.
I think (but I'm not sure) that these errors occur when the user has an
"unexpected" login cookie. I.e. the user has already logged in to
another list and then tries to check options or visit private archives
for a different list or has logged in to one subscription (e-mail
address) on the current list and then tries to check options for
In any case, the "memberships" should have been converted automatically
by bin/update during the upgrade process. You can always try running
bin/update again, but I don't think it will make any difference.
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users