james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <server-...@james.apache.org>
Subject [jira] [Resolved] (JAMES-1615) Write a SieveDefaultRepository that correspond to the today defaut behaviour
Date Tue, 15 Dec 2015 14:10:46 GMT

     [ https://issues.apache.org/jira/browse/JAMES-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tellier Benoit resolved JAMES-1615.
-----------------------------------
    Resolution: Fixed

Contributed.

Warning : you need an updated JSIEVE jar in order to build James project...

> Write a SieveDefaultRepository that correspond to the today defaut behaviour
> ----------------------------------------------------------------------------
>
>                 Key: JAMES-1615
>                 URL: https://issues.apache.org/jira/browse/JAMES-1615
>             Project: James Server
>          Issue Type: New Feature
>          Components: UsersStore & UsersRepository
>    Affects Versions: Trunk
>            Reporter: Tellier Benoit
>             Fix For: Trunk
>
>
> Todays, a direct lookup for Sieve scripts is directly done in var/sieve directory.
> It does not correspond to the SieveFileRepository works (a directory per user + active
script).
> We should implement a READ only repository that retrieve scripts directly stored in var/sieve
directory 
> The idea behind that is to be able to switch SIEVE script localisation from direct FileSytem
lookup to SIEVEReposioty use without loosing retro-compatibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message