On Wednesday 16 June 2004 23:46, Robin Lynn Frank might have typed:
> I just set up a new box with postfix/maildrop/spamassassin. The problem is
> that if I use the following in my maildrop configuration, a couple of spamd
> PIDs just sit there sucking up CPU and RAM (forever, if I let them).
>
> from /etc/maildrop/maildroprc:
> # up tp 50k only
> if ( $SIZE < 50000 )
> {
> xfilter "/usr/bin/spamc"
> }
> [...]
>
Real users or virtual?
if ($1 eq 'spam')
{
to $SPAM
}
exception {
xfilter "/usr/bin/spamc -u [EMAIL PROTECTED]"
}
if (/X-Spam-Status: yes/)
{
to $SPAM
}
is my .mailfilter file, but should work equally well in a global setup.
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/bin/maildrop
-d [EMAIL PROTECTED] ${extension} ${recipient} ${user} ${nexthop}
is the calling line. No issues with spamd running away or anything silly.
/usr/bin/spamd -d -r /var/run/spamd.pid -a -c -q -u vmail is the running
process.
