1 Topic by jstewart

  • jstewart
  • Member
  • Offline
  • Registered: 2017-02-10
  • Posts: 102

Topic: Managesieve error

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.8
- Linux/BSD distribution name and version: Centos 7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
When clicking on Filters in Roundcube settings:

"An error ocurred:
Unable to connect to server."

sieve.log:
Oct 12 14:53:55 servername dovecot: managesieve-login: Aborted login (auth failed, 1 attempts in 2 secs): user=<userf@domain.net>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<qzbimwx4Dod/AAAB>

I had updated dovecot to 2.3 following these instructions: https://docs.iredmail.org/upgrade.dovecot.2.2-2.3.html

I just did a yum update and dovecot is currently:
dovecot-pigeonhole-2.3.3-2.x86_64
dovecot-2.3.3-2.x86_64
dovecot-mysql-2.3.3-2.x86_64

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ketan.aagja

  • ketan.aagja
  • Member
  • Offline
  • From: UK
  • Registered: 2012-05-15
  • Posts: 252

Re: Managesieve error

Did you restart service after upgrade?

Can you verify following sections in dovecot.conf?

# Authentication mechanisms.
auth_mechanisms = PLAIN LOGIN

service auth {
    unix_listener /var/spool/postfix/private/dovecot-auth {
        user = postfix
        group = postfix
        mode = 0666
    }
    unix_listener auth-master {
        user = vmail
        group = vmail
        mode = 0666
    }
    unix_listener auth-userdb {
        user = vmail
        group = vmail
        mode = 0660
    }
}


protocol sieve {
  managesieve_implementation_string = Dovecot Pigeonhole
  managesieve_max_line_length = 65536
}


service managesieve-login {
    inet_listener sieve {
        # Listen on localhost (ipv4)
        address = 127.0.0.1
        port = 4190
    }

}

3 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,160

Re: Managesieve error

jstewart wrote:

I just did a yum update and dovecot is currently:
dovecot-pigeonhole-2.3.3-2.x86_64
dovecot-2.3.3-2.x86_64
dovecot-mysql-2.3.3-2.x86_64

Which repo did you use? As far as i know, iRedMail repo and EPEL don't offer dovecot-2.3.

Try to restart Dovecot service again, then check its log files immediately, there must be some relevant error or warning info, because you need to convert Dovecot 2.2 config file to 2.3 format.

4 Reply by jstewart

  • jstewart
  • Member
  • Offline
  • Registered: 2017-02-10
  • Posts: 102

Re: Managesieve error

Just thought I'd let you know I downgraded dovecot back to 2.2 from 2.3 and that solved my problem.

I had installed 2.3 from the dovecot repo for Centos7, and all seemed to work great, except for the sieve issue.

After rolling it back and restoring all of my original conf files everything is back to normal.

I guess I'll wait until there is an official update.

5 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,160

Re: Managesieve error

jstewart wrote:

I had installed 2.3 from the dovecot repo for Centos7, and all seemed to work great, except for the sieve issue.

Did you also upgrade package "dovecot-pigeonhole"?

6 Reply by jstewart

  • jstewart
  • Member
  • Offline
  • Registered: 2017-02-10
  • Posts: 102

Re: Managesieve error

This is what I downgraded from:
dovecot-pigeonhole-2.3.3-2.x86_64
dovecot-2.3.3-2.x86_64
dovecot-mysql-2.3.3-2.x86_64

This is current:
dovecot-mysql-2.2.32-2.el7.centos.x86_64
dovecot-pigeonhole-2.2.32-2.el7.centos.x86_64
dovecot-2.2.32-2.el7.centos.x86_64

As far as I could tell everything was configured correctly, so I don't know what was causing the issue. It's working now, so I figure if it ain't broke don't fix it. I'll wait for official upgrades.