Package: sogo
Version: 4.0.1-1
Severity: normal

Dear Maintainer,


   * What led up to the situation?
     I guess a recent update to the Sogo package?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I have found no workaround, yet! Tried update scripts for the database, enabled verbose
     logging but nothing which gave a hint to why Mail/view returns a 404.
   * What was the outcome of this action?
     The problem persist.

I'm using a mariadb backend with ldap authentication. Sogo config looks like this:
{
  WOPort = 20000;
  WOWorkersCount = 8;
SOGoProfileURL = "mysql://sogo:***@192.168.18.1:3306/sogo/sogo_user_profile"; OCSFolderInfoURL = "mysql://sogo:***@192.168.18.1:3306/sogo/sogo_folder_info"; OCSSessionsFolderURL = "mysql://sogo:***@192.168.18.1:3306/sogo/sogo_sessions_folder"; OCSEMailAlarmsFolderURL = "mysql://sogo:***@192.168.18.1:3306/sogo/sogo_alarms_folder";
  SOGoTimeZone = "Europe/Amsterdam";
  SOGoLanguage = English;
  SOGoAppointmentSendEMailNotifications = YES;
  SOGoMailingMechanism = smtp;
  SOGoSMTPServer = 192.168.18.1;
  SOGoMailDomain = "****";
  SOGoTimeZone = UTC;
  SOGoSentFolderName = Sent;
  SOGoTrashFolderName = Trash;
  SOGoDraftsFolderName = Drafts;
  SOGoIMAPServer = "imap://192.168.18.1:143/?tls=YES";
  SOGoSieveServer = "sieve://192.168.18.1:4190/?tls=YES";
  SOGoIMAPAclConformsToIMAPExt = YES;
  SOGoVacationEnabled = NO;
  SOGoForwardEnabled = NO;
  SOGoSieveScriptsEnabled = NO;
  SOGoFirstDayOfWeek = 0;
  SOGoMailMessageCheck = manually;
  SOGoMailAuxiliaryUserAccountsEnabled = NO;
  SOGoMemcachedHost = 127.0.0.1;
  SOGoMailCustomFromEnabled = YES;
  SOGoCalendarDefaultRoles = (
        PublicViewer,
        ConfidentialDAndTViewer
    );
  SOGoSuperUsernames = (****);
  SOGoUserSources = (
    {
        type = ldap;
        CNFieldName = cn;
        IDFieldName = uid;
        UIDFieldName = uid;
        IMAPHostFieldName = mailHost;
        baseDN = "ou=users,dc=***,dc=org";
        bindDN = "cn=admin,dc=***,dc=org";
        bindPassword = "****";
        canAuthenticate = YES;
        displayName = "LDAP Users";
        hostname = "ldap://192.168.18.1:389";;
        id = public;
        isAddressBook = NO;
    },
  );
}

The exact error from the webclient:

An error occurred during object publishing

the requested object could not be found!

sogo.log:
Aug 16 10:26:47 sogod [231]: 145.107.221.216 "GET /SOGo/so/<user>/Mail/view HTTP/1.1" 404 208/0 0.037 - - 0

Calendar and addressbook work fine.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 4.4.147-0a333a8e606ab056173befac424900d2-1 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sogo depends on:
ii  adduser               3.117
ii  gnustep-base-runtime  1.25.1-4
ii  libc6                 2.27-5
ii  libcurl3-gnutls       7.61.0-1
ii  libgcc1               1:8.2.0-3
ii  libglib2.0-0          2.56.1-2
ii  libgnustep-base1.25   1.25.1-4
ii  libgnutls30           3.5.19-1
ii  liblasso3             2.6.0-2+b1
ii  libmemcached11        1.0.18-4.2
ii  libobjc4              8.2.0-3
ii  libsbjson2.3          2.3.2-3+b1
ii  libsope1              4.0.1-1
ii  lsb-base              9.20170808
ii  memcached             1.5.6-1
ii  sogo-common           4.0.1-1
ii  systemd               239-7
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 [not included]

-- no debconf information

Reply via email to