* Mark Martinec <[EMAIL PROTECTED]> [2007-12-02 02:32:46 +0100]: > > Based on the FAQ and actual SA headers, I understand that local.cf is > > interpreted by SA running through amavisd (even though some scores/rules > > may be ignored). But I could not find any information on the > > handling/loading of modules. What is the right way to disable an SA module > > with an amavisd setup? Should I be editing the bin? > > The plugin usage is disabled, despite being loaded. > > Either deinstall these modules and they will not get loaded, > or edit the above list of modules to be pre-loaded, or just > not worry about a small wastage of memory which never gets used.
Agreed; memory was not my concern. > > The problem is that there is no way for amavisd to know > ahead of time which modules SpamAssassin will need, and some > of these modules are not preloaded by SpamAssassin initialization, > so they get loaded later with every child process creation, > or when chrooted, such functionality just fails. > > The built-in list of modules to be preloaded consists of modules > which SpamAssassin will likely need but fail to preload. Currently > it is just a best guess, in absence of a better way. Thanks for the explanation. -- Sahil Tandon <[EMAIL PROTECTED]> ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
