On Thu, 2010-01-07 at 14:06 +0100, Stephan Bosch wrote:
> Timo Sirainen wrote:
>
> > I think this should be handled the same way as Dovecot does if mail
> > root's parent directory is 01777. Now, I'm not sure what Dovecot
> > actually currently does in that situation.. :) v1.1 might do
> > whateve
Timo Sirainen wrote:
I think this should be handled the same way as Dovecot does if mail
root's parent directory is 01777. Now, I'm not sure what Dovecot
actually currently does in that situation.. :) v1.1 might do
whatever, I think v1.2+ would try to make it 0777 and shouldn't try
to change the
On 7.1.2010, at 11.44, Stephan Bosch wrote:
>> 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 t
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 di
On Mon, 4 Jan 2010, wolfgang.frie...@desy.de wrote:
After upgrading from dovecot 1.2.3, managesieve 0.11.8, sieve 0.1.11 to
dovecot 1.2.9, managesieve 0.11.10 and sieve 0.1.14 users who do not have
sieve rules yet and use managesieve for the first time do trigger error
messages in the log file
After upgrading from dovecot 1.2.3, managesieve 0.11.8, sieve 0.1.11 to
dovecot 1.2.9, managesieve 0.11.10 and sieve 0.1.14 users who do not have
sieve rules yet and use managesieve for the first time do trigger error
messages in the log file (for the authenticated user ggg in group syspr):
Ja
