> Rather > these mailets should be getting the raw string headers of the message > being forwarded (be it to the Postmaster or to the Sender), putting them > into the message, and sending. The exception being generated is the > result of an exception when one of these headers is invalid - why should > these mailets care if the headers are valid?
I can see this point now, that it should be OK to get the illegal raw header for any other purpose than creating a mailheader from it. > As I mention in the bug, a more serious problem is the hang/crash > reported. The Mailet API should be fairly bulletproof when it comes to > exceptions. I couldn't find an immediate reason why a hang/crash type > behavior was being observed even when this exceptional condition was > being triggered... Quite. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
