> Now as a side question: I can't seem to find any reference in SpamAssassin 1.5
> to actually *use* the SQL implementation of user preferences. I see the
> user_scores_* variables in the spamassassin.cf, but nothing referencing that
> in /usr/bin/spamassassin or spamassassin.prefs.
>
> Am I miss
> Hi Justin,
>
> Along the sames lines, do you mind if I modify the source for the mysql
> lookups to include a larger username and submit it back to you?
>
> 1) A lot of systems have user names longer than 8 chars
> 2) A lot of us are running qmail with vpopmail or vmailmgr (I run both) and
> the
>
> Sure. Apparently there's more internet cafes in Nepal than there
> are in Dublin so that shouldn't be a problem ;)
>
Can I join you there in Nepal? :)
Justin
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/list
>
> I did some reading on using SA with mysql and this having the ability to
> enable / disable per user. Is there a simple interface to this or is
> mysql even required for what I am trying to do?
In my local copy of my global prefs, I have required_hits 80, then when
one of my customers wants
The README file in the sql directory should explain most of what you need.
Basically, it will read the same options that could be set in the user's
$HOME/.spamassassin/user_prefs file.
Justin England [EMAIL PROTECTED]
Network Administrator
E-Net Information Ser
copy of it just as it came into my account.
Justin England [EMAIL PROTECTED]
Network Administrator
E-Net Information Services http://www.enetis.net
Tel: 605-341-3638 Fax: 605-341-8880
> (aside: can *any* preference be in the SQL table? I have some required_hits
> which work, but whitelist_from seems to be ignored. individual users seems
> to work and GLOBAL does seem to be recognized.)
>
Anything that can be found in the users $HOME/.spamassassin.prefs (or
wherever the file
ers and if
they only come from local IPs, then it would give them the whitelist
score. All of our IPs have both A and PTR records in our DNS server, so
it should be easy to determine if the e-mail is "local" meaning that it was
sent from a local IP to our mail server, then
> SpamAssassin website, would be worth a look too.
>
> > So, the thing which popped into my head today was to digest
> > the SA spam up, and send a daily or weekly summary through,
> > of spam, based upon the SA score. The digest would have an
> > index of sender, subject, and be ordered by SA sco
