timeout after CONNECT, no HELO/EHLO response from clients

2011-03-09 Thread Adam N. Copeland
Seeing a problem with inbound delivery from relays. Incoming client connections are timing out, but I'm able to telnet to port 25 on my host and immediately get the 220 banner every time. Sometimes the connection times out before the 220 banner is displayed, sometimes it doesn't and the client neve

Re: timeout after CONNECT, no HELO/EHLO response from clients

2011-03-10 Thread Adam N. Copeland
Yes, that time out setting is still definitely the default. Snoop is basically Solaris' native version of tcp dump, and shouldn't be putting the packets out of order when capturing. Maybe the client is making more than one connection attempt? The part that made me suspect my server is that the sa

Re: timeout after CONNECT, no HELO/EHLO response from clients

2011-03-10 Thread Adam N. Copeland
fo] timeout after CONNECT from unknown[128.180.2.160] Mar 10 12:17:31 pmx4 postfix/smtpd[25758]: [ID 197553 mail.info] disconnect from unknown[128.180.2.160] Adam N. Copeland wrote, On 3/10/11 10:32 AM: > Yes, that time out setting is still definitely the default. > > Snoop is basic