Joachim Draeger wrote: > Sent: 13 January 2007 10:06 > To: 'James Developers List' > Subject: RE: Sieve integration Was: svn commit: r495746 - > in/james/server/trunk: ./ lib/ src/conf/ src/java/ > src/java/org/apache/james/src/java/org/apache/james/transport/ > mailets/sr > c/java/org/apache/james/transport/mailets/sieve/ > > > Am Freitag, den 12.01.2007, 21:55 +0000 schrieb Steve Brewin: > > [EMAIL PROTECTED] wrote: > > Whoa! Great stuff Joachim! > > Well, almost copy&paste from the jSieve samples. :-) But in fact a > server side, user editable, mail sorting is a great feature, I > personally don't want to miss anymore. > (I'm accessing my IMAP account by PC, notebook and webmail) > > > I don't have much bandwidth, but feel free to ask if you > need any help. > > First let me say, that this is an important point but currently not on > top of my roadmap. But I'm willing to implement basic > functionality and > maybe someone else wants to pick up and make it stable.
Whatever you manage is infinitely more than the progress I've made :) > I'm not so familiar with the Mailet API and how Mail is > handled there. > > At the moment Actions awaits a Mail object with a single recipient and > fails if there are more. > Original example seems to split up multiple recipients in a first step > and put them back on the queue. There are also traces of a > duplicateMail > method. > Another aspect is that sieve script can test the envelope. Maybe we > should leave envelope complete, and pass over the current recipient > outside the Mail object? As Stefano noted in his reply, Sieve expects a sole recepient. The sample code achieves this be cloning the mail once for each recipient prior to exposing it to Sieve. This makes sense as each recipient will have their own script to apply to their copy of the mail. > BTW: What happens if sieve script passes and no action has been taken? > Should the mail be stored in INBOX just like when the keep command is > performed? The default action of keep should be taken. > IMO the keep command should not directly fileinto INBOX but sieve > processing should give a corresponding result, to tell if normal > delivery should be continued or has finished. Because of the cloning described above and whatever each user's script has done, each user's version of the original mail may have been transformed in a variety of ways. The only safe thing to do is treat the Sieve mailet as the end of the road and not pass the transformed mails back into the processor. When the final implicit of explicit scripted action is keep, the mail should be stored in the appropriate INBOX. Think of this as the equivalent of a POP3 client processing the mail for the user which you wouldn't expect to make the mail available for further processing. Its just that with Sieve we are running the client processing server side on behalf of the user. Many thanks for your efforts. Cheers -- Steve > > Joachim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
