The message still says "unable to connect to sieve server" ,and dovecot log shows nothing about sieve problem.. and port 2000 is on listening .
dovecot managesiev 2329 4 tcp4 *:2000 *:*
I found the directory plugins/managesieve/ ,so should I set the main config
$config['plugins'] = array('sieverules');
to
$config['plugins'] = array('sieverules' 'managesieve');
?
Whats different between sieve and managesieve ,I think managesieve is a service for sieve ,am I right ?
Below is dovecot log
Feb 24 15:55:55 dovecot: Info: Dovecot v1.2.17 starting up
Feb 25 10:39:39 dovecot: Warning: Killed with signal 15 (by pid=17550 uid=0 code=kill)
Feb 25 11:29:07 imap-login: Warning: Killed with signal 15 (by pid=17911 uid=0 code=kill)
Feb 25 11:29:07 imap-login: Warning: Killed with signal 15 (by pid=17911 uid=0 code=kill)
Feb 25 11:29:07 auth-worker(default): Warning: Killed with signal 15 (by pid=17911 uid=0 code=kill)
Feb 25 11:29:07 auth(default): Warning: Killed with signal 15 (by pid=17911 uid=0 code=kill)
Feb 25 11:29:07 imap-login: Warning: Killed with signal 15 (by pid=17911 uid=0 code=kill)
Feb 25 11:29:07 dovecot: Warning: Killed with signal 15 (by pid=17911 uid=0 code=kill)
Feb 25 14:03:58 dovecot: Warning: Killed with signal 15 (by pid=1659 uid=0 code=kill)
Feb 25 14:12:32 dovecot: Warning: Killed with signal 15 (by pid=1763 uid=0 code=kill)
Below is dovecot-debug log
root@backup1:/root # cat /var/log/dovecot-debug.log
Feb 25 10:39:39 dovecot: Info: Dovecot v1.2.17 starting up
Feb 25 13:06:33 dovecot: Info: Dovecot v1.2.17 starting up
Feb 25 14:03:58 dovecot: Info: Dovecot v1.2.17 starting up
Feb 25 14:12:32 dovecot: Info: Dovecot v1.2.17 starting up