"Jason R. Mastaler" <[EMAIL PROTECTED]> writes: > Tim Legant <[EMAIL PROTECTED]> writes: > >> 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.
Hmm. A clarification to this, too. This is not just a tmda-cgi / Pending.py problem. Although John may not be aware of it, this message is causing output to LOGFILE_DEBUG (or TMDA_DELIVERY_FAILURE) each time his MTA tries to deliver it. It cannot be successfully parsed by HeaderParser and so Util.msg_from_file fails when tmda-filter runs. Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
