We suspect this is known issue starting from already nonexistent ver 2051. We experienced this nightmare at the very beginning of July. According to some opinions of other users in v 2057 this problem has not been solved (we do not decided to run antispasmodic option unless is finally fixed). Your post looks to confirm that eset is still working on a solution
Up to ver 2046 anti spam was working properly. Maybe Marcos will give us any updated info https://forum.eset.com/topic/33024-outlook-and-eset-outlook-add-in-sync-issuesconflicts/#comment-153420