Matt Kettler wrote:
Do I need to put in /etc/spamassassin/local.cf something like
' user_scores_dsn
ldap://host:port/dc=basedn,dc=de?attr?scope?uid=__USERNAME__' or what?
And I don't want at all to extend Windows AD schema (this is our
ldap :) with spamassassin attributes.
Is there a solution?
At 09:38 AM 2/16/2005, Andrew Afliatunov wrote:
But how spamd will know what ldap server to contact?
Well clearly this has *nothing* to do with the --setuid-with-ldap
parameter. --setuid-with-ldap can't tell SA what ldap server to use.
Note: you still probably want to pass -x and --ldap-config b
Matt Kettler wrote:
At 02:12 AM 2/15/2005, Andrew Afliatunov wrote:
I use spamassassin-3.01 in site-wide mode (spamd+spamc) on Linux
Slackware-9.1 mail server.
Everything worked just fine - about 300 spam-letters dayly was
filtered. But then I made system to look up mail-users in ldap
database.
At 02:12 AM 2/15/2005, Andrew Afliatunov wrote:
I use spamassassin-3.01 in site-wide mode (spamd+spamc) on Linux
Slackware-9.1 mail server.
Everything worked just fine - about 300 spam-letters dayly was filtered.
But then I made system to look up mail-users in ldap database. And removed
accounts
Sorry, mistake, must be
"3000 spam-letters dayly was filtered."
--
Andrew.
Hello!
I use spamassassin-3.01 in site-wide mode (spamd+spamc) on Linux
Slackware-9.1 mail server.
Everything worked just fine - about 300 spam-letters dayly was filtered.
But then I made system to look up mail-users in ldap database. And
removed accounts from linux system.
Now spamc can't check
