Ricardo Kleemann wrote: >> What mail filters are you running? What is the load average reported by >> "uptime"? > > I'm using the pureperlfilter, with clamav, spamassassin, greylist... > nothing that takes a really long time
Well, there you go... pureperlfilter is a single-threaded filter. Message filtering doesn't have to take a "really long time" to cause problems. The way pureperlfilter is written, a small number of messages submitted simultaneously will cause the error that you're seeing. I don't know if there are stability problems with threads in pureperlfilter, or something else that's kept Julian from enabling it, but the code has been commented out for several years. You might consider using pythonfilter instead. >>> I already have MAXDAEMONS at 150 in esmtpd. What else should I adjust so >>> I don't get the resource unavailable error? >> Increasing that setting will only make the problem worse ... > The reason I have it high is because this server is busy with a lot of > outbound traffic... will increasing the MAXDAEMONS not allow it to > process outbound traffic better? No, it won't. Increasing that setting only allows more incoming connections, and you're already taking more than you can handle. You want to modify etc/courier/module.esmtp instead, and increase MAXDELS. (This documentation looks a little out of date): http://www.courier-mta.org/modules.html ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
