1 Topic by luxus

  • luxus
  • Member
  • Offline
  • Registered: 2011-03-04
  • Posts: 46

Topic: Unable to connect to managesieve server

I am unable to connect to the managesieve server for new users.
Users that have already configured there managesieve once are able to connect to their managesieve server from roundcube.

We are using Iredmail 0.7.4 with roundcube 0.7.2 on a Centos 5 x64 server.

When looking at the server I see that the pysieved service is not running, when I try to start it I get the following Error:

[root@mailserver config]# service pysieved start
Starting pysieved:Traceback (most recent call last):
  File "/usr/sbin/pysieved", line 173, in ?
    main()
  File "/usr/sbin/pysieved", line 165, in main
    s = Server((addr, port), handler)
  File "/usr/lib64/python2.4/SocketServer.py", line 330, in __init__
    self.server_bind()
  File "/usr/lib64/python2.4/SocketServer.py", line 341, in server_bind
    self.socket.bind(self.server_address)
  File "<string>", line 1, in bind
socket.error: (98, 'Address already in use')
                                                           [FAILED]

Attached you can find the sieve.log file

Post's attachments

sieve.rar 410.55 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

----

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

2 Reply by ZhangHuangbin

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

Re: Unable to connect to managesieve server

We don't use pysieved for a long time. Managesieve is provided by Dovecot, and it complains "Address already in use", that means managesieve (Dovecot) is running. Try to use 'netstat' to verify it:

# netstat -ntlp | grep '2000'
# netstat -ntlp | grep '4190'

3 Reply by luxus

  • luxus
  • Member
  • Offline
  • Registered: 2011-03-04
  • Posts: 46

Re: Unable to connect to managesieve server

ZhangHuangbin wrote:

We don't use pysieved for a long time. Managesieve is provided by Dovecot, and it complains "Address already in use", that means managesieve (Dovecot) is running. Try to use 'netstat' to verify it:

# netstat -ntlp | grep '2000'
# netstat -ntlp | grep '4190'

Netstat -ntlp | grep 4190 gives not result, port 2000 gives dovecot.

But I still get the message Unable to connect to managesieve server in Roundcube

4 Reply by ZhangHuangbin

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

Re: Unable to connect to managesieve server

Check roundcubemail/plugins/managesieve/config.inc.php, make sure you're using port 2000 instead of 4190.

P.S. port of managesieve service is changed to 4190 on RHEL/CentOS 6, Debian 6, Ubuntu 11.x+, ...

5 Reply by luxus

  • luxus
  • Member
  • Offline
  • Registered: 2011-03-04
  • Posts: 46

Re: Unable to connect to managesieve server

ZhangHuangbin wrote:

Check roundcubemail/plugins/managesieve/config.inc.php, make sure you're using port 2000 instead of 4190.

P.S. port of managesieve service is changed to 4190 on RHEL/CentOS 6, Debian 6, Ubuntu 11.x+, ...

The port is set to port 2000 but it is still not working.
The strange thing is that managesieve is working for the people that have used it before, it's only not working for people that haven't used it yet

6 Reply by ZhangHuangbin

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

Re: Unable to connect to managesieve server

No idea at all, sorry.

- Is this server upgraded from older iRedMail version?
- iRedMail installs Dovecot-1.2 on CentOS 5 by default, do you have Dovecot-1.x running or 2.x?
- Any differences of LDIF data (if you're running OpenLDAP backend) between working accounts and failed accounts?
- Does your mail user has below LDAP attribute/value:

enabledService: sieve
enabledService: sievesecured
enabledService: managesieve
enabledService: managesievesecured

1st and 2nd value are used in Dovecot-1.x, 3rd and 4th are used in Dovecot-2.x.

7 Reply by luxus

  • luxus
  • Member
  • Offline
  • Registered: 2011-03-04
  • Posts: 46

Re: Unable to connect to managesieve server

ZhangHuangbin wrote:

No idea at all, sorry.

- Is this server upgraded from older iRedMail version?
- iRedMail installs Dovecot-1.2 on CentOS 5 by default, do you have Dovecot-1.x running or 2.x?
- Any differences of LDIF data (if you're running OpenLDAP backend) between working accounts and failed accounts?
- Does your mail user has below LDAP attribute/value:

enabledService: sieve
enabledService: sievesecured
enabledService: managesieve
enabledService: managesievesecured

1st and 2nd value are used in Dovecot-1.x, 3rd and 4th are used in Dovecot-2.x.

I did have the managesieve and managesievesecured services enable, but I'm still using Dovecot-1.2 so that was the problem.