Re: QWK - messed up posting
By: deon to Digital Man on Tue Jan 24 2023 07:44 am

> Re: QWK - messed up posting
> By: Digital Man to deon on Mon Jan 23 2023 09:07 am
>
> Howdy,
>
> > Check the SCFG->Networks->QWK->Hubs->*->Sub-boards mappings. That (the
> > "qhubsub" sections of msgs.ini) the area that would get messed-up when
> > inserting sub-boards before the committed fix in v3.20a.
>
> Yup, that's what I compared - and they are all the same.
>
> (And my compile should have that fix in it.)
>
> ALTTEST has:
> [qhubsub:ALTERANT:2007]
> sub=DOVE-SYNCDISC
> settings=0x0
>
> And ALTERANT has
> ▒▒▒▒│ │2007 0011:DOVE-net 07:Synchronet Discussion

Okay, so you'll need fix ALTERANT. Either restore the [qhubsub:ALTERANT:*] sections from a backup of ctrl/msgs.ini (there should be auto-backups as msgs.#.ini) or just fix them by hand by either editing the msgs.ini file with a text editor or fix them in SCFG->Networks.
--
digital man (rob)

Synchronet "Real Fact" #4:
Synchronet version 3 is written mostly in C, with some C++, x86 ASM, and Pascal
Norco, CA WX: 55.1°F, 27.0% humidity, 1 mph SSW wind, 0.00 inches rain/24hrs
---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net

Re: QWK - messed up posting
By: Digital Man to deon on Mon Jan 23 2023 07:12 pm

