General discussion on installation and configuration of SOGo

Text archives Help

[SOGo] Error in ManageSieve configuration

Chronological Thread 
  • From: "Steffen" ( ) < >
  • To:
  • Subject: [SOGo] Error in ManageSieve configuration
  • Date: Sun, 16 Jul 2017 12:34:30 +0200
  • Dmarc-filter: OpenDMARC Filter v1.2.0 BA89DF0661A

I'm trying to connect the Nightly Build of SOGo to my external Dovecot
IMAP-Server with ManageSieve.

Unfortunately, I cannot correctly set the config option. When setting

SOGoSieveServer = "sieve://<snip>:4190?tls=YES";

The settings-page never loads (clicking the cogwheel after logging in)
and I get error messages after the workers hang for about 1 minute,
before finally giving up with the error

Jul 16 12:22:39 sogod [434]: [WARN]
<0x0x563419591ad0[WOWatchDogChild]> pid 437 has been hanging in the same
request for 1 minutes
Jul 16 12:23:39 sogod [434]: [WARN]
<0x0x563419591ad0[WOWatchDogChild]> pid 437 has been hanging in the same
request for 2 minutes
Jul 16 12:23:46 sogod [437]: [ERROR]
<0x0x563419bed5f0[SOGoSieveManager]> Sieve connection failed on

Clearly, the added sieve:// in front and :2000 in the end are not from
my config setting and are added "automagically".

When I instead remove the "sieve://" in my string, like

SOGoSieveServer = "<snip>?tls=YES";

I get a different error (but no worker hangs and the settings page loads

Jul 16 12:26:41 sogod [602]: [ERROR]
<0x0x55862eb7c650[SOGoSieveManager]> Sieve connection failed on (null)

Any hints how I could resolve this issue? The ManageSieve-Server works
correctly, and as an added note, when I remove the ?tls=yes from the
first configuration setting, the connection to the sieve-server works,
but fails since plaintext auth over unencrypted connections is not allowed.


Archive powered by MHonArc 2.6.18.

Top of page