>>>> This would for example allow switching between several rulesets or >>>> bayes databases. >> >> I have thought about trying to do something similar to allow for 'domain >> based' baysian tables (as amavisd sets up and calls sa->new, set the ENV >> variables so that SA can look up the domain in the bayes-vars tables) > > Per-recipient bayes would require either amavisd to abandon its paradigm > of one SA call per message and switch to one SA call per recipient, > or would require a reorganization of SpamAssassin. > Neither of these will likely to happen soon or without much effort. > I guess its the same thing... Per recipient or per domain. (with 1200 domains and 25000 users on one cluster, I sure would NOT want per domain bayes..)
So, guess I don't even try since amavisd does a 'per message' call. MAYBE, but less than useless I guess would be to examine the number of recipients in the email and switch. Ok, thanks. I won't even try. Turn Bayes off for hosted servers. -- Michael Scheidell, CTO >|SECNAP Network Security Winner 2008 Network Products Guide Hot Companies FreeBSD SpamAssassin Ports maintainer _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ _________________________________________________________________________ ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
