Hello Quentin, Out of curiosity, where are these config parameters coming from? Looking at https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#_installation, I did not find many of these params.. Are they secret? :-)
SoObjectRequestHandlerDebugEnabled = YES; SoSelectorInvocationDebugEnabled = YES; SoDebugRequestClassification = YES; SoDebugObjectTraversal = YES; SOGoDebugRequests = YES; ImapDebugEnabled = YES; ImapLogEnabled = YES; MySQL4DebugEnabled = YES; SOGoUIxDebugEnabled = YES; SoObjectMethodDispatcherDebugEnabled = YES; SoPageInvocationDebugEnabled = YES; SoRendererDebugEnabled = YES; WOLogComponents = YES; WODebugComponentLookup = YES; WODebugResourceLookup = YES; SoProductResourceManagerDebugEnabled = YES; WOResourceURLAssociationDebugEnabled = YES; WEResourceManagerDebugEnabled = YES; NGLogDefaultLogLevel = "ALL"; On Mon, Jan 5, 2026 at 4:41 PM qhivert <[email protected]> wrote: > Well, no errors in your log, I've tested your sogo.conf and it works > well... > > Either there is something very obvious that I don't see, or you found a > very peculiar bug. > > Put that in your sogo.conf and reproduce the problem. > > SoObjectRequestHandlerDebugEnabled = YES; > SoSelectorInvocationDebugEnabled = YES; > SoDebugRequestClassification = YES; > SoDebugObjectTraversal = YES; > SOGoDebugRequests = YES; > ImapDebugEnabled = YES; > ImapLogEnabled = YES; > MySQL4DebugEnabled = YES; > SOGoUIxDebugEnabled = YES; > SoObjectMethodDispatcherDebugEnabled = YES; > SoPageInvocationDebugEnabled = YES; > SoRendererDebugEnabled = YES; > WOLogComponents = YES; > WODebugComponentLookup = YES; > WODebugResourceLookup = YES; > SoProductResourceManagerDebugEnabled = YES; > WOResourceURLAssociationDebugEnabled = YES; > WEResourceManagerDebugEnabled = YES; > NGLogDefaultLogLevel = "ALL"; > > Then send me the log directly (not here) in an attachment file please. > > Regards, > -- > Quentin Hivert || Alinto || R&D Lead Developer > 19 Quai Perrache 69002 Lyon > www.alinto.com > > -----Original Message----- > From: [email protected] <[email protected]> On Behalf Of "Oli Z." > Sent: lundi 5 janvier 2026 12:37 > To: [email protected] > Subject: Re: [SOGo] Debian 13 / SOGo / 500 error > > update: it added now that table (empty) after > setting SOGoEnableEMailAlarms to YES, but still the same error. > > Am 05.01.26 um 12:17 schrieb "Oli Z." ([email protected]): > > Thanks, that sounds reasonable, but the documentation says this is > > only required if SOGoEnableEMailAlarms is set. I did not set this > > flag. I added now: > > OCSEMailAlarmsFolderURL = > > "mysql://xx:xxx@localhost/sogo/sogo_alarms_folder"; - and: > > OCSAdminURL = "mysql://xx:xxx@localhost/sogo/sogo_admin"; > > > > Because i also found an error because of missing OCSAdminURL. > > Unfortunately, the error still exists. It added now the sogo_admin > > table but not the sogo_alarms_folder > > > > Am 05.01.26 um 10:35 schrieb qhivert ([email protected]): > >> Hello, > >> I think the table for alarm is missing in this case: > >> OCSEMailAlarmsFolderURL > >> > -- 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]
