This article applies to:

• Trustwave MailMarshal (SEG) 6.9.5 and above
• Trustwave ECM/MailMarshal Exchange 7.1 and above

Question:

• What are the Dead Letter reason codes?

Information:

A Dead Letter message is an email message that MailMarshal cannot deliver due to a processing problem. By default, MailMarshal moves these messages to special folders.

These message cannot be managed with SQM or other end-user tools.

The most common reason for Engine dead letters is a problem with unpacking of the message or attachments.

In the named versions of MailMarshal, you can choose to release these messages automatically using Dead Letter Policy. You can apply Dead Letter Policy based on text matching of the reason code that MailMarshal logs for a message.

Note: The deadletter reason code is inserted in the Envelope information of the message file. You can review this information by viewing the message in the MailMarshal Console. Specific information about the reason may be available in the Engine log file for the message.
 

 
Reason Codes:

The reason code logged by MailMarshal is the entire string from the list below (including numeric code and text). The Dead Letter Rule condition allows you to enter all or part of these strings. For example, if you enter DL440 the condition will match any of the unpacking reason codes.

General:

These errors are generated before a file is opened by the Engine.

• DL00000 Unexpected error
• DL10000 Unexpected error while scanning the incoming directory
• DL10001 Message file doesn't obey the naming convention
• DL10002 Message file causes the engine to crash
  • If the Engine service fails while processing a message, when the service restarts the message will be deadlettered with this code.

Criteria:

• DL20000 Unexpected error while performing rule/component processing
• DL20001 External command criteria result is undetermined
• DL20002 External command action result is undetermined

MailMarshal Exchange:

The following errors are specific to MailMarshal Exchange processes.

• DL30000 Unexpected error while moving a message to the replay directory
• DL31000 Message processing caused an error
  • A filesystem error occurred when attempting to move a message to the replay directory.
• DL32000 Envelope processing caused an error
  • The engine is unable to locate the envelope start marker in the message file.  An invalid or corrupt mail message could cause this.
• DL33000 Replay message processing caused an error

Message Pre-Processing:

• DL40000 Unexpected error while processing a message
• DL41000 Message errors
  • A filesystem error occurred when attempting to open the message file.
• DL42000 Envelope errors
  • The engine is unable to locate the envelope start marker in the message file.  An invalid or corrupt mail message could cause this.
• DL43000 Message splitting errors
  • A problem occurred in the process of splitting a message into multiple editions (splitting occurs when different rules apply to different recipients).

Unpacking:

These errors are generated during the process of reading the components of a message and its attachments. They could be caused by a corrupt file, or unknown file format variant.

• DL44000 Unexpected error while unpacking a message
• DL44001 Apple Single unpacker failed
• DL44002 Archive unpacker failed
• DL44003 B64 unpacker failed
• DL44004 Bin Hex unpacker failed
• DL44005 CMS unpacker failed
• DL44006 EMF unpacker failed
• DL44007 MailBody unpacker failed
• DL44008 MailMsg unpacker failed
• DL44009 MAPI Block unpacker failed
• DL44010 MS Excel unpacker failed
• DL44011 MS Outlook unpacker failed
• DL44012 MS Power Point unpacker failed
• DL44013 MS Word unpacker failed
• DL44014 Office 2007 unpacker failed
• DL44015 OLE unpacker failed
• DL44016 PDF unpacker failed
• DL44017 RTF unpacker failed
• DL44018 RTF Object unpacker failed
• DL44019 Simple unpacker failed
• DL44020 TNEF unpacker failed

Message Post-Processing:

• DL45000 Message body errors
  • The engine could not parse the message body while attempting to create a preview for the database.
• DL46000 Running rules errors
  • The rules processor failed to rename a message (filesystem error)
  • The rules processor failed to move a message to the output directory (filesystem error).
  • The rules processor is unable to delete a message (filesystem error).
• DL46001 Outstanding Goto
  • A goto (pass message to rule) condition could not be satisfied (configuration is inconsistent).
• DL46002 Virus scan error
  • A virus was found in the message, and the message was not quarantined (or virus clean was requested but could not be completed).
  • CAUTION: The message is likely to contain a virus or malware. In most cases you should not allow such messages to be passed through.
• DL47000 Logging attachment errors
  • A problem happened while writing the information about message attachments to the database.