A. Modify /org/apache/james/transport/JamesSpoolManager.java to put a delay into the accept() call for the inbound spool. This has the disadvantage of delaying processing of all messages, not just a subset. In addition we have to spin
a build of James, which isn't a big deal but is less convient than using the Mailet API.
B. Write a matcher for the set of messages we want to delay, route them to a custom processor. In that processor have
a custom Mailet which writes to a custom Spool repository and runs a number of threads which then pluck from that
repository using an accept(delay) call.
Would prefer something akin to B, only not sure if it is possible or straightforward to configure an additional spool and get a handle to it inside our "Delay" mailet.
Any feedback welcome.
Using James 2.1.3 on Linux under JDK1.3.X.
Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
