[Mailman-Developers] [ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11

noreply at sourceforge.net noreply at sourceforge.net
Fri Jan 3 06:56:44 EST 2003

Bugs item #563336, was opened at 2002-06-01 16:48
You can respond by visiting: 

Category: (un)subscribing
Group: 2.0.x
Status: Open
Resolution: None
Priority: 1
Submitted By: Federico Sevilla III (jijo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unexpected MMBadUserError with MM-2.0.11

Initial Comment:
Just upgraded to Mailman 2.0.11. The upgrade itself
worked fine, and basic tests after the upgrade seem to
have worked okay, and mail has been getting delivered.

However I got an email (as administrator) about an
unexpected Mailman error. I have yet to get a complaint
from our users so I do not know exactly what caused the
problem. All I can deduce from the logs is that at
around the same time, someone was
subscribing/unsubscribing via email.

The error message I got by email was:

-----[ START ]-----
An unexpected Mailman error has occurred in
MailCommandHandler.ParseMailCommands().  Here is the

Traceback (most recent call last):
"/usr/lib/mailman/Mailman/MailCommandHandler.py", line
223, in ParseMailCommands
    self.__dispatch[cmd](args, line, msg)
"/usr/lib/mailman/Mailman/MailCommandHandler.py", line
364, in ProcessSetCmd
    self.ConfirmUserPassword(sender, args[2])
  File "/usr/lib/mailman/Mailman/SecurityManager.py",
line 144, in ConfirmUserPassword
    raise Errors.MMBadUserError
-----[ END ]-----

Some more miscellaneous information:

- system is Debian GNU/Linux
- mailman package is mailman-2.0.11-1
- python package is python-2.1.3-3

If anyone has tips as to where to dig for more
information on the cause of this unexpected error,
please do let me know and I will be more than happy to
supply the missing details. It would also help calm my
nerves if I knew whether this was fatal or not. :)


Comment By: Uche Ogbuji (uche)
Date: 2003-01-03 14:56

Logged In: YES 

Hmm.  Looks as if Barry lowered the priority for this with
no comment.  I think that's unfortunate.  I just ran into
this as well.

If this is truly just some user getting their password
wrong, why isn't the exception trapped, and the user allowed
to try again?  This is the reason this puzzles me so:
putting in the wrong password is a common thing to do.  I
myself sometimes trip up the password to my list admin
areas.  So when mailman goes out of its way to send me an
e-mail with such a traceback, it makes me wonder whether
something especially nasty is going on.

A better message would help a lot.  I'd be grateful for some
note on this open issue from the developers, at least.


You can respond by visiting: 

More information about the Mailman-Developers mailing list