Thanks for the info Viktor. That sounds like a rather bold statement and I don't think customers at times are willing to concede that it's something on their end causing it.
Is there anything else that we could do further to prove to the customer that it was their application that as you have said is not closing the TCP socket nor sending QUIT after completing a message delivery? On Mon, Jun 2, 2014 at 10:19 AM, Viktor Dukhovni <postfix-us...@dukhovni.org > wrote: > On Mon, Jun 02, 2014 at 08:35:25AM +1000, tswmmeejsdad . wrote: > > > May 19 16:06:50 smtp01 postfix/smtpd[21940]: timeout after END-OF-MESSAGE > > from unknown[10.84.72.227] > > The SMTP client neither closes the TCP socket nor sends QUIT after > completing a message delivery. Fix the client. > > -- > Viktor. >
