... In this context, at least in Debian 12 repo, the most recent package 'grommunio-index' does not contain any grommunio-index-run.sh anymore at all.
Now, grommunio-index is started directly with options -Aq by systemd. The package changelog states that the script functionality has been integrated into grommunio-index itself and the option -A has been introduced. This leads then in my case to the following side effect that grommunio-index can not communicate to exmdb interface anymore (which is localhost (::1:5000)) but tries to communicate via grommunio.domain.local as being set for -e in my case where indeed no exmdb port 5000 is available. Consequence is that the start procedure is ending with a 'FATAL: write failed: Permission denied'.
My current assumption is that this could be a side effect of setting the host name in /etc/host as described here
[https://community.grommunio.com/d/753-why-the-hostname-is-so-important-for-grommunio], in my case I followed Scenario 2
So, to make a long story short: how is then configuration working? (eg -e, -o options, formerly provided by grommunio-index-run.sh)? How can I for example influence the value for the -e option ($HOST) of grommunio-index?
Looking forward to any comments ...