NB>> Date : Sun Dec 02, 20:20
 NB>> From : Nicholas Boel                              1:154/10
 NB>> To   : mark lewis
 NB>> Subj : Hrm.
 NB>> ŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽŽ
 NB>> {at}TZUTC: 0000
 NB>> {at}MSGID: 1:154/10 50bc0d8b
 NB>> {at}REPLY: 1:3634/12.42 0bb9fa50
 NB>> {at}PID: GED+LNX 1.1.5-b20120229
 NB>> {at}TID: SBBSecho 2.20-Linux r1.216 Nov 22 2012 GCC 4.5.4
 NB>> {at}CHRS: LATIN-1 2

 ml> ok... above is your header and control lines... taking the timestamp
 ml> with the TZUTC, it says that you wrote your message at 20:20UTC...
 ml> that would be
 ml> 14:20CST or 2PM...

 ml> is that when you wrote your message?

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

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

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

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

)\/(ark

---