You can use per user settings..
I have used one litle pm in my sa to fake the getpwnam and getpwuid.
you can download it from http://www.ebrain.com.br/~cassiano/AuthLdap.pm
just save this file to the Mail/SpamAssassin perl directory, open the
file and edit the ldap settings, open your spamd file and put
use Mail::SpamAssassin::AuthLdap;
right after the comments in the begin of the script
I have been using this to 200.000 accounts about 6 months without any
problem.
Ted Zlatanov wrote:
On 5 Jan 2005, [EMAIL PROTECTED] wrote:
you probably have an error in your logic. You usually only have one of
these:
- one SA run per recipient, thus obeying per-user settings, or
- one global SA run per message, thus ignoring per-user settings.
Right, and both have their advantages. I was hoping to combine them -
my logic is not wrong, only hopeful :)
Except in case you find it useful to run SA both in front of
qmail-send and behind, too, first implementing some global policies,
then, afterwards, adding per-user adjustments. If you want to
exclude some mailing lists from running SA on every recipient (where
it probably makes the least sense anyway), you will probably find
yourself running SA both in frond and behind qmail-send, and some
trickery in the invocation scripts to select the stage at which you
run for each message individually.
Unfortunately this seems to be the only way. I thought about it and
the advantages of per-user SA scanning don't justify the development
time right now, so we're just going to stick with global scanning and
enable SA through procmail for the users that need it.
Thank you for the help!
Ted
|
