Serge Knystautas wrote: > This just came across the Sieve extensions mailing list and > thought it's > relevant to Was: SMTPACL.
One of the goals in my mind for the James implementation of Sieve is to be able to leverage all of the existing good stuff in implemented Mailets and Matchers by enabling Sieve Commands and Tests to invoke them. This will avoid coding behaviours as Sieve Commands and Tests that we already have in Mailets and Matchers. The first demo. implementation of Sieve on James will be a Mailet, which is almost complete, will not be able to do this. It is not possible to set up a Mailet environment from within Sieve invoked from a Mailet as James resources are required that are (correctly) not exposed in the Mailet API. Once Sieve is invocable at the container level, these problems disappear. This means any work done implementing SMTPACL, or whatever, can ultimately be leveraged by Sieve. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
