Hi!
Since around 14 days we experience issues with Vacation and Forward
functions. Hitting the green diskette button on the web interface's
Vacation configuration page, the user will be returned the error message
"Service temporarily unavailable".
In the sogo.log I get the following entries whenever I hit the green
save button:
###################################################################
Aug 17 10:07:39 sogod [2204]: [ERROR]
<0x0x55e3f4c92210[SOGoSieveManager]> Sieve connection failed on
sieve://myserver.mydomain.mytld:4190/?tls=YES
Aug 17 10:07:39 sogod [2204]: 192.168.120.198 "POST
/SOGo/so/mytest.user@mydomain.mytld/Preferences/save HTTP/1.0" 503
46/4770 0.140 - - -2788K - 18
####################################################################
On my web research I found this thread
https://www.mail-archive.com/users@sogo.nu/msg29875.html which helped me
to solve some error messages in the sogo.log like the following. The
solution was to replace the parameters
SOGoSieveServer = "sieve://127.0.0.1:4190/?tls=YES";
SOGoIMAPServer = = "imap://127.0.0.1:143/";
by
SOGoSieveServer = "sieve://myserver.mydomain.mytld:4190/?tls=YES";
SOGoIMAPServer = = "imap://myserver.mydomain.mytld:143/";
Background info: We use a wildcard certificate: *.mydomain.mytld
#####################################################################
2020-08-16 22:52:23.344 sogod[2480:2480] SSL(cert_verify_callback):
Certificate validation failed
2020-08-16 22:52:23.344 sogod[2480:2480] ERROR(-[NGActiveSSLSocket
startTLS]): couldn't setup SSL connection on host 127.0.0.1
(error:00000001:lib(0):func(0):reason(1))...
Aug 16 22:52:23 sogod [2480]: <0x0x558c6cf319f0[NGSieveClient]> Could
not start TLS.
#######################################################################
Unfortunately the Sieve functions Vacation and Forward still fail. I
assume that they fail since the last updates, where the following
packages were installed/updated (Note: SELinux is disabled on the server):
######################################################################
[root@myserver ~]# yum history info 115
Loaded plugins: fastestmirror
Transaction ID : 115
Begin time : Mon Aug 3 18:58:53 2020
Begin rpmdb : 788:9fcad6b4f57ce8505a220c927ae8cadc1f3069c3
End time : 19:01:17 2020 (144 seconds)
End rpmdb : 789:e054d904ca85bfcd08cabd80ce9d52a37d7d0f3a
User : root <root>
Return-Code : Success
Command Line : update -y
Transaction performed with:
Installed rpm-4.11.3-43.el7.x86_64 @base
Installed yum-3.4.3-167.el7.centos.noarch @base
Installed yum-plugin-fastestmirror-1.1.31-54.el7_8.noarch @updates
Packages Altered:
Updated ca-certificates-2019.2.32-76.el7_7.noarch
@updates
Update 2020.2.41-70.0.el7_8.noarch
@updates
Updated clamav-0.102.3-1.el7.x86_64 @epel
Update 0.102.4-1.el7.x86_64 @epel
Updated clamav-filesystem-0.102.3-1.el7.noarch @epel
Update 0.102.4-1.el7.noarch @epel
Updated clamav-lib-0.102.3-1.el7.x86_64 @epel
Update 0.102.4-1.el7.x86_64 @epel
Updated clamav-update-0.102.3-1.el7.x86_64 @epel
Update 0.102.4-1.el7.x86_64 @epel
Updated clamd-0.102.3-1.el7.x86_64 @epel
Update 0.102.4-1.el7.x86_64 @epel
Updated dbus-1:1.10.24-13.el7_6.x86_64
@updates
Update 1:1.10.24-14.el7_8.x86_64
@updates
Updated dbus-libs-1:1.10.24-13.el7_6.x86_64
@updates
Update 1:1.10.24-14.el7_8.x86_64
@updates
Updated fail2ban-0.10.5-2.el7.noarch @epel
Update 0.11.1-9.el7.2.noarch @epel
Updated fail2ban-firewalld-0.10.5-2.el7.noarch @epel
Update 0.11.1-9.el7.2.noarch @epel
Updated fail2ban-sendmail-0.10.5-2.el7.noarch @epel
Update 0.11.1-9.el7.2.noarch @epel
Updated fail2ban-server-0.10.5-2.el7.noarch @epel
Update 0.11.1-9.el7.2.noarch @epel
Updated grub2-1:2.02-0.81.el7.centos.x86_64 @base
Update 1:2.02-0.86.el7.centos.x86_64
@updates
Updated grub2-common-1:2.02-0.81.el7.centos.noarch @base
Update 1:2.02-0.86.el7.centos.noarch
@updates
Updated grub2-pc-1:2.02-0.81.el7.centos.x86_64 @base
Update 1:2.02-0.86.el7.centos.x86_64
@updates
Updated grub2-pc-modules-1:2.02-0.81.el7.centos.noarch @base
Update 1:2.02-0.86.el7.centos.noarch
@updates
Updated grub2-tools-1:2.02-0.81.el7.centos.x86_64 @base
Update 1:2.02-0.86.el7.centos.x86_64
@updates
Updated grub2-tools-extra-1:2.02-0.81.el7.centos.x86_64 @base
Update 1:2.02-0.86.el7.centos.x86_64
@updates
Updated grub2-tools-minimal-1:2.02-0.81.el7.centos.x86_64 @base
Update 1:2.02-0.86.el7.centos.x86_64
@updates
Updated kernel-headers-3.10.0-1127.10.1.el7.x86_64
@updates
Update 3.10.0-1127.18.2.el7.x86_64
@updates
Updated kernel-tools-3.10.0-1127.10.1.el7.x86_64
@updates
Update 3.10.0-1127.18.2.el7.x86_64
@updates
Updated kernel-tools-libs-3.10.0-1127.10.1.el7.x86_64
@updates
Update 3.10.0-1127.18.2.el7.x86_64
@updates
Dep-Install libsodium-1.0.18-1.el7.x86_64 @epel
Updated microcode_ctl-2:2.1-61.6.el7_8.x86_64
@updates
Update 2:2.1-61.10.el7_8.x86_64
@updates
Updated munin-common-2.0.54-1.el7.noarch @epel
Update 2.0.63-1.el7.noarch @epel
Updated munin-node-2.0.54-1.el7.noarch @epel
Update 2.0.63-1.el7.noarch @epel
Updated ntpdate-4.2.6p5-29.el7.centos.x86_64 @base
Update 4.2.6p5-29.el7.centos.2.x86_64
@updates
Updated python-perf-3.10.0-1127.10.1.el7.x86_64
@updates
Update 3.10.0-1127.18.2.el7.x86_64
@updates
Updated python2-acme-1.4.0-2.el7.noarch @epel
Update 1.6.0-1.el7.noarch @epel
Updated rsyslog-8.24.0-52.el7.x86_64 @base
Update 8.24.0-52.el7_8.2.x86_64
@updates
Updated selinux-policy-3.13.1-266.el7.noarch @base
Update 3.13.1-266.el7_8.1.noarch
@updates
Updated selinux-policy-targeted-3.13.1-266.el7.noarch @base
Update 3.13.1-266.el7_8.1.noarch
@updates
Updated sogo-4.3.2.20200612-1.el7.x86_64 @SOGo
Update 4.3.2.20200803-1.el7.x86_64 @SOGo
Updated sogo-activesync-4.3.2.20200612-1.el7.x86_64 @SOGo
Update 4.3.2.20200803-1.el7.x86_64 @SOGo
Updated sogo-ealarms-notify-4.3.2.20200612-1.el7.x86_64 @SOGo
Update 4.3.2.20200803-1.el7.x86_64 @SOGo
Updated sogo-tool-4.3.2.20200612-1.el7.x86_64 @SOGo
Update 4.3.2.20200803-1.el7.x86_64 @SOGo
Updated sope49-appserver-4.9-20200603_1664.el7.1.x86_64 @SOGo
Update 4.9-20200731_1664.el7.1.x86_64 @SOGo
Updated sope49-cards-4.3.2.20200612-1.el7.x86_64 @SOGo
Update 4.3.2.20200803-1.el7.x86_64 @SOGo
Updated sope49-core-4.9-20200603_1664.el7.1.x86_64 @SOGo
Update 4.9-20200731_1664.el7.1.x86_64 @SOGo
Updated sope49-gdl1-4.9-20200603_1664.el7.1.x86_64 @SOGo
Update 4.9-20200731_1664.el7.1.x86_64 @SOGo
Updated sope49-gdl1-contentstore-4.3.2.20200612-1.el7.x86_64 @SOGo
Update 4.3.2.20200803-1.el7.x86_64 @SOGo
Updated sope49-gdl1-mysql-4.9-20200603_1664.el7.1.x86_64 @SOGo
Update 4.9-20200731_1664.el7.1.x86_64 @SOGo
Updated sope49-ldap-4.9-20200603_1664.el7.1.x86_64 @SOGo
Update 4.9-20200731_1664.el7.1.x86_64 @SOGo
Updated sope49-mime-4.9-20200603_1664.el7.1.x86_64 @SOGo
Update 4.9-20200731_1664.el7.1.x86_64 @SOGo
Updated sope49-sbjson-2.3.1-20200603_1664.el7.1.x86_64 @SOGo
Update 2.3.1-20200731_1664.el7.1.x86_64 @SOGo
Updated sope49-xml-4.9-20200603_1664.el7.1.x86_64 @SOGo
Update 4.9-20200731_1664.el7.1.x86_64 @SOGo
Updated systemd-219-73.el7_8.6.x86_64
@updates
Update 219-73.el7_8.8.x86_64
@updates
Updated systemd-libs-219-73.el7_8.6.x86_64
@updates
Update 219-73.el7_8.8.x86_64
@updates
Updated systemd-python-219-73.el7_8.6.x86_64
@updates
Update 219-73.el7_8.8.x86_64
@updates
Updated systemd-sysv-219-73.el7_8.6.x86_64
@updates
Update 219-73.el7_8.8.x86_64
@updates
#################################################################
Anybody an idea, what to do in order to track down the Sieve issue? Arte
there further logs I could invetigate for instance?
Thanks a lot!
Best regards
Armin
__________ Information from mm-lab IT security __________The message was
checked by ESET Mail Security.
--
users@sogo.nu
https://inverse.ca/sogo/lists
