On Wed, 7 May 2014 15:02:59 Carlos E. R. wrote:
On 2014-05-07 06:33, Per Jessen wrote:
Carlos E. R. wrote:
How big is the email itself?
"Just" 19 MB. Not that /huge/.
[...]
SPAMD_AWL=no SPAMD_NICE=yes SPAMD_ARGS="-d -c --max-children=8 " SPAM_SA_UPDATE="no" SPAM_SA_COMPILE="no" SPAM_AMAVISD_RESTART="no" SPAM_SPAMD_RESTART="yes"
Carlos, I've not read this entire thread, but I thought that it might be useful if I mentioned that I have spamd running on a Raspberry Pi filtering ALL my incoming mail from 5 different accounts, and the load average rarely gets above 0.05. RAM usage never gets above 25% (of 512MB). The "magic bullet" on this was a) use spamc/spamd instead of calling spamassassin for every mail (which I note that you are doing) and b) use COMPILED rulesets (I see above that SPAM_SA_COMPILE is set to "no"). When I moved it to compiled rulesets the load average dropped from 28 (no, that is not a typo) to 0.05. I think the maximum of children it is allowed to spawn is 5. Try running sa-compile on your ruleset and set SPAM_SA_COMPILE to "yes" and see if that makes any difference for your setup. After about a week of experimenting when I first set it up on the Rpi I was just about ready to give it up as impossible; the compiled rulesets were the key. BTW, that Rpi runs fetchmail, sendmail (yes, sendmail 8.1.5; not postfix - I could never get along with it), procmail, spamassassin, clamav and dovecot and handles all my email (including remote access from outside). Ticks along beautifully, makes no noise and uses less than 5W of power. :) Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org