|Main Archive Page > Month Archives > postfix-users archives|
On 5/12/14, 12:27 PM, "Paul C" <firstname.lastname@example.org> wrote:
>Ya that's touch to see without more tests, losing connection after
>helo might have something to do with the problem injecting in to
>postfix, maybe its not liking the response its getting and not
>finishing the full smtp commands. In your log, this line stands out:
>match_list_match: 10.12.0.101: no match
>since its happening after the helo and that's where you are losing
>connection, might want to check if you have whatever is doing the
>match is configured correctly. What you're using to do that match I'm
>not familiar with, so maybe someone else can jump in to help there?
>On Mon, May 12, 2014 at 1:18 PM, Blake <email@example.com> wrote:
>> To me it seems that everything should work just fine but yet it fails.
>> Prior to during on debugging for the IPs in question the only error in
>> logs was the following.
>> smtp1 postfix/smtpd: connect from
>> smtp1 postfix/smtpd: lost connection after HELO from
Lost connection after HELO, but the debugging below uses EHLO.
>> smtp1 postfix/smtpd: disconnect from
>>>> Sending machine Error
>>>> An Error occurred trying to test SMTP Mail Server smtp1.(domain).com:
>>>> Client send command : EHLO 10.12.0.100 - SMTP Server reply message :
>>>> smtp.(domain2).com ESMTP Postfix, return code : 220 - SMTP Client send
>>>> command : HELO 10.12.0.100 - SMTP Server reply message :
>>>> 250-SIZE 25480000
>>>> 250 DSN, return code : 250 - SMTP Client send command : QUIT - SMTP
>>>> reply message: 250 smtp.(domain2).com
>>>> 221 2.0.0 Bye, return code : 250 - SMTP Client connection normal