Tag Info

New answers tagged

0

An alternate answer and perspective, hopefully much simpler: Using sensitivity headers + IRM. Read on... Outlook/Exchange already supports "sensitivity" properties of an email, but they are advisory only until you enable IRM. In other words, I can send you an email and set it as sensitivity=Private, but when you view the email, you simply see an info tip ...


1

You could use one of two methods, both require some input/work from the end user and the IT staff. Option 1: Use Outlook Rules and apply a rule that states that when an email is received from HR to not forward it (whether by OOF or some other means). The problem here, is that you have to leave Outlook running on the users computer for the rule to function ...


1

I haven't done this, but it seems like you could probably do this in Exchange 2010/2013 using Information Rights Management (IRM). If you've ever seen Outlook messages marked as "Do not forward", this is what I'm talking about. You can configure it in Exchange Management Console from the Hub Transport server or via the New-OutlookProtectionRule cmdlet. ...



Top 50 recent answers are included