During my investigation of how this image works and reading a lot of tutorials about Postfix + AMaViS + SpamAssassin + ClamAV integrations I was wondered why many tutorials have no words about spamd or service spamassassin start, but AMaViS requires SpamAssassin to be installed.
That's why I have googled more about how AMaViS uses SpamAssassin and finally found this archived mail which makes things clear.
According to that explanation amavisd represents some kind of spamd by itself and uses SpamAssasin via Perl API directly. So, actually, no spamd running is required if we use amavisd.
I've tested this stuff making amavisd running in separate container which does not run spamd process and it has worked OK as expected. The only thing required still to be run periodically is sa-update cron job.
So, the question is:
Do I miss some caveats which complicate things? Or, if not, can we improve image by disabling spamd as unnecessary process and leave only sa-update cron jobs?
During my investigation of how this image works and reading a lot of tutorials about Postfix + AMaViS + SpamAssassin + ClamAV integrations I was wondered why many tutorials have no words about
spamdorservice spamassassin start, but AMaViS requires SpamAssassin to be installed.That's why I have googled more about how AMaViS uses SpamAssassin and finally found this archived mail which makes things clear.
According to that explanation
amavisdrepresents some kind ofspamdby itself and uses SpamAssasin via Perl API directly. So, actually, nospamdrunning is required if we useamavisd.I've tested this stuff making
amavisdrunning in separate container which does not runspamdprocess and it has worked OK as expected. The only thing required still to be run periodically issa-updatecron job.So, the question is:
Do I miss some caveats which complicate things? Or, if not, can we improve image by disabling
spamdas unnecessary process and leave onlysa-updatecron jobs?