Problem with Pigeonhole/Sieve

Kamil Kapturkiewicz horizn at wp.pl
Mon May 1 21:17:16 EEST 2017


Hi,

I am trying to configure Pigeonhole to get filters in RoundCube working. 
Unfortunately I am getting following error in DoveCot log instead:

May 01 14:35:41 managesieve-login: Error: auth: connect(login) in 
directory / failed: Permission denied (euid=248(<getpwuid() error>) 
egid=248(<getgrgid() error>) missing +x perm: /, we're not in group 202, 
dir owned by 0:202 mode=0750)
May 01 14:35:41 managesieve-login: Error: auth: connect(login) in 
directory / failed: Permission denied (euid=248(<unknown>) 
egid=248(<unknown>) missing +x perm: /, we're not in group 202, dir 
owned by 0:202 mode=0750)
May 01 14:36:00 master: Warning: Killed with signal 15 (by pid=37695 
uid=0 code=kill)
May 01 14:36:36 managesieve-login: Error: auth: connect(login) in 
directory / failed: Permission denied (euid=248(<getpwuid() error>) 
egid=248(<getgrgid() error>) missing +x perm: /, we're not in group 202, 
dir owned by 0:202 mode=0750)
May 01 14:36:36 managesieve-login: Error: auth: connect(login) in 
directory / failed: Permission denied (euid=248(<unknown>) 
egid=248(<unknown>) missing +x perm: /, we're not in group 202, dir 
owned by 0:202 mode=0750)
May 01 15:17:08 managesieve-login: Error: auth: connect(login) in 
directory / failed: Permission denied (euid=248(<getpwuid() error>) 
egid=248(<getgrgid() error>) missing +x perm: /, we're not in group 202, 
dir owned by 0:202 mode=0750)
May 01 15:17:08 managesieve-login: Error: auth: connect(login) in 
directory / failed: Permission denied (euid=248(<unknown>) 
egid=248(<unknown>) missing +x perm: /, we're not in group 202, dir 
owned by 0:202 mode=0750)

Above appears in log, when I am trying to access filters configuration 
in RC or manually connecting to sieve using telnet.

My DoveCot configuration:

# 2.2.27 (c0f36b0): /usr/local/dovecot/etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.15 (97b3da0)
# OS: Linux 4.4.38 x86_64 Slackware 14.2 ext4
debug_log_path = /var/log/dovecot/dovecot-debug.log
first_valid_gid = 12
first_valid_uid = 8
info_log_path = /var/log/dovecot/dovecot-info.log
last_valid_gid = 12
last_valid_uid = 8
listen = *, [::]
log_path = /var/log/dovecot/dovecot.log
mail_location = maildir:/var/mail/%d/%n
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope 
encoded-character vacation subaddress comparator-i;ascii-numeric 
relational regex imap4flags copy include variables body enotify 
environment mailbox date index ihave duplicate mime foreverypart extracttext
passdb {
   args = /etc/dovecot/dovecot-sql.conf
   driver = sql
}
protocols = imap pop3 sieve
service auth {
   user = dovecot
}
service imap-login {
   user = dovecot
}
service pop3-login {
   user = dovecot
}
ssl_cert = </etc/letsencrypt/live/domain/fullchain.pem
ssl_cipher_list = ALL:!ADH:!LOW:!SSLv2:!SSLv3:!EXP:!aNULL:+HIGH:+MEDIUM
ssl_key =  # hidden, use -P to show it
userdb {
   driver = prefetch
}
verbose_proctitle = yes
protocol pop3 {
   pop3_uidl_format = %08Xu%08Xv
}

What could be a reason of that?


-- 
skype. kamil.kapturkiewicz
tel/whatsapp. +44 758 306 8467



More information about the dovecot mailing list