Outlook restricted permission warning

[Robert A]

Several users receive this message when previewing a message.

"This message with restricted permission cannot be viewed in the reading
pane until you verify your credentials. Open the item to read its contents
and verify your credentials."

If you double-click to open the message, nothing happens.

There is no IRM installed in this corporate environment.

There is no Google Desktop installed [this was mentioned in another web site].

Client software:
Outlook 2003, Sp3

Exchange software:
Exchange 2003

 

[VanguardLH]

Several users receive this message when previewing a message.

"This message with restricted permission cannot be viewed in the reading
pane until you verify your credentials. Open the item to read its contents
and verify your credentials."

If you double-click to open the message, nothing happens.

There is no IRM installed in this corporate environment.

There is no Google Desktop installed [this was mentioned in another web site].

Client software:
Outlook 2003, Sp3

Exchange software:
Exchange 2003

My guess is those users installed an e-mail certificate so they could
digital sign or encrypt e-mails. With the cert, they can digital sign
their outbound e-mails. With the cert, they can dole out its public key
(by the digital signature on an outbound e-mail) for someone else to use
when encrypting their e-mail sent to this user (who then uses their
private key to decrypt the e-mail). If the user did a fresh install or
deleted their e-mail cert then they no longer have it to decrypt those
inbound e-mails that were encrypted using the old cert's private key.

My other guess is that you are having network outages for those users.
They lose connectivity and the connection times out to the Exchange
server, they regain connectivity later whereupon the user clicks on an
item but has to reestablish a connection to the server. See:

http://support.microsoft.com/kb/910346
http://support.microsoft.com/kb/820281

 

[Robert A]

I have asked the recipients to try these steps and they will respond to me.

I will post the results when I have received them.

 

[Robert A]

Hello,

This problem still exists. The person started Outlook in Safe Mode
(outlook /safe) to eliminate interference from any add-ins.

The problem seems to occur when the e-mail message crosses from one Exchange
ORG to a different Exchange ORG (within our same corporation).

A similar problem is noted by someone on the Microsoft Outlook Team blog
site. (URL:
http://blogs.msdn.com/outlook/archive/2008/06/17/irm-in-outlook-2007.aspx )


I have just started a tech support case with Microsoft but we have not begun
the troubleshooting process yet. [REG:109071365597044]

 

[Robert A]

fyi:

In the Exchange forum, James-Luo (MSFT, Moderator) says:


There’s a bug for what appears to be a regression probably restricted to
either 6.5.7653.28 or 6.5.7653.29 of the Store.exe, which can cause same
symptom

And the symptom is:

When attempting to view affected email in Outlook 2003, users see the
following message in the viewing pane: “This message with restricted
permission cannot be viewed in the reading pane until you verify your
credentials. Open the item to read its contents and verify your credentialsâ€.
Users are also unable to open the message by double clicking. They also
receive this error (slightly differently worded) when using outlook 2007
clients and OWA

Also there are 1083 or 1084 events indicating corruption in compressed RTF

That’s why I would like you to try MS08-039, which has eliminated such
behavior with store build 6.5.7653.38
<<<

Hello,

This problem still exists. The person started Outlook in Safe Mode
(outlook /safe) to eliminate interference from any add-ins.

The problem seems to occur when the e-mail message crosses from one Exchange
ORG to a different Exchange ORG (within our same corporation).

A similar problem is noted by someone on the Microsoft Outlook Team blog
site. (URL:
http://blogs.msdn.com/outlook/archive/2008/06/17/irm-in-outlook-2007.aspx )


I have just started a tech support case with Microsoft but we have not begun
the troubleshooting process yet. [REG:109071365597044]