I have also done a similar thing. I am now working on modifying
vpopmail/qmailadmin to put this information in individual users .qmail
files. This is because my domain method fell apart when email was
addressed to an alias, or caught by a domain catchall address. With
individual .qmail files, the -u option for spamc can be specified
manually in the mailfilter file.. This means it is the mailbox not the
address which is protected.

On Wed, 2003-06-04 at 03:30, Dzuy Nguyen wrote:
> Funny I just modified qmailadmin to incorporate similar features.  I would like
> to get involved in this project and contribute but with the condition that it
> will make it to the official qmailadmin code so that I can benefit from future
> code.
> 
> My implementation is done at the domain level rather than at the user's level,
> i.e. put either vdelivermail or maildrop filter into .qmail-default.  This is
> my own hack to get qmail/vpopmail/maildrop/spamassassin to work in my
> environment, but I'm opened to any discussions.
> 
> Dzuy
> 
> Joe Young wrote:
> > Joseph Young
> > Involved.com
> > System Admin
> > 
> > I am working on a patch for adding spamassassin into the QmailAdmin. I have
> > beginner's experience at C++ and have some of the work done. It is difficult
> > to say where I am at in the process. The patch is still beta and works for
> > only qmailadmin-1.0.7.01132003. If anyone is interested in helping get the
> > patch finished or working for another version, goto
> > http://naos.involved.com/
> > 
> > I have qmailadmin to show a check box that is checked if there is the
> > line,"enable_spamassassin", to .qmailadmin-limits. So the next step is to
> > have in user.c to add the line,"|/var/qmail/bin/preline
> > /usr/local/bin/maildrop /home/vpopmail/etc/mailfilter", in the user's .qmail
> > when it when user selects it.
> > 
> > I need help in writing the code to modusergo() in user.c to check .qmail and
> > to write to .qmail.
> > 
> > 
> > I have set up a anonymous cvs server for this project.
> > 
> > cvs -d :pserver:[EMAIL PROTECTED]:/home/cvsroot login
> > Use password: cvs
> > cvs -d :pserver:[EMAIL PROTECTED]:/home/cvsroot checkout
> > qmailadminspam
> > 
> > 
> > joe
> > 
> > ----- Original Message -----
> > From: "Dave Weiner" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, March 07, 2003 1:45 PM
> > Subject: Re: Re[4]: [vchkpw] SpamAssassin/vmodinfo changes
> > 
> > 
> > Gabriel Ambuehl wrote:
> > 
> >>-----BEGIN PGP SIGNED MESSAGE-----
> >>
> >>Hello Dave,
> > 
> > 
> > Hi Gabriel.  No need to CC me, I get the list email just as fast :)
> > 
> > 
> >>Friday, March 7, 2003, 9:09:17 PM, you wrote:
> >>
> >>>The lack of being able to turn it off per user is probably the only
> >>>thing that holds me back from using it :)
> >>
> >>I suppose adding a new field into vpasswd is a nono as it would break
> >>a lot of existing code, right? So the flagfile is probably the best
> >>idea (easy to implement, too). Thoughts?
> > 
> > 
> > Yes, I think some sort of dotfile would be the best.  Then any number of
> > tools could use it.
> > 
> > Suggestion, for those of us that use sql user prefs.  If the dotfile is
> > present but empty, just make the connection to spamc/spamd, assuming that
> > vpopmail support in spamassassin is being used.  If there's text in the
> > dotfile, use that for the -u option
> > 
> > 
> >>
> >>Best regards,
> >> Gabriel
> >>
> > 
> > 
> > Dave
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 


Reply via email to