Your system clock is more than 15 seconds off after upgrade to build 9400.
Problem reported by Brian Bjerring-Jensen - VonBjerring GmbH - 9/28/2025 at 11:18 AM
Submitted
Now its started again... and no. its not off. Its manually synced every 5  mins.

Zach Sylvester Replied
Employee Post
Hey Brian, 

If you go to https://time.is on the server what does it say?

Kind Regards, 
Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com


This could be a clue.... And that the value needs adjusting. That 0,015 seconds is interpreted as 15 seconds by the software.

And steady as a rock :)

Zach Sylvester Replied
Employee Post
Hey Brian, 

Thank you for those details. I'm going to open a ticket for you so support can investigate this. 

Kind Regards, 
Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
Tony is on it. I dont get the message anymore. Neither did he when he logged on to the server.

So currently waiting for this to happen again.
Matt Petty Replied
Employee Post
We do the check every midnight there is a chance it maybe messed up. Unfortunately it seems there is no logging around this area. If you continue to get the error or once we get to addressing the ticket we may wanna add some logging around this area so we can see what calls may have failed.
Matt Petty Senior Software Developer SmarterTools Inc. www.smartertools.com
Web Team Replied
We have not had customers randomly logged out of webmail, ever. Suddenly the past few months, now we have this problem.

Our mail server time is EXACT. We have 5 customers reporting being logged out. SmarterTools Support wants each client to check their time settings. Even sending links to adjust registry settings on Windows 11. Yet again, never been an issue for years. 

I believe SmarterMail needs code research on their end to alleviate these timeout issues on sudden recent updates. I can't recall any other web software which has broken due to local computer time.
Richard Laliberte Replied
Web Team, we've noticed the same logout issues on our end, currently running 9294. it doesn't seem to affect everyone on our end though and it's very random. but we've experienced these issues randomly for a couple years now honestly, just seems to be popping up more lately. we've also confirmed server times and such, but given that it's random and doesn't affect everyone equality / at the same time.

We always believed there was some cookie / caching issues between SM and the chrome engine (we have uses on edge and chrome experiencing the same issues). i should get a few clients to try a non-chrome based browser for a while to see if the issue persists even on those systems.

Reply to Thread

Enter the verification text