traceback for set nomail for non-member

Bug #265779 reported by Marilyndavis
2
Affects Status Importance Assigned to Milestone
GNU Mailman
New
Low
Unassigned

Bug Description

If a non-member of a list sends a mail message to the
request address
to "set nomail on passwd", the non-member gets a
traceback and the
admin gets an "unexpected mailman error" message.

Instead, the MailCommandHandler probably wants to
catch the exception
and suggest to the non-user that she joins the list before
she turns
off her mail stream.

I did this accidentally, first with an unknown password
and the second
time with the admin's password. Each traceback is a
little different.

I hope this is helpful.

Thank you,

Marilyn Davis

The MailCommandHandler.py

>From <email address hidden> Tue Nov 19
14:24:13 2002
Date: Tue, 19 Nov 2002 13:31:01 -0800
From: <email address hidden>
To: <email address hidden>
Subject: Mailman results for T2

This is an automated response.

There were problems with the email commands you sent
to Mailman via
the administrative address <t2-
<email address hidden>>.

To obtain instructions on valid Mailman email
commands, send email to
<email address hidden> with the
word "help" in the subject
line or in the body of the message.

If you want to reach the human being that manages this
mailing list,
please send your message to <t2-
<email address hidden>>.

The following is a detailed description of the problems.

>>>>> Subject line ignored:
>>>>> Re: Mailman results for T2

***** set nomail on XXXXXXXX
>>>>> An unexpected Mailman error has occurred.
>>>>>
>>>>> Please forward your request to the human list
administrator in charge
>>>>> of this list at <t2-
<email address hidden>>. The traceback is
>>>>> attached below and will be forwarded to the list
administrator
>>>>> automatically.

Traceback (most recent call last):

File "/home/mailman/Mailman/MailCommandHandler.py",
 line 235, in ParseMailCommands
    self.__dispatch[cmd](args, line, msg)

File "/home/mailman/Mailman/MailCommandHandler.py",
 line 376, in ProcessSetCmd
    self.ConfirmUserPassword(sender, args[2])
  File "/home/mailman/Mailman/SecurityManager.py",
line 144, in ConfirmUserPassword
    raise Errors.MMBadUserError
MMBadUserError

>From <email address hidden> Tue Nov 19
14:24:19 2002
Date: Tue, 19 Nov 2002 13:32:01 -0800
From: <email address hidden>
To: <email address hidden>
Subject: Mailman results for T2

This is an automated response.

There were problems with the email commands you sent
to Mailman via
the administrative address <t2-
<email address hidden>>.

To obtain instructions on valid Mailman email
commands, send email to
<email address hidden> with the
word "help" in the subject
line or in the body of the message.

If you want to reach the human being that manages this
mailing list,
please send your message to <t2-
<email address hidden>>.

The following is a detailed description of the problems.

***** set nomail on (the admin password)
>>>>> An unexpected Mailman error has occurred.
>>>>>
>>>>> Please forward your request to the human list
administrator in charge
>>>>> of this list at <t2-
<email address hidden>>. The traceback is
>>>>> attached below and will be forwarded to the list
administrator
>>>>> automatically.

Traceback (most recent call last):

File "/home/mailman/Mailman/MailCommandHandler.py",
 line 235, in ParseMailCommands
    self.__dispatch[cmd](args, line, msg)

File "/home/mailman/Mailman/MailCommandHandler.py",
 line 412, in ProcessSetCmd
    self.SetUserOption(sender, option_info[args[0]], value)
  File "/home/mailman/Mailman/MailList.py", line 206, in
SetUserOption
    user = self.GetUserCanonicalAddress(user)
  File "/home/mailman/Mailman/MailList.py", line 174, in
GetUserCanonicalAddress
    cpuser = self.GetUserSubscribedAddress(member)
  File "/home/mailman/Mailman/MailList.py", line 159, in
GetUserSubscribedAddress
    member = string.lower(member)
  File "/usr/local/lib/python2.2/string.py", line 54, in lower
    return s.lower()
AttributeError: 'NoneType' object has no attribute 'lower'

[http://sourceforge.net/tracker/index.php?func=detail&aid=641436&group_id=103&atid=100103]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.