Op 2/11/2017 om 3:24 PM schreef dovelist:
> OK, I've figured it out:
>
> In the dovecot profile for apparmor the sieve directory is not
> confgured. I solved it this way:
>
> To configure only one directory in the apparmor profile, I placed the
> active-script link inside the .sieve directory. Kee
Op 2/10/2017 om 5:05 PM schreef dovelist:
> Hi Stephan,
>
>> Normally, Dovecot permission errors are more helpful than that. So, this
>> error message in itself is a bit of a bug:
>
> I'm glad to h've been able to help with this beta-test ;-)
>
>
>> About the cause of this error: keep in mind that
OK, I've figured it out:
In the dovecot profile for apparmor the sieve directory is not
confgured. I solved it this way:
To configure only one directory in the apparmor profile, I placed the
active-script link inside the .sieve directory. Keeping the scripts
separate in a store subdirectory
Hi Stephan,
Normally, Dovecot permission errors are more helpful than that. So,
this
error message in itself is a bit of a bug:
I'm glad to h've been able to help with this beta-test ;-)
About the cause of this error: keep in mind that the whole directory
path needs read/execute permission
Op 2/5/2017 om 8:53 PM schreef dovelist:
> Hi,
>
> I am trying to get sieve working on a new OpenSuse leap 42.2 install.
> On my 'old' OpenSuse 13.2 machine it worked fine.
>
> The problem is that Managesieve can't access the script store and
> won't let me create any script. It says permission den
Hi,
I am trying to get sieve working on a new OpenSuse leap 42.2 install. On
my 'old' OpenSuse 13.2 machine it worked fine.
The problem is that Managesieve can't access the script store and won't
let me create any script. It says permission denied on ~/sieve
directory. See log below. I 've a