Hello there,
I have been using pysieved and avelsieve and it has been working great. I decided to do test with the ManageSieve patch and got this problem:
Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using active sieve script path: ~/.dovecot.sieve Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using sieve script storage directory: ~/.sieve Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: relative path to sieve storage in active link: .sieve/ Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: Active sieve script symlink /home/admsis/miguel/.dovecot.sieve is broken: invalid scriptname (points to .sieve/phpscript).
Well as you can see, a file without the .sieve is not welcome :-(
I checked the RFC and there is no requirement for a .sieve file extension when considering scriptnames.
http://tools.ietf.org/html/draft-martin-managesieve-12#section-1.6
Is this a misplaced restriction or it really should be enforced for any reason?
I hope that this can be tolerable, or I will have to rename a lot of scripts and remove all hardcoded "phpscript" strings from avelsieve :-(
Regards and thanks for the great work.
Miguel