Caused by: java.net.SocketTimeoutException: connect timed out
Looks like it cannot connect to SIEVE server at all.
- Is sieve service port (4190) open in iptables?
- Is sieve service only listening on 127.0.0.1?
root@vm-iredmail:/var/log# netstat -tupan| grep 4190
tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 10283/dovecot
root@vm-iredmail:/var/log# iptables --list
Chain INPUT (policy DROP)
target prot opt source destination
fail2ban-postfix tcp -- anywhere anywhere multiport dports www,https,smtp,ssmtp,pop3,pop3s,imap2,imaps,sieve
fail2ban-ssh tcp -- anywhere anywhere tcp dpt:ssh
fail2ban-dovecot tcp -- anywhere anywhere multiport dports www,https,smtp,ssmtp,pop3,pop3s,imap2,imaps,sieve
fail2ban-roundcube tcp -- anywhere anywhere multiport dports www,https,smtp,ssmtp,pop3,pop3s,imap2,imaps,sieve
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere multiport dports www,https,smtp,ssmtp,pop3,pop3s,imap2,imaps,submission,ssmtp,ssh,zabbix-agent,zabbix-trapper
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp echo-request
Chain FORWARD (policy DROP)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain fail2ban-dovecot (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Chain fail2ban-postfix (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Chain fail2ban-roundcube (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Chain fail2ban-ssh (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere