INTERNALDATE one hour in future for sent message

[Phil Pennock]

On 2006-06-28 at 16:43 -0400, Jim Brett wrote:
> Thanks, your response is greatly appreciated.  Here's OS info:
> 
> # uname -a
> SunOS machine.company.com 5.8 Generic_117350-13 sun4u sparc 
> SUNW,Sun-Fire-V240

Edit /etc/TIMEZONE, zone information available in
/usr/share/lib/zoneinfo/

$ man -s 4 timezone

You may also want to look at /etc/defaults/cron, if you want to make
cronjobs stick to GMT or somesuch.

You'll probably need a reboot somewhere in there, and to make sure that
you adjust the system clock to compensate for adjusting the zone
information.


A lot of time issues just go away if you keep system clocks
automatically synchronised.  ntpd helps here, which on Solaris 9 (don't
know about 8, sorry) is in: SUNWntpr SUNWntpu
(NTP = Network Time Protocol)

That's the terse version, but should provide enough pointers for going
on with.  I'm only assuming that you're not already using NTP, but I
suspect that it would've been difficult to keep a system clock outside
GMT whilst using ntpd.

Social benefit to using GMT with mail-servers, even outside the UK (full
disclosure: I'm expat British, so perhaps biased) is that when it comes
to reporting abuse and providing logs to correlate events, it's *really*
useful to have a common timezone standard which everyone needs to be
able to map to their local time easily, without needing to learn
acronyms.  Even better is when you can say, "Log timestamps are in GMT
with time synchronised via NTP to high stratum, so we believe them to be
accurate."
-- 
"Everything has three factors: politics, money, and the right way to do it.
 In that order."  -- Gary Donahue