Subj : QWK - messed up posting
To   : deon
From : Digital Man
Date : Tue Jan 24 2023 14:02:16

  Re: QWK - messed up posting
  By: deon to Digital Man on Wed Jan 25 2023 08:28 am

 >   Re: QWK - messed up posting
 >   By: Digital Man to deon on Tue Jan 24 2023 11:48 am
 >
 > Howdy,
 >
 >  > If the qhubsub sections in your msgs.ini was corrupted, then it still
 >  > needs to be fixed. Even if you're running the version of sbbs with the
 >  > fix, the configuration file (msgs.ini) that may have been previously
 >  > corrupted does not get magically fixed.
 >
 >  > Please restate the problem you're having. I thought you had a cross-up
 >  > betwen DOVE-Net conferences and the conferences in some other QWK network
 >  > (for which ALTERANT is your hub). Please clarify.
 >
 > ALTTEST has never been v3.20 before commit cadada4d. IE: It was upgraded
 > from v3.19 to v3.20 (cadada4d) and I ran upgrade_to_320*. So msgs.ini would
 > never have been corrupted by the known issue that cadada4d was committed to
 > fix. In many respects its a vanilla SBBS with little configuration (so it
 > has mostly all the defaults a new install would have).
 >
 > ALTERANT is my BBS still v3.19 - its not a QWK hub for *any* network, but it
 > as assumed that role as a QWK hub for ALTTEST. It's what I'm on now, and it
 > gets QWK mail from VERT and DIGDIST for those respective conferences.
 >
 > I set up ALTERANT/ALTTEST to debug qnet-http to see if I can figure out what
 > the issue is with #310 (and so far it seems to work for me - except
 > conferences are importing incorrectly).
 >
 > On ALTERANT, I have a PVT_TEST sub (that I also use for FTN testing) - Im
 > also using that for QWK testing - I assigned it a "manual" conference of
 > 9900
 > in SCFG. I setup a user for ALTTEST to be able to receive QWK packets - of
 > the DOVE and PVT_TEST conferences. The setting for that use is the same as
 > in the wiki.
 >
 > On ALTTEST - the DOVE configuration is configured from defaults - its never
 > received DOVE before, nor have I had any reason to change that config. I
 > renamed the default "VERT" config (Networks -> QWK -> ... -> VERT) to
 > ALTERANT and added conference 9900.
 >
 > I also changed the callout command to use qnet-http instead of qnet-ftp.
 >
 > When ALTTEST collects mail from ALTERANT, the PVT_TEST messages are imported
 > successfully (into the right sub). However the DOVE subs are imported
 > *incorrectly* they go into the wrong subs. In the message dialogue up to
 > now, I've been giving you Sync Discussion as an example, but they are all
 > wrong.
 >
 > Posts from Sync Discussion that arrive on ALTERANT (from VERT) arrive in Pro
 > Audio in ALTTEST. My post in Sync Discussion on ALTTEST arrived in Ham Radio
 > on ALTERANT, and thus I assume that message also went to VERT in that sub
 > too.
 >
 > Where do I look? Just looking at Sync Discussion, the conference numbers are
 > the same, the QWK name is the same, as is the Internal Code.

The QWK names and internal codes are not relevant, only the conference numbers matter.

On a QWKnet node (e.g. ALTTEST), the conference numbers that *matter* are in SCFG->Networks->QWK->Hubs->...

On a QWKnet hub (e.g. ALTERANT), the conference numbers that matter are in SCFG->Message Areas... and should be set to "static" and also match what is configured on the *node* in SCFG->Networks->QWK->Hubs...

If you don't use static conference numbering on the hub (in SCFG->Message Areas), then different users/nodes may get different conference numbers depending on their access.

If you need to look further for issues, you can examine the HEADERS.DAT in the downloaded QWK packets.
-- 
                                            digital man (rob)

Rush quote #9:
One likes to believe in the freedom of ... baseball!
Norco, CA WX: 66.4øF, 24.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrs
---
 þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

.