Error: Data Completion Status...' received.


This article applies to:

  • Trustwave MailMarshal (SEG)

Symptoms:

  • Error: Data Completion Status...' received.
  • Error: Data Completion Status -1 failed to send "END OF DATA"
  • Error: Data Completion Status -2 no response to "DATA"
  • Error: DATA completion status -3 got bad "DATA" response

Information:

If a problem occurs during the transmission of the message by the MailMarshal Sender service, the message is typically queued for another delivery attempt at a later time. Depending on the nature of the error, and at what point in the proceedings it occurs, a status error is logged.

Here are some common errors that you may encounter for SMTP transmission issues, along with explanations for each error:

Data Completion Status -2
no response to "DATA" - err 0

This usually occurs if there is some sort of communication problem at the end of the transmission of the message. One common example is when MailMarshal sends a "Data Complete" signal, but gets no acknowledgment <250 OK> from the other server to say the message was received. MailMarshal must get this acknowledgement back, otherwise it must assume that the message was not received properly by the remote server. This is frequently caused by a problematic firewall or router between MailMarshal and the remote server which actually strips out the <250 OK> when it is sent from the remote server to MailMarshal. If this happens it is likely to cause the same message to be delivered repeatedly by MailMarshal.

Data Completion Status -1
failed to send "END OF DATA" - err 10053 - WSAECONNABORTED

A communication problem occurred during the transmission of data. This will not cause duplicate messages as there is no way the remote server could be confused into thinking it had received the message correctly as with the previous "no response to "DATA" error.

DATA completion status -3
got bad "DATA" response

MailMarshal gets an unexpected or bad response when transmitting the data of the message (I.E. when the actual message itself is transmitted after the initial SMTP handshake).

This article was previously published as:
NETIQKB45301

 


Last Modified 4/1/2020.
https://support.trustwave.com/kb/KnowledgebaseArticle10129.aspx