If memory serves, you can't increase the incoming concurrency limit above 200 unless you've patched qmail to make that possible. You could be hitting the limit even though you've set the value to 1024.
When your server stops accepting connections, are you seeing any errors in your logs? Do the running spamdyke processes consume a lot of CPU or memory? If you enable full logging, do those logs show anything to indicate where the processes are becoming "stuck"? One important thought: have you tried installing a caching name server on your mail server? That's usually the single biggest thing you can do to improve performance. -- Sam Clippinger Ulrich Eckardt wrote: > Hi Sam et all, > > just wanted to let you know that a lot of customers complained about > timeouts when trying to connect to the smtp port after I upgraded to > 3.1.5 (from 3.1.0) > I tested everything for about a week - all possible config, other > programs, etc. but the only thing that helped was installing 3.1.0 again. > > We have set the concurreny incoming to a max of 1024 and that limit was > never reached. A count of actuall spamdyke processes came up with about > 50 to 200 simultanious runs, but the ability to send or get dropped > didn´t seem to corralate to higher amounts of spamdykes running. > > I checked everything else (qmail-smtpd in general, clamd, spamc, > whatever) only 3.1.0 solved the problem. Since spamdyke really is agreat > piece of software, I just wanted to inform you, maybe you can find > whatever makes the difference. > > Thanks - Ulrich > > > > ------------------------------------------------------------------------ > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
