Unable to connect to dovecot via pop3, although the authorization succeeds.
In **/var/log/mail.err
**
dovecot: doveconf: Fatal: execvp(/usr/lib/dovecot/managesieve) failed: Argument list too long
dovecot: config: Error: managesieve-login: dump-capability process returned 89
I ManageSieve all disabled in the config dovecot (by default).
But its inclusion and change any limits options no effect.
Even the port 4190 is silent. https://wiki2.dovecot.org/Pigeonhole/ManageSieve/Configuration
This manual not halp me.
How do I configure ManageSieve or disable it to dovecot accept connections on pop3?
**doveconf | grep sieve
**
doveconf: Fatal: execvp(/usr/lib/dovecot/managesieve) failed: Argument list too long
doveconf: Error: managesieve-login: dump-capability process returned 89
managesieve_client_workarounds =
managesieve_implementation_string = Dovecot Pigeonhole
managesieve_logout_format = bytes=%i/%o
managesieve_max_compile_errors = 5
managesieve_max_line_length = 65536
managesieve_sieve_capability =
sieve = file:~/sieve;active=~/.dovecot.sieve
service managesieve-login {
executable = managesieve-login
inet_listener sieve {
protocol = sieve
service managesieve {
executable = managesieve
protocol = sieve
unix_listener login/sieve {
Even if /etc/dovecot/conf.d/90-sieve.conf comment out the line #sieve = file:~/sieve;active=~/.dovecot.sieve
and restart dovecot it does not make any changes.
Log connection attempts to pop3.
Dec 20 17:21:30 master: Info: Dovecot v2.2.27 (c0f36b0) starting up for imap, pop3, lmtp (core dumps disabled)
Dec 20 17:24:08 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/modules/auth
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2002, ret=-1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2002, ret=-1: unknown state [209.85.220.164]
Dec 20 17:24:08 auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libdriver_mysql.so
Dec 20 17:24:08 auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libdriver_pgsql.so
Dec 20 17:24:08 auth: Debug: Module loaded: /usr/lib64/dovecot/modules/auth/libdriver_sqlite.so
Dec 20 17:24:08 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat
Dec 20 17:24:08 auth: Debug: passwd-file /etc/dovecot/users: Read 1 users in 0 secs
Dec 20 17:24:08 auth: Debug: auth client connected (pid=29847)
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2001, ret=1: unknown state [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [209.85.220.164]
Dec 20 17:24:08 pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [209.85.220.164]
Dec 20 17:24:09 auth: Debug: client in: AUTH 1 PLAIN service=pop3 secured session=xKiyoBhE34PRVdyk lip=178.150.103.17 rip=209.85.220.164 lport=995 rport=33759 resp=AGlseWFAaWx5YS5wcC51YQBTeG9ha2FXZ0VpODBaU3h5 (previous base64 data may contain sensitive data)
Dec 20 17:24:09 auth: Debug: passwd-file(ilya@ilya.pp.ua,209.85.220.164,<xKiyoBhE34PRVdyk>): lookup: user=ilya@ilya.pp.ua file=/etc/dovecot/users
Dec 20 17:24:09 auth: Debug: client passdb out: OK 1 user=ilya@ilya.pp.ua
Dec 20 17:24:09 auth: Debug: master in: REQUEST 756285441 29847 1 5a69b044f09d1f1309177b4ecdbcfbbb session_pid=29852
Dec 20 17:24:09 auth: Debug: passwd-file(ilya@ilya.pp.ua,209.85.220.164,<xKiyoBhE34PRVdyk>): lookup: user=ilya@ilya.pp.ua file=/etc/dovecot/users
Dec 20 17:24:09 auth: Debug: master userdb out: USER 756285441 ilya@ilya.pp.ua
Dec 20 17:24:09 pop3-login: Info: Login: user=<ilya@ilya.pp.ua>, method=PLAIN, rip=209.85.220.164, lip=178.150.103.17, mpid=29852, TLS, session=<xKiyoBhE34PRVdyk>
Dec 20 17:24:09 pop3(ilya@ilya.pp.ua): Debug: Added userdb setting: plugin/=yes
Dec 20 17:24:09 pop3-login: Debug: SSL alert: close notify [209.85.220.164]
More precisely in the presence of one extra characters left angle bracket.
Without it works fine, but it gives the logs God knows that in no way connected, even with SSL.
dovecot: doveconf: Fatal: execvp(/usr/lib/dovecot/managesieve) failed: Argument list too long
dovecot: config: Error: managesieve-login: dump-capability process returned 89
While some certificates are specified at the left angle bracket, but namely this certificate are specified without it.
So for instance you’re probably better off commenting out the MANAGESIEVE logout format string.
Recommend you modify each other setting similarly and then enable later one by one so you’re certain what may cause an error or not.