1 (edited by rprata 2019-04-09 02:11:58)

Topic: managesieve issues

iRedMail Version: 0.9.9
Deployed with downloaded installer script
Ubuntu 18.04 running on AWS / EC2
MySQL Server
NGinx
iRedMail (NOT Pro)


Installed a little over a week ago.  IMAP / SMTP working fine.  After install everything working fine.  RoundCube working fine.  Yesterday I logged into RoundCube with one of my accounts, and tried to change a filter setting.  When I click Settings --> Filters, I get "Unable to connect to server" dialog in RoundCube, and in /var/log/maillog:


Apr  8 18:02:33 mail roundcube: ERROR: Connection refused (111)
Apr  8 18:02:33 mail roundcube: <0japcrtt> PHP Error: Unable to connect to managesieve on 127.0.0.1:4190 in /opt/www/roundcubemail-1.3.8/plugins/managesieve/lib/Roundcube/rcube_sieve_engine.php on line 222 (GET /mail/?_task=settings&_action=plugin.managesieve-vacation)
Apr  8 18:02:33 mail ool inet: ERROR: Not currently connected (1)

I am not very familiar with managesieve, so I'm not really sure where to go with this.  I will make the filter changes via the MySQL database for now, but it would be nice to figure out what went wrong here.  Thanks in advance.

Post's attachments

2019-04-08 14_02_37-.png
2019-04-08 14_02_37-.png 4.95 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

Re: managesieve issues

- Is Dovecot listening on port 4190 (for managesieve service)?
- Please check log files under /var/log/dovecot/, especially managesieve.log. it should contain some error when this error arise.

3

Re: managesieve issues

ZhangHuangbin wrote:

- Is Dovecot listening on port 4190 (for managesieve service)?
- Please check log files under /var/log/dovecot/, especially managesieve.log. it should contain some error when this error arise.

Hello,

sieve.log contains nothing at all since April 1st, and there are 4 lines with informational log on / log off.  No errors, and nothing logged since then.

dovecot.log contains:
Apr  8 17:36:10 mail dovecot: master: Dovecot v2.2.33.2 (d6601f4ec) starting up for imap (core dumps disabled)
Apr  8 17:36:10 mail dovecot: doveconf: Warning: SSLv2 not supported by OpenSSL. Please consider removing it from ssl_protocols.

I have not made any changes to any Dovecot configuration files at all since I brought the system live.  I can disable SSL2 in Dovecot if you think that will make a difference.

netstat -pnltu |grep 4190 shows nothing listening on the port.  I have Dovecot listening on:


tcp        0      0 0.0.0.0:143             0.0.0.0:*               LISTEN      942/dovecot
tcp        0      0 127.0.0.1:24242         0.0.0.0:*               LISTEN      942/dovecot
tcp        0      0 0.0.0.0:993             0.0.0.0:*               LISTEN      942/dovecot

143 is the port my clients connect to for IMAP.

4

Re: managesieve issues

Do you have plugin name "sieve" listed in "protocols =" in /etc/dovecot/dovecot.conf?

5

Re: managesieve issues

rprata wrote:

Apr  8 17:36:10 mail dovecot: doveconf: Warning: SSLv2 not supported by OpenSSL. Please consider removing it from ssl_protocols.

Please remove "!SSLv2" from parameter "ssl_protocols =" in /etc/dovecot/dovecot.conf.

6

Re: managesieve issues

ZhangHuangbin wrote:
rprata wrote:

Apr  8 17:36:10 mail dovecot: doveconf: Warning: SSLv2 not supported by OpenSSL. Please consider removing it from ssl_protocols.

Please remove "!SSLv2" from parameter "ssl_protocols =" in /etc/dovecot/dovecot.conf.

How ingenius.  I have been struggling with this same problem.   I don't see this documented anywhere.   This indeed solved the problem with the following error message.

    (doveconf: Warning: SSLv2 not supported by OpenSSL. Please consider
    removing it from ssl_protocols.)

Although the error message itself is faulty.   Every online citation suggests using this line of code

ssl_protocols = !SSLv2 !SSLv3

Can you explain why that line of code generates the warning message?

7

Re: managesieve issues

Because the OpenSSL running on your server doesn't support SSLv2 at all.