[ response to message tmda-users, moved here because it's a real bug ] "Jason R. Mastaler" <[EMAIL PROTECTED]> writes:
> Are you running TMDA 1.0? I'm not sure this will fix your problem, > but we fixed lots of similar bugs, so it just might. This appears to be a real problem. In the first place, Pending.Message.__init__ catches BoundaryErrors, but not HeaderParseErrors. Sigh. It should catch MessageErrors. 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. Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
