ESET & Outlook Programmatic Access Security

Is it normal for Outlook (2007) not to able to detect NOD32 v5 with regard to Programmatic Access...?

Action Center reports NOD32 installed just fine.

I'm having some problems with a certain 3rd party app accessing Outlook data, a pop-up keeps popping up every time the plug-in is used.

Cheers.

Reference: http://office.microsoft.com/en-us/o...-sending-e-mail-on-my-behalf-HA001229943.aspx

 

Re-installing NOD32 didn't help. But I’m onto something else…

If Outlook is started a few minutes after the system finished booting (after the Startup Scan?), the status will become “valid”.

However, if Outlook is started at boot, and as long as it’s running, the status will remain “invalid”.

It’s possible to restart Outlook after a few minutes and the status will also become “valid”.

Any idea...?

BTW, I found that the ESET certificate under Outlook’s Trust Center is an expired one. Not sure if it’s related or not.

 

OK... I'm a monkey... : )

Maybe it's not related to NOD32 afterall. Cause I tried Microsoft Security Essentials and AVAST Free (separately, after NOD32 was uninstalled), and they had the same problem.

The only scenario that made a difference was when there's no antivirus solution installed at all. In that case, the status remains "invalid" indefinitely...

If anybody has any idea, please do let me know...

Still have no idea about that ESET certificate though. Even when NOD32 was uninstalled it remained there.

Cheers.