You can use Redemption (http://www.dimastr.com) to bypass that warning. This
also won't happen with OL 2003 if you derive all your variables from the
intrinsic Application object.

More info:

Microsoft Outlook "Object Model Guard" Security Issues for Developers:
http://www.outlookcode.com/d/sec.htm

--
Eric Legault (Outlook MVP, MCDBA, old school WOSA MCSD, B.A.)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


"dthmtlgod" wrote:

Thank you. What I did was forward the e-mail as a new mail and I am then
able to send it without a sensitivity flag. It seems to work pretty good
other than the warning about "a program is trying to access e-mail addresses
you have stored in Outlook. Do you want to allow this?"


"Eric Legault [MVP - Outlook]" wrote in
message ...
No; if it's read-only in the UI, it's usually read-only in code.

--
Eric Legault (Outlook MVP, MCDBA, old school WOSA MCSD, B.A.)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


"dthmtlgod" wrote:

I am attempting to change the sensitity of an incoming message.

Sub CustomMailMessageRule(Item As Outlook.MailItem)

If Item.Sensitivity olNormal Then
Set oNewItem = Item.Forward
With oNewItem
.To = "
.Sensitivity = olNormal
.Send
End With
Item.Delete
End If
End Sub


This works, but it won't work on a PRIVATE e-mail. Is there a way to
change
this?

Thanks