"Jason R. Mastaler" <[EMAIL PROTECTED]> writes:
Tim Legant <[EMAIL PROTECTED]> writes:
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.
I didn't realize this. And there is no way to avoid the HeaderParser error?
No. That's why I made the comment about Parser raising the HeaderParseError even when self.strict is False. In all other cases Parser will only raise the HeaderParseError exception if self.strict is True. Perhaps that is because messages with this particular error can't really be parsed -- they completely violate RFC2822 formatting rules.
Are you saying we can't catch the HeaderParser error for some reason and ignore the message until the pending queue cleans it up, or are you saying we can't somehow force the message to be parseable?
Is there an example message?
-- Jim Ramsay
_________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
