Hey all,

Have an odd problem I was hoping someone could give me some ideas on
how/where I could look to diagnose the problem.

Our application uses james 2.2.0 (not sure of the point release off hand) to
pass messages to our application via a mailet.  Sometimes we're noticing an
occasional message gets left behind in the spool directory after being
processed.

There doesn't seem to be any exception or error messages in the logs for the
message id or sender etc. that I can see, just the two files
(FileStreamStore and FileObjectStore) for each message that somehow gets
left behind.

Its as thou James failed to physically delete the files, but thinks that it
has.  Does anyone know if this was a known bug in James 2.2.0 at all?

Cheers,
Mark

Reply via email to