JDG

I had default antispam settings - yes. The problem seems to be rules that move messages to a folder when the message arrives - ie the rule is triggered immediately. In my case I have ***SPAM*** tagged to spam messages on the server and the Outlook rule would check for the ***SPAM*** text in the subject and move the message to the junk folder. I have discovered (I think) a workaround. Instead of having the rule move the message you can change this to copy instead of move and them add another line to the same rule to permanently delete the message. Doing things this way seems to work and the end result is the same. Hope this helps others with the same problem.

Just to update this it seems that some rules do work correctly but rules that filter on specific words in the subject matter don't. However even these rules work if run manually but rules set to run when a message arrives do not run (if based on a subject match). Problem goes away if Eset is removed. A fix for this would be good seeing as it does affect multiple users.

I never resolved this issue, ended up moving my Eset license to a PC without Outlook and installing Kaspersky instead. I'd still be interested in a resolution though as otherwise I like Eset.

I have a problem where Outlook 2013 rules do not run automatically when the Eset Smart Security 6 Outlook plugin is enabled. I can manually run rules with the plugin enabled but I have to disable it for rules to run automatically when messages are received. As an example my server tags suspect spam with a ***SPAM*** tag and I have an Outlook rule that moves messages with the tag to the junk folder. When Eset version 6 316 is installed the rules are not triggered when an email arrives. I can run the same rule manually and it works but it should run automatically when a message arrives. Win 8 64 bit with Outlook 2013 (32bit). This was reported on the Wilders forum 2 months ago but was never answered.