FortiClient damages S/MIME Certificate

[FlashOver]

we have the latest FortiClient installed on our Win7 computers, with disabled everything except VPN we use for IPSec. Since two days, when we receive a digital signed email using S/MIME, the certificate get' s touched and is not valid anymore. When we disable the FortiClient, it' s working fine again. We tried is with active and inactive AntiSpam Feature with the same result. Because we can not install the VPN part alone (hopefully that will be proved in future releases) this is a problem for us. Problem occurred when receiving a signed mail with Outlook 2013 with a GlobalSign and Comodo certificate. A PKI expert analyses the certificate and told us, that the FortiClient check may open the cert file and repacks it and therefore it' s not valid anymore... If we can not find a quick solution, we have to deinstall it on our user basis and switch to L2TP/IPSec with native operating system connectivity - without FortiToken... Hope somebody can help.

[Chris_Lin_FTNT]

A couple questions: 1. How did you disable features? Was it by XML config <enabled>0</enabled> for each of them? Better yet, you can run diagnostic tool and send result to forticlient-feedback@fortinet.com. 2. Can you explain in details how you create and verify your e-mail? Because it seems to have couple different ways to sign e-mails.

[Chris_Lin_FTNT]

More specific config you could try: <forticlient_configuration> <antivirus> <email> <smtp>0</smtp> <pop3>0</pop3> <outlook>0</outlook> </email> </antivirus> </forticlient_configuration>