View Issue Details

IDProjectCategoryView StatusLast Update
0005265SOGoWeb Mailpublic2021-02-22 04:38
ReporterRigacci.Org Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformServerOSDebianOS Version10.8 (Buster)
Product Version4.0.7 
Summary0005265: Cannot use TLS with SOGoSieveServer, "no authname supported" error and "Service temporarily unavailable"
Description

I have Sogo 4.0.7 on a Debian GNU/Linux 10.8, with server dovecot-managesieved 2.3.4.1 on the same host. Everything works fine if I have the following in /etc/sogo/sogo.conf:

SOGoSieveServer = "sieve://localhost:4190/?tls=NO";

But if I set tls=YES, I'm unable to save Sieve preferences in the webmail. If I save e.g. the vacation settings, I get the "Service temporarily unavailable" pop-up.
Dovecot is configured for SSL using a Let's Encrypt certificate and it is working nicely as IMAP serever for SOGo. From the log (see below) it seems that it is not a TLS protocol problem.
Please advise how can I increase the SOGo logging during Sieve login, may be it can help.

Steps To Reproduce

In sogo.conf: set "tls=YES" for SOGoSieveServer option, restart SOGO.
Login to the SOGo webmail.
Click Preferences => Mail => Vacation => Enable vacation auto reply (set your preferences) => Click save icon.
I get the "Service temporarily unavailable" pop-up.

In sogo.conf: set "tls=NO" for SOGoSieveServer option, restart SOGO.
Login to the SOGo webmail.
Click Preferences => Mail => Vacation => Enable vacation auto reply (set your preferences) => Click save icon.
I get the "Preferences saved" pop-up.

Additional Information

This is the SOGo log, it seems that TLS is initialized nicely:

<0x0x55e5ea808e20[SOGoCache]> Cache cleanup interval set every 300.000000 seconds
<0x0x55e5ea808e20[SOGoCache]> Using host(s) '127.0.0.1' as server(s)
<0x0x55e5ea9bc930[NGSieveClient]> TLS started successfully.
<0x0x55e5ea98a3c0[SOGoSieveManager]> failure. Attempting with a renewed password (no authname supported)
<0x0x55e5ea9bc930[NGSieveClient]> TLS started successfully.
<0x0x55e5ea98a3c0[SOGoSieveManager]> Could not login 'username@example.org' on Sieve server: <0x0x55e5ea9bc930[NGSieveClient]: socket=<NGActiveSSLSocket[0x0x55e5ea8b1010]:
mode=rw address=(null)>>: {RawResponse = "{}"; result = 0; }

Also for the managesieve daemon it seems that TLS is OK:

managesieve-login: Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data
managesieve-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished
managesieve-login: Debug: SSL: where=0x20, ret=1: SSLv3/TLS write session ticket
managesieve-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket
managesieve-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket
managesieve-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully
managesieve-login: Debug: SSL error: read(size=599) failed: Connection reset by peer

TagsSOGoSieveManager, TLS

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2021-02-22 04:38 Rigacci.Org New Issue
2021-02-22 04:38 Rigacci.Org Tag Attached: SOGoSieveManager
2021-02-22 04:38 Rigacci.Org Tag Attached: TLS