> W dniu 2019-05-01 o 10:05, A. Schulze pisze: >> Hello, >> >> we've a number of SA instances that need rule updates. For now we configured >> them to use a proxy. Works... >> But there are also instances that can't us a proxy at all. >> >> My idea was to setup a private SA-Mirror (apache+rsync) but, I've to manage >> DNS-Data for mirrors.spamassassin-mirror.example and >> 2.3.4.spamassassin-mirror.example. >> :-/ >> >> Are there other methods to distribute current ruleset to SA-instances using >> sa-update?
There are many ways to accomplish this. The best one will depend on your network layout and what tools you have available. I suspect you already manage your SA local/custom rules/plugins/add-ons/etc from a central location and sync them out from there. This would work very similar to that. Pick one central server that will be your sa-update "master" then rsync the /var/lib/spamassassin/<version>/updates_spamassassin_org from it using native rsyncd or rsync over SSH with empty passphrase keys. If you are using spamd, amavis-new, etc. then setup monit to detect a checksum/timestamp change on the updates_spamassassin_org directory then reload/restart the daemon that is the "glue" to SpamAssassin. https://mmonit.com/monit/ -- David Jones
