Steve Brewin wrote: A few more observations. org.apache.jsieve.samples.james.JSieve contains the following Javadoc (I guess I knew not to trust my hazy memory)...
/** * <p> * Class JSieve is a DEMONSTRATION Mailet that invokes JSieve to * perform mail processing. There is a single configuration parameter, * <code>scriptURL</code>. This a URL pointing to the resource containing * the Sieve script to run. * </p> * * <p> * This Mailet is intended to replace the <code>LocalDelivery</code> * Mailet in James. Sieve's Keep Action is functionally equivalent to the * <code>LocalDelivery</code> Mailet's processing. The Sieve script may * explicitily or implicitly invoke this Action, and/or any other * configured Action. Actions are configured in class * <code>ActionDispatcher</code>. * </p> * * <p>IMPORTANT NOTES</p> * * <p> * This is NOT production quality code! It is a test harness for exercising * jSieve. At least the feutures listed below would be required to consider * this of production quality. * </p> * * <p>REQUIRED FEATURES</p> * * <p> * To be truly useful, this mailet needs to be configurable to invoke * user specific Sieve scripts so that indivual users have control of their * mail processing. * </p> * * <p> * In a Mailet environment, a generic Sieve command to invoke a Mailet * would be extremely powerful as jSieve could then leverage the abilities * of all available Mailets. Currently, Sieve must wastefully duplicate * the same behaviour as Sieve commands. * </p> * * <p>The converse also applies. Provision should be made for a Mailet to * reuse jSieve commands. As the primary difference between the two is * that Sieve deals with a single recipient while Mailets deal with * multiple recipients, a Mailet could simply iterate over all of its * recipients invoking the Sieve command for each recipient. * </p> */ <snipped> They key thing here, which I haven't previously mentioned, is that to achieve 'Mailet Nirvana' whereby we could invoke a pre-existing Mailet as a Sieve custom action, an Adapter would be required to invoke Mailets that would bridge the different sematics of Sieve and the Mailet chain. The converse, having Mailets invoke jSieve commands, is very easy to do and much more efficient. Unfortunately, it doesn't bring much to the table as there aren't any! Its more an observation how the semantics differ. A further issue, one discussed at length on relation to IMAP, is that our POP3 implementation does not support sub-folders of the INBOX. The sample code simply prepends to the mail header where it would have written the mail to, physically everything stays in the users INBOX. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
