-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 28 Nov 2008, Miguel Filho wrote:
So Avelsieve will manage, whatever Managesieve places there, and Managesieve does not detect the alien interference.
Avelsieve doesn't manage anything, pysieved does.
OK, so you do use two interfaces, managesieve and pysieved ;-)
But why are you using two sieve management interfaces?
I'm not. I'm testing the ManageSieve patch and preparing to replace pysieved, because it lacks encryption and I need to open direct access to it for my users.
Do the migration pysieved -> managesieve like so:
- Connect with an user without .dovecot.sieve symlink to managesieved.
- Upload a new script.
- Check where the script has been filed into.
- Then replicate the structure for each user and rename the existing file into "phpsieve.sieve" (phpsieve is the name of the script) and adjust the ~/.dovecot.sieve symlink to point there.
E.g. my real users with Maildir
- have ~/.dovecot.sieve -> Maildir/sieve/horde-ingo.sieve
- Maildir base path is ~/Maildir
- and Horde uses "horde-ingo" as script name.
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJL93CVJMDrex4hCIRAi4EAKDDZWVuJ9EgUYiO9xOz9fMXoaWAfwCgyOyq 0Gbh/xj4c0Zb3g3pMd7X26k= =bgr0 -----END PGP SIGNATURE-----