the WG have been really quite active and a lot of internet SMTP servers now include sieve support. i've been wondering whether we need to take another look at the way the sieve mailet works.
ATM the sieve mailet is the primary means of pushing incoming mail into IMAP. it only works with the IMAP backend and getting mail into IMAP requires the sieve mailet. i was wondering whether we might need to rethink the way sieve interacts with other mailets and matchers. i think it might be more elegant to separate the storage from the sieve mailet. 'fileinto' would then be implemented as a keep plus an attribute setting (org.apache.james.FILEINTO, say) which could be used by any subsequent mailet. storage into IMAP would be supported by a separate storage mailets in the imap project. opinions? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
