• May see some *errors*....

    From Ozz Nixon@1:275/362 to All on Wednesday, March 20, 2019 20:31:24
    I am going to start Alpha testing my NNTP server (to drop JAMNNTPd)... its from
    scratch, so it may have a few bugs... I do appologize in advance!

    O.

    PS. I am open to in internal header/footer bug reports that I may miss.

    PSPS. Also with the topic of TZUTC, if my engine auto calculates UTC as timestamp, is TZUTC: Z valid or just 0000? (And any reason I should not adjust from local to UTC?)

    --
    .. Ozz Nixon
    ... Author ExchangeBBS (suite)
    .... Since 1983 BBS Developer

    --- FMail-W32 2.0.1.4
    * Origin: ExchangeBBS WHQ (1:275/362.0)
  • From mark lewis@1:3634/12.73 to Ozz Nixon on Friday, March 22, 2019 08:03:00
    On 2019 Mar 20 22:31:24, you wrote to All:

    PSPS. Also with the topic of TZUTC, if my engine auto calculates UTC as timestamp, is TZUTC: Z valid or just 0000?

    only four digits with maybe leading "+" or "-"...

    http://ftsc.org/docs/fts-4008.002

    ----- snip -----
    4. Control paragraph specification
    -----------------------------

    Messages which conform to this specification must add the following
    control paragraph:

    ^aTZUTC: <current offset from UTC>

    Where ^a is ASCII 1, 01h.

    The offset has the format <[-]hhmm>, where hhmm is the number of
    hours and minutes, zero-padded to two digits each, that local time
    is offset from UTC. If local time is WEST of UTC, then the offset
    is NEGATIVE. See the table below for typical offsets.

    Note that the hh in a time zone offset is not limited to a maximum
    of 12. This is because the International Date Line does not run
    exactly along the boundary between zone -1200 and +1200. The
    minutes part is 00 for most time zones.

    All four digits must be present. If the offset is negative, there
    must be a minus ('-', ASCII 45, 2Dh) in front of the offset.

    Implementations must NOT put a plus ('+', ASCII 43, 2Bh) in front of
    the offset for positive numbers, but robust implementations should
    be prepared to find (and ignore) a plus if it exists.

    If local time changes as a result of, for example, daylight savings
    time, then the offset in the TZUTC control paragraph should change
    to reflect this.
    ----- snip -----

    (And any reason I should not adjust from local to UTC?)

    you can set any time as long as the TZUTC is correct to reflect the actual local time of the post... i think i said that right...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... RTFM: Read The Fine Manual.
    ---
    * Origin: (1:3634/12.73)
  • From Ozz Nixon@1:275/362 to mark lewis on Friday, March 22, 2019 13:46:20
    On 2019-03-22 14:03:00 +0000, mark lewis -> Ozz Nixon said:

    On 2019 Mar 20 22:31:24, you wrote to All:

    ON> PSPS. Also with the topic of TZUTC, if my engine auto calculates UTC as
    ON> timestamp, is TZUTC: Z valid or just 0000?

    only four digits with maybe leading "+" or "-"...

    http://ftsc.org/docs/fts-4008.002

    Thank you, I was hoping *you* would respond. I am letting FSC and FTS documents
    criss-cross in my mind...

    --
    .. Ozz Nixon
    ... Author ExchangeBBS (suite)
    .... Since 1983 BBS Developer

    --- FMail-W32 2.0.1.4
    * Origin: ExchangeBBS WHQ (1:275/362.0)
  • From Ozz Nixon@1:275/362 to Ozz Nixon on Friday, March 22, 2019 15:48:50
    On 2019-03-21 03:31:24 +0000, Ozz Nixon -> All said:

    Anything look wrong for an NNTP header from a message I have in my ASIAN_LINK (my nntpd):

    Path: ExchangeBBS!NNTPD!not-for-mail
    Newsgroup: ASIAN_CHAT
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit
    X-JAM-MSGID: 1:275/362.0 5c5ba34a
    Message-ID: <1$ASIAN@ExchangeBBS.com>
    X-JAM-From: Ozz Nixon
    From: Ozz Nixon
    X-JAM-To: All
    X-Comment-To: All
    Subject: Testing Again
    X-JAM-Orig: 1:275/362.0
    X-JAM-FTSCKludge: REPLYADDR ozznixon@gmail.com
    X-JAM-PID: JamNNTPd/Win32 1.2.3
    X-JAM-FTSCKludge: TZUTC: -0600

    Ozz

    * I am just a couple hours shy from switching to ExchangeBBS NNTPd for all my messages...

    --
    .. Ozz Nixon
    ... Author ExchangeBBS (suite)
    .... Since 1983 BBS Developer

    --- FMail-W32 2.0.1.4
    * Origin: ExchangeBBS WHQ (1:275/362.0)