Why are some rules client-only?

Topic

New Reply

I just created a filter in Outlook 2000 to permanently delete any incoming mail with “Mawanella” in the subject line (some people just don’t learn), but Outlook tells me this is a client-only rule.

My question is, why is it a client-only rule? And what is it, in general, that forces a rule to be client-only?

Sadly, Outlook’s help doesn’t answer this question.

Thanks in advance,

Paulius

Reply | Quote

Replies

client side rules are ones only the client is capable of processing. i’m not exactly sure why, except the capability to process them was not built into the server.

when mail hits your inbox on the server it just sits there, exchange can’t do a lot with it. exchange is capable of replying to it, so server rules work there. it can also move it to a new folder, at least if it’s based on an address. It can flag based on addresses too, but it can’t fire my exception list or delete. those rules fire when i first open outlook and they are processed. the only real problem is if you are using OWA or other method of access too – they won’t be processed until outlook gets them.

if you aren’t using exchange server, then all rules are client side, since outlook can’t “talk” with pop servers correctly.

Reply | Quote

The reason why is quite simple. A rule is designated client-only when something has to be processed by the client instead of the server. For example, moving a message to a “Personal Folders” (PST) file.

From Microsoft’s KB:
Rules either run on the server or the client. Rules that run on the server are in effect even when you are not running Outlook (the client). Rules marked in the Rules Wizard as “(client-only)” may only work when you are running Outlook. If a rule requires access to your personal folders, it is a client-only rule, since your personal folders (.pst) file is located on your client computer. Rules that present you with a message are also client-side rules. If the rule only depends on mailbox folders, located on the server, then it is a server-side rule and can run as long as the mail server is running.

HTH

Reply | Quote

But that doesn’t say where the determination is made that a rule is client or server.

rules are funky in that ones that you think should be server end up client, even on an exchange mailbox. (which is the only way to have server rules)

it’s partly becaue many rule actions were added later – the original inbox assistant handled only a few tasks and everything was server side. the server was not updated to handle all the rules features users want, but rules wiz was added to meet the users needs.

Reply | Quote

Thanks for the tips.

I guess “client-sidedness” is not easily predicted, but I think I’ve got a better idea of what to expect now.

Thanks again,

Paulius

Reply | Quote