wolfgang.frie...@desy.de wrote:
On Mon, 4 Jan 2010, wolfgang.frie...@desy.de wrote:
This piece of code is (if I understand it correctly) trying to set the
group permissions according to the parent directory (assuming that the
sieve storage is somewhere in the users home dir).
Right.
I did however choose to have a different dir layout, the sieve storage
is under /var/spool/sieve/ which has permissions 1777 and is owned by
root:root. Therefore the chown(dir, -1, 0) call is failing, as the
parent dir does not belong to the group of the user but to root.
Ok.
As the directory structure is nevertheless created (with the correct
permissions), the next use of managesieve does no longer complain about
wrong permissions and managesieve is correctly working.
Should I change my choice of sieve_dir as suggested in the wiki:
# Directory for :personal include scripts. The default is to use home
directory.
sieve_dir = %h/sieve
or is my setting a correct alternative?
I try to provide administrators like you with much flexibility, and I
don't see why this kind of directory structure should be discouraged.
Timo, any ideas? I guess I can implement a check to handles this
situation gracefully.
Regards,
Stephan.
