I have just installed the version 6.3.0 plugin for Outlook on an XP machine with Office 2007. I can find the Add-In in the Send mail window, but it does not change the subject line or activate any other detectable changes. Anyone else trying this?
The Send Secure is there under the Add-In tab. When clicked, it appears that nothing happens - no subject modification, not sent at all. I discussed the issue with Ironport Support and they told me that the plug-in is not compatible with Office 2007. A compatible version should be available early next year.
The version from the .msi I installed is DS-6.3.0-009. Any ideas on why it is not working? I can try support again I guess, but would also be interested if you have any other information. Thank you for your assistance!
I have the Send Secure button in the Add-Ins menu. After typing up an e-mail and ready to send. Click the Send Secure button and nothing happens. Click the Send button and the e-mail goes out normally, no encryption.
Did anyone ever get a fix from IronPort on the issue where the plug-in is installed in Outlook2007 - yes, we can find it under AddIns - but there is no response when you click the button? I spent an hour on the phone with support last Friday trying to convince them there was a problem so it's like they never heard of this before, contrary to these postings.
The button works on most of my very limited 2007 installs and the only difference I can see is that the machines where the button does not work have additional Exchange entries in the registry. Needless to say, these are IS machines but I'm afraid to roll out to the enterprise until I understand the issue.
The Send Secure Plug-in for Outlook 2007 (6.3.0) doesn't work on workstations running Microsoft's Exchange System Manager (ESM) due to a conflict with a required version of mapi32.dll which is deployed as part of ESM installation.
Defect number 7307 has been filed for the issue you have encountered.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...