[Rspamd-Users] Simple rule trouble.

[Michelle Sullivan]

Appreciate the thought but...

> On 11 Sep 2025, at 02:18, Florian Piekert <floppy at floppy.org> wrote:
> 
> Hello,
> 
> ...
> 
>> Fantastic, perfect for the example (which would solve a chunk of rules I have/want) as they are static.
>> However, still runs into the issue of I have to deploy them which is change control, peer-review, approval, scheduling then finally 4 hours of someone deploying them which is impractical for something that needs a dynamic response.
> 
> change control, use git.

Yup (bitbucket here)

> peer-review solve it as you need, same with approval.

Have multiple people and ITIL as the change framework.


> deploy? use parallel rsync/scp to all targets.

Yeah nah, this is where we diverge.. ansible here


> 
>> Thank you, I will use this for a chunk of stuff for sure.
> 
> Setting up the rules is the task at hand, once you configured it (not the map-files) appropriately, you only need to update the dynamic files and have a cron task fire up a Makefile make script to rspamd reload.

Yeah not that simple I’m afraid .. in SORBS I used to have puppet check the version control for an update and if it saw and update it deployed to test, test build, deploy to prod, restart on each server… here it’s very much different, ansible, build to stage, complete change notifications, approval, push to prod, service-ami’s change control etc..


> 
> Good luck with the rules.
> 

Thanks.

Michelle