This box does one thing only cleans email before forwarding onto an exchange forest. The system is over kill, quad core intel, 16GB memory, hdd is a velociraptor. This is for a network on which we get around 1 email every second. System load never gets >0.1. DNS are two servers both on gigabit on diff networks. All of the body checks are post queue, done by amavis.
Will check synchronous syslog, but given the lack of load, not that hopeful. No its a problem up stream, one that tcpdump will help me get an answer. Thank you though. best eric eric smith senior network administrator http://www.techsoft3d.com email: e...@techsoft3d.com skype: eric_ae_smith On 7/21/11 12:13 PM, "Victor Duchovni" <victor.ducho...@morganstanley.com> wrote: >On Thu, Jul 21, 2011 at 07:05:41PM +0000, Eric Smith wrote: > >> Damn that was what I was afraid of?.. >> >> >> So I am probably missing something in either my setup or in the log >>file >> >> hence why its included. >> > >> >No, the remote SMTP server not connecting to your server is not caused >> >by your configuration. >> >Do a tcpdump *on the internet connection*, to see what's what. > >Actually, it can be your configuration if low throughput drives up >concurrency to the configured limit, and then connection service latency >climbs. > >Poor throughput can be caused by many factors: > > - Slow DNS resolution > - Inadequate disk I/O capacity > - Insufficient network bandwidth > - Misconfigured synchronous syslog (default Linux) > - Excessive cleanup header/body checks > - Slow proxy filters > - Slow milters > - Slow policy services > - Slow lookup tables (MySQL, ...) > ... > >-- > Viktor.
