Hello, all.
Here's the current situation with what I was concerned was a memory
leak. Since the Network Settings DNS was changed to the named process
on the same machine as the CG Pro mail server some 36 hours ago, and
the spamd settings were changed to
spamd -d -x -q -u nobody -x -m 4 --max-conn-per-child=50 --timeout-
child=180 -r /var/Communigate/spamdprocessid
There has been NO further apparent memory issues and no backlog of
email (and Spotlight, i.e. mdworker, was still running, Joanne.)
One other thing that is of note is that we had also institute
blocklists which had previously been disabled. In order to get a
better picture of how much mail was then coming into the server prior
to this change, I've gone back to the logs for some tallies. Here's
the way those numbers stack up:
Email that was not culled by the blocklists that required spamd
scanning: ~13,000 pieces in 24 hours.
SMTP connections that were refused outright (no spamd scanning
required): ~100,000 pieces in 24 hours.
Total then for the last 24 hours of spam was 113,000, if you
considered all 13,000 pieces that got through the blocklist as spam.
(Now I suspect that about 60% to 70% of what got through was really
determined to be spam.) That comes to 1.307 spam pieces per second.
Now Joanne suggest I do a time spamc test which I did:
My results for time spamc < (test email):
real 0m0.354s
user 0m0.001s
sys 0m0.005s
My results for time spamassassin < (test email):
real 0m5.310s
user 0m1.969s
sys 0m0.521s
I clearly see slowdowns in spam on the weekend so these numbers
represent likely the lower end of the scale for incoming, so a valid
estimate would certainly be that there are 150,000 to 200,000 spam
connections under a weekday load.
Now my question is this. Could the apparent memory issue simply under
the crush of the above load actually have been a combination of not
having the blocklists on, having the DNS for the mail machine set to
reference another DNS host server on my LAN, and perhaps a less than
optimal spamd process?
I'm not sure how the statistics here shake out here. How many pieces
of email would a spamd child process be able to process per second
given the numbers above? If I have 3 child processes, would they be
overwhelmed by this load so that I have just misinterpreted a memory
leak issue?
Ron Smith
[EMAIL PROTECTED]
"Having an email problem is painful, but character-building."
