Clean up the outdated configuration files.

WalterH

Some configuration files are no longer used for historical reasons. Currently, we have three such files: /etc/gromox/autodiscover.ini, /etc/gromox/autodiscover.cfg and /etc/gromox/adaptor.cfg.
Read the second post to learn how to clean up these files.

WalterH

To clean up these three files:

1. /etc/gromox/autodiscover.cfg requires special handling:

The x500_org_name variable must be migrated to gromox.cfg, run the following command:
cat /etc/gromox/autodiscover.cfg | grep x500_org_name >> /etc/gromox/gromox.cfg
to copy the content of autodiscover.cfg to gromox.cfg. Note: Using only one ">" (greater than sign) will overwrite the gromox.cfg file and destroy its contents, so be sure to use two ">>" (greater than) signs.

2. Then delete the autodiscover.cfg file:

rm /etc/gromox/autodiscover.cfg

3. The other two files can be deleted if they exist:

rm /etc/gromox/autodiscover.ini
rm /etc/gromox/adaptor.cfg

4. Restart gromox-http to read the x500_org_name variable from /etc/gromox/gromox.cfg:

systemctl restart gromox-http

Please note that these three files may or may not exist. This depends on the age of your installation.

Enjoy Grommunio!

abox

Good to know.
Do you know where the configuration in autodiscover.ini would go?
Is this ignored anyway?

In zcore and exchange_emsmdb configurations the default value of the submit_command setting is /usr/bin/php /usr/share/gromox/submit.php. submit.php has a dependency (conf.php) that could read this file and its options.
The part of the code looks like this:

$a["database"] ??= [];
$a["database"]["host"] ??= $b["mysql_host"];
$a["database"]["username"] ??= $b["mysql_username"];
$a["database"]["password"] ??= $b["mysql_password"];
$a["database"]["dbname"] ??= $b["mysql_dbname"];

$a["exchange"] ??= [];
$a["exchange"]["organization"] ??= "Gromox default";
$a["exchange"]["hostname"] ??= gethostname();
$a["exchange"]["mapihttp"] ??= 0;

$a["default"] ??= [];
$a["default"]["timezone"] ??= "Europe/Vienna";

$a["http-proxy"] ??= [];
$a["http-proxy"]["/var/lib/gromox/user/"] ??= $a["exchange"]["hostname"];
$a["http-proxy"]["/var/lib/gromox/domain/"] ??= $a["exchange"]["hostname"];

Maybe this is dead code, but at the moment I am unsure to delete this file, as the (I assume) defaults differ from what is set in autodiscover.ini.

Duese6

Hi abox
I don't have either of these files (autodiscover.ini or adaptor.cfg) on any of my systems.

Regards.

WalterH

Duese6 This is OK.

Duese6

Okay. I got one.
It's one of our Debian 13 Testssystem. Installed three month ago.

The strange thing is here. There is no gromox.cfg file. And only autodiscover.ini (and some other) with this content.
At first glance, I wouldn't just delete that. 😉

[database]
host = localhost
username = 'grommunio'
password = 'xyzabc'
dbname = 'grommunio'

[exchange]
organization = 'iabcabc'
hostname = grom.test.com
mapihttp = 1

[default]
timezone = 'Europe/Berlin'

[system]

[http-proxy]
/var/lib/gromox/user = grom.test.com
/var/lib/gromox/domain = grom.test.com

WalterH

You should migrate only one line from autodiscover.cfg to gromox.cfg:
cat /etc/gromox/autodiscover.cfg | grep x500_org_name >> /etc/gromox/gromox.cfg
The autodiscover.ini and autodiscover.cfg files will then no longer be used, see above.

Duese6

Hi, @WalterH
Okay, then I won't touch the Debian configurations.
The others (official, appliance-based Leap 15.6) were migrated as described above. Thx.

WalterH

Duese6 This applies to all distributions. Therefore, make the same changes in Debian as well.

Duese6

Okay, understood. But there is no autodiscover.cfg and no gromox.cfg.
The screenshot above shows the /etc/gromox folder, right after installation.
So are you sure, I should delete autodiscover.ini ?

It contains an entry like that.

[exchange]
organization = 'i69611333'

for me it looks like the mentioned x500_org_name.

So for sure I can create a gromox.cfg file with the entry
x500_org_name = i69611333

But what happens to the remaining entries in the ini file?

WalterH

Yes, and as you stated, migrate the line: x500_org_name = i69611333 to gromox.cfg.

Duese6 But what happens to the remaining entries in the ini file?

The are not used any longer.

Duese6

Hi @WalterH

with the latest gromox 3.7.240 update I started seeing additional deprecated configuration warnings.

Before just blindly migrating everything from http.cfg into gromox.cfg, I wanted to double-check what the recommended approach currently is.

From what I understand, the system still supports a mixed configuration state, and the warnings are more of a heads-up for future changes rather than something that must be fixed immediately.

Can someone confirm what exactly should be migrated at this point (especially for http.cfg), and whether it's safe to leave things as-is for now?

Regards

WalterH

Duese6 whether it's safe to leave things as-is for now?

It will remain safe until the developers finally switch to the variables in http.cfg.

Duese6

I actually came across these two deprecation warnings by accident while investigating an unrelated issue:

/etc/gromox/http.cfg:http_listen_port is deprecated in favor of /etc/gromox/gromox.cfg:http_listen
/etc/gromox/http.cfg:http_listen_tls_port is deprecated in favor of /etc/gromox/gromox.cfg:http_listen_tls

I moved the settings to gromox.cfg:

http_listen=[::]:10080
http_listen_tls=[::]:10443

and removed the old entries from http.cfg:

listen_port=10080
listen_ssl_port=10443

After restarting the gromox-http service, the deprecation warnings disappeared and everything appears to be working normally so far.

Just sharing this in case anyone else comes across the same warnings (http_log_level=6 was set).