1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • Mystic Point to SBBS Node

    From Black Panther@24:150/2.2 to All on Monday, January 02, 2017 12:59:00
    Ok,

    After some discussion in DoveNet about SBBSEcho, we have found where the problem lies.

    When a message is posted on my point system, MysticBBS, it creates the .pkt file to send to my main BBS, SBBS. In this packet, Mystic is not putting the point in the PATH or the SEENBY lines. This is causing SBBS to send the
    message back to the point system.

    Does anyone know if there is a workaround for this, or is it a known issue? Like I stated, it's more of an annoyance than anything else.

    Below is a paste of the lines from the .pkt.


    * Origin: Castle Rock BBS 2 - Test Point (24:150/2.2)
  • From Richard Menedetter@21:1/104 to Black Panther on Monday, January 02, 2017 21:53:00
    Hi Black!

    02 Jan 2017 12:59, from Black Panther -> All:

    When a message is posted on my point system, MysticBBS, it creates the .pkt file to send to my main BBS, SBBS. In this packet, Mystic is not putting the point in the PATH or the SEENBY lines. This is causing
    SBBS to send the message back to the point system.

    PATH and SEENBY are 2D.
    Meaning that there cannot be point (or zone) addresses there.
    21:1/104 will be 1/104.

    So this behaviour of Mystic is OK.

    SBBS seems to do something strange, as the tosser part of it "knows" that the PKT came from the Point, and it should NOT send it back to the point where it came from.

    Seems to be an issue with the tosser used by SBBS.
    (You can try to rectify it by using a real tosser, instead of the built in one in SBBS)

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Illiterate? Write for a free brochure! (21:1/104)
  • From Dan Richter@21:1/186 to Richard Menedetter on Monday, January 02, 2017 15:47:00
    Re: Mystic Point to SBBS Node
    By: Richard Menedetter to Black Panther on Mon Jan 02 2017 21:53:00

    When a message is posted on my point system, MysticBBS, it creates
    the .pkt file to send to my main BBS, SBBS. In this packet, Mystic
    is not putting the point in the PATH or the SEENBY lines. This is
    causing SBBS to send the message back to the point system.

    PATH and SEENBY are 2D.
    Meaning that there cannot be point (or zone) addresses there.
    21:1/104 will be 1/104.
    So this behaviour of Mystic is OK.

    It seems a bit weird that it wouldn't indicate it was seen by the point system though.

    SBBS seems to do something strange, as the tosser part of it "knows" that the PKT came from the Point, and it should NOT send it back to the point where it came from.

    According to Rob, SBBSEcho seems to only look at the PATH and SEENBY lines to determine where to send the message to. I would think it should also look at the origin and MSGID.

    Seems to be an issue with the tosser used by SBBS.
    (You can try to rectify it by using a real tosser, instead of the built in one in SBBS)

    I'm not sure if it's possible with the propriatary message system that SBBS uses. Otherwise I would love to go back to FMail, which I used in the past.

    Thanks for the input. This is part of the reason why I'm checking out different BBS programs. I want to be able to set them up they way I want them to work, and not have any issues. (I can dream, can't I) :)



    Dan Richter
    aka Black Panther
    Sysop
    Castle Rock BBS
    Rio Rancho, NM



    Dave. Put down those Windows disks, Dave. DAVE! - HAL9000
    --- SBBSecho 3.00-Win32
    * Origin: Castle Rock BBS - Rio Rancho, NM (21:1/186)
  • From Richard Menedetter@21:1/104 to Dan Richter on Tuesday, January 03, 2017 23:38:00
    Hi Dan!

    02 Jan 2017 15:47, from Dan Richter -> Richard Menedetter:

    PATH and SEENBY are 2D.
    Meaning that there cannot be point (or zone) addresses there.
    21:1/104 will be 1/104.
    So this behaviour of Mystic is OK.
    It seems a bit weird that it wouldn't indicate it was seen by the
    point system though.

    This is how FTS-0004 specifies it.

    Zone information is not needed as they assumed zonegating, and point information is not needed as the boss node will send it to all points subscribed.

    SBBS seems to do something strange, as the tosser part of it
    "knows" that the PKT came from the Point, and it should NOT send
    it back to the point where it came from.
    According to Rob, SBBSEcho seems to only look at the PATH and SEENBY
    lines to determine where to send the message to. I would think it
    should also look at the origin and MSGID.

    And it should not send back the message to the originating point!

    Seems to be an issue with the tosser used by SBBS.
    (You can try to rectify it by using a real tosser, instead of the
    built in one in SBBS)
    I'm not sure if it's possible with the propriatary message system that SBBS uses. Otherwise I would love to go back to FMail, which I used in
    the past.

    Thanks for the input. This is part of the reason why I'm checking out different BBS programs. I want to be able to set them up they way I
    want them to work, and not have any issues. (I can dream, can't I) :)

    Ouch ... proprietary stuff is a pain in th a** ... and should be avoided at all
    costs.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: When the cat's away the mice will play (21:1/104)
  • From Black Panther@21:1/186.1 to Richard Menedetter on Tuesday, January 03, 2017 18:56:00
    On 01/03/17, Richard Menedetter said the following...

    Ouch ... proprietary stuff is a pain in th a** ... and should be avoided at all costs.


    I lived by that statement back in the day, but for some reason I ignored it when I found SBBS. That is another on my list of reasons for seriously
    looking at changing over to Mystic...


    Dan Richter
    aka Black Panther
    Sysop - Castle Rock BBS (1&2)

    --- Mystic BBS v1.12 A31 (Linux)
    * Origin: Castle Rock BBS 2 - Rio Rancho, NM (21:1/186.1)