Bug encountered when doing global change of address

Bug #265983 reported by Clydec-users
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Fix Released
Medium
Unassigned

Bug Description

I was trying to do a global change of name/address for
myself and encountered this bug. The new address was
already a member of one of the mailing lists

--------------------------------------------------------

Bug in Mailman version 2.1.2

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 "/home/usr/local/mailman/scripts/driver", line
87, in run_main
    main()
  File
"/home/usr/local/mailman/Mailman/Cgi/confirm.py", line
131, in main
    addrchange_confirm(mlist, doc, cookie)
  File
"/home/usr/local/mailman/Mailman/Cgi/confirm.py", line
492, in addrchange_confirm
    op, oldaddr, newaddr =
mlist.ProcessConfirmation(cookie)
  File "/home/usr/local/mailman/Mailman/MailList.py",
line 1113, in ProcessConfirmation
    self.ApprovedChangeMemberAddress(oldaddr, newaddr,
globally)
  File "/home/usr/local/mailman/Mailman/MailList.py",
line 1032, in ApprovedChangeMemberAddress
    self.changeMemberAddress(oldaddr, newaddr)
  File
"/home/usr/local/mailman/Mailman/OldStyleMemberships.py",
line 251, in changeMemberAddress
    password=password, language=lang)
  File
"/home/usr/local/mailman/Mailman/OldStyleMemberships.py",
line 175, in addNewMember
    raise Errors.MMAlreadyAMember, member
MMAlreadyAMember: <email address hidden>

---------------------------------------------------------------------------
-----

Python information:
Variable Value
sys.version 2.2.3 (#2, Jul 17 2003, 14:48:38) [GCC
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)]
sys.executable /usr/bin/python
sys.prefix /usr/local
sys.exec_prefix /usr/local
sys.path /usr/local
sys.platform linux2

---------------------------------------------------------------------------
-----

Environment variables:
Variable Value
HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg, application/vnd.ms-powerpoint,
application/vnd.ms-excel, application/msword,
application/x-shockwave-flash, */*
CONTENT_TYPE application/x-www-form-urlencoded
HTTP_REFERER
http://www.clydec.net/mailman/confirm/jujitsu/fe77e7f88cdb236aef702757e6be5
7e4b9f81338

SERVER_SOFTWARE Apache/1.3.22 (Unix) (Red-Hat/Linux)
PHP/4.3.3 mod_perl/1.21
PYTHONPATH /home/usr/local/mailman
SCRIPT_FILENAME /home/usr/local/mailman/cgi-bin/confirm
SERVER_ADMIN <email address hidden>
SCRIPT_NAME /mailman/confirm
SERVER_SIGNATURE Apache/1.3.22 Server at
www.clydec.net Port 80
REQUEST_METHOD POST
HTTP_HOST www.clydec.net
PATH_INFO /jujitsu
SERVER_PROTOCOL HTTP/1.1
QUERY_STRING
HTTP_CACHE_CONTROL no-cache
REQUEST_URI /mailman/confirm/jujitsu
CONTENT_LENGTH 69
HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.0)
HTTP_CONNECTION Keep-Alive
SERVER_NAME www.clydec.net
REMOTE_ADDR 209.150.103.223
REMOTE_PORT 2500
HTTP_ACCEPT_LANGUAGE en-us
PATH_TRANSLATED /home/httpd/html/jujitsu
SERVER_PORT 80
GATEWAY_INTERFACE CGI/1.1
REMOTE_HOST clydec2.qis.net
HTTP_ACCEPT_ENCODING gzip, deflate
SERVER_ADDR 209.150.103.222
DOCUMENT_ROOT /home/httpd/html

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

Tags: web-cgi
Revision history for this message
Barry Warsaw (barry) wrote :

Fixed for Mailman 2.1.4

Revision history for this message
Michael Shulman (shulman) wrote :

I encounter something that looks exactly like this bug using Mailman 2.1.9 (specifically, the Debian mailman package 1:2.1.9-7). Any chance it got broken again?

Revision history for this message
Mark Sapiro (msapiro) wrote :

There were changes in this area between 2.1.9 and 2.1.10. It is possible that the 2.1.4 fix was incomplete and the bug wasn't fully fixed until 2.1.10. I'm not certain without looking in detail whether this could be a 2.1.9 bug or may be caused by a Debian patch, but I suspect it may be a bug in 2.1.9, and if so, I think it was fixed in 2.1.10.

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.