Hi Norman,
Thanks for your answers
M> Now I wonder what would be the best way to handle unexpected
M> Excpeptions in my custom mailets, for example a NullPointerException
M> or a problem with the Database Connection. As i've observed the
M> message gets forwarded to the error processor and put into the error
M> repository. It seems that this is an dead end. Is there an easy way to
M> put these mails back to the inbound queue again after fixing the
M> problem (ie properly handling the Exception)? Maybe it's possible to
M> configure the error processor in a way that the delivery is "retried"
M> for some time.
Read this:
http://wiki.apache.org/james/HandlingExceptions
Thanks for this, i've already read it. If i understand correctly, James
would leave a message in the spool if an exception occured before
version 2.2.0a7. Is there a way to achieve the same with James 2.3.0?
Maybe you can also comment on the error spool, is there an easy way to
"resend" a message that went there? Is there some spool manager
interface or is it safe to update/delete/move the spool records while
JAMES is running (i use the db spool with MySQL)?
For greylinsting you should write a new SMTP CommandHandler. .. BTW,
this is allready done in trunk.
Can i write a SMTP CommandHandler for 2.3.0? This should become a
production system and I would be wary to use an unreleased version of
JAMES for it. Maybe it's possible to use the CommandHandler from trunk
and put it into 2.3.0?
with kind regards,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
