All versions of Symantec Mail Security and Symantec Messaging Gateway.
Cause: Symantec Messaging Gateway cannot write a file to the disk. This may be caused by low disk space on Symantec Messaging Gateway. If low disk space is the cause, you will likely see other errors and the performance of Symantec Messaging Gateway will degrade. Starting with Symantec Brightmail Gateway 7.7, you can check disk usage and disk capacity in the Control Center.
To check disk usage and available disk space
Log into the Control Center as admin user.
Click Status > System > Hosts
The Disk Usage column lists the amount of disk space currently used.
Click Hardware Information
The Disk column lists the hard disk capacity. Subtract the Disk column on this page from the Disk Usage column on the previous page to determine the available disk space.
Resolution: Delete data from Symantec Messaging Gateway to free disk space. The following types of data are most likely to take up large amounts of space on the Symantec Messaging Gateway hard disk. The Control Center locations specified are valid for Symantec Brightmail Gateway 8.0.
Message audit logs
Message audit logs are disabled by default, but if enabled can consume a lot of disk space. Instead of storing message audit log data in the Control Center, you can send message audit log data to remote syslog on another server for long term storage.
To delete all existing message audit log data:
Log in to the command line and run "clear mallog".
To limit the amount of message audit log data stored: Administration > Settings > Logs > [Message Audit Logs/Days to store log data before deleting:]
If you are not experiencing any issues with Symantec Messaging Gateway, set the local log components to the errors or warnings level to reduce the amount of log data stored. Setting any local log component to the debug level can create large amounts of log data and should only be done if recommended by Symantec Technical Support. Instead of storing log data in the Control Center, you can send log data to remote syslog on another server for long term storage.
To delete existing log data: Log in to the command line and run "clear scannerlogs" or "clear bcclogs".
To limit the amount of log data stored: Administration > Settings > Logs > [Database Log Storage Limits]
The additional report data required for some reports can consume large amounts of disk space. Compare your report settings to the reports that you typically use to ensure that you have not enabled additional report data that is not used. Instead of storing report data in the Control Center, you can schedule reports to be emailed and save those reports for long term storage.
To delete all existing reports: Administration > Settings > Reports > Delete Data Now
To limit the amount of report data stored: Administration > Settings > Reports > [Reports Data Storage ] Administration > Settings > Reports > [Report and Dashboard Expunger Settings]
Spam Quarantine messages
Spam Quarantine is disabled by default, but if enabled can consume a lot of disk space.
To delete all quarantined email messages: Spam > Quarantine > Email Spam > Delete All
To limit the amount of spam quarantine messages stored: Spam > Settings > Quarantine Settings > [Spam Quarantine Expunger] and Spam > Settings > Quarantine Settings > [Thresholds]
If you create incidents to monitor outgoing email messages and the number of messages diverted to content incident folders is large, the messages may consume a lot of hard disk space.
To delete all messages in compliance folders: Compliance > Incident Management > [folder] > Delete All
To limit the amount of messages in compliance folders: Compliance > Settings > Compliance Folders > Maximum size for all Content Compliance folders
Imported Document ID: HOWTO65694
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe