Systemd as tragedy

Someone else explained the problem with regards to spamd/clamav.

I uses cfengine, which has its own rather dependable solution to authorizing/authentication access to the
policy distribution process (or the policy activation on a client.)
Writing a systemd aware version of cf-serverd (which distributes policy and also
is used to activate the installed policy) would require a fork of the software ie cfengine due to:

the rule languages itself has constructs to authorize policy users ie hosts with only particular
IP addresses will get an open socket at all, other hosts will not get anything ie connects at all

cf-serverd uses a private-public private key pair to authenticate the connection including authenticating itself !

The authentication is done in C(C++) code, and has had basically no security holes the last 10 years.