When querying the Message Queues page of the Control Center web interface, some messages appear stuck in the Inbound queue with the error: 421 4.7.7 [internal] Unable to process message at this time.
Run mta-control command to query queue also shows the same phenomenon. On further review of the mail log, there are errors stating “Deferring message: failed to filter message” .
There are insufficient resources available to the SMG image. On review of the system status, the swap used about 50% and the CPU is busy with I/O wait.
This can also happen, if customer has enabled Directory Integration and SMG is resolving recipient addresses. If connectivity to LDAP source has failed or there is an issue pertaining specifically to the LDAP source, emails will queue up in the inbound queue with the aforementioned error message.
If Directory Integration is enabled, investigate if the issue is caused by LDAP source, by telneting to the LDAP source. If there is no connection, you should either fix the LDAP source or configure another in the SMG configuration.
If this is not resolving the issue, then continue with the following steps.
Reboot the appliance to release the exhausted resource and the product recovered.
Suggestion: 1. Too many compliance polices can contribute to negative performance. Each message should be reproduced in the local file system and then use an additional socket connection to destination in memory. If possible choose dedicated archive product to achieve this requirement.
2. If more than 1000 mailboxes exist in the environment, please deploy a Vmware image of SBG in ESXi server(free) to achive a load balance.
3. Tuning the database backup schedule to a low usage time as the backup consumes disk space and CPU I/O.
4. When the administrator receives a swap space alert this naturally suggests that resources are exhausted and must be addressed.
Imported Document ID: TECH178997
Subscribing will provide email updates when this Article is updated. Login is required.