Grigory Morozov

Key generation: mkdir -p /etc/opendkim/keys/example.com opendkim-genkey -r -d example.com -D /etc/opendkim/keys/example.com chown opendkim:opendkim /etc/opendkim/keys/example.com/default.private public key will be in /etc/opendkim/keys/example.com/default.txt

Postfix: > milter_protocol = 2 > milter_default_action = accept > smtpd_milters = inet:localhost:12301 > non_smtpd_milters = inet:localhost:12301

Rspamd Key generation: > rspamadm dkim_keygen -b 2048 -d example.com -s default -k /var/lib/rspamd/dkim/example.com.default.key > /var/lib/rspamd/dkim/example.com.default.public dkim_signing.conf: > path = "/var/lib/rspamd/dkim/$domain.$selector.key"; and it will pick up the keys automatically

I hope @Logicbloke can help with that :)

Absolutely, so the only thing Froxlor needs to do is to create/update these two: /etc/opendkim/KeyTable /etc/opendkim/SigningTable generate the keys, and be able to restart opendkim

Yes there is: https://github.com/cyrusimap/opendkim/blob/master/opendkim/README.SQL But this will require additional systemd configuration for OpenDKIM to start it after MySQL

I am aware of that vulnerability, but it is NetBox that tries to use SSL. Filezilla uses TLS1.2 just fine. Configuration of that FTP server is: SSLv2 not offered (OK)...