I'm traying to add a new server to my sogo installation and now the config in the new sogo server points to the database in the original server, thus i had to change "localhost" by the name/ip of the original sogo server.

But now, when I connect to the second server, although it connects to the database does not retrieve any data because the info about calendars and addressboks are hardcoded in the database with the old database configuration ("localhost").

How I can workaround this issue?

Why the config es hardcoded in the database? Have to do with performance?

This design is not flexible; changing some basic config parameters as a password for a database user implies to change the fields c_quick_location, c_acl_location and c_folder_type in the table sogo_folder_info.

Thanks

Federico
--
[email protected]
https://inverse.ca/sogo/lists

Reply via email to