IronPort PlugIn for Outlook .enc files?

Question

We have started to roll out the IronPort plugin for Outlook for both Encryption and SPAM reporting.  On the SPAM reporting side I do see the e-mails that are getting reported but the e-mails are formatted differently.   I am guessing that the original e-mail being reported is now in the .enc attachment?  Is there any way that I can view these so that I can see what kind of e-mail is being reported by my users?  In the past I would check in on this from time to time and see if there were any mass e-mails that were getting through that I needed to create a custom filter for, now with these .enc files I'm not sure I can do that anymore.
I'll post one of the .enc files here in a bit.
Jason

Answer 1

So I can confirm that the new 7.4 Outlook plugin, feature does work to submit spam/phish/virus as plaintext. Basically you just need to set (ignore the attachment name option):
<report>
        <format>plain</format>
        <subject>Cisco Email Security Plug-in Report (${reportType})</subject>
 </report>
Also for those upgrading to 7.4, be sure to manually upgrade yourself first, and set all your configurations using the BCE_config file first. Then follow the admin document for deploying the config file mass. The 7.3 and older config files will not work with the new plugin.
This configuration is only recommended if you will be checking report submissions or using some form of Phishing education solution and want to exclude these e-mails from actual submission. Here is a good outline how I implemented it. If anyone is interested I can probably do a quick video demonstration while it's all fresh in my mind and post it here.
1. Create one or more Quarantines (either on your central SMA or individual ESA/Ironport):
    Example: Reported_TestPhish (delete after a period of time), Reported_Spam, Reported_Phish, Reported_Virus, Reported_Ham, Microsoft_Junk
2. create a Outgoing Mail filter that matches a header in your Test Emails so you can capturing them. 
    Example Match Content in Attachment: X-TEST(replace with your header) and if you use the Microsoft Report Junk Plugin, you should also use the condition to match the same text inside the mail body. Then point the action to Quarantine to your Report_TestPhish where after a period of time it will be deleted. I choose to use Quarantines rather then sending e-mails via notifications, but you could do this as well, for example if your Email Education provider can use the e-mail to track which employees reported the test e-mails for you.
3. Create individual Outgoing filters using the recipient email address to dump it into the right Quarantine. This will allow you to to not only Quarantine and view the messages, but also will add to your reporting. You can choose to use fewer Quarantines and filters to bundle together to fit your requirements.
4. Rather then adding these filters to your default policy, I suggest creating a new Outgoing Mail Policy called Report_Email (using the recipient email addresses). I then disable some of the policies such as DLP, A/V, and so on as needed and only apply the new filters we just created. 
Hope this was useful for someone out there.