james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JSIEVE-56) Provide a way to determine if a keep action is implicit or explicit
Date Wed, 22 Jul 2009 15:59:14 GMT

    [ https://issues.apache.org/jira/browse/JSIEVE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734172#action_12734172

Robert Burrell Donkin commented on JSIEVE-56:

Making available the Context seems like the right way to approach this.

A couple of alternatives:

* Pass the context into every method
* Add a setter together with an API contract

Using a setter is only practical if MailAdapter is not concurrently reused. This needs to
be looked into a little deeper.

> Provide a way to determine if a keep action is implicit or explicit
> -------------------------------------------------------------------
>                 Key: JSIEVE-56
>                 URL: https://issues.apache.org/jira/browse/JSIEVE-56
>             Project: JAMES jSieve
>          Issue Type: Improvement
>          Components: JSieve (Main)
>    Affects Versions: 0.3
>            Reporter: Boris Burtin
> There's no way to distinguish an implicit keep from an explicit keep in jSieve 0.3. 
The Zimbra code needs this distinction because implicit keeps are affected by spam filtering
and explicit keeps are not.  This was possible in jSieve 0.2 with CommandStateManager.getInstance().isImplicitKeep(),
but no longer possible in 0.3 after the changes for JSIEVE-26.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message