Ok at the risk of having to flame again, I'll offer a forward looking view.
Yes, 32k is the current limit. No, we don't want MS to invest in changing that code. What do we want? The rules engine should be more than just a message routing PEP (policy enforcement point). It should also be the interface for all communications user controlled flow control, or policies. As we install a variety of extensions to Exchange, it becomes threaded into the overall communications environment. There are two components of some concern: the MCU and the voice server. The MCU provides real time streaming session aggregation for multi-party calls, whether they are voice, data, video or some combination of two or all three. The Exchange product MCU is the Conference Server, but in a VoIP world, you do not want two or more MCU systems. The voice conferencing bridge function of your VoIP telephone system and the data conferencing system (T-120 style data sharing) should be one system, not two. This is important, because it is unlikely that IP telephone planning and messaging system planning are being done by the same people in the typical enterprise. This will lead to a show down and a lot of rework at some point. But, the interfaces to the rules engine (Outlook, OWA, and voice/DMTF) should be able to exercise any controls on the conference server (auto-accept is a good example). The voice server (sometimes called a UM/UC server) introduces additional message flow controls and the opportunity to control rules via a dial-up interface. When serving as the voice mail interface to a VoIP system, it provides several rules type of functions such as extended absence. But, it can also provide a front-end to the switch controls, such as auto-forward and ring-now answer instructions. In this more rich world of rules, you don't want the rules cache to be in either the message server or the voice server. You want them to be in a cache that is an accessory to the switch. Think about this. Right now, in a telephone system you set an out of office rule in the voice server, but it does not get processed until after a ring-no answer auto forward series of steps has been accomplished and the message server gets a chance to process the call. This is exactly backward. Rules should be processed before the switch attempts to disposition the connection request. What we want Microsoft to do is to redesign the rules in Exchange to be DEN/CIM objects, and to make storage requests for each rule based on the system component that is going to provide the PEP service for that particular rule. Then we want all of the servers to hand off their user interfaces for the aggregated rules engines to Exchange Server, and for the server to present this to all possible user interfaces (MAPI, web pump, DTMF, etc.). Yes of course we need more than 32k of rules storage, but not for the current system It must be for a fully DEN/CIM aware rules engine. Now that would be worth investing some Exchange team development time in producing. The rest would just be noise and more of yesterday's "less than WinRules capable junk." -----Original Message----- From: missy koslosky [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 2:12 PM To: Exchange Discussions Subject: Re: Exchange 5.5 rules 32KB of rules is the absolute limit. I'd suggest that you send a message to [EMAIL PROTECTED] if you would like this changed. Missy Koslosky ----- Original Message ----- From: "Ed Esgro" <[EMAIL PROTECTED]> To: "Exchange Discussions" <[EMAIL PROTECTED]> Sent: Wednesday, February 06, 2002 4:31 PM Subject: Exchange 5.5 rules Does anybody know what the limitations are to the amount of rules one can have for a mailbox. I have a user that gets an error message when creating a rule. After disabling another rule, the new rule will work. It appears to me that there is a limitation to the amount of rules one mailbox can have. Am I correct? If so what is the limit? Thanks All. Ed _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
