At 2:04 PM -0600 on 3/29/02, Dallas Engelken wrote:
>If you need to set a catchall, then you'd edit $VPOP.
>NOTE: Editing the catchall through QmailAdmin will screw up your
>.qmail-default file. You would need to patch QmailAdmin to edit the new
>.qmail-default file... or just set .qmail-default to 0400 so QmailAdmin
>cannot write to it.
>
>Thats how I like to do it... hopefully that gives you ideas!
Dallas,
Thanks very much for the thorough and detailed response. I was hoping
to find a much simpler solution though. My needs are pretty simple
and I'm still a little intimidated by the complexity of keeping a
mail server happy. :-) Here's what I'd like to do... On the command
line, I can specify the prefs file like this:
spamassassin -P -p spamassassin.conf < possible_spam.txt
That works fine and would make an ideal solution *if* I can get it to
work when invoking spamassassin from maildrop's mailfilter file. To
illustrate, here's how the mailfilter file looks currently, minus a
few unrelated bits:
--------
# SPECIFY THE PATH TO THE MAILDIR
STD_PATH="/home/vpopmail/domains/$DOMAIN/$USER/Maildir"
# INVOKE SPAMASSASSIN, FILTERING FLAGGED MESSAGES TO THE TRASH MAILBOX
xfilter "/usr/local/bin/spamassassin -P"
if ( /^X-Spam-Flag: YES/ )
{
to "$STD_PATH/.Trash/"
}
--------
This setup works great. I can even add sqwebmail's filters by
invoking them as an include below the spamassassin xfilter line.
Unfortunately, it all breaks when I attempt to introduce the
user-specific config file by changing the xfilter line to read:
xfilter "/usr/local/bin/spamassassin -P -p $STD_PATH/spamassassin.conf"
To be thorough, the spamassassin.conf file contains 1 line which
reads: required_hits 4
I earlier tested the same file on the command line and it worked well.
Is there a simple way to make this work?
Again, thanks very much for your help.
Gawain
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
