Bug#932081: sogo: Unable to connect to a remote IMAP server.

Koichi MATSUMOTO

unread,

Jul 14, 2019, 4:10:02 PM7/14/19

to

Package: sogo
Version: 4.0.7-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?

*** End of the template - remove these template lines ***

-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ja_JP.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sogo depends on:
ii adduser 3.118
ii gnustep-base-runtime 1.26.0-4
ii libc6 2.28-10
ii libcurl3-gnutls 7.64.0-4
ii libgcc1 1:8.3.0-6
ii libglib2.0-0 2.58.3-2
ii libgnustep-base1.26 1.26.0-4
ii libgnutls30 3.6.7-4
ii liblasso3 2.6.0-2+b2
ii libmemcached11 1.0.18-4.2
ii libobjc4 8.3.0-6
ii libsbjson2.3 2.3.2-4+b1
ii libsope1 4.0.7-1
ii lsb-base 10.2019051400
ii memcached 1.5.6-1.1
ii sogo-common 4.0.7-1
ii systemd 241-5
ii zip 3.0-11+b1

sogo recommends no packages.

Versions of packages sogo suggests:
pn postgresql | default-mysql-server | virtual-mysql-server <none>

-- Configuration Files:
/etc/sogo/sogo.conf changed:
{
SOGoProfileURL = "postgresql://sogo:pass...@192.168.207.11:5432/sogo/sogo_user_profile";
OCSFolderInfoURL = "postgresql://sogo:pass...@192.168.207.11:5432/sogo/sogo_folder_info";
OCSSessionsFolderURL = "postgresql://sogo:pass...@192.168.207.11:5432/sogo/sogo_sessions_folder";
OCSEMailAlarmsFolderURL = "postgresql://sogo:pass...@192.168.207.11:5432/sogo/sogo_alarms_folder";
SOGoLanguage = English;
SOGoAppointmentSendEMailNotifications = YES;
SOGoMailingMechanism = smtp;
SOGoSMTPServer = 127.0.0.1;
SOGoTimeZone = Asia/Tokyo;
SOGoSentFolderName = Sent;
SOGoTrashFolderName = Trash;
SOGoDraftsFolderName = Drafts;
SOGoIMAPServer = "imap://localhost:143/?tls=NO";
SOGoSieveServer = "sieve://localhost:4190/?tls=NO";
SOGoIMAPAclConformsToIMAPExt = YES;
SOGoVacationEnabled = NO;
SOGoForwardEnabled = NO;
SOGoSieveScriptsEnabled = NO;
SOGoFirstDayOfWeek = 0;
SOGoMailMessageCheck = manually;
SOGoMailAuxiliaryUserAccountsEnabled = YES;
SOGoMemcachedHost = 127.0.0.1;
SOGoUserSources =
(
{
type = sql;
id = directory;
viewURL = "postgresql://sogo:pass...@192.168.207.11:5432/sogo/sogo_users";
userPasswordAlgorithm = plain;
canAuthenticate = YES;
displayName = "Default Address Book";
}
);
}

-- no debconf information

Koichi MATSUMOTO

unread,

Jul 14, 2019, 5:10:02 PM7/14/19

to

*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?

Fresh install of Dovecot IMAP server with SSL.
Fresh install of Sogo on a different instance from Dovecot server.

* What exactly did you do (or not do) that was effective (or ineffective)?

I add account to SOGo on a remote IMAP server that I could retrieve mails from Desktop mail client.

* What was the outcome of this action?

Please see attached the log file.

* What outcome did you expect instead?

Connection to a remote IMAP server successfully.

*** End of the template - remove these template lines ***

—Log File

Log.txt

Gerald Turner

unread,

Jul 24, 2019, 11:50:02 AM7/24/19

to

Package: sogo
Version: 4.0.7-1
Followup-For: Bug #932081

I encountered the same problem.

I'm in the process of upgrading several servers from Debian stretch to
Debian buster.

SOGo is installed on a separate server which I upgraded first.
Initiallly all was well after the upgrade, although it took me a moment
to discover that /usr/share/doc/sogo/sql-update-3.2.10_to_4.0.0.sh
needed to be run in order for Address Book to work correctly.

