We are enforcing prohibit send levels at the user level in AD and we have a problem that when a user exceeds their mailbox limits (past prohibit send levels) and then cleans out their mailbox to get it well below the limit, it still takes a long time for them to be able to start sending mail again.Replication between the DCs is confirmed to be fine andeven if I launchRUS and the mailbox maintenanceprocess it still takes at least an hour for them to be able to start sending email. I do not think the problem is at the client level, because they have trouble sending througheither Outlook 2003 or OWA. I am guessing that maybe the RUS is having a problem? Is that what gets updated limits into Exchange andback down to Outlook? We do have the Enterprise and Domain RUS pointed to a DC(in the same site that andhas the global catalog on it) and they are set to "always run", but still not working correctly. Again the problem is not replication between DCs or anything like that. It happens the other way as well. If I take my email account and put an extremely low limit into AD it takes a while for Exchange to realize I am over my limit(even if I am closing out and starting new Outlook orOWA sessions) System and Application logs on the Exchangeservers are clean. Any help on how this works so I can troubleshoot it faster would be appreciated. This is not a problem with items hidden in the mailbox or anything where the mailbox might be over still be over it limit. Thanks, Dan

This has nothing to do with RUS. Exchange has cached some info and it takes some time for this cache to timeout and read new values. Simply give it time.