-={ Friday, 16 October 2015, 11:24:25 -0400 }=-

Hey Janis!

 JK> Friday16October201500:33:09-0400

Not sure what app you used to produce the above with the missing whitespaces
but it does look right, especially the %z part which is the specifier for utc
offset, -0400 in your case.  Note that it is the same in this reply between the
-={ and }=- characters at the top of this reply with the whitespaces retained. 
Also note that when compared to the obsolete FTN datetime stamp in the msg
header - "%d %b %y  %T" - you should readily see is in UTC which all
obsolete/abandonware/corrupted apps *should* stick to given their obvious
handicap.

From this angle BBBS looks to be doong datetime stamps incorrectly and probably
is also using the corrupted FTN TZUTC kludge ala golded and the such.

For the record my timezone on ALL machines here is UTC by default but just to
play it safe in WeBeBashing I have TZ=UTC to produce the FTN datetime stamp in
the msg header and as you say;

 JK> and it's just right 

Yes indeed.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.42(1)-release (x86_64-unknown-linux-gnu)