[EMAIL PROTECTED] wrote, on 08. feb 2007 18:23:
I'm trying to use DSPAM with a system than now uses SpamAssassin. I need antispam solution can test LDAP to get some user attributes (really only "homeDirectory" is needed). For this, I've modified "spamd" source code of SpamAssassin (Perl), and now it searches in LDAP the home directory of each user, to save there its files (user_pref, bayes...).
Sounds good.
Would I need to do the same thing in DSPAM? Because I think DSPAM only "verify" users in LDAP, but does not obtain any users attributes from LDAP.
Indeed, you're right. We're a 100% LDAP house and when the dspam LDAP code was first introduced I flew to it to see what it could do for us (or we for it :) The immediate conclusion was, that it was redundant on our systems, since all it did was verify the mail recipient, whilst our MTA (Postfix) had already done that (also using LDAP) prior to accepting the message initially. So we dropped the dspam LDAP stuff.
I can imagine a use for it on a system that does absolutely no prior recipient validation - but such a system would have no place in any of our design hierarchies.
--Tonni -- Tony Earnshaw Email: tonni at hetnet dot nl
