-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
On Thursday 17 June 2004 00:28, Duncan Hill wrote:
> 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.
I discovered, that for whatever reason, dcc was dying. When I turned off the
dcc and razor2 checks, the problem went away. In retrospect, I have enough
native SA rules, that dcc and razor2 aren't really needed.
- --
Robin Lynn Frank
Director of Operations
Paradigm-Omega, LLC
======================
And they shall beat their swords into plowshares, for if you hit a man
with a plowshare, he's going to know he's been hit.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Sed quis custodiet ipsos custodes?
iD8DBQFA0fOro0pgX8xyW4YRA6+KAKCYZ3Rd5OdN5hqyieWrZM81bbYf7QCfQmPU
DXQDW+Gb3tdvM7yZi3hvkyM=
=dva5
-----END PGP SIGNATURE-----
