SpamAssassin user prefs w/DB and MailScanner

[Martin Hepworth]

Leah

First thing you'll have to do is split the email into individual recipients
which can only be done on sendmail or exim to the best of my knowledge.

(see http://www.fsl.com/support/QuarantineReport.tar.gz for howto).

A lot of ISPs run MS without per-user stuff and have no issues..but
splitting the email and using the customfunction you should be able to do
white/blacklisting on a per recipient address basis - calling the function
from "Is Definitely Spam" and "Is Definitely NOT Spam" settings.

SA scoring/rules on a per user basis is NOT possible.

--
Martin Hepworth 
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-
> bounces at lists.mailscanner.info] On Behalf Of Leah Cunningham
> Sent: 20 April 2006 16:22
> To: mailscanner at lists.mailscanner.info
> Subject: Re: SpamAssassin user prefs w/DB and MailScanner
> 
> On Thursday 20 April 2006 04:33, Jan Brinkmann wrote:
> > On Thu, Apr 20, 2006 at 12:50:58AM -0400, Leah Cunningham wrote:
> > > I've been starting to deploy MailScanner on several servers and have
> been
> > > quite pleased so far.  I am doing a migration now from a server that
> was
> > > utilizing the SpamAssassin user prefs features to allow users to set
> > > custom whitelists, blacklists, and other settings.  These were being
> > > stored in a mysql backend.  Some relevant old spamassassin settings:
> > >
> > >  user_scores_dsn
> > > DBI:mysql:sqmaildb:somehost.example.net:3306 use_bayes 1
> > >  bayes_auto_learn 0
> > >  bayes_store_module        Mail::SpamAssassin::BayesStore::SQL
> > >  bayes_sql_dsn
> > > DBI:mysql:sqmaildb:somehost.example.net:3306 auto_whitelist_factory
> > > Mail::SpamAssassin::SQLBasedAddrList user_awl_dsn
> > > DBI:mysql:sqmaildb:somehost.example.net:3306
> > >
> > > Does anyone have any experience integrating this type of configuration
> > > w/MailScanner, or pointers to docs?
> >
> > You can do this using CustumFunctions. Take a look into for example
> > '/optMailScanner/lib/MailScanner/CustomFunctions'. There is a file
> > called MyExample.pm. You have to write a function, which looks up the
> > settings in the database. Then you return either 0 for no or 1 for yes
> > from your function. Scan Messages should be set to yes, and for example
> > Virus Scanning could be set to &YourCustomFunction :
> >
> > Scan Messages = yes
> > Virus Scanning = &YourCustomFunction
> 
> Ah, I had been hoping that you could just add the spamassassin settings to
> do
> the user prefs lookups.
> 
> Is there another way to implement user level preferences in MailScanner
> that
> would end up being similar to the SpamAssassin user prefs functionality.
> Basically, I want to be able to allow each user to have their own white
> and
> black lists that only apply to mail sent to their address, at a minimum.
> It
> would be nice if each user can set their own spam scoring prefs, etc.
> 
> Leah
> 
> --
> Leah Cunningham : d416-585-9971x692 : d416-703-5977 : m416-559-6511
> Frauerpower! Co. : www.frauerpower.com : Toronto, ON Canada
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
> 
> Before posting, read http://wiki.mailscanner.info/posting
> 
> Support MailScanner development - buy the book off the website!


**********************************************************************

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.	

**********************************************************************