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 robert burrell donkin <ro...@gmail.com> on 2007/01/16 14:02:16 UTC

[SIEVE] creating SIEVE scripts

i've never liked the SIEVE format. it seems too easy to make mistakes
and not at all human readable. i've done some reading and the
reasoning behind this seems to be that SIEVE was intended to be a
machine generated format and that users would use a GUI to create
SIEVE scripts.

so as a server side filtering option, it has drawbacks. a few things strike me:

1. it should be possible to create an xml language which can be
checked against a schema and which can be transformed into a SIEVE
execution script. there are plenty of UIs out there for xml.

2. jochen's code is well factored: it should be easy to separate the
filtering from the SIEVE implementation. maybe james could support a
common filtering interface and allow any compliant mail filter to be
plugged in.

3. a web UI is probably needed before it's realistic to expect
non-developers to use this feature.

opinions?

- robert

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