Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm being placed under quite a lot of pressure from senior management over a relatively trivial issue. Basically the vast majority of users are complaining that they receive not read notifications (NRNs) for old emails and meeting requests in large numbers multiple times a day. I know something strange is happening because some are delivered at silly times in the morning (i.e 3AM or 4AM).

The problem I have is that these some of these NRNs are from meeting requests and messages that are 120 days old, so some users have deleted the original message so I don’t actually know if the NRN is from an email or meeting request.

This is typical of what users receive as a NRN:

From: Sender 
Sent: 23 March 2012 04:16
To: Recepient
Subject: Not read: Accepted: Status update

Your message 

   To: Sender 
   Subject: Accepted: Status update
   Sent: Wednesday, November 23, 2011 8:59:00 AM (UTC) Dublin, Edinburgh, Lisbon, London

 was deleted without being read on Friday, March 23, 2012 4:15:32 AM (UTC) Dublin, Edinburgh, Lisbon, London.


From: Sender 
Sent: 18 March 2012 01:13
To: Recepient
Subject: Not read: Gold delivery - Sourcing module

Your message 

   To: Sender
   Subject: Gold delivery - Sourcing module 
   Sent: Friday, November 18, 2011 9:37:58 AM (UTC) Dublin, Edinburgh, Lisbon, London

 was deleted without being read on Sunday, March 18, 2012 1:12:37 AM (UTC) Dublin, Edinburgh, Lisbon, London.

I have done a search and found the following:

But we already installed 'Update Rollup 6 for Exchange Server 2010 Service Pack 1' back in December, so I am not sure what we can do to fix this?

BTW we are running Windows Small Business Server 2011

share|improve this question
Did you see this note: Note The NRNs are not completely flushed until 120 days have passed after the hotfix is installed. Has it been 120 days since the update rollup was applied? – Coding Gorilla Mar 23 '12 at 19:40
I did but I was hoping I would not have to wait 120 days! I have just checked when the update was installed (which was 103 days ago). Can anyone confirm that this will fix the problem once the NRN queue has been fulshed? and that there is no way of speeding this process up? – Exile Mar 26 '12 at 10:02
It seems that your problem is exactly matching the one fixed by this update, so it seems reasonable that after 120 days your problem will go away. But I can't confirm for sure that it will. – Coding Gorilla Mar 26 '12 at 17:10
@Exile Did it go away after 120 days? – Mathias R. Jessen Apr 13 '12 at 19:15
As far as I can tell, Yes it has now 121+ days has elapsed! If I have anymore problematic NRNs from 120 days ago I will post here to let you guys know. I also made a post on technet about this which you can read here:… – Exile Apr 16 '12 at 11:20
up vote 1 down vote accepted

'Update Rollup 6 for Exchange Server 2010 Service Pack 1' seemed to fix my problem after waiting over 121 days.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.