Re: Managesieve problem

What directory is sieve configures to use? Mine is: sieve = ~/Maildir/dovecot.sieve

Which is: drwxr-xr-x. 13 root root system_u:object_r:home_root_t:s0 4096 Jul 17 2015 /home drwx------. 13 bill bill unconfined_u:object_r:user_home_dir_t:s0 4096 Aug 30 2015 /home/bill drwx------. 84 bill bill system_u:object_r:mail_home_rw_t:s0 8192 Jul 22 17:02 /home/bill/Maildir drwxr-x---. 3 bill bill system_u:object_r:mail_home_rw_t:s0 4096 May 27 08:09 /home/bill/Maildir/sieve

Bill

On 7/19/2016 7:19 PM, Joseph Mays wrote:

Sorry, meant to include the dovecot version.

root@4s-mail:~# dovecot --version 2.0.19

-----Original Message----- From: Joseph Mays Sent: Tuesday, July 19, 2016 7:03 PM To: dovecot@dovecot.org Subject: Managesieve problem

Trying to get either avelsieve or server side filters to work with managesieve. Managesieve is running but whenever avelsieve or the server settings backend try to talk to it the same thing happens. So I guess it's really a problem with something about managesieve at this point. I hit the Message Filters option, it takes a long time for it to come back, though it finally just times out and does nothing, and immediately when I click on the Message Filters link the following two messages appear in /var/log/dovecot....

2016-07-18 17:03:02 managesieve-login: Error: auth: connect(login) in directory / failed: Permission denied (euid=108() egid=65534() missing +x perm: /, dir owned by 0:111 mode=0750) 2016-07-18 17:03:02 managesieve-login: Error: auth: connect(login) in directory / failed: Permission denied (euid=108() egid=65534() missing +x perm: /, dir owned by 0:111 mode=0750)

Seems to be straightforwardly a permissions error on a directory, but I don't believe it's really the / directory, so which directory is it? Any insights on where to look would be appreciated.