Handling Exceptions in Mailets, Sending custom SMTP responses

[Michael Weissenbacher <we...@dermichi.com>]

Hi List,
I am new to this list and semi-new to JAMES. I've sucessfully set up 
JAMES and i've made some custom matchers and mailets. Reading through 
the documentation, the wiki and "Working with James" from the IBM 
developerworks I consider myself informed :)

Now I wonder what would be the best way to handle unexpected Excpeptions 
in my custom mailets, for example a NullPointerException or a problem 
with the Database Connection. As i've observed the message gets 
forwarded to the error processor and put into the error repository. It 
seems that this is an dead end. Is there an easy way to put these mails 
back to the inbound queue again after fixing the problem (ie properly 
handling the Exception)? Maybe it's possible to configure the error 
processor in a way that the delivery is "retried" for some time.

As far as I followed the documentation and tested JAMES it is not yet 
possible to send back a custom SMTP response like "450 Temporary 
problem". I would need this to implement graylisting. Have i missed 
something or is this still not supported?

I hope that i have made myself clear, otherwise please ask. I can 
provide snippets from my config, matchers and mailets if needed.

thanks for your time,
Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org