Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-26 Thread dman
On Tue, Feb 26, 2002 at 02:12:06AM -0800, Karsten M. Self wrote: [...] | I'd had exim running from inetd rather that as a daemon, which might | also explain the many forkings. [...] Yeah, that would have an effect on it. If exim runs as a daemon, then it can monitor and control the various forks

Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-26 Thread Karsten M. Self
on Fri, Feb 22, 2002, dman ([EMAIL PROTECTED]) wrote: > On Fri, Feb 22, 2002 at 04:47:52AM -0800, Karsten M. Self wrote: > | on Thu, Feb 21, 2002, Alan Shutko ([EMAIL PROTECTED]) wrote: > > I agree -- it sounds like exim is forking lots of processes (one for > each delivery) as it tries to deliver

Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-22 Thread Manoj Srivastava
>>"Karsten" == Karsten M Self writes: Karsten> The problem I'm having as a dialup user is when I pull mail Karsten> periodically. With several hundred emails stacked up, I can Karsten> readily run into user process limits (256 processes per Karsten> user) while handling mail. I use

Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-22 Thread dman
On Fri, Feb 22, 2002 at 04:47:52AM -0800, Karsten M. Self wrote: | on Thu, Feb 21, 2002, Alan Shutko ([EMAIL PROTECTED]) wrote: | > "Karsten M. Self" writes: | > | > > When pulling mail, I'll see the system spike to 350 or more processes. | > > It appears that each mail delivery initiates a separ

Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-22 Thread Karsten M. Self
on Thu, Feb 21, 2002, Alan Shutko ([EMAIL PROTECTED]) wrote: > "Karsten M. Self" writes: > > > When pulling mail, I'll see the system spike to 350 or more processes. > > It appears that each mail delivery initiates a separate exim process > > (which I hadn't expected) and procmail process (this I

Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-22 Thread Karsten M. Self
on Thu, Feb 21, 2002, christophe barbé ([EMAIL PROTECTED]) wrote: > > spamd/spamc are your friends. Yes, they are. I'm already running them. Still have the problem. I did do some trials a couple days ago on up to 2,000 messages. spamc was about 4x faster than spamassassin -- 1 second per mess

Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-21 Thread christophe barbé
spamd/spamc are your friends. When I started using spamassassin on my laptop I got the same problem each time I plug it on the network. My conclusion was that spamassassin was the real problem (with the forked perl interpretor for each mail). Worst than you, it triggered the bug in current 2.4 ker

Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-21 Thread dman
On Thu, Feb 21, 2002 at 02:46:24PM -0800, Karsten M. Self wrote: | I've been running spamassassin on several boxes (home and work) over the | past few weeks. It rocks. Completely replaced my own procmail spam | detection recipies. Sweet. | The problem I'm having as a dialup user is when I pull

Re: Spamassassin, fetchmail, exim, and system resource issues

2002-02-21 Thread Alan Shutko
"Karsten M. Self" writes: > When pulling mail, I'll see the system spike to 350 or more processes. > It appears that each mail delivery initiates a separate exim process > (which I hadn't expected) and procmail process (this I had). I don't send fetchmail's output through exim, I just put this i

Spamassassin, fetchmail, exim, and system resource issues

2002-02-21 Thread Karsten M. Self
I've been running spamassassin on several boxes (home and work) over the past few weeks. It rocks. Completely replaced my own procmail spam detection recipies. The problem I'm having as a dialup user is when I pull mail periodically. With several hundred emails stacked up, I can readily run int