Re: [pysieved] Unable to delete rule

[Neale Pickett <neale at woozle dot org>]

On Monday 30 April 2007 12:57:55 pm Martin Konopka wrote:

> 1177959286.97 C: 'DELETESCRIPT "phpscript"'
> 1177959286.97 C: 'NO "Script is active"\r\n'

My first thought is that it is an avelsieve bug; the managesieve RFC states 
that you must deactivate a script before you can delete it, and pysieved 
tests many delete scenarios in the test script, including this one.

It's entirely possible that timsieved allows you to delete an active 
script--it wouldn't be the first time an implementation got an RFC detail 
wrong.  If this is the case, we have two options:

1. Take the moral high ground and submit a patch to avelsieve
2. Add a "timsieved compatibility" mode to pysieved which will allow deletion 
of an active script

Does anybody on the list have access to a running timsieved (Cyrus) instance 
to verify it's possible to delete and active script?

Neale