Fwd: Re: [sam] SAM + LDAP Backend

[amith at xalan.com]

The way SpamAssassin works usually is to

1) figure out who the mail was sent to
2) figure out their home directory
3) look for the prefs file in the home directory
4) if prefs file not found then use the global one

The nice thing about the SQL based backend for SAM prefs is that its all stored
in the database and makes it nice for administration.  You could conceivably
write a driver to support the text files, but imho that would be way too
complicated and not worth it.  its easier to throw mysql on the machine and use
that then write a text based driver for SAM due to the way that SpamAssassin
sets up its config files.

As far as ingo goes, it is like a web based frontend for filters that you
define.  Right now it only support cyrus, but its being changed to perform
general filtering for IMP.  the difference is that Ingo/Sieve was not designed
to designate SPAM from non-SPAM.  Sure you can write a filter that does a good
job, but SpamAssassin is supposed to be much more sophisticated by using rules
and Bayesain filtering (the newer versions anyway)

Amith


----- Forwarded message from garycnew at yahoo.com -----
    Date: Sat, 19 Apr 2003 12:45:35 -0700 (PDT)
    From: "Gary C. New" <garycnew at yahoo.com>
Reply-To: "Gary C. New" <garycnew at yahoo.com>
 Subject: Re: [sam] SAM + LDAP Backend
      To: "amith at xalan.com" <amith at xalan.com>

That was the quickest, non-automated reply I've ever
received from a mailing list!  Thanks.

If it doesn't make sense to use ldap as the backend
for sam because spamassassin doesn't use it; doesn't
spamassassin provide for text file based storage of
rules?  Does sam provide this type of backend for text
file based storage?

What's the difference between sam and ingo?  Ingo
seems to be trying to accomplish some of the same
filtering functionality, but using sieve text based
files.

Thanks for you assistance.

Respectfully,


Gary


--- "amith at xalan.com" <amith at xalan.com> wrote:
> | Does sam currently support the use of ldap as a
> | backend?
>
> I don't think it makes sense to support ldap as a
> backend for SAM because as far
> as i know (and maybe this has changed) SpamAssassin
> only support a SQL backend.
>  All SAM does is allow users to change their
> whitelist/blacklist and other
> SpamAssassin config items.  SpamAssassin actually
> reads out of the database the
> preferences for each user when assigning a score to
> the e-mail.  While SAM is
> written to support multiple backends, i don't think
> SpamAssassin is.
>
> Amith
>
>
> --
> sam mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: sam-unsubscribe at lists.horde.org

__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com


----- End forwarded message -----