Danita Zanre wrote:

I have an offtopic question (but since it's my amavis server I'm going to be bold 
<g>).

I have two SLES 9 servers that are configured almost identical at the server, but are not the same hardware. The postfix/amavis setup is exactly the same (in fact I copied the config files from the original "fast" server to the new "slow" server. The original server is a P4 2.8 Ghz machine with 1.5 Gig memory. It processes 20000 messages a day or so. The new server is a dual Xeon 2.8 Ghz machine with 1 Gig memory.
Here's my problem.  The new dual Xeon machine is often taking a HUGE amount of time to issue a 220 
at the connection.  And it shows many, many "lost connection after CONNECT" errors.  I'm 
fairly new to Linux, and I don't know where to start looking.  I'm a NetWare person by background, 
and am looking for something that will show me all of the port 25 connections, for example, or shed 
some light on why the server is not accepting connections as fast as its "sister" 
machine, which accepts them almost as fast as the log will scroll for me to watch.
Hi

Well, I'd say 95% of all slow connections just at the start are related to reverse DNS lookups...
Is it postfix or amavisd-new timing out?? I guess postfix, right?
Check your config if postfix does any reverse DNS which do fail because of some DNS misconfiguration... Try to reverse-lookup the ones with the lost connections manually and see what happens...

Matt


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to