NB>> Just went back to that message, and yes, that's exactly when it
 NB>> was posted. 29 seconds into 2:20pm even. :)

 ml> hummm... ok so you have golded configured to NOT put in the TZUTC
 ml> because sbbsecho forces its one in (and at the top of the control
 ml> lines), right?

 NB> Correct. The -0600 kludge that was added before (that I removed)
 NB> was from Golded.

ok...

 ml> if yes, then the one above is sbbsecho's and the timestamp is
 ml> evidently also adjusted to UTC in the packed and shipped messages...
 ml> interesting... no wonder golded's was wrong with sbbesecho making
 ml> these changes instead of exporting as written...

 NB> I don't think Synchronet touched anything of Golded's. That's why
 NB> there were two TZUTC kludges at one point. I disabled Golded's and
 NB> now we're left with one. 

right and this one is correct because the time in the message is either
also converted when exported or your software is converting it for
display... i suspect it is being converted on export if golded is showing
you that it was written at 14:20 since it was wanting to put in the -0600
TZUTC entry...

 ml> on the one hand, i can understand that... set everything to and export
 ml> as UTC to prevent ambiguity... it is a different method than what
 ml> other systems use... they do not convert anything when scanning out
 ml> and packing mail for transmission to other systems... they leave
 ml> everything as it is expecting that the software that created the
 ml> messages knows what it is doing...

 NB> You know how Rob and Stephen like to do things their way. I don't
 NB> think they care much for keeping other software happy. :)

hahaha... well... it is just another way of doing things... traditionally,
though, software simply used the local clock for everything with no
conversions at all... TZUTC was created so as to allow software to more
accurately depict when a message was written since the message header
doesn't allow for the timezone...

 NB> SO, what you're getting at here is, my TZUTC 0000 kludge is
 NB> actually right when comparing to the exact time my message was
 NB> posted?

yes... because the time has been converted to UTC time and not local time
;) golded appears to work the other way around in the traditional fashion
so if you were able to turn off sbbsecho's TZUTC and it still converted the
time to UTC, then the TZUTC control line would be wrong... this applies not
only to golded but to any other 3rd party software that you may use with
your bbs setup... especially if sbbsecho is the only tosser and always
converts the message header time to UTC...

)\/(ark

---