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

2011-03-10 Thread Victor Duchovni
On Thu, Mar 10, 2011 at 02:35:56PM -0500, Adam N. Copeland wrote: > This is happening to many clients that are trying to deliver to my domain. > > This is a pretty straightforward example of a connection and failure. > This is not spam, it's verified legitimate traffic from another .edu > that su

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

2011-03-10 Thread Adam N. Copeland
This is happening to many clients that are trying to deliver to my domain. This is a pretty straightforward example of a connection and failure. This is not spam, it's verified legitimate traffic from another .edu that successfully delivers to other domains. Mar 10 12:12:30 pmx4 postfix/smtpd[257

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-09 Thread Jeroen Geilman
On 03/10/2011 01:56 AM, Victor Duchovni wrote: On Thu, Mar 10, 2011 at 01:14:48AM +0100, Jeroen Geilman wrote: Mar 9 18:38:03 pmx4 postfix/smtpd[13358]: [ID 197553 mail.info] connect from unknown[134.53.6.74] okay Mar 9 18:41:03 pmx4 postfix/smtpd[13243]: [ID 197553 mail

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

2011-03-09 Thread Victor Duchovni
On Thu, Mar 10, 2011 at 01:14:48AM +0100, Jeroen Geilman wrote: >> Mar 9 18:38:03 pmx4 postfix/smtpd[13358]: [ID 197553 mail.info] connect >> from unknown[134.53.6.74] >> > okay > >> Mar 9 18:41:03 pmx4 postfix/smtpd[13243]: [ID 197553 mail.info]> >> unknown[134.53.6.74]: 421 4.4.2 smtp-in.m

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

2011-03-09 Thread Jeroen Geilman
On 03/10/2011 01:00 AM, Adam N. Copeland wrote: 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 d

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: no helo

2009-09-24 Thread Victor Duchovni
On Thu, Sep 24, 2009 at 09:59:21AM -0400, Wietse Venema wrote: > > to the servers that do not require HELO. If the server requires HELO > > the error is: > > 550 Forged host name (in reply to RCPT TO command)) > > Please show evidence that Postfix sends no HELO or EHLO c

Re: no helo

2009-09-24 Thread Wietse Venema
Antanas Kneita: > The thing is that there is no error message and the email is delivered > to the servers that do not require HELO. If the server requires HELO > the error is: > 550 Forged host name (in reply to RCPT TO command)) Please show evidence that Postfix sends no HELO or

Re: no helo

2009-09-24 Thread Wietse Venema
Antanas Kneita: > Hello, > > i have a problem with my postfix. It doesn't send HELO when the > hostname is set to a real FQDN name (A and PTR records are done). If i > change the hostname or smtp_helo_name to something that is not my > original FQDN, then it sends the HELO. Please report the ERRO

no helo

2009-09-24 Thread Antanas Kneita
Hello, i have a problem with my postfix. It doesn't send HELO when the hostname is set to a real FQDN name (A and PTR records are done). If i change the hostname or smtp_helo_name to something that is not my original FQDN, then it sends the HELO. Thanks in advance