SMTP dispatcher closes connection before receiving answer to the EHLO command

• Related Articles

• Fragmented messages from SMTP server with no AUTH in the answer cause the runtime to stop responding

  Summary If SMTP is used and the SMTP server uses fragmented messages to get the answer to the EHLO or HELO request, Message Control is waiting for fragments which results in an unresponsive runtime if no fragments are left to receive. Description If ...

• Message Control SMTP sending type: Not robust against lagging SMTP connection

  Summary The message control engine tried to send the EHLO before the received server greeting was fully received (due to lagging connection - there was just one receive attempt without timeout). Now, the engine uses a 10 second timeout for completely ...

• When using SMTP dispatcher to send messages from Message Control, the Diagnosis Viewer shows error messages although messages are sent properly

  Summary If a mail is sent by the SMTP dispatcher of Message Control, the Diagnosis Viewer shows several messages containing "Receiving Data failed. Errorcode: 0" which are written in the message level "ERRORS". This occurs because the dispatcher ...

• FAQ: From a certain amount of connected Smart Clients the Smart Server closes unexpectedly, what can I do?

  It is possible that the Smart Server closes as it runs out of possible memory address space for a 32-bit application. In this case use the Smart Server 64-bit version.

• T5BusProfNetIO: stratonrt closes unexpectedly when receiving an invalid ProfiNet DCP frame

  Summary The zenon logic application using a ProfiNet IO Contoller fieldbus driver closes unexpectedly on receiving an invalid ProfiNet message. Description The zenon logic application using a ProfiNet IO Contoller fieldbus driver closes unexpectedly ...