On Tuesday 20 January 2004 10:01 am, Jeff Koch wrote:
> Hi Ken:
> Is this going to be coordinated with qmailadmin? 
Yes. Eventually

> Currently we use
> qmailadmin to add some mail filtering code that calls spamc. Qmailadmin
> also has the Spam Detection enable box at the bottom. Will the patch
> interfere with this.
No, if you like how things are working now, dont use --enable-spamassassin
with vpopail.

> We also, store the user spam prefs in a MySQL table - will this continue to
> work?

> Also, will this patch now allow spam filtering of mail delivered to remote
> forwards?
Yes, but not if the forward is done with a .qmail-user file in the main
directory, since qmail-inject will be forwarding it. But if it's a users
.qmail file then it will filter it.

Ken Jones

> Thanks,
> At 09:32 AM 1/20/2004, you wrote:
> >On Monday 19 January 2004 9:43 pm, Jeff Koch wrote:
> > > Is there an explanation of what this patch does somewhere?
> >
> >Not yet. It's fairly simple. It adds a new configuration option
> >--enable-spamassassin. Then the vdelivermail program will
> >call the spamc program with the right options unless the users
> >no-spamassassin flag is turned on. spamd will then check
> >if the user has a .spamassassin/user_prefs file or use the
> >default settings for the server. Also adds a vmoduser -f option
> >to turn off spam assassin for any one user.
> Best Regards,
> Jeff Koch

Reply via email to