1. Forum
  2. FSXNet
  3. FSX_TST

  • Re: Testing

    From Zip@21:1/202 to slacker on Saturday, July 25, 2026 09:22:53
    Hello slacker!

    On 24 Jul 2026, slacker said the following...

    Testing to see if/when this message may go out.



    --- NE BBS v2.02 (linux; x64)
    * Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

    Got you here!

    Best regards
    Zip

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From slacker@21:3/193 to All on Friday, July 24, 2026 21:05:59
    Testing to see if/when this message may go out.



    --- NE BBS v2.02 (linux; x64)
    * Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)
  • From Sean Rima@21:1/229 to slacker on Saturday, July 25, 2026 12:24:04
    slacker wrote to All <=-

    Testing to see if/when this message may go out.

    Got to Ireland so no didn't go out :)

    Sean

    ... TCOB1: binkd.rima.ie or bbbs.rima-iot.eu

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1 https://binkd.rima.ie (21:1/229)
  • From Bucko@21:4/131.1 to All on Saturday, July 25, 2026 08:15:03
    Got to NY too!


    --- EXCELSIOR! 1.23; XMAIL! 1.92
    * Origin: The Wrong Number Family Of BBS' - Bucko's Den (21:4/131.1)
  • From slacker@21:3/193 to Zip on Saturday, July 25, 2026 23:02:33
    Got you here!

    Thanks for the confirmation!


    --- NE BBS v2.02 (linux; x64)
    * Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)
  • From J0hnny A1pha@21:4/158.1 to All on Wednesday, September 09, 2026 03:41:04
    Testing the new setup... This going out?
    --- ViSiON/3 v0.8.2/Linux
    * Origin: Broken Bit Syndicate - ViSiON/3 HQ (21:4/158.1)
  • From Zip@21:1/202 to J0hnny A1pha on Wednesday, September 09, 2026 21:00:38
    Hello J0hnny!

    On 09 Sep 2026, J0hnny A1pha said the following...

    Testing the new setup... This going out?
    --- ViSiON/3 v0.8.2/Linux
    * Origin: Broken Bit Syndicate - ViSiON/3 HQ (21:4/158.1)

    Yep! Got you here!

    Best regards
    Zip

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Accession@21:1/200 to J0hnny A1pha on Wednesday, September 09, 2026 18:20:56
    Hey J0hnny!

    On Wed, Sep 09 2026 03:41:04, you wrote:

    @AREA:FSX_TST

    Should this kludge have a space in it? Seems to have changed in the clrghouz automated reply, like it was parsed wrong, is why I ask.

    Regards,
    Accession

    ... Take my advice, I don't use it anyway.
    --- AmberEdit/linux 0.8.1
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From deon@21:2/116 to Accession on Thursday, September 10, 2026 13:51:59
    Re: Testing
    By: Accession to J0hnny A1pha on Wed Sep 09 2026 06:20 pm

    Howdy,

    @AREA:FSX_TST

    Should this kludge have a space in it? Seems to have changed in the clrghouz automated reply, like it was parsed wrong, is why I ask.

    Should there be a space between the colon and the area name? No (FTS-0004) - but I've seen some packed messages that do have it and clrghouz will ignore the space.

    Interesting though, the source message had two area tags:

    00000000: 41 52 45 41 3a 46 53 58 5f 54 53 54 0d 01 4d 53 [AREA:FSX_TST..MS] 00000010: 47 49 44 3a 20 32 31 3a 34 2f 31 35 38 2e 31 20 [GID: 21:4/158.1 ] 00000020: 36 61 36 35 30 38 64 65 0d 01 50 49 44 3a 20 56 [6a6508de..PID: V] 00000030: 69 53 69 4f 4e 2f 33 20 76 30 2e 38 2e 32 2f 4c [iSiON/3 v0.8.2/L] 00000040: 69 6e 75 78 0d 01 41 52 45 41 3a 46 53 58 5f 54 [inux..AREA:FSX_T] 00000050: 53 54 0d 01 54 49 44 3a 20 56 69 53 69 4f 4e 2f [ST..TID: ViSiON/] 00000060: 33 20 76 30 2e 38 2e 32 2f 4c 69 6e 75 78 0d 54 [3 v0.8.2/Linux.T] 00000070: 65 73 74 69 6e 67 20 74 68 65 20 6e 65 77 20 73 [esting the new s] 00000080: 65 74 75 70 2e 2e 2e 20 54 68 69 73 20 67 6f 69 [etup... This goi] 00000090: 6e 67 20 6f 75 74 3f 0d 2d 2d 2d 20 56 69 53 69 [ng out?.--- ViSi]


    ...лоеп
    --- SBBSecho 3.37-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From J0hnny A1pha@21:4/158.1 to Accession on Thursday, September 10, 2026 13:21:59
    --- Accession Said ---
    @AREA:FSX_TST

    Should this kludge have a space in it? Seems to have changed in the clrghouz automated reply, like it was parsed wrong, is why I ask.

    --- Accession Done ---

    Good catch, and thanks for the hex dump Deon, that made it easier to spot.

    1. Confirmed, no space needed after colon per FTS-004
    3. Double area problem will be fixed (ViSiON/3 was writing it twice, as bare area (top) then as kludge down with PID/TID).

    I'm in there now and i also made the inbound parser tolerant of the variant
    you are seeing in the wild (space + leading SOH). That would have triggered a BAD message flag on my end!

    Making these corrections now and will put this out in a hotfix today and re-test...

    .jA
    --- ViSiON/3 v0.9.0/Linux
    * Origin: Broken Bit Syndicate - ViSiON/3 HQ (21:4/158.1)
  • From Storm@21:1/128 to All on Thursday, September 10, 2026 15:46:05
    Testing the new software/mailer to ensure things work properly.

    - Storm
    --- Lighthouse 1.0
    * Origin: LighthouseBBS.com - Rockport, TX (21:1/128)
  • From Accession@21:1/200 to deon on Thursday, September 10, 2026 21:33:58
    Hey deon!

    On Thu, Sep 10 2026 13:51:58 +1000, you wrote:

    Should there be a space between the colon and the area name? No (FTS-0004) - but I've seen some packed messages that do have it and clrghouz will ignore the space.

    Ah, ok. I only mentioned it because it looked like your automated reply removed the colon, or something. Either way, it wasn't the same as it was in his header.

    Interesting though, the source message had two area tags:

    Maybe that's why?

    Regards,
    Accession

    ... Take my advice, I don't use it anyway.
    --- AmberEdit/linux 0.8.1
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From deon@21:2/116 to Accession on Friday, September 11, 2026 21:00:47
    Re: Testing
    By: Accession to deon on Thu Sep 10 2026 09:33 pm

    Howdy,

    Ah, ok. I only mentioned it because it looked like your automated reply removed the colon, or something. Either way, it wasn't the same as it was in his header.

    Yes, so the display of the kludges in the test message response, is a "key"/"value" display, where the key is the kludge and the value is the kludges value.

    The delimiter is the space, because the kludge inludes the colon, eg: MSGID:, TID:, PID:. When there is no space, clrghouz will fall back to delimit on the colon, hence why it was rendered as "AREA FSX_NET", because it was packed as AREA:FSX_NET, not AREA: FSXNET (with a space).

    (AREA tags are not a \x01 kludge, so normally it is not included in the output, but in that packet it was included a second time as a kludge.)

    Interesting though, the source message had two area tags:

    Maybe that's why?

    Yup, the first AREA tag was taken as the message area, the second was just kept verbatim (and parsed for the test output).


    ...лоеп
    --- SBBSecho 3.37-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)