Encryption error while encrypting input data
Last Updated February 08, 2013
 Encryption error while encrypting input data
Error code: 2045
Error text: Encryption error while encrypting input data
Affected module: conduit
Product version: Symantec Brightmail Gateway 9.0 and later versions
One or more antispam rulesets is not current.
Many possible causes for this error including the system running out of disk space. The most common cause for this issue is a problem with a downloaded ruleset or ruleset update.
The Symantec Messaging Gateway is designed to download rule updates every few minutes, and can recover from most such issues without intervention within 5 to 10 minutes. Any ruleset that encounters a problem is discarded, and the previous version of the rules continues to be used for filtering.
Additionally, the scanning engine uses several different antispam technologies and rulesets to filter messages. This error may apply to a single antispam technology and all other antispam rulesets are being updated.
If the error only occurred once, or a few times in close succession, it may be safely ignored, as the system has recovered on its own.
If the error continues to occur, complete the following steps:
log in to the system's command line.
Delete the rule files by using the delete allrules command.
Restart the connector by using the service connector restart command.
Force the compliance ruleset to be refreshed.
Do this refresh by making a minor change to an existing compliance rule or creating a new one. You may immediately reverse the change if you want. This change is referred to as a 'dummy change'.
You may halt incoming mails while doing so, then once the rulesets have been refreshed, restart mail flow. Mail flow may be halted by setting the MTA to 'Pause scanning and delivering' from the Edit Host Configuration screen, or from the command line with the mta-control pause-mode pause-scan command. Either of these actions allow mail to be accepted, but it is not processed until MTA operation is restored. Another option is to completely halt the MTA from the command line by using the service mta stop command.
Once the rules have been deleted, wait 4 to 5 minutes for new rules to be downloaded, and resume scanning either by setting the MTA to Accept and deliver messages normally from the Edit Host Configuration screen, or from the command line with mta-control pause-mode resume-scan command. If you completely halted the MTA, you need to restart it from the command line by using the service mta start command.
Imported Document ID: HOWTO75081
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe