On 4/13/05, Maciej Soltysiak <[EMAIL PROTECTED]> wrote:
> Hello Maciej,
>
> Wednesday, April 13, 2005, 4:06:33 PM, you wrote:
>
> > Hi Jason,
>
> > I will try that, thanks!
>
> >> If you use qmailadmin, then use the --enable-modify-spam and the
> >> --enable-spam-command to allow the option of spam filtering on a
> >> per-user basis from within qmailadmin.
> > I am using it, I recompiled it and reconfigured it.
> Well, I tried that. Adding spam detection in qmailadmin for one user
> added a .qmail file in his directory containing:
> |/var/qmail/bin/preline /usr/local/bin/maildrop /home/vpopmail/.mailfilter
>
> And I guess that is being executed, because I had problems
> with permissions at first.
>
> /etc/maildroprc is
> # Global maildrop filter file
>
> # Uncomment this line to make maildrop default to ~/Maildir for
> # delivery- this is where courier-imap (amongst others) will look.
> #DEFAULT="$HOME/Maildir"
>
> For a test i wanted to catch cron mail and send to a different folder.
> I created the folder and set this up, but cron mail that has X-Cron-Env:
> headers go to the INBOX as usual.
>
> My .mailfilter file is:
> if (/^X-Cron-Env/)
> {
> exception {
> to "Maildir/.cron/"
> }
>
> # if no cron folder, go on with delivery
> exception {
> to "Maildir/"
> }
> }
> else
> {
> exception {
> to "Maildir/"
> }
> }
>
> --
> Regards,
> Maciej
>
>
Also, the .mailfilter file must be owned by vpopmail.vchkpw.
You can turn on maildrop debugging in your .mailfilter file as well:
VERBOSE=10
logfile "/home/vpopmail/maildrop.log
maildrop.log needs to be chown'd to vpopmail.vchkpw as well
--
Jason
[EMAIL PROTECTED]
