All the time.... constantly popping up for no reason.

Why is old resolved issues constantly coming back in new releases??

it's strange: I have 5 SmarterMail servers, all of them updated to 8818, and none of them are having these issues...

I would say that after a reboot again (3rd time) and a time to settle in, then  the time notification hasnt returned so far.

Brian - I think if I remember correctly we found your server has time resolution issues on occasion that show up in the Event Viewer, and those would definitely cause a variety of connectivity and other issues. Do you have any of those errors showing up this time around? 

No not this time. Everything is running accordingly.

Anyone noticing IMAP issues?

On our Samsung devices particularly, we keep getting notifications of new messages (that are very old). It's like it's re-syncing.

At the moment I don't have any reports

We had initial IMAP issues in outlook and my personal MAPI account needed a resync which left me with 3000+ unread emails.

Other than that I havent heard anything from clients.

@Michael: I saw this briefly after an iOS update a couple of weeks ago until I rebooted my device. Probably an odd question, but how often do you reboot your Samsung device?

For the time issues, we noticed that the windows time daemon which sync the system time is often going bozo.

It depends on what source it is using for time sync. If it's a VM it can be syncing to the virtualisation host, but it might also try to sync through the domain controller, if your smartermail server is in a windows domain.

We have seen wt32 doing time jumps back and forth.

I ended up disabling the wt32 service, disable time sync in virtualisation, and using a 3rd party utility to sync the time only with ntp servers.

We use this, an old tool but still working on windows 2019 server at least.

Emailing from webmail it's not passing the defined username.

For time issues, as Sébastien stated, the Windows time daemon is garbage, always has been, probably always will be. https://www.meinbergglobal.com/english/sw/ntp.htm we use this across all physical hosts, have not had time issues in well over a decade. I'd like to note though that we also have our own local GPS-sync'd time server, but use (with permission) the NIST time servers as a backup source.

We run this every 3 hours to make sure that everything is aligned.

@echo off
w32tm /query /peers
sc config w32time start= auto
w32tm /config /syncfromflags:manual /manualpeerlist:"time.nist.gov, 0.dk.pool.ntp.org, 1.dk.pool.ntp.org, 2.dk.pool.ntp.org, 3.dk.pool.ntp.org"
w32tm /config /reliable:yes
net stop w32time
net start w32time
w32tm /resync /nowait

Works on all servers and workstations.