Take a look at the new vpopmail integration in SA 2.20 first before resorting to SQL. See the README.spamd-vpopmail in the spamd dir of the 2.20 distribution for details. It gives support for virtual vpopmail users. I wrote the patch and use it daily and works great.
-- Ed. > > Chris, > > take a look at storing the userprefs in a SQL database instead of > as files. > Search the mailing list archives for vpopmail or virtuser and > you'll probably > find lots of info. > > C > > Christopher Kunz wrote: > > CK> Hey there, > CK> > CK> since yesterday, I'm a happy SpamAssassin user (thanks to > Sascha Schumann, > CK> who might even read this list, too) on my VPopMail setup. I'm now > CK> investigating the possibility of setting SA as the default > spam blocking > CK> tool for all our domain customers. Unfortunately, vpopmail > uses virtual > CK> users, so the per-user configuration file generation will > propably not be a > CK> good approach. What to do - use -c and -p for each and every > mail account? > CK> Is there anyone who has done that already? > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
