Symptom: Your email gateway server is unable to deliver messages to your backend Exchange mail server because of an “Insufficient system resources” error.
Source: This is an Exchange-specific issue, which happens when less than 4 gigs of free disk space remain on the Exchange server’s queue drive for a particular domain.
Here’s a sample log snippet from our own gateway server:
|“Delivery of message E:\SPOOL3\DOMAINS\FN.CL\B0055738340.RCP to recipient email@example.com is delayed: ‘452 4.3.1 Insufficient system resources\r\n’.Message E:\SPOOL3\DOMAINS\domain.com\B0055738340.RCP deferred (.DEF) for recipient(s) in domain domain.com“
Analysis: This is likely caused by the back pressure feature in Exchange’s Transport Service. In Exchange Server 2007, the Transport Service monitors system resources such as disk space and memory on the Transport servers (e.g., Hub Transport and Edge Transport servers), and will stop new message submission if these resources run low. Existing messages in the queue will continue to be delivered, and when resource utilization returns to normal, message submission resumes. This feature is called back pressure.
Solution: To remedy the issue, you will need to reconfigure the Transport Service by doing the following:
1- Open the “EdgeTransport.exe.config” file, which is located under the C:\Program Files\Microsoft\Exchange Server\Bin directory.
2- Disable resource monitoring or change the monitoring configuration:
Open the “EdgeTransport.exe.config” file with Notepad and change the resource values; or an easier option is to just disable the monitoring completely.
To change the resource values, the string should go from: add key=“EnableResourceMonitoring” value=”true” /
To add key=“EnableResourceMonitoring” value=”false” /
Once this is done, save the file and restart the Microsoft Exchange Transport Service.
Trackback from your site.