[Mailman-Developers] [ mailman-Bugs-551730 ] traceback on double rename

Thu, 02 May 2002 23:50:59 -0700

Bugs item #551730, was opened at 2002-05-03 06:50
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100103&aid=551730&group_id=103

Category: (un)subscribing
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Marc Merlin (marcmerlin)
Assigned to: Nobody/Anonymous (nobody)
Summary: traceback on double rename

Initial Comment:
I have a user who says he got this on mailman 2.1b1cvs

He explains below how he did it.                      

----- Forwarded message from David T-G
<davidtg@justpickone.org> -----          

Subject: Mailman results for Empeg-faq                

From: empeg-faq-request@merlins.org                   

To: davidtg-empeg@justpickone.org                     

X-List-Administrivia: yes                             

This is an automated response.                        

There were problems with the email commands you sent to
Mailman via             
the administrative address
empeg-faq-request@empeg.merlins.org.                 

To obtain instructions on valid Mailman email commands,
send email to           
empeg-faq-request@empeg.merlins.org 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
empeg-faq-owner@empeg.merlins.org.                  

The following is a detailed description of the
problems.                        

***** confirm 97bbfd70939538b155776d5e652af14bc6032c36

>>>>> An unexpected Mailman error has occurred.       

>>>>>                                                 

>>>>> Please forward your request to the human list
administrator in charge     
>>>>> of this list at
<empeg-faq-owner@empeg.merlins.org>.  The traceback is    
>>>>> attached below and will be forwarded to the list
administrator            
>>>>> automatically.                                  

Traceback (most recent call last):                    

  File
"/var/local/mailman/Mailman/MailCommandHandler.py",
line 273, in         
ParseMailCommands                                     

    self.__dispatch[cmd](args, line, msg)             

  File
"/var/local/mailman/Mailman/MailCommandHandler.py",
line 727, in         
ProcessConfirmCmd                                     

    results = self.ProcessConfirmation(args[0], msg)  

  File "/var/local/mailman/Mailman/MailList.py", line
1041, in                  
ProcessConfirmation                                   

    self.ApprovedChangeMemberAddress(oldaddr, newaddr,
globally)                
  File "/var/local/mailman/Mailman/MailList.py", line
976, in                   
ApprovedChangeMemberAddress                           

    self.changeMemberAddress(oldaddr, newaddr)        

  File
"/var/local/mailman/Mailman/OldStyleMemberships.py",
line 234, in        
changeMemberAddress                                   

    self.__assertIsMember(member)                     

  File
"/var/local/mailman/Mailman/OldStyleMemberships.py",
line 113, in        
__assertIsMember                                      

    raise Errors.NotAMemberError, member              

NotAMemberError: davidtg@bigfoot.com                  

----- End forwarded message -----                     

----- Forwarded message from David T-G
<davidtg@justpickone.org> -----          

% Were  you trying  to change  your subscription  from
davidtg@bigfoot.com  to  
% davidtg-empeg@justpickone.org via the mail interface?

No; I did it thru the web interface.                  

% If so,  do you  mind sending me  a copy of  the mails
 you sent to  the list  
% manager (I run  a devel version of  the upcoming
mailman, and I  try to help  

Sorry; any sort of subscribe and confirm messages I
just toss in the bit        
bucket.  In addition, once the subscriptions were
confirmed, I tossed the       
list server messages as well.  Sorry!                 

% out with small bugs. This one seems to be minor, but
we should probably look  
% into it anyway)                                     

Sorry :-)  It should be easy to duplicate, though;
subscribe to two lists       
(like empeg-faq and empeg-announce), open two web
browsers, go to the two       
list control pages and log in on each, and then send a
change from one          
and a change from the other.  Remember to hit "global"
at some point            
along the way.  When replying to the confirmation
messages, reply to the        
first before doing the global change but the second,
which might                
confusingly arrive after said global change, later
after the web is done.       

----- End forwarded message -----

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

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100103&aid=551730&group_id=103