Jim Conner wrote: > Believe it or not I am simply running this for one user....me :)
*OUCH* > So, > just one account. However, the volume can get quite high as I have > had the same email account for several years so there is lots of spam > involved. What's more is that I am on several mail lists so the > volume per day is in the thousands...an average of 2.5 to 3K per day. > However, this problem that I am seeing lately is occurring when I am > only grabbing around 300 messages. Hmmm. > This machine has 256 Mb of ram. As I stated before, its only being > used for one user. For single-user the hardware isn't much of a limit- usually. > I am using this machine as my spam filter. So, I have fetchmail > fetching my mail and then I have a forward rule in my .forward file > to pipe messages into spamassassin. Ummmm.... Do you have fetchmail feeding into a local MTA? > This is probably where the > serialness of the spamassassin processes that you see is coming from. > Then I am using popfile to grab my mail...yes, superfluous, but it > was in use before I started using spamassassin and just never stopped > using it. Ah, OK; you're not running a "real" server. <g> That changes things quite a bit. IIRC fetchmail can feed directly into procmail; you might want to spend some time looking into that to serialize the fetchmail->procmail part of your local delivery. I *think* that will effectively force fetchmail to wait for procmail to finish before starting on the next message. You may still want to look seriously into using spamd/spamc instead of spamassassin due to the startup overhead. -kgd -- "Sendmail administration is not black magic. There are legitimate technical reasons why it requires the sacrificing of a live chicken." - Unknown
