Link State Information – E2K3


  • 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

Mail is not reaching the Inbox

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.

Slow Mail flow?

Would the Disk bottleneck affect the mail flow?

As well all know, yes that will “affect the slow or affect” the mail flow


Every message that is received by an SMTP gateway is saved to a disk.

  • With a default message size of 50 KB, about 7 to 8 disk writes occur for each message processed by the SMTP gateway.
  • This behavior is expected. Generally, SMTP performs 7 disk writes for every message queued that is smaller than 32 KB.
  • An SMTP gateway’s write buffer is 32 KB. Therefore, messages that are larger than 32 KB require an additional disk write for every 32 KB.

For example, a 100-KB message requires 10 disk writes to save the message in the queue.than 1 GB of memory.

it is good to run EXTRA to check the disk bottleneck and blame the “Third party” with a proof J

X:400 NDR Error when sending emails to E2K7 Server

I’ve recently come across a problem where, For Exchange 2003 and 2007 co-existence environment, When an mail-enabled object is created, the x:400 address will not be stamped.

This would result in an NDR’s with the recipient name “BsB57FD40C9308F7479BF159E9F227E5DD_


This would happen because of mission X:400 address


  • The Exchange 2003 RUS is responsible to update the object attributes in a co-exist Environment.
  • The Recipient Update Service has three System Policies that are installed by default when you install Exchange 2003. They are “Mail Enable Recipient”, “Mailbox Enable User” and “Hidden DL membership”.
  • If the recipient update service identifies than a new entry was added (or modified), and it does have the mailNickname to be considered mail-enabled.  Therefore, by default, the purportedsearch attribute should be below:





  • You can locate the “Mail Enable Recipient” object by using Adsiedit.msc tool:

CN=Mail Enable Recipient, CN=System Policies, CN=ORG_NAME, CN=Microsoft Exchange, CN=Services, CN=Configuration, DC=DOMAIN_NAME,DC=com

  • The user, contact and public folder object which have mailnickname and targetaddress (not for public folder) attributes.