Hello mark,

On 04 Dec 12 at 11:24, you wrote to me:

 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?

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

 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...

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

 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...

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

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

Regards,
Nick

--- SBBSecho 2.20-Linux