__                 _ _                _
  / _| ___   ___   __| | |__   __ _ _ __| | __
 | |_ / _ \ / _ \ / _` | '_ \ / _` | '__| |/ /
 |  _| (_) | (_) | (_| | |_) | (_| | |  |   <
 |_|  \___/ \___/ \__,_|_.__/ \__,_|_|  |_|\_\

A personal BBS  ·  Missoula, Montana  ·  formerly NaClCON BBS

Connect from your terminal: telnet naclconbbs.net 23  |  ssh naclconbbs.net -p 2222

  1. Forum
  2. DOVE-Net
  3. Synchronet Discussion

  • Qwk Posting Issue

    From Khronos@VERT/CWSHACK to All on Sat Oct 17 08:52:16 2026
    Hi,
    Yesterday or the day before I was using my Multimail qwk client to reply to a message in this area and a user on musicalnet stated that my message appeared in their bases.
    Musicalnet's mapping to 2017 is the same as this one in the qwk configuration. I was replying from the qwk client instead of a telnet connection to tthe bbs. It seems that when I reply from the qwk client it is sending the message back to the 2017 qwk tag on the second net I added instead of this one.
    Has anyone seen this before?

    ---
    þ Synchronet þ telnet://cwshack.ddns.net:2330
  • From Digital Man@VERT to Khronos on Sat Oct 17 13:50:20 2026
    Re: Qwk Posting Issue
    By: Khronos to All on Sat Oct 17 2026 08:52 am

    Hi,
    Yesterday or the day before I was using my Multimail qwk client to reply to a message in this area and a user on musicalnet stated that my message appeared in their bases.
    Musicalnet's mapping to 2017 is the same as this one in the qwk configuration. I was replying from the qwk client instead of a telnet connection to tthe bbs. It seems that when I reply from the qwk client it is sending the message back to the 2017 qwk tag on the second net I added instead of this one.
    Has anyone seen this before?

    The QWK conference numbers on your QWKnet *hub* (e.g. VERT for DOVE-Net) are (normally) *different* than the QWK conference numbers that your BBS exposes to your users (or any downstream QWK nodes). Unless your system is itself a QWKnet hub, then your sub-boards in SCFG->Message Areas should all be configured to use "dynamic" QWK conference numbering and then such collisions as you described (2017 being used for multiple QWK nets) won't be an issue.

    It sounds like you've confiugred some sub-boards to use static QWK conference numbering and should not have.
    --
    digital man (rob)

    Synchronet "Real Fact" #111:
    Weedpuller "World Of My Own" http://youtu.be/V-gmT5N6kYo
    Norco, CA WX: 86.9øF, 21.0% humidity, 2 mph WSW wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Khronos@VERT/CWSHACK to Digital Man on Sat Oct 17 17:35:32 2026
    Digital Man wrote to Khronos <=-

    Re: Qwk Posting Issue
    By: Khronos to All on Sat Oct 17 2026 08:52 am

    Hi,
    Yesterday or the day before I was using my Multimail qwk client to reply to a message in this area and a user on musicalnet stated that my message appeared in their bases.
    Musicalnet's mapping to 2017 is the same as this one in the qwk configuration. I was replying from the qwk client instead of a telnet connection to tthe bbs. It seems that when I reply from the qwk client it is sending the message back to the 2017 qwk tag on the second net I added instead of this one.
    Has anyone seen this before?

    The QWK conference numbers on your QWKnet *hub* (e.g. VERT for
    DOVE-Net) are (normally) *different* than the QWK conference
    numbers that your BBS exposes to your users (or any downstream
    QWK nodes). Unless your system is itself a QWKnet hub, then your sub-boards in SCFG->Message Areas should all be configured to use "dynamic" QWK conference numbering and then such collisions as
    you described (2017 being used for multiple QWK nets) won't be an
    issue.

    It sounds like you've confiugred some sub-boards to use static
    QWK conference numbering and should not have. --

    I rebuilt the message group from scratch and I believe I have fixed the
    issue.
    The mappings on the other end for musicalnet have bases that start with
    2001 through 2030 that are in the same range as Dovenet.
    This would be an issue on the remote board's site with the numbering
    logic.



    --- MultiMail/Linux v0.52
    þ Synchronet þ telnet://cwshack.ddns.net:2330
  • From Digital Man@VERT to Khronos on Sat Oct 17 15:08:28 2026
    Re: Re: Qwk Posting Issue
    By: Khronos to Digital Man on Sat Oct 17 2026 05:35 pm

    I rebuilt the message group from scratch and I believe I have fixed the issue.
    The mappings on the other end for musicalnet have bases that start with
    2001 through 2030 that are in the same range as Dovenet.
    This would be an issue on the remote board's site with the numbering
    logic.

    That would not be an issue unless that remote board was also a DOVE-Net hub.
    --
    digital man (rob)

    Synchronet "Real Fact" #130:
    Synchronet v3.20b was released on January 3, 2025 (3 years after v3.19b)
    Norco, CA WX: 87.7øF, 21.0% humidity, 2 mph SSE wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Nightfox@VERT/DIGDIST to Khronos on Sun Oct 18 15:07:44 2026
    Re: Re: Qwk Posting Issue
    By: Khronos to Digital Man on Sat Oct 17 2026 05:35 pm

    I rebuilt the message group from scratch and I believe I have fixed the issue. The mappings on the other end for musicalnet have bases that start with 2001 through 2030 that are in the same range as Dovenet. This would be an issue on the remote board's site with the numbering logic.

    That shouldn't be an issue. MusicalNet and Dove-Net are hosted by two different BBSes: MusicalNet is hosted by my BBS and Dove-Net is hosted by Vertrauen - so their conference numbers wouldn't conflict with each other.

    Nightfox

    ---
    þ Synchronet þ Digital Distortion: digitaldistortionbbs.com