> Okay, so you'll need fix ALTERANT. Either restore the [qhubsub:ALTERANT:*]
> sections from a backup of ctrl/msgs.ini (there should be auto-backups as
> msgs.#.ini) or just fix them by hand by either editing the msgs.ini file
> with
> a text editor or fix them in SCFG->Networks.

ALTERANT is still running 3.19 - so it doesnt use the new msgs.ini right?

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

Re: QWK - messed up posting
By: deon to Digital Man on Tue Jan 24 2023 03:33 pm

> Re: QWK - messed up posting
> By: Digital Man to deon on Mon Jan 23 2023 07:12 pm
>
> > Okay, so you'll need fix ALTERANT. Either restore the
> > [qhubsub:ALTERANT:*] sections from a backup of ctrl/msgs.ini (there
> > should be auto-backups as msgs.#.ini) or just fix them by hand by either
> > editing the msgs.ini file with
> > a text editor or fix them in SCFG->Networks.
>
> ALTERANT is still running 3.19 - so it doesnt use the new msgs.ini right?

The hub and the nodes don't have to be running the same version.

I have no idea what version of sbbs ALTERANT is running and if that's not your system, then you shouldn't care.
--
digital man (rob)

Synchronet/BBS Terminology Definition #30:
FF = Form Feed (ASCII 12, Ctrl-L)
Norco, CA WX: 52.6°F, 37.0% humidity, 1 mph NW wind, 0.00 inches rain/24hrs
---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net

Re: QWK - messed up posting
By: Digital Man to deon on Mon Jan 23 2023 09:18 pm

> > ALTERANT is still running 3.19 - so it doesnt use the new msgs.ini right?
>
> The hub and the nodes don't have to be running the same version.
>
> I have no idea what version of sbbs ALTERANT is running and if that's not
> your system, then you shouldn't care.

They are both mine.

So again, I hope I've shown that:

ALTERANT - v3.19 has the correct DOVE subs conference number configuration
ALTTEST - v3.20 has also the correct DOVE subs conference number configuration

Why is it when ALTTEST collect mail from ALTERANT, that the mail gets imported into the incorrect subs?

Is this a bug with 3.20?

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

Re: QWK - messed up posting
By: deon to Digital Man on Tue Jan 24 2023 05:04 pm

> Re: QWK - messed up posting
> By: Digital Man to deon on Mon Jan 23 2023 09:18 pm
>
> > > ALTERANT is still running 3.19 - so it doesnt use the new msgs.ini right?
>
> > The hub and the nodes don't have to be running the same version.
>
> > I have no idea what version of sbbs ALTERANT is running and if that's not your system, then you shouldn't care.
>
> They are both mine.
>
> So again, I hope I've shown that:
>
> ALTERANT - v3.19 has the correct DOVE subs conference number configuration ALTTEST - v3.20 has also the correct DOVE subs conference number configuration
>
> Why is it when ALTTEST collect mail from ALTERANT, that the mail gets imported into the incorrect subs?
>
> Is this a bug with 3.20?

You previosly pasted here:

> ALTTEST has:
> [qhubsub:ALTERANT:2007]
> sub=DOVE-SYNCDISC
> settings=0x0

Which demonstrates that you have messages that download from the ALTERANT hub being imported into the DOVE-SYNCDISC sub. You need fix that by either hand editing the msgs.ini file or via SCFG->Networks->QWK->Hubs->ALTERANT. It may have been caused by the bug previously fixed that would mess up the mapping of subs for QWKnet hubs when a new message sub-board was inserted in SCFG before others.
--
digital man (rob)

This Is Spinal Tap quote #37:
David St. Hubbins: We are Spinal Tap from the UK - you must be the USA!
Norco, CA WX: 49.3°F, 40.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net

Re: QWK - messed up posting
By: Digital Man to deon on Mon Jan 23 2023 10:55 pm

> You previosly pasted here:
>
> > ALTTEST has:
> > [qhubsub:ALTERANT:2007]
> > sub=DOVE-SYNCDISC
> > settings=0x0
>
> Which demonstrates that you have messages that download from the ALTERANT
> hub being imported into the DOVE-SYNCDISC sub. You need fix that by either
> hand editing the msgs.ini file or via SCFG->Networks->QWK->Hubs->ALTERANT.
> It may have been caused by the bug previously fixed that would mess up the
> mapping of subs for QWKnet hubs when a new message sub-board was inserted in
> SCFG before others.

So, I'm still confused.

ALTTEST (that receives the message) - as built *after* you committed the fix to the msgs.ini corruption. It was built with commit #cadada4df that fixes that issue (unless there is another one?).

When I go to SCFG->Networks->QWK->Hubs->ALTERANT it shows this for Sync Discussion:

│ Networked Sub-board │
├──────────────────────────────────────────────────────────
│Sub-board 0072:DOVE-Net Synchronet Discussion │
│Conference Number 2007 │
│Ctrl-A Codes Strip out │

Which is consistent with what you pasted above (that happens to be in
msgs.ini).

What am I changing? The conf number is the same - is that not the important item?

I've compared the "Internal Code" on both ALTERANT and ALTTEST (DOVE-SYNCDISC) and they are the same, and so is the "QWK Name" (SyncDiscus).

I dont know what needs a fixing.

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

Re: QWK - messed up posting
By: deon to Digital Man on Tue Jan 24 2023 07:54 pm

> Re: QWK - messed up posting
> By: Digital Man to deon on Mon Jan 23 2023 10:55 pm
>
> > You previosly pasted here:
>
> > > ALTTEST has:
> > > [qhubsub:ALTERANT:2007]
> > > sub=DOVE-SYNCDISC
> > > settings=0x0
>
> > Which demonstrates that you have messages that download from the ALTERANT
> > hub being imported into the DOVE-SYNCDISC sub. You need fix that by
> > either hand editing the msgs.ini file or via
> > SCFG->Networks->QWK->Hubs->ALTERANT. It may have been caused by the bug
> > previously fixed that would mess up the mapping of subs for QWKnet hubs
> > when a new message sub-board was inserted in SCFG before others.
>
> So, I'm still confused.
>
> ALTTEST (that receives the message) - as built *after* you committed the fix
> to the msgs.ini corruption. It was built with commit #cadada4df that fixes
> that issue (unless there is another one?).

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.

> When I go to SCFG->Networks->QWK->Hubs->ALTERANT it shows this for Sync
> Discussion:
>
> │ Networked Sub-board │
> ├──────────────────────────────────────────────────────────
> │Sub-board 0072:DOVE-Net Synchronet Discussion │
> │Conference Number 2007 │
> │Ctrl-A Codes Strip out │
>
> Which is consistent with what you pasted above (that happens to be in
> msgs.ini).
>
> What am I changing? The conf number is the same - is that not the important
> item?

Is ALTERANT your DOVE-Net hub? If ALTERANT is another QWK network hub (for some other QWK network, not DOVE-Net), then that is incorrect - it shouldn't have a DOVE-Net sub-board.

> I've compared the "Internal Code" on both ALTERANT and ALTTEST
> (DOVE-SYNCDISC) and they are the same, and so is the "QWK Name"
> (SyncDiscus).
>
> I dont know what needs a fixing.

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.
--
digital man (rob)

This Is Spinal Tap quote #18:
Sustain, listen to it. Don't hear anything. You would though were it playing.
Norco, CA WX: 62.5°F, 25.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net

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.

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

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

Re: QWK - messed up posting
By: Digital Man to deon on Tue Jan 24 2023 02:02 pm

Howdy,

> 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...

OK that was painful.

It was set to "Dynamic", so going through them all to key in the conference number fixed it. BTW It let me give 2 subs the same conference number - I'm thinking that would cause problems? (Or perhaps thats a desired outcome..)

I guess I dont understand QWK enough, but it seems you have to manage these conference numbers in multiple places - and thus an opportunity for mistakes. Anyway, only a 1 time operation, so hopefully set and forget is all that's needed... :)

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI