We were on the latest version for a week before the notifications started appearing.
We're also in perfect sync.
They've been becoming more frequent.
As our server load increased with adding a couple domains, that's when they started. The notice appears randomly. Like something in SM's check is affected by delay in CPU load in a return function or something along those lines.
We're not a large installation -- so far, 180 users (of which 130 are actual users, the rest are domain admin accounts that will never be used) across 50 domains - and the notifications didn't start appearing until about 2 days ago after the server was rebooted from the latest MS updates. We don't think it's the updates. The reboot flushed something out in SM and when it re-loaded that's when they started.
We will be making some changes and rebooting tonight - will report back.
It does appear that ANY resolution you attempt to implement requires a full server reboot in order to see if the changes/fix is picked up by SmarterMail -- a service restart and IIS restart does not cover it.
MailEnable survivor / convert --