Follow up: KAM.cf is update daily, as is the sa-update command being run: https://github.com/apache/infrastructure-puppet/blob/deployment/modules/spamassassin/manifests/spamd.pp#L191-L202
Also, rbldnsd is setup already to send data to the mx hosts: https://github.com/apache/infrastructure-puppet/blob/deployment/modules/rbldnsd/manifests/init.pp >From this, you should be able to see which services are pulled from. That being said, it might be worthwhile for us to check out the spamc/d cluster to make sure the rbl checks being performaed aren't being blocked for some reason. If you have more suggestions on what to edit (or want to see any more compiled/rendered config files, happy to get that information). On Wed, Aug 9, 2017 at 7:07 PM, Geoffrey Corey <cor...@apache.org> wrote: > yeah, a jira for tracking this would be good. > > Iirc the KAM.cf is updated using from, however I'm unsure of the frequency > (the puppet manifest linked should be able to show this) > > On Wed, Aug 9, 2017 at 9:21 AM Kevin A. McGrail <kevin.mcgr...@mcgrail.com> > wrote: > >> On 8/9/2017 11:34 AM, Geoffrey Corey wrote: >> > It's been a while since I looked, but our spamassassin setup is using >> > your KAM.cf file: >> > https://github.com/apache/infrastructure-puppet/blob/ >> deployment/modules/spamassassin/manifests/spamd.pp#L16 >> > >> > >> > As for the RBLs, I know we use some of it, and I indeed worked to fix >> > dns on the spamassassin cluster to not be blocked from the RBLs. >> > >> > Unsure what the status now is of the spamassassin cluster though. >> >> Well getting the RBLs local will save a lot of query time if I had to >> guess. >> >> And the KAM.cf should be updated a few times a week. >> >> Anyway, happy to help. I can open a ticket if you like, perhaps? >> >>
