On Thu, Apr 08, 2021 at 07:00:57PM +0200, Benny Pedersen wrote: > On 2021-04-08 18:54, Michael Grant wrote: > > > This may be a stupid question... but for a spamassassin module, for > > example spamassassin-esp, how would one normally "install" this so > > that it reads the .pre file? > > all content should be placed in same dir as local.cf > > and custom plugins should have there own <pluginname>.pre with the > loadplugin > > i think it works if Esp.cf is in same dir as local.cf > then there is no need to make include lines
This is what I want to avoid which was the goal of my original post. 1. Many modules are from git repos and need to live in their own directory to be updated from time to time, 2. the /etc/spamassassin/ directory can get very messy if you just dump things in there. Hard to know what's what, it becomes impossible to maintain. So I don't see any alternative to keeping such modules in separate directories like this. Is there really no way to tell spamassassin where to look for such modules, like some sort of search path? I'm surprised if not, and if not, would something like this be a reasonable feature to add in the future?
signature.asc
Description: PGP signature
