Cyrus Daboo <[EMAIL PROTECTED]> writes:
> I would like to see a standard protocol that all clients could
> use. This would act as a 'wrapper' for whatever storage mechanism a
> particular implemenation may want to use on the back-end, e.g. file
> system, ACAP, IMSP, LDAP etc, but would provide sieve clients with a
> single upload/download API to use.
I think this is a good idea. Some sieve specific things simply don't
map to all protocols -- such as reporting syntactical errors in sieve
scripts, or setting the active script -- and will never work well in
the face of users if clients need to implement several upload
protocols, IMHO.
The managesieve draft mention ACAP as the long term solution. Does
long error message about syntactic errors (which would require a sieve
parser in the ACAP server) fit into the ACAP model? IMHO something
similar to managesieve is simpler and better.
