You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Eric Charles (Created) (JIRA)" <se...@james.apache.org> on 2012/02/14 16:02:04 UTC

[jira] [Created] (JAMES-1373) Test and document jsieve in server 3.0b4

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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] [Commented] (JAMES-1373) Test and document jsieve in server 3.0b4

Posted by "Brad Koehn (Commented) (JIRA)" <se...@james.apache.org>.
    [ https://issues.apache.org/jira/browse/JAMES-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207969#comment-13207969 ] 

Brad Koehn commented on JAMES-1373:
-----------------------------------

I'd be happy to implement the logic to evaluate the fieldActions and act accordingly. I would seem to make sense to have a process that takes in the fieldActions list and outputs a list that follows the guidelines in 3028 §2.10. Once that process has been applied, have processors that understand how to execute the various types of actions. 

With regards to the mailet infrastructure, wouldn't it make sense to enable Sieve by simply replacing the LocalDelivery mailet with a SieveLocalDeliveryMailet? One could then through configuration override the processors that are used to execute the actions. 
                
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] [Commented] (JAMES-1373) Test and document jsieve in server 3.0b4

Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
    [ https://issues.apache.org/jira/browse/JAMES-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207790#comment-13207790 ] 

Eric Charles commented on JAMES-1373:
-------------------------------------

The scripts are correctly parsed (see log hereafter), but the SieveMailboxMailet must be enhanced to further process the commands results.
This is also related to JAMES-1365

INFO  16:37:51,692 | james.mailetcontext | Command name: if Arguments: [] Tests: TEST LIST: [Test name: size Arguments: [:over, 102400] Tests: null] Block: BLOCK: COMMANDS: [Command name: reject Arguments: [[I'm sorry, I do not accept mail over 100kb in size. 
Please upload larger files to a server and send me a link.
Thanks.]] Tests: null Block: null]
INFO  16:37:51,692 | james.mailetcontext | Expression starts line 9 column 1
INFO  16:37:51,692 | james.mailetcontext | Expression ends line 13 column 1
INFO  16:37:51,692 | james.mailetcontext | Test name: size Arguments: [:over, 102400] Tests: null
INFO  16:38:06,079 | james.mailetcontext | Command name: elsif Arguments: [] Tests: TEST LIST: [Test name: address Arguments: [:is, [From, To], [eric@localhost.net]] Tests: null] Block: BLOCK: COMMANDS: [Command name: fileinto Arguments: [[INBOX.mailinglist]] Tests: null Block: null]
INFO  16:38:06,079 | james.mailetcontext | Expression starts line 17 column 1
INFO  16:38:06,079 | james.mailetcontext | Expression ends line 19 column 1
INFO  16:38:06,079 | james.mailetcontext | Test name: address Arguments: [:is, [From, To], [eric@localhost.net]] Tests: null

                
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] [Commented] (JAMES-1373) Test and document jsieve in server 3.0b4

Posted by "Stefano Bagnara (Commented) (JIRA)" <se...@james.apache.org>.
    [ https://issues.apache.org/jira/browse/JAMES-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207796#comment-13207796 ] 

Stefano Bagnara commented on JAMES-1373:
----------------------------------------

I don't remember past discussions about this. So maybe it has to be analyzed, yet. I don't have enough sieve knowledge to help here.
                
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] [Commented] (JAMES-1373) Test and document jsieve in server 3.0b4

Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
    [ https://issues.apache.org/jira/browse/JAMES-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207794#comment-13207794 ] 

Eric Charles commented on JAMES-1373:
-------------------------------------

Any input regarding the integration of the sieve scripts result? (previous discussion... ?)

For now, I read that the sieve scripts is evaluated (sieveMessageEvaluate), and whatever the result is, storeMessageInbox is called, so the mail is simply directed to the user's INBOX whatever the scripts result are.

If such, we need to discuss how to process the results, taking into account we have a mailet infrastructure. If it take too long, the integration will be postponed after 3.0b4 release, otherwise it would be a nice feature to offer now.

                
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] [Commented] (JAMES-1373) Test and document jsieve in server 3.0b4

Posted by "Eric Charles (Commented) (JIRA)" <se...@james.apache.org>.
    [ 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org