On Fri, 04 Oct 2013, Ed Vance wrote to Holger Granholm:

 HG> Yeah, I saw it. My only comment to that is that the time of day 
 HG> doesn't reflect when the message was written but the time it was 
 HG> uploaded to the BBS.

 EV> I dkdn't know that. I thought the Time shown in the messages I 
 EV> read were when they were written.

generally they are but offline stuff may not have the time written but the
time and date uploaded to the bbs... this depends on the software used on
the bbs... the time stamp will generally be the bbs' local time if it is
overridden when the messages are imported at upload time... i note that
your message carried a control line indicating -0400 from UTC which would
be east coast USA timezone for a few more weeks until daylight saving
switches again... then that control line should switch to -0500...

 EV> It is 9:58AM as I am writing this message.
 EV> After I upload the .REP packet to Capcity BBS I will Log On to see
 EV> what Time my messages have in them.


here's the info of your message as it appears on my system...

  Message info:

  Date written : Fri Oct 04 '13, 11:02:00
  Date arrived : Sat Oct 05 '13, 08:02:58
  Date received: -
  Message size : 3455 (body: 3318  controlinfo: 137)
  Files        : None
  Message UID  : 45240

  Area info:

  Desc : Windows95
  Tag  : win95
  Type : Echomail
  Attr : loc
  Path : X:\MSGS\JAM\FIDO04\WIN95
  Base : JAM
  AKA  : 1:3634/12.0
  Chars: IBMPC (write), IBMPC (read)


from the above, you can see that it is stamped 11:02AM friday morning and
it arrived on my system at 8:02AM this saturday morning...

i'm kinda wondering about the connectivity of the systems between us and
what caused such a long delay... even if it was an 11PM upload, we're
looking at roughly 9 hours and that's a long time with today's
always-connected pipes... this is even longer...

)\/(ark