Then most probably you do not have the right time on your Server machine.
Well, it might not even be your FM server, it could be the email server machine. If you're sending emails, the server with the SMTP service or Exchange server is the one doing the timestamp.
No the time on the server is correct.
Found that it has been a known issue during daylight savings time since FM Server 13....hoping that there is some work around
1 of 1 people found this helpful
If you do a Get ( CurrentHostTimestamp ), what does it give you?
By the way, FM just uses the OS's time... so its not a FM problem, it would be an OS problem.
All the times in the e-mail headers are correct. Only the "Created at" time is incorrect which is provided be the application.
Which ends up looking like this
Fri, Jul 14, 2017 at 12:01 PM (Delivered after -3572 seconds)
with the negative delivery time
To echo what Taylor said . . .could be the time on the exchange server. Once it leaves FM the SMTP server does stuff to it and on it's way it goes . . .
Is your server located in a timezone that is one hour in the future from your computer? If so, there's your problem.
There are two timestamps in FMP: local computer and host computer.
Typicaly the host computer is one or more hours away from the local computer.
get(currenttimestamp) and get(currenthosttimestamp) can be different times.
I try to use get(currenthosttimestamp) when I want a consistent time reference since logins can be in time zones anywhere in the universe.
The computer should be setting its time using an atomic clock on the Internet but there could be a daylight savings time problem due to human error in preferences.