On Tue, 2 Oct 2007, Obantec Support wrote: > From: "Matthias Häker" <[EMAIL PROTECTED]> > > > SPAM='spam' > > > > :0fw: $SPAM$LOGNAME.lock > > > > this will scan only one message for one user at a time. > > i thought the reason for using spamd/spamc was to provide a more > efficient processing of spam thru spamassassin. > does locking each mail coming in not increase the overhead?
No, locking the spamc rule means SA will be scanning only one message at a time (either globally or per-user, depending on how you create the lock), thus it *reduces* the overhead. Locking the spamc/spamassassin rule is a resource-usage-control method similar to limiting the number of child processes you allow spamd to spawn. I do this on my virtual-hosted MTA as it is very memory-limited. If you have a well-provisioned MTA box, then don't lock the spamc rule. Let SA scan as many messages as the resources allow, and control resource usage through the SA maximum-child-process limit. -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ [EMAIL PROTECTED] FALaholic #11174 pgpk -a [EMAIL PROTECTED] key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- Pelley: Will you pledge not to test a nuclear weapon? Ahmadeinejad: CIA! Secret prison in Europe! Abu Ghraib! -- Mahmoud Ahmadeinejad clumsily dodges a question (60 minutes interview, 9/20/2007) ----------------------------------------------------------------------- 236 days until the Mars Phoenix lander arrives at Mars
