Re: [SOGo] Debian 13 / SOGo / 500 error

["Oli Z."]

Thats my view:
MariaDB [postfixadmin]> describe sogo_mailbox;
+------------+--------------+------+-----+---------+-------+
| Field      | Type         | Null | Key | Default | Extra |
+------------+--------------+------+-----+---------+-------+
| c_uid      | varchar(255) | NO   |     | NULL    |       |
| c_name     | varchar(255) | NO   |     | NULL    |       |
| c_cn       | varchar(255) | NO   |     | NULL    |       |
| mail       | varchar(255) | NO   |     | NULL    |       |
| c_password | varchar(255) | NO   |     | NULL    |       |
+------------+--------------+------+-----+---------+-------+
5 rows in set (0,004 sec)

when i do a select on it i get:





Am 23.12.25 um 15:19 schrieb Oli Z.:

| x...@mydomain.de         | x...@mydomain.de         | Test Account   | x...@mydomain.de         | {SHA512-CRYPT}$6$m6wJGw/xxx0 From the documentation, i see no domain field for viewUrl. So i assume thats not mandatory?

I created the view as described in the documentation, thats what is in use:

viewURL = "mysql://xxx:xxx@127.0.0.1:3306/postfixadmin/sogo_mailbox";


OCSAdminURL = "postgresql://xxx@127.0.0.1:5433/sogo/sogo_admin";



I can paste the full config if required.

Am 23.12.25 um 12:32 schrieb Washington Odhiambo (odhia...@gmail.com):

But Sogo still requires a DB, to store data, e.g. calendar information. And i prefer postgre, thats why i have: SOGoProfileURL = "postgresql://xxx@127.0.0.1:5433/sogo/sogo_user_profile"; OCSFolderInfoURL = "postgresql://xxx@127.0.0.1:5433/sogo/sogo_folder_info"; OCSSessionsFolderURL = "postgresql://xxx@127.0.0.1:5433/sogo/sogo_sessions_folder"; OCSEMailAlarmsFolderURL = "postgresql://xxx@127.0.0.1:5433/sogo/sogo_alarms_folder"; As mentioned, the sql auth works like a charm, but SOGo somehow fails _after_ authentication. From the log, i assume it should load some sort of calendar information or so.

On Tue, Dec 23, 2025 at 2:02 PM "Oli Z." <users@sogo.nu> wrote:

    I am not exactly sure what you mean. My users are in mariadb, the
    database is called "postfixadmin" because i set this email server up
    about 15 years ago and did not know that its a bad idea to call
    the db
    like the product thats in use :D




    I have about 7 users (friends). Next time i would call it
    "mailbox_users" or so. Anyway... i followed this guide
https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#Authentication-using-SQL


    splash with my name, and then the white page appears. So
    authentication
    against SQL works. But i did not run any other SQL to populate the
    SOGo DB.


You actually do NOT need the SOGo DB!

Who said that it's a bad idea to call the db like the product that's in use??     and the authentication works. When i log in to SOGo, it shows a green If you had an existing database with your users, it should have been easier to create a view of your existing tables for use with SOGo. For example, with Mariadb, for postfixadmin, I used: https://narkive.com/gJeHppYI.4

    I was not aware that anything like this is required. Thats why
    i migrated this mysql sql script to postgresql so that i have at
    least the
    sogo_user_profile table. I have the feeling there is a lot missing
    in the documentation... or i am blind. Or both 😉

    Maybe something in the log shows something that i dont see, which
    might be a problem or relevant.








--
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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

Once you create the VIEW, you just configure SOGo with the DB details, using the VIEW as the table. [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

smime.p7s
Description: Kryptografische S/MIME-Signatur