Getting ClamAV and amavis back to service

The time has come to put amavisd and ClamAV into service but I want to keep spamassasin and policydweight in service and in place. So that my roundcube-users can define their filterrules the same way as before. Additonally the ISPConfig Spamfilter-Stuff shall run.

I've disabled the anti-spam stuff of ISPConfig according to this in the main.cf (but I did neither uninstall nor stop amavis or clamAV). So to put them back to service I removed the uncomment-tags and ended up with the following errors when an user tried to send E-Mails:

amavisd is a replacement for spamassassin, as it uses spamassassin internally. So running a separate spamassassin beside amavis makes no sense. Using policyd is not problem.

Regarding the error that you get, it seems as if you configured your postfix to require tls. But the internal connection to amavisd does not need tls and amavisd does not support tls for the internal mail exchange with postfix. So you should remove the tls reqzirement in your main.cf.

I totally agree that an TLS-Encryption on a loopback interface is a waste of processor time. But the consequence to shut down the entire TLS-Encryption for the server is a major hit on the security concept.

Instead I disabled the tls-encryption for the amavis loopback in the master.cf: