Tim Legant <[EMAIL PROTECTED]> writes: > This appears to be a real problem.
Bummer. > In the first place, Pending.Message.__init__ catches BoundaryErrors, > but not HeaderParseErrors. Sigh. It should catch MessageErrors. Can you clarify what you mean by this? > However, that won't fix the problem in John's case. The code will > still throw an exception when __init__ tries to use the HeaderParser. > The problem is that the message is completely unparsable because > > 1) It has a continuation line before any header field begins; it's > format is completely bogus. > > 2) Parser raises the HeaderParseError in that case regardless of > whether it is in strict mode or not. There's no way that I can see > to solve the problem. Jim/Greg, Is there any way for tmda-cgi to work around this in the UI? Possibly allowing the user to delete a horribly bogus message when such an exception is triggered. Otherwise, admin intervention is required to remove the message which is undesirable. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
