![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2014-05-07 14:01, Anton Aylward wrote:
So what's the significance of this?
Like many others here I run a single user system, its just me who who uses it.
Like me.
I bring in my mail using fetchmail which feeds into procmail. The procmail makes use of spamc, the client that calls on spamd.
My fetchmail sends to postfix, who eventually calls procmail. And it can send several posts at the same time. If the email is processed by procmail faster than fetchmail gets them, it goes one by one. If not, it starts sending more simultaneously, up to a limit defined in "/etc/postfix/master.cf": procmail unix - n n - 7 pipe flags=R user=nobody argv=/usr/bin/procmail -t -m /etc/procmailrc ${sender} ${recipient} 7 is the limit in my case, and they do get used. And I need more than one, because each email takes time to process; currently: spamd: clean message (-2.7/5.0) for cer:1000 in 2.7 seconds, 6835 bytes. spamd: clean message (-2.6/5.0) for cer:1000 in 3.7 seconds, 8887 bytes. spamd: clean message (0.4/5.0) for cer:1000 in 3.5 seconds, 8195 bytes. spamd: clean message (-2.6/5.0) for cer:1000 in 3.7 seconds, 7195 bytes. spamd: clean message (-1.6/5.0) for cer:1000 in 3.4 seconds, 11125 bytes. Some take longer: spamd: clean message (-101.9/5.0) for cer:1000 in 9.7 seconds, 3561 bytes. Some way longer: spamd: clean message (-2.7/5.0) for cer:1000 in 57.3 seconds, 5630 spamd: clean message (-2.6/5.0) for cer:1000 in 53.2 seconds, 7839 bytes. (see the size) or spamd: identified spam (6.5/5.0) for cer:1000 in 213.1 seconds, 15976538 by At times, I got consistent processing times of 6..12 seconds each. A hundred emails would be processed in 1200 seconds, which I find intolerable - with 5% CPU load at most. The hurdle were the network test timeouts, I think. So yes, spamd with fetchmail paralelizes - if you put postfix in the equation. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)