New Appliance v2026.06.2 - Online Build 1.3 - Anti-Spam won't start

Mister2

I have just started a test install of the new appliance and found that the anti-spam service will not start.

A bit of digging has found the permissions on file '/etc/grommunio-antispam/local.d/worker-controller.inc' are incorrect. On installation permissions are set as 640 - should be 644.

ls -l /etc/grommunio-antispam/local.d/worker-controller.inc gives

-rw-r----- 1 root root 103 Sep 30 21:02 /etc/grommunio-antispam/local.d/worker-controller.inc

rather than

-rw-r--r-- 1 root root 103 Sep 30 21:02 /etc/grommunio-antispam/local.d/worker-controller.inc

correcting this permission allows the antispam service to start.

Hope this helps others testing the new appliance build.

mwilliams

Thanks for reporting, indeed the setup hardening went on in too agressive here. The right approach though would be:

chown :grommunio /etc/grommunio-antispam/local.d/worker-controller.inc

The fix is being pushed as we speak - re-running grommunio-setup resolves it for already run installations.

Confirmation(s) from 13:00 CEST are very welcome.

Mister2

mwilliams Thanks for explaing what caused the issue. However, if the right approach is:-

chown :grommunio /etc/grommunio-antispam/local.d/worker-controller.inc

then why is this not included in the post install processes within Grommunio-Setup.

As a non developer - I am lost as to what permissions should be where. Last night I looked on my live 2026.06.1 Appliance and found all the files in the /etc/grommunio-antispam/local.d/ directory are set as 644 for root:root. Replicating these security settings to my test 2026.06.2 instance fixed the issue, which I reported. If the permissions should be different then the setup program really should set them correctly during installation of Grommunio.

EDIT: Just rerun another test setup.

Firstly the new Boot Screen is a big improvement - looks much better now.

I can confirm the settings suggested above are applied by the new Grommunio-Setup, BUT the new grommunio-setup needs to have been aplied to the server before running the setup wizard. So during initial install run the update before running the setup wizard.