dovecot - Jan 2009 - managesieve/README sieve_storage doc confusion

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

http://hg.rename-it.nl/dovecot-1.2-managesieve/file/tip/README contains 
the paragraphs (line 47):

"
mail_location      If, for some inobvious reason, the sieve_storage remains
unset, the
     managesieve daemon uses the specification of the mail_location to find out
     where to store the sieve files. However, this is provided only for
backwards
     compatibility and you should always use the sieve_storage setting in stead.

Additionally, the ManageSieve service uses the following settings from the
plugin
section of the config file. These settings are the ones used by the Sieve
plugin.

sieve_dir      This specifies the path to the directory where the uploaded
scripts are
     stored. Scripts are stored as separate files with extension .sieve, all
other
     files are ignored when scripts are listed by a ManageSieve client. If this
     setting remains unspecified, the mail_location setting is used as explained
     above.
"


Because sieve_storage is not mentioned anywhere else in the document
and because of this discussion:
http://dovecot.markmail.org/message/kzjpwdhyqhdn53zd , I suspect that
sieve_dir is the older naming of it. However, the source code uses
getenv("SIEVE_DIR") in lib-cmusieve, so this assumption is probably
wrong.

What's the correct meaning and placement of sieve_storage and sieve_dir ?

Bye,

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBSYMey3WSIuGy1ktrAQIfSwf/bF7ATn3MLDHL/rMZgqj5+cbHT5t60+UJ
Zq3ktiUePwbk1bP04Xtm0zrhY9g/E7pk3Q5WUAR2+laVUAYz1FIg5wp+ukS/lTpi
cbM3cXC4ZqcOPVqcb2Ntxjujx0FRjJzH/KVVp8JBTkHUQ3HWV8dXuyWxkpfAgnpw
O7t2uPW9fgzF7ACqQndjN/Qo/Xj6WUzICgI+SndNMscxipU20DY6CfMtOWDXJxl9
UPoLhHtB9GuylaKDNChY6bmYkO023veHuQMsOsziit0Ks25BO7J/bbiOieRaTesh
+O33abIQv8mzj186YZ34Z5zRtn1xa7gFNntkbk31zi2xYkCmo2atUw==DyFs
-----END PGP SIGNATURE-----

Steffen Kaiser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> http://hg.rename-it.nl/dovecot-1.2-managesieve/file/tip/README contains 
> the paragraphs (line 47):
> 
Do'h! I forgot to rename those into sieve_dir. As per v1.2, the 
sieve_storage setting was renamed to sieve_dir and moved to the plugin 
section. This setting was already in use by the Sieve plugin and this 
change removes the possibility of specifying different directories for 
the ManageSieve service and the Sieve plugin.

I revised the README a little more than only the mention of 
sieve_storage. It was not very coherent anymore since the last major 
config changes. It should be much clearer now.
> What's the correct meaning and placement of sieve_storage and sieve_dir
?
Sieve_storage is depricated (if accepted at all). You should only use 
sieve_dir and place it in the plugin section. This way, both Sieve and 
ManageSieve use the same directory at all times. For identical reasons, 
the 'sieve=' setting is now located solely in the plugin section as
well.

Regards,

Stephan.