[per Jason's message, I'll step up to the plate...] Paul Fisher <[EMAIL PROTECTED]> writes:
> We're running into the previously reported get_payload issue (a > lot), and it's something that should probably be handled in TMDA > itself. I agree. I took at quick glance at this when Cory mentioned it on tmda-users and I think the solution is a custom Generator class. The problem is that we only parse the headers but we use a Generator class to output the message that expects the entire message to have been parsed. I need to look at it in more detail to be sure I don't bork anything else in TMDA, but I think this can be solved. > Could tmda-filter be changed to return a different status code (to > represent a permanent failure) for this error situation? Hopefully this won't be necessary. TMDA should handle those messages appropriately. Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
