[Dovecot] ManageSieve and invalid scriptname
skdovecot at smail.inf.fh-brs.de
Fri Nov 28 14:02:08 EET 2008
-----BEGIN PGP SIGNED MESSAGE-----
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the dovecot