Comment 6/15/2019 3:42 PM

Hey,

On wildcat! bbs I though I could set a read messages that are only 7
days old. Is that possible? Thanks

-Lucas

Lucas Heuman wrote:

From headers:

Organization: Prison Board BBS

Might need to contact whomever is the sysadmin at your prison.

On wildcat! bbs I though I could set a read messages that are only 7
days old. Is that possible? Thanks

That is a function of your client program which neither you nor your
post's headers have identified.

Wildcat BBS, renamed to WINServer, is the server program that got sold
to Santronics back in 1998.

http://www.santronics.com/index.php

From your post, you are unlikely the admin for that server host or its
software.

On Sat, 15 Jun 2019 15:42:56 -0500, (Lucas
Heuman) wrote:

Hey,

On wildcat! bbs I though I could set a read messages that are only 7
days old. Is that possible? Thanks

6/15/2019 is an invalid date.


-Lucas

Lucifer wrote:

On Sat, 15 Jun 2019 15:42:56 -0500, (Lucas
Heuman) wrote:

On wildcat! bbs I though I could set a read messages that are only 7
days old. Is that possible? Thanks

6/15/2019 is an invalid date.

Okay, I'll risk a retort. Why is June 15, 2019 (in mm/dd/yyyy format),
3 days ago from this reply, an invalid date? Don't know why the OP put
the datestamp in his Subject header as clients will show the value of
the Date header (and compensate for the timezone offset to show the post
in the client user's own timezone).

From the OP's headers:

Date: Sat, 15 Jun 2019 15:42:56 -0500

In UTC format (not used by the OP's unidentified client), that would be:

Date: Sat, 15 Jun 2019 20:42:56 -0000 UTC

My guess is the OP is geolocated in the CDT timezone (daylight savings
for the CST timezone) in the USA hence the -0500 timezone offset. So,
the "3:42 PM" string in the Subject appears to match on the poster's
time, and I don't see why the date is invalid. mm/dd/yyyy is the date
format most commonly used in the USA. dd/mm/yyyy seems to be more
common in European countries. Of course, neither present a format that
by itself will sort well, so a date format of yyyy/mm/dd is better
suited for sorting. However, in Usenet or for any Internet messages as
per RFC, the date is not used for sorting messages into hierarchical
order. The References header (created by the client) is used for that.

From your headers:

Date: Tue, 18 Jun 2019 15:14:52 +1000

So, your timezone offset of +10 hours means you are posting from
somewhere in the Whiskey (W) timezone. See:

https://en.wikipedia.org/wiki/UTC%2B10:00
https://upload.wikimedia.org/wikiped..._Zones_Map.png

Because of the various timezone offsets used in the Date header, I
usually convert them to UTC to then compare timestamps. The OP is 5
hours after UTC. You are 10 hours before UTC.

In article , Lucifer
wrote:

On Sat, 15 Jun 2019 15:42:56 -0500, (Lucas
Heuman) wrote:

Hey,

On wildcat! bbs I though I could set a read messages that are only 7
days old. Is that possible? Thanks

6/15/2019 is an invalid date.

not only is it a valid date, but the formatting is done at *your* end,
which means it's up to *you* to change it.