1/11    FIX YOUR SPAMASS
  3293 root           60   0 22512K 16640K RUN     42:15 12.74% 12.74% perl5.005
  2610 root           60   0 22328K  8036K RUN    277:52 12.60% 12.60% perl5.005
  amirs     3293 12.7  2.1 22512 16640  ??  R     4:08PM  42:18.75 /usr/local/bi\
n/spamd -a -c -d -m 5 -r /var/run/spamd.pid (perl5.00503)
s  etol     2610 10.9  1.0 22328 8036  ??  R     3:29AM 277:55.77 /usr/local/bin\
/spamd -a -c -d -m 5 -r /var/run/spamd.pid (perl5.00503)
        \_ pretty sad that spamass can run out of control like that
           \_ It is.  It might also be the fault of the ancient perl we're
              running it on.
              \_ I dunno, the docs I read specifically warn against
                 running spam assassin on large emails. (>250K)
        \_ I switched from spamd to spamass after spamd kept dumping
           huge cores in my home directory, putting me over quota.
           Has this problem been fixed?
           \_ I dunno, did you ever tell root that that was happening?
              \_ No, I just switched to using spamassin directly.