From: "Nicholas Boel" 
Subject: date time qwk
To: Leslie Given

  To: Leslie Given
Hello Leslie,

05 Dec 13 00:39, you wrote to me:

 NB>> Was this the first time you tried it? Or does the same thing
 NB>> happen every time? I'd like to see if it can be pinpointed if
 NB>> it's a lastread pointer issue or not. If it works fine the second
 NB>> time, then it's because the first time the QWK lastread pointers
 NB>> haven't been set yet,

 LG> Yeah, I see what your taking about.. good point. But, the samething
 LG> happens everytime. Like this one was also d/l and dated 01/01/2098.
 LG> unpacked the data and zipped up and remain *.qwk in order to read it
 LG> in multi-mail. The samething happens when I grab a packet on 1:275/92
 LG> mys_a37 linux box

Damn. Hopefully James makes his way back soon and can take care of that. I 
suppose it probably wasn't a found issue in the past because not many people 
actually do offline mail. There was a couple quirks about uploading a .REP 
packet in an earlier version, but I think that one was fixed. Now it seems you 






















































































































































































































































































































went a little further into it and found some more things wrong.

 LG> Right, I guess that, telneting from the linux nodespy term to d/l a
 LG> packet would be the same outcome. But, I haven't tried that yet.
 LG> *shrug* (:

Well, thanks at the very least for trying more than once to make sure it 
wasn't 
the lastread pointers. We can count that one out now. Must just be something 
in 
the code that doesn't set the time/date properly or something.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
 * Origin: Dark Sorrow | bbs.darksorrow.us (1:154/701)

--- Internet Rex 2.29
 * Origin: bbs-scene usenet news (999:1/1)