Its not the log timezone Im talking about.. However I may be mistaken in
my details.
For some reason I thought we were already in regular not day light
savings. Actually we are still in DLS time, so exims GMT of -7 is correct.
We'll see what happens we the system turn to GMT -8, but after looking
around somemore I found a reference to setting
timezone =
in the exim config file, which would make it use system time. I don't
know for sure if this will work, but I won't know until Oct 30th..
My current problem seems to be a product of my webmail system not
supporting Daylight Savings Time.
Thanks.
Joe
Adam Funk wrote:
>>Recently I noticed my time stamps(in exim received headers) are off
>>by 1 hour. I believe this is due to day light savings? It's my
>>understanding that exim uses the time zone of the system at build
>>time. Which would be correct, but when daylight savings adjusted
>>the system time, exim doesn't??
>>
>>So once we fell forward my exim received headers have been off my 1
>>hour.
>>
>>
>
>http://www.exim.org/exim-html-4.50/doc/html/spec_14.html#IX1255
>
>--> By default, the timestamps on log lines are in local time
>--> without the timezone. This means that if your timezone
>--> changes twice a year, the timestamps in log lines are
>--> ambiguous for an hour when the clocks go back. One way of
>--> avoiding this problem is to set the timezone to UTC. An
>--> alternative is to set log_timezone true. This turns on the
>--> addition of the timezone offset to timestamps in log lines.
>--> Turning on this option can add quite a lot to the size of
>--> log files because each line is extended by 6 characters.
>
>Basically, just add the line
>
>log_timezone
>
>to the general part of your config file and you'll get this
>
>2005-10-03 14:19:14 +0100 End queue run: pid=17826
>
>instead of this
>
>2005-10-03 14:19:14 End queue run: pid=17826
>
>in the log file.
>
>
>
>
