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
LINK STATE TABLE
- Link state table contains the following information
o List of all Connectors -> Name
o Link status of the connectors -> Up/Down
o Link cost of the connectors -> Value
- Link state table information will be available with the Routing group master
- The Routing Group Master will be communicating with the other exchange server to update the LST through the TCP port 691
- The Routing Group Master will update the LST to the bridgehead server and bridgehead server sends the updated LST to the other bridgehead server in other routing group through TCP Port 25
What is use of Temp tables?
The Exchange Temp tables are special-purpose subfolders of the SMTP service’s logon to the Message Database. They are used for the creation of the bifurcated messages in the message categorizer, and as temporary storage for SendQ-submitted mail messages if SMTP cannot keep up with the processing of SendQ mail. When the SMTP service logs in to the Message Database, it forces an enumeration and submission of mail in the temp tables. So when we restart the Exchange server or restart the SMTP service, the mails in the temp tables will be resent.
Why the old messages are stuck in the queue?
- An error occurs each time the particular message is processed. For
example, the Information Store may return a retry-able error when an
attempt is made to relay the message, or the connector to the message
destination is unavailable.
- The message was categorized to go to a specific Message Database for
local delivery, but the Message Database is no longer available.
- An unknown or unexpected behavior caused by message damage.
What are roles and responsibilities of temp table?
- Act as a temporary Storage place for messages submitted via local Store Mailboxes while they are processed by Transport
- Persisting messages for bifurcation (for content conversion, DL expansion).
- Periodically removing messages from Send Queue (preventing “mail stuck in the Outbox” complaints).
- Enumerated via asynchronous op on VS logon to MDB.
- Can exist in every MDB for each virtual server to logon to it. Called TempTable#1, TempTable#2 etc… By default have 20 subfolders each for storing actual messages: configurable via
instance#\TempTable” Registry value
In recent past, we had few cases with “Incoming emails to the server does not reach the users inbox” problem. In all the instances we were able to fix the problem with solution provided in this email.
Issue : Incoming emails to the server does not reach the users inbox
Solution : Follow the steps if the conditions are satisfied
Condition 1 : Do is message tracking
Condition 2 : If the email either in the Deleted items or Recover deleted items (Dumpster)
Step 1 : download and run the mfcmapi.exe
Step 2 : Follow these steps to delete the junk email rule
1. Click Mfcmapi.exe
2. Click Session -> click Logon And Display Store Table
3. Choose the Profile Name -> click ok
4. Click MDB -> Get Mailbox Table
5. Double click on the user Mailbox
6. Expand Top of information Store table
7. Right Click on the inbox -> Open Assosicated Mailbox
8. Right click on the Junk email rule ->Delete messages
Step 3 : Close the outlook of the user and reopen it again
Reason : The emails are routed to the Dumpster or the Deleted items due to the corrupted junk email rule installed by the IMF.