No, you can not get around this programmatically. The security feature of Outlook is getting tighter and tighter
with each version. The .Body property is now on the list of protected properties and the .SaveAs is on
the list under protected methods.

You may want to look at re-writing it as a Trusted Outlook Add-In. This is the only way to get around it using the OOM.
This is the proper way to get around it. There are third party products that may seem to help, but they are reliant
upon Outlook not changing. So if the next version of Outlook adds more security then you need to re-write
your code again anyways