gatewayProxy Vs GatewayProxy - E2K3

Exchange 2003

gatewayProxy Vs GatewayProxy – E2K3

1. Difference between ‘gatewayProxy’ attribute on the Recipient Update Service object and ‘GatewayProxy’ attribute on the Recipient Policies object.

  • gatewayProxy is populated when the policy is applied and Recipient Update Service begins processing all the users who match the filter on the applied policy.
  • If the Recipient Update Service finishes processing the users successfully, it clears the corresponding entries from the gatewayProxy
  • If you clear the gatewayProxy attribute on the Recipient Update Service will not do anything, just helps the RUS to update the address to the object.

***If you clear the GatewayProxy attribute on the Recipient Policies will not do anything, it just stops the email flow. *** Do not try on the customer’s server.

2. Why the gatewayProxy on the Recipient Update Service is not cleared after the policy is applied?????

The possible reasons are:

  • When the Recipient Update Service or the Mad.exe process is killed or stops responding,  gatewayProxy attribute is not cleared because it has not completed processing the objects that apply to the policy.  Even when you restart the Recipient Update Service or the Microsoft Exchange System Attendant service(mad.exe) does not remove or clear the gatewayProxy attribute.
  • When Exchange System Manager and The System attendant (mad.exe) tries to access the gatewayProxy attribute at the same time

Leave a Reply

Your email address will not be published. Required fields are marked *