# try using "Redirect" in the error processor (and elsewhere) to redirect # them as attachements, that way the "error" will be much less likely to be # recreated. # The risk of re-inserting flawed messages is well known, in this case it # would be of a pernicious (structural?) error in the original message still # affecting delivery, even when wrapped in a new message, causing an # infinite # loop round spool->error->spool->error with the message growing at each # iteration until you run out of ram or storage space.
The mail was dropped into the error bin because of an unhandled ClassCastException that was thrown by the Mailet, which in its own right is enough to give me the heebie-jeebies. The Mailet has been extended to accommodate this so it won't happen again. The trouble is that I can not have the mail re-sent, but I do need to collect it from the James server via POP3. I've tried every thing that I could think of and find through Google, but I just can't get at it, and desperately need to. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
