On Mon, Jan 5, 2026 at 10:39 AM "Oli Z." <[email protected]> wrote:
> i created the mariadb db and configured sogo to use that. i can see it > created the tables: > > MariaDB [sogo]> show tables; > +-------------------------------+ > | Tables_in_sogo | > +-------------------------------+ > | sogo_folder_info | > | sogo_sessions_folder | > | sogo_user_profile | > | sogomedom0016dd9f714 | > | sogomedom0016dd9f714_acl | > | sogomedom0016dd9f714_quick | > +-------------------------------+ > 6 rows in set (0,001 sec) > > but i still get the exact same behaviour. I am wondering if it could be > because of the passwords. I use special chars, so all my passwords are > more or less %xy. Could it be that the backend has problems with that? > It always fails with the same error: Jan 02 13:03:00 sogod [302429]: > 85.xxx "GET > /SOGo/so/[email protected]/Calendar/alarmslist?browserTime=1767355380 > HTTP/1.1" 500 36/0 0.049 - - 340K - 14 > > I can execute the sql that is shown in the log > > MariaDB [sogo]> SELECT c_path4 FROM sogo_folder_info WHERE c_path2 = > '[email protected]' AND c_folder_type = 'Appointment'; > +----------+ > | c_path4 | > +----------+ > | personal | > +----------+ > 1 row in set (0,001 sec) > > Is there any way to turn on debug logging in the backend itself? Because > everything else is just wild guessing. It clearly fails in the backend, > not in any way with the db. > PS: I am so used to bottom-posting, as opposed to top-posting (which is what you do) so I will post at the bottom. Top-posting is discouraged on mailing lists. It breaks the threading hierarchy. Having said that.. If you are able to authenticate against the IMAP4 (Dovecot) then the same encryption scheme you configured in dovecot should be the same one you specify in sogo.conf. For example, in my sogo.conf, I have this: userPasswordAlgorithm = sha512-crypt; In my dovecot configuration, I have: default_password_scheme = SHA512-CRYPT The backend should not have a problem with your password scheme as long as it's a supported one. When you ask: "Is there any way to turn on debug logging in the backend itself?", which backend are you referring to? SOGo has the following options for debugging, more or less (because I haven't touched my sogo.conf in a while): /* Debug */ //SOGoDebugRequests = YES; //SoDebugBaseURL = YES; //ImapDebugEnabled = YES; //LDAPDebugEnabled = YES; //PGDebugEnabled = YES; //MySQL4DebugEnabled = YES; //SOGoUIxDebugEnabled = YES; //WODontZipResponse = YES; //WOLogFile = /var/log/sogo/sogo.log; //GCSFolderDebugEnabled = NO; //GCSFolderStoreDebugEnabled = NO; //NGImap4DisableIMAP4Pooling = NO; //OCSFolderManagerSQLDebugEnabled = NO; //PGDebugEnabled = MO; //SOGoMailKeepDraftsAfterSend = NO; //SoDebugObjectTraversal = YES; //SoSecurityManagerDebugEnabled = NO; //WODebugZipResponse = NO; Here is my working sogo.conf: https://paste.ubuntu.com/p/ZVGFTCzsXs/ It's not the cleanest, but it works. Please customize the DBNAME and login credentials with yours and run a test with it. Possibly the encryption scheme as well. Let me know what you get. One thing I realized is that you do not have a table named sogo_admin, which, IIRC, became mandatory at some point. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
