[
https://issues.apache.org/jira/browse/JAMES-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208379#comment-13208379
]
Eric Charles commented on JAMES-1373:
-------------------------------------
Hi Brad, It would be great if you could contribute some code on this :)
In fact, the LocalDeliveryMailet calls the SieveMailet, so what you propose
with SieveLocalDeliveryMailet is in a way already the case.
Regarding 3028 ยง2.10, we already evaluate the script
(SieveMailboxMailet.sieveMessage() which calls sieveMessageEvaluate(), catches
exception, and finally storeMessageInbox()).
storeMessageInbox() calls SieveMailet.post() which in all cases invokes the
mailbox for the user and appends the message in the INBOX (whatever the sieve
result is).
There may be a missing step 'processSieveResult()' between the
sieveMessageEvaluate() and storeMessageInbox().
If you look at the different sieve commands, many are really close to some
existing james mailets. I wonder if we could find some kind of mapping and
reuse some mailet for each of the sieve action/result.
Are maybe each of the Sieve Action should have a corresponding Mailet, or even
be a mailet (they already depend on mailet packages).
> Test and document jsieve in server 3.0b4
> ----------------------------------------
>
> Key: JAMES-1373
> URL: https://issues.apache.org/jira/browse/JAMES-1373
> Project: JAMES Server
> Issue Type: Improvement
> Reporter: Eric Charles
>
> Now that jsieve is update for mime4j-0.7.2, we can further test and document
> the sieve scripts in server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
