No specific permissions are required for users to create rules and there exists no method to limit this type of rule. This may cause issues in environments that want to control where their data is stored and how it is transmitted. This obviates the need for administrators to be involved in the day-to-day management of these rules.Ĭlient-side rules though are not immediately obvious to administrators. From an administrative standpoint client-side rules can also be helpful since they can be managed by the user. The rules wizard allows this level of granularity. For example, say you want to forward emails to another internal or external recipient based on who sent the messages. In the example below, a rule has been created that forwards all messages received in the mailbox to an external recipient.Ĭlient-side rules allow a great deal of flexibility when establishing forwarding. One of the options is a rule to forward messages to a different recipient, which can be an internal or external recipient. Users can create Inbox rules in both Outlook and Outlook Web App (OWA). In this post, I’m going to review each of these methods, the pros and cons, and the administrator controls in place for these options.įorwarding rule within Outlook and Outlook Web App: An administrator can set the ForwardingAddress parameter on a mailbox.An administrator can set the ForwardingSMTPAddress parameter on a mailbox.An administrator can create a client rule for forwarding.Users can create a forwarding rule within Outlook or Outlook Web App.Each of these methods has both pros and cons when implemented: The forwarding options available to clients and administrators are described below. Administrators can also control how forwarding is handled within the organization. Some of these options exist for users and others are for administrators. Exchange Server and Office 365 offer many different options for forwarding messages to different recipients.
0 kommentar(er)
