I am testing with containerizing the spamd and I was wondering what would be a 
good solution to configure multiple spamd. What is the general advice on this 
here?



1. multiple instances

If I spawn multiple instances of the same container, I would get multiple ip 
addresses something like:

[@]# dig +short spamassassin.prod.local
192.168.200.246
192.168.200.147
192.168.200.149

It looks like this is still handled sort of ok by the spamass-milter. In case 
the ip is not available I am getting ' spamc[19094]: connect to spamd on 
192.168.200.x failed, retrying'


2. multiple different containers

What if I would create two different containers spamassassin.prod.local and 
spamassassin.dev.local

Is it possible to give multiple hostnames and ports to spamass-milter? 

Or is it better to have some sort of conditional expression in the MTA 
configuration that if one is not available process the other? Which requires a 
milter daemon running for each differently named container (I am currently 
using sendmail)



Reply via email to