mark lewis wrote in a message to Ramon van der Winkel:

 ml> ok, tell me what you'd do with this message... this is a FTN
 ml> message being forwarded in a FTN network...

 ml> Sat  3 Aug 96 20:48

WaterGate detects this and says "shit, Seadog style date", then
removes the "Sat " part and inserts an extra space between the
date and time and adds seconds, resulting in:

" 3 Aug 96  20:48:00"

And since a few minutes (after checking fts-0001) it will make sure the day
is 0-filled, and thus results in:

"03 Aug 96  20:48:00"

 ml> i'll tell you exactly what the problem is... it is a screwed
 ml> up implementation of forwarding code WRT opus/seadog date
 ml> formats. in forwarded messages, the date format should be
 ml> the same as it was when the message left the originating
 ml> system, correct?

Eh, yes. But, the date _is_ the same. I just formatted it a bit different ;)

 ml>  yes, i understand and recognise the need to convert the dates 
 ml> when importing to the message base but this should NOT (imo) be 
 ml> done on forwarded messages.

This is what I do: I do the date checking and conversion when I read the
messag from a .PKT file. I store the corrected format and this reduces the
requirements on the rest of the code. If I happen to write the message out
again, then I use the corrected format. This will be the same format in 99%
of the cases and a corrected format in the rest of the cases.

Ramon

--- WtrGate+ 0.92.p3-d gamma sn 1