1

Topic: different version 2.0.18 lib90_sieve_plugin_so

==== Provide required information ====
- iRedMail version and backend (LDAP/MySQL/PGSQL):
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====
iRedMail-0.8.1 MySQL
CentOS 6
Linux galeweb.utahgale.com 2.6.32-220.23.1.el6.x86_64 #1 SMP Mon Jun 18 18:58:52 BST 2012 x86_64 x86_64 x86_64 GNU/Linux

Since installing iRedMail, I have been working through issues as they come up and much of the answers to my questions I got from here.  Now I see the following messages in /var/log/sieve.log

Jun 28 15:20:57 lda: Error: Module is for different version 2.0.18: /usr/lib64/dovecot/lib90_sieve_plugin.so
Jun 28 15:20:57 lda: Fatal: Couldn't load required plugins

I have looked for a different version of the plugin that would work for me but without success.

The version of sieve I have installed is dovecot-managesieve-0.3.0-22.el6.x86_64

What is the work-around for this problem?

Any help will be really appreciated.

----

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

2

Re: different version 2.0.18 lib90_sieve_plugin_so

You should have below package and version installed on CentOS 6:

- dovecot-2.0.18-1_134.el6.x86_64.rpm
- dovecot-managesieve-0.2.6-21.el6.x86_64.rpm
- dovecot-pigeonhole-0.2.6-21.el6.x86_64.rpm

They're available in iRedMail yum repository: http://www.iredmail.org/yum/rpms/6/

3

Re: different version 2.0.18 lib90_sieve_plugin_so

OK I removed all three and installed them from iredmail.
[root@galeweb ~]# rpm -q -a | grep dovecot
dovecot-pigeonhole-0.2.6-21.el6.x86_64
dovecot-managesieve-0.2.6-21.el6.x86_64
dovecot-2.0.18-1_134.el6.x86_64

Now when I try to start dovecot, I get the following error.

[root@galeweb ~]# service dovecot start
Starting Dovecot Imap: Error: service(pop3-login): listen(localhost, 110) failed: Address already in use
Error: service(imap-login): listen(localhost, 143) failed: Address already in use
Fatal: Failed to start listeners
                                                           [FAILED]

4

Re: different version 2.0.18 lib90_sieve_plugin_so

Please STOP service first, then try to start it.

# service dovecot stop
# service dovecot start

Also, do you have correct Dovecot config files (/etc/dovecot/*) after you re-installed RPM packages?

5

Re: different version 2.0.18 lib90_sieve_plugin_so

Thanks.  I recovered the config file from rpmsave and now I am receiving emails.  However I am getting an error in sieve.log that looks like this:

from mail_gid setting) failed with euid=99(nobody), gid=99(nobody), egid=99(nobody):

I can't seem to find the right place to change this to.

I think we are getting close.

6

Re: different version 2.0.18 lib90_sieve_plugin_so

I believe that I have resolved the sieve question.  It always helps when you install new aliases after you create them.  Now that I am receiving emails I am trying to retrieve them using the wordpress plugin wp-mail.php.  I know that this is not the forum for wordpress questions but I just wondered if the following error makes sense to anyone.  I have updated the "disable_plain_text_auth" field in dovecot.conf to "no" and restarted dovecot but the error persists.  Any help will be appreciated.

POP3 user: Error [-ERR Plaintext authentication disallowed on non-secure (SSL/TLS) connections.]

7

Re: different version 2.0.18 lib90_sieve_plugin_so

Update 'ssl =' in dovecot.conf like below:

ssl = yes

Default is "ssl = required" to enforce STARTTLS for secure connection.

8

Re: different version 2.0.18 lib90_sieve_plugin_so

Solved.  Thank you very much for all your help.  The server is delivering mail as expected and all is well with the world.  I appreciate your time.

9

Re: different version 2.0.18 lib90_sieve_plugin_so

If I hadn't seen so many postings from people saying that they got it to work and then it stopped working I would be really frustrated.  I was receiving emails just fine for a while and then it suddenly stopped.  I have checked all the services and they seem to be running.  I have checked all the logs and I don't find any errors.  The one thing that I don't see is any indication that emails are being received.  I did a port scan to see if all necessary ports are still open and the scan showed that 110, 142, 993, and 995 are all listening and responding.  I did restart the server this morning and afterwards checked for errors in the logs and do not see any.

Any ideas?  I'm not even sure where to start looking.  If I could see some errors, that would be a place to start.

10

Re: different version 2.0.18 lib90_sieve_plugin_so

- What do you mean "it suddenly stopped"?
- Did you check iptables rules which updated by Fail2ban? Try:

# iptables -L -n

11

Re: different version 2.0.18 lib90_sieve_plugin_so

Emails that are being sent are no longer being delivered to the server.  No errors are being reported on the sending side or in my logs.

I created another post since this issue does not seem to be related to different versions of plugins.  The new post is "After reboot, email is no longer received".  We can continue to use this thread if you like or switch to the new one.  I will post this to both.  Your choice which one we use.

iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
fail2ban-dovecot  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 80,443,25,587,110,995,143,993,4190
fail2ban-postfix  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 80,443,25,587,110,995,143,993,4190
fail2ban-ssh  tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:22
fail2ban-roundcube  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 80,443,25,587,110,995,143,993,4190
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:21
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:80
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:137
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:138
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:139
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:445
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:631
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:631
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:1194
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 25,110,143,443,587,993,995,2000,10000
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 25,110,143,443,587,993,995,2000,10000
ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         state NEW udp dpt:5353
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpts:5800:5802
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpts:5800:5802
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpts:5900:5902
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpts:5900:5902
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain fail2ban-dovecot (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-postfix (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-roundcube (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-ssh (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

12

Re: different version 2.0.18 lib90_sieve_plugin_so

I have started to get failure emails from yahoo from emails I tried to send yesterday indicating that it was unable to make an SMTP connection.  I have re-installed since then but even a failure gives some information.

Sorry, I wasn't able to establish an SMTP connection. (#4.4.1)
I'm not going to try again; this message has been in the queue too long.