@jengelh Thank you for your insight.
I know gromox-cleaner is disabled by default. I am raising this here so I can get some feedback, as it's not the first time I ran gromox-cleaner, and never had trouble.
As I said: " I don't want to outrule some non-grommunio reason."
TBH, I even wrote a first draft of gromox-cleaner here before @crpb made a better version than mine 🙂
I executed the gromox-cleaner service after a gromox update and reboot. Perhaps I got an FS problem at the time.
I think the best I can do is restore my grommunio VM from the day before, and replay the same actions.
I'll report back in any case.
I play with it on my own private server of which I'm the only administrator. The gromox-cleaner service file seems vanilla
cat /usr/lib/systemd/system/gromox-cleaner.service
[Unit]
Description=Gromox mailbox cleaner
Requisite=gromox-http.service
After=gromox-http.service
[Service]
# Fallback if EnvironmentFile hasn't got any value
Environment=softdelete_purgetime=30d
EnvironmentFile=-/etc/gromox/gromox.cfg
ExecStart=/usr/sbin/gromox-mbop foreach.here.mb ( purge-softdelete -t ${softdelete_purgetime} -r / ) ( purge-datafiles )
MemoryDenyWriteExecute=yes
PrivateDevices=yes
PrivateNetwork=no
PrivateUsers=no
ProtectControlGroups=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
SystemCallFilter=@default @file-system @basic-io @system-service
Type=oneshot
Also, a rpm -V gromox
didn't return anything changed.
There is no override file for the unit file either.
It's the first time I ever experience email loss since I am hosting my own mails (I begun with zaraf... then kopa...).
I even said in another thread that I never experienced any loss with Grommunio a couple of weeks ago.
Anyway, I will report back once I got to replay the actions on my backed up server.