I have a SBS 2003 (SP2) with Exchange SP2. Public Folders are used to store Contacts, and emails. The emails usually have CAD drawings attached. There is one user with Outlook 2003 on XP Pro SP3 that gets this notice when they try and move an email from their mailbox to the appropriate Public Folder: [Header] Microsoft Office Outlook [Body] Can't move the items. A rule in this public folder prevents a message this large from being posted.In the Exchange System Manager there are NO limit set in either of the following areas: Public Store default setting- Organization\ Administration Groups Container\ Admin Group \ Servers Container\ Server\ Storage Group \ Public Foler Store - Properties, "limit" tabSpecific folder setting- Organization\ Administration Groups Container\ Admin Group \ Folders \ Public folders \ individual folder - PropertiesOther users are able to move emails with attachments to this folder.

Additional Information: I have logged into the Terminal Server (2003 SP2) as the same user. Using Outlook 2003I get the same notice from Outlook when I attempt to move the same email into the same Public Folder (same as on the desktop).

Additional Information: I created a new Public Folder from within Outlook while logged in as the user with the issue. This gave the user Owner rights to the public folder. I was able to copy the email in question to this new test folder. I am still in Outlook logged in as the user having the problem. So I went back to the public folder that was having the issue and went to Properties -> Permissions and removed the user who already had Owner's rights then added the user back and gave back owners rights. I was then able to move the email and did not get the notice.Is this a work around to a issue or a solution. I am still not sure what would cause someones permissions to lose validity?

The error is usually because of an attachment in a private folder that is too large for the public folder store, resulting in a failed attempt to copy it to a public folder destination But, permission corruption seems the cause in this case. It’s possible that the related ACE isn’t set correctly due to user operation, public folder replication and the likeJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com