"One or more rules could not be uploaded to Exchange server and have been deactivated. This could be because some of the parameters are not supported or there is insufficient space to store all of your rules."
The Microsoft knowledgebase gives information (Article ID 886616) regarding the size of the rule, along with possible workarounds that can be made, which I have tried. Before I created this new rule, this computer had one rule on it that has been run in the past, but it won't run now. The one rule was a simulation for the out of office assistant. The new rule I'm trying to implement is not big or complicated, only trying to delete those e-mails that are still coming through after our AV program has stripped the e-mail of its virus. We have other computers that are configured exactly like this one where there is no problem running this rule and other rules.
MS says to shorten the name of the rule (I have, it's called "spam"), to clear the "on this machine only" check box (it wasn't checked), delete old rules (there's only one other rule), combine similar rules (none to combine). There is one other method it mentions that I need to ask a question about: "Move your personal folders (.pst) file to a location that has the shortest path name." The .pst file is on our server, however, there is an archive file on the C drive of the computer that appears to be the actual access point of Outlook. If I moved the archive file, but not the actual .pst file, do you think this would work? I don't think I should be moving the .pst file from the Server.
I also checked Article #241325 (previously published under Q241325), that addresses the Exchange side of the problem. It says to create DL's to group recipients in rules instead of using individual recipients, keep the number of recipients small in rules, and keep the names of recipients as small as possible. I have no idea how to do any of these 3 things.
It also seems that all of my research results deal only with the size of the rule, although the error message states that it could be that some of the parameters are not supported. Of course, none of it makes sense to me since other computers using Outlook 2003 aren't experiencing any problem. I thought at first maybe it was because it's Outlook 2003 and Exchange 2000 may not support something, but no one else has a problem.
I have made sure that all office updates are current, I've done a detect and repair. This computer belongs to the President and owner of the company (of course!), so ANY suggestions you can give me are definitely welcome!