Later I upgraded the server which runs dovecot-imapd. Now SOGo can't
display Mail, but Address Book and Calendar still work.

Logs look very similar to Koichi MATSUMOTO's report.

-- System Information:
Debian Release: 10.0
APT prefers stable

APT policy: (701, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-cloud-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sogo depends on:
ii adduser 3.118
ii gnustep-base-runtime 1.26.0-4
ii libc6 2.28-10
ii libcurl3-gnutls 7.64.0-4
ii libgcc1 1:8.3.0-6
ii libglib2.0-0 2.58.3-2
ii libgnustep-base1.26 1.26.0-4
ii libgnutls30 3.6.7-4
ii liblasso3 2.6.0-2+b2
ii libmemcached11 1.0.18-4.2
ii libobjc4 8.3.0-6
ii libsbjson2.3 2.3.2-4+b1
ii libsope1 4.0.7-1
ii lsb-base 10.2019051400
ii memcached 1.5.6-1.1
ii sogo-common 4.0.7-1
ii systemd 241-5

ii tmpreaper 1.6.14

ii zip 3.0-11+b1

sogo recommends no packages.

Versions of packages sogo suggests:

ii postgresql 11+200+deb10u1

-- Configuration Files:
/etc/cron.d/sogo [Errno 13] Permission denied: '/etc/cron.d/sogo'
/etc/default/sogo changed:
PREFORK=4

/etc/sogo/sogo.conf [Errno 13] Permission denied: '/etc/sogo/sogo.conf'

-- no debconf information

--
Gerald Turner <gtu...@unzane.com> Encrypted mail preferred!
OpenPGP: 4096R / CA89 B27A 30FA 66C5 1B80 3858 EC94 2276 FDB8 716D

signature.asc

sogo.log

dovecot.log

Gerald Turner

unread,

Jul 24, 2019, 11:50:03 AM7/24/19

to

FYI, there had been a short thread on the SOGo mailing list two months
ago, with no solution.

https://lists.inverse.ca/sogo/arc/users/2019-06/msg00005.html

Looks like the bug has been reported upstream, with no update:

https://sogo.nu/bugs/view.php?id=4783

signature.asc

Gerald Turner

unread,

Aug 8, 2019, 8:40:02 PM8/8/19

to

Control: found -1 4.0.8-1

FYI, bug still exists in 4.0.8-1 (bullseye version).

signature.asc

Nicolas Höft

unread,

Sep 1, 2019, 7:40:03 AM9/1/19

to

It is very well possible this is fixed already upstream by this commit:

https://github.com/inverse-inc/sogo/commit/
f7f0af67d82cf1e15daf69247a9b54df8eefd155

Can you try?

Nicolas

Adi Kriegisch

unread,

Jan 24, 2020, 8:00:03 AM1/24/20

to

Dear Nicolas,

> It is very well possible this is fixed already upstream by this commit:
>
> https://github.com/inverse-inc/sogo/commit/
> f7f0af67d82cf1e15daf69247a9b54df8eefd155
>
> Can you try?

This commit does not fix the issue for me; I even tried to compile
upstream SOGo and it fails exactly the same (4.2.0 - 4.3.0) when SOPE is
compiled/linked with gnutls support; when using OpenSSL everything works
just fine.[1]

best regards,
Adi Kriegisch

[1] https://sogo.nu/bugs/view.php?id=4783

signature.asc

Gerald Turner

unread,

Feb 5, 2020, 4:20:03 PM2/5/20

to

FWIW, I rebuilt 4.1.1 sogo and sope packages from bullseye modified
slightly to link against OpenSSL instead of GnuTLS, installed on a
production buster system, success!

Thank you Adi Kriegisch for pointing this out.

signature.asc

Nicolas Höft

unread,

May 13, 2020, 4:20:03 AM5/13/20

to

As discussed downstream in the sogo bug tracker, here another attempt to
fix this:

https://github.com/inverse-inc/sope/pull/51

This seems to fix the issue.

Nicolas

Paul van der Vlis

unread,

Feb 6, 2021, 6:30:03 PM2/6/21

to

So far I see Sogo does not work for e-mail in Buster, because it cannot
login to the IMAP server. Even without TLS and database/imap on localhost.

Good to see the problems are fixed in testing.