Hi all,
I have an interesting problem with SpamAssassin-2.60-rc2. Actually that
problem has existed since at least SA-2.50 and I'm kinda pulling my hair out
on this one. It would be nice to hear some feedback or suggestions as I might
be doing something wrong here.
Quick description:
===============
SPAMd child processes stay around and do not die naturally when the following
conditions are met:
- Local user to which email was destined is over his alloted disk quota
- DCC is used
The SPAMd child associated with this delivery will sit around indefenitely -
eating up ressources:
Diagnosis:
=========
I created user "full" with a disk quota of 1MB. I then put a 5MB tarball in
his home directory and chowned it to his UID to make sure that user "full" is
defenitely over quota. Next I sent two sample-spam.txt's his way. The email's
bounced properly back to sender as it should be when the recipient is over
quota.
However: "ps auuxwf|grep spamd" reports:
root 14995 0.1 4.6 26036 23948 ? S 07:18 0:00
/home/spam-filter/bin/perl /home/spam-filter/bin/spamd -d -a -c --paranoid
full 15055 52.2 4.8 27136 24804 ? R 07:19 3:20 \_
/home/spam-filter/bin/perl /home/spam-filter/bin/spamd -d -a -c --paranoid
full 15280 48.5 4.8 27136 24804 ? R 07:20 2:45 \_
/home/spam-filter/bin/perl /home/spam-filter/bin/spamd -d -a -c --paranoid
In this case one SPAMd child is idling since 3:20 minutes and one since 2:45.
The related procmail and SPAMc processes have since long terminated.
I tried various switches to SPAMd in different combinations:
-d -a -m 5 --paranoid
-d -a -m 5
-d -a --paranoid
-d -a
-d --paranoid
-d
None of them fixed the problem and the SPAMd childs remained around whenever I
sent an email to the user which is over quota. I understand that signal
handling is somewhat hosed if the "-m" switch is used, so I tried with and
without.
Hotfix:
======
- Adding -L to the command line of SPAMd to disable all network test
OR
- Disabling DCC in local.cf with "use_dcc 0".
Disabling either the network tests or just DCC fixes the issue and the SPAMd
childs then die when they're no longer needed.
My setup:
========
Hardware & OS: Sun Cobalt RaQ550 (Runs modified RedHat-7.3).
Perl: ActiveState's Perl-5.8.0 (installed separate from onboard Perl-5.6.0)
MTA: Sendmail-8.11.6 (patched)
Local mail delivery: Procmail-3.22
DCC: dcc-dccproc-1.1.45
Razor: Razor V2.22
My /etc/procmailrc:
------------------------------------------------------------------------
SHELL=/bin/sh
TIMEOUT=60
:0fw
|/home/spam-filter/bin/spamc -s 80000 -u $1
------------------------------------------------------------------------
Tested with SpamAssassin-2.54, SA-2.55 and SA-2.60-rc2. Problem is always the
same. I tried to run SPAMd with the -D switch from the console, but I see
nothing out of the ordinary there.
Question:
========
Any ideas how to fix this aside from disabling DCC? I wonder if I have some
kinks in my DCC installation, but as far as I can tell DCC is installed
properly and works just fine - except on accounts which are over quota.
Many thanks in advance for any ideas and suggestions.
--
With best regards,
Michael Stauber
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
