Decomposition time out (the message has taken longer than the configured time seconds to decompose)
Last Updated February 08, 2013
 Decomposition time out (the message has taken longer than the configured time seconds to decompose)
Error code: 27225
Error text: Decomposition time out (the message has taken longer than the configured time seconds to decompose)
Affected module: brightmail_engine
Product version: Symantec Brightmail Gateway 9.0 and later versions
If virus scanning is enabled, the message is marked as Unscannable, and the appropriate policy action is performed. The policy action that is performed by default is delete message. The message scan stops when the current message part or file attachment is finished being scanned, and the remaining message parts and attachments are not scanned.
The message currently being scanned takes more time than the amount of time that is specified in the warning to scan. The default time for the warning to scan is 60 seconds. This is most likely because the message is extremely complex, with a number of attachments, or perhaps a ZIP file with several hundred files, or something about the message is causing scanning to take much longer than expected. It is possible that this condition can be worsened by the system being under heavy load, particularly in a virtual environment.
No action is necessary. The message that causes this warning completes processing and the appropriate actions are applied. If virus scanning is not enabled, Symantec recommends that you enable virus scanning, and set the desired action for the messages that are Unscannable.
If you get this message often, you may consider changing your business practices to avoid the email messages with attachments causing this warning. If you want to increase the time out value, click Protocols > Settings > Scanning > Container Limits > Maximum time to open container and edit the setting. A value of 0 results in no limit. However, this setting is intended to protect you from a denial-of-service attack , where a specially constructed message or multiple messages consume all scanning resources on your system and hence blocks mail flow.
The following is an example of the error message as it appears in the bmserver_log.
 Decomposition time out (the message has taken longer
than the configured 60 seconds to decompose).
Imported Document ID: HOWTO66285
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe