I will try the patch out. Because I was not able to personally replicated it and it was difficult to get an explanation from users I made the error page just go back to pending. This prevented panic from users that do not need to panic.
An idea for the future may be to do something with tmda-cgi that is more friendly. Those python errors just freak normal people out when there is not really a sesrious problem. Maybe tmda-cgi, instead of dumping information to the user, could dump it to a log file instead. Then, tmda-cgi just goes back to pending or displays a friendly message like "error occurred, please log in again). The template is easy enough to change but I am not sure how to get tmda-cgi to write to a log file only admins read instead. Thank you. Sam -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Ramsay Sent: Wednesday, February 18, 2004 11:35 AM To: [EMAIL PROTECTED] Subject: Re: %s not found! - TMDA-CGI error Samuel Hill wrote: > I have been getting the following reports of errors using tmda-cgi. > The reports indicate that they are clicking allow or maybe delete on > certain messages and it dumps. > > I have not been able to duplicate this problem. > I thought that because it said "message not found" that it may be > trying to allow a message that is gone. That does not appear to be the > case, at least in my testing I could not get the error. > In the past I had this same problem but it was patched and then fixed in > the last version. > > I am using tmda-cgi-0.12. > > At the very bottom of this message is the message that is listed in > this error. I have many reports of this problem but have not been able > to actually duplicate it so there most be some sequence I am missing > to have this happen. I don't know exactly how to replicate it either, but one possible scenario is: - User logs in and goes into Pending List - Pending List code builds a list of pending messages internally, based on a directory listing. - Pending List code then begins going through the messages it needs to display from this list, displaying each one. It gets through #1 and #2 - As it is going through #3, #10 is deleted by some other method (cron job, tmda auto-cleaning the pending queue, another user sharing the pending queue deletes it) - When the Pending List gets to #10, it trys to display this message, but cannot, and then the error comes up. I have fixed this (I think) in CVS. Before the next release, you can try the following patch, and please report any errors with it immediately: Index: PendList.py =================================================================== RCS file: /cvsroot/tmda/tmda-cgi/PendList.py,v retrieving revision 1.34 diff -r1.34 PendList.py 431c431,432 < except (IOError, email.Errors.MessageError), ErrStr: --- > except (IOError, Errors.MessageError, \ > email.Errors.MessageError), ErrStr: -- Jim Ramsay "Me fail English? That's unpossible!" _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
