This information is using the most current version of Mystic BBS at the time of this writing, which is 1.12 A 31.

running 1.12 A46

Let me first say, my public and main bbs runs Synchronet (ATHEL) but wanted to test a few things with Mystic so here we are. Trying to get DOVE-Net from my system, not VERT.

----- ---------------
First, make sure you have a QWK account set up on the hub BBS. If this is Synchronet, make sure you log in and set the areas you would like, along with the message pointers. Make sure you obtain a list of the conferences and the QWK Base ID numbers, as you will need that information to set up the message bases.

1 - Open Mystic with "mystic -cfg" (or ./mystic -cfg in Linux).

2 - Under Configuration, select "QWK Networking"

3 - If nothing is listed in this menu, select "/" on your keyboard, and chose "Insert"

4 - Hit enter on the newly created network connection

<snip>

So I followed these instructions step-by-step, ATHEL is the packet id. Downloads a QWK packet and imports. Can anyone tell me why when I login to my Mystic board that, posts for Synchronet Announcements show up in the HAM Radio sub? DOVE-Net is group 2 here, and groups are showing just fine.

? Active Poll ? Yes ?
? Network Name ? DOVE-Net ?
? Member Type ? Node ?
? FTP Host ? athel.synchro.net ?
? Login ? MYTEST1 ?
? Password ? ******* ?
? Use Passive ? Yes ?
? Packet ID ? athel ?
? Archive Type ? ZIP ?
? Use QWKE ? Yes ?

? Name ? Dove HAM Radio Operators ? ? Base Type ? Local Quote Color ? Sample ? ? Newsgroup ? Text Color ? Sample ? ? QWK Name ? HAM Radio Tear Color ? Sample ? ? Echo Tag ? Origin Color ? Sample ? ? File Name ? dove-ham Kludge Color ? Sample ? ? Path ? /mystic/msgs/ Max Msgs ? 5000 ? ? List ACS ? s10g2 Max Msg Age ? 1000 ? ? Read ACS ? s10g2 New Scan ? Yes ? ? Post ACS ? s20g2 QWK Scan ? Yes ? ? Sysop ACS ? s255g2 Header ? msghead ? ? List EACS ? R Template ? ansimrd ? ? ? L Template ? ansimlst ? ? Net Address ? 0:0/0 (Local Address) Real Names ? No ? ? Export To ? 0 node(s) Autosigs ? Yes ? ? Origin ? Private ? No ? ? QWK Network ? DOVE-Net Pvt Reply ? No ? ? QWK Base ID ? 2015 Allow ANSI ? No ?

and..

? Name ? Dove Synchronet Announcements ? ? Base Type ? Local Quote Color ? Sample ? ? Newsgroup ? Text Color ? Sample ? ? QWK Name ? SyncAnnoun Tear Color ? Sample ? ? Echo Tag ? Origin Color ? Sample ? ? File Name ? dove-syncanno Kludge Color ? Sample ? ? Path ? /mystic/msgs/ Max Msgs ? 5000 ? ? List ACS ? s10g2 Max Msg Age ? 1000 ? ? Read ACS ? s10g2 New Scan ? Yes ? ? Post ACS ? s500g2 QWK Scan ? Yes ? ? Sysop ACS ? s255g2 Header ? msghead ? ? List EACS ? R Template ? ansimrd ? ? ? L Template ? ansimlst ? ? Net Address ? 0:0/0 (Local Address) Real Names ? No ? ? Export To ? 0 node(s) Autosigs ? Yes ? ? Origin ? Private ? No ? ? QWK Network ? DOVE-Net Pvt Reply ? No ? ? QWK Base ID ? 2030 Allow ANSI ? No ?

There's maybe 2 of the messages bases showing with correct messages, the rest aren't in their proper section. I've confirmed the QWK Base ID matches the Synchronet Conference Numbers for all of them as well as the QWK Names.

-altere
--- SBBSecho 3.11-Linux
* Origin: Athelstan - athelstan.org (21:1/113)

Re: Re: QWK networking?
By: Altere to All on Wed Oct 14 2020 11:00 am

to test a few things with Mystic so here we are. Trying to get DOVE-Net from my system, not VERT.

? ? QWK Base ID ? 2030 Allow ANSI ? No

There's maybe 2 of the messages bases showing with correct messages, the rest aren't in their proper section. I've confirmed the QWK Base ID matches the Synchronet Conference Numbers for all of them as well as the QWK Names.

It's the conference numbers that matter (not the names). Unless you have 30 subs in DOVE-Net *or* you have static QWK conference numbering enabled for those subs, then 2030 is probably incorrect. If you look at the CONTROL.DAT file included in the QWK packet downloaded from the hub, that should inform you what the actual/correct conference numbers should be for that hub.

digital man

Sling Blade quote #26:
Karl: kaiser blade, ax handle with long blade on it shaped kinda like a banana. Norco, CA WX: 92.5°F, 23.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs

It's the conference numbers that matter (not the names). Unless you have 30 subs in DOVE-Net *or* you have static QWK conference numbering enabled for those subs, then 2030 is probably incorrect. If you look at the CONTROL.DAT file included in the QWK packet downloaded from the hub, that should inform you what the actual/correct conference numbers should be for that hub.

Thanks. Just give me a kick, I've been looking at the wrong screen this whole time. One has qwk packets from vert and the other from athel. Seemed odd mine would match. 2001-2022 works much better. lol Do this much longer I'm going to have to start a new workspace screen to keep the boards seperate.

-altere
--- SBBSecho 3.11-Linux
* Origin: Athelstan - athelstan.org (21:1/113)

Re: Re: QWK networking?
By: Alpha to Vk3jed on Wed Apr 15 2020 03:03 pm

From Dan/Black Panther:
----
In order to set up a QWK network within Mystic is not very difficult, and it does work. Trust me.

I copied these instructions to http://wiki.synchro.net/howto:dove-net-for-mystic

Please feel free to update with additional details (e.g. isn't some "networking" toggle needed to enable QWKnet taglines for exported messages?).

A screen-shot or two would be nice too.
--
digital man (rob)

Sling Blade quote #1:
Karl: I've killed Doyle with a lawn mower blade. Yes, I'm right sure of it. Norco, CA WX: 77.2°F, 52.0% humidity, 17 mph SSW wind, 0.00 inches rain/24hrs

I copied these instructions to http://wiki.synchro.net/howto:dove-net-for-mystic

Hi Rob,

Do you happen to know if Mystic A47 still has the QWK bug mentioned within the post above? As I don't really know much about QWK, I was wondering if this is still something I need to be worried about?

===============================================================
TALIADON (Lee Westlake) | TALIADON BBS (taliadon.ddns.net:23)
FidoNet: 2:250/6 | fsxNet: 21:3/138 | tqwNet: 1337:1/116 ===============================================================

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: TALIADON BBS (21:3/138)

On 09 Jul 2022, TALIADON said the following...

I copied these instructions to http://wiki.synchro.net/howto:dove-net-for-mystic

Do you happen to know if Mystic A47 still has the QWK bug mentioned
within the post above? As I don't really know much about QWK, I was wondering if this is still something I need to be worried about?

Nope, that was solved long ago. A lot of work went in to making MSGID work right in mystic. Those problems were all gone by A46 on. Since then the
polling has been changed to be handled by mis. So we now use mis to do the polling, not sure if that really affects qwkpoll. I haven't really used the qwk, but have used mmail to send and receive messages from the BBS which
works fine these days.

... A .GIF is worth a thousand .TXT.

--- Mystic BBS v1.12 A47 2021/12/24 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

On 09 Jul 2022, TALIADON said the following...

Do you happen to know if Mystic A47 still has the QWK bug mentioned
within the post above? As I don't really know much about QWK, I was wondering if this is still something I need to be worried about?

Or better yet, you could just upgrade to A48 and not have to worry if an A47 bug is still around or not, especially since it is most likely already fixed. ;)

Regards,
Nick

--- Mystic BBS v1.12 A48 2022/04/26 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Or better yet, you could just upgrade to A48 and not have to worry if an A47 bug is still around or not, especially since it is most likely
already fixed. ;)

Thanks for the feedback Nick, much appreciated.

As this particular bug was listed for A31, I was hoping it had long since been fixed.

Do you know when A48 will be officially released - A47 is still listed as the stable version on mysticbbs.com?

===============================================================
TALIADON (Lee Westlake) | TALIADON BBS (taliadon.ddns.net:23)
FidoNet: 2:250/6 | fsxNet: 21:3/138 | tqwNet: 1337:1/116 ===============================================================

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: TALIADON BBS (21:3/138)

Hello TALIADON!

On 09 Jul 2022, TALIADON said the following...

Do you know when A48 will be officially released - A47 is still listed
as the stable version on mysticbbs.com?

The stable releases (actual releases) are often rather far apart, perhaps 1-2 years. Given that A47 was released last Christmas, I would say perhaps in a year or so.

But the A47 release was actually very good, so I think you'll be doing rather fine on it. :)

Best regards
Zip

--- Mystic BBS v1.12 A48 2022/07/07 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

The stable releases (actual releases) are often rather far apart,
perhaps 1-2 years. Given that A47 was released last Christmas, I would
say perhaps in a year or so.

But the A47 release was actually very good, so I think you'll be doing rather fine on it. :)

Yeah, I'm in no rush to be honest - A47 appears to be meeting my needs without issue at the moment :)

===============================================================
TALIADON (Lee Westlake) | TALIADON BBS (taliadon.ddns.net:23)
FidoNet: 2:250/6 | fsxNet: 21:3/138 | tqwNet: 1337:1/116 ===============================================================

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: (21:3/138)

On 09 Jul 2022, TALIADON said the following...

As this particular bug was listed for A31, I was hoping it had long
since been fixed.

Yikes. Then I would assume it has long since been fixed. I don't even remember A31 it's been that long ago. ;)

Do you know when A48 will be officially released - A47 is still listed
as the stable version on mysticbbs.com?

To be completely honest, no. But I've never really thought of Mystic having many "official releases". A47 is/was a prealpha, yet there may have been some kind of A47 "is as stable as can be" release right before A48 was started. There were MANY versions of A47 leading up to it, though. This is exactly how A48 has been going. The only reason there isn't a stable version of A48 listed on mysticbbs.com yet is because A49 hasn't been started yet.

I've been upgrading the prealphas as they're released and have had no issues. Sure there may be a few bugs here and there (definitely nothing show-stopping), but g00r00 is on top of it and usually pushes fixes as soon as he is able to.

http://mysticbbs.com/downloads/prealpha

.. if you like to be cool and edgy. lol

I think the more people that are on the latest version finding bugs and reporting them would be much more helpful to development than people reporting bugs from previous versions. And actually, I'm not sure previous versions are even supported. The first thing you would be asked to do would be to upgrade to the latest prealpha and see if the bug/issue is still there, since it may have already been fixed (this is why the whatsnew.txt is important, as well).

Regards,
Nick

--- Mystic BBS v1.12 A48 2022/04/26 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Yikes. Then I would assume it has long since been fixed. I don't even remember A31 it's been that long ago. ;)

To be fair, as Rob's main concern is Synchronet rather than Mystic, I was hoping the documentation was simply out of date. No one appears to have experienced problems with DOVE on A47, so I'll naively assume it is for now :)

To be completely honest, no. But I've never really thought of Mystic having many "official releases". A47 is/was a prealpha, yet there may
have been some kind of A47 "is as stable as can be" release right before A48 was started. There were MANY versions of A47 leading up to it,
though. This is exactly how A48 has been going. The only reason there isn't a stable version of A48 listed on mysticbbs.com yet is because A49 hasn't been started yet.

Considering the monumental amount of work that goes into Mystic, this approach certainly makes sense to me.

I've been upgrading the prealphas as they're released and have had no issues. Sure there may be a few bugs here and there (definitely nothing show-stopping), but g00r00 is on top of it and usually pushes fixes as soon as he is able to.

http://mysticbbs.com/downloads/prealpha

Thanks Nick, this link will prove most useful.

I think the more people that are on the latest version finding bugs and reporting them would be much more helpful to development than people reporting bugs from previous versions. And actually, I'm not sure
previous versions are even supported. The first thing you would be asked to do would be to upgrade to the latest prealpha and see if the
bug/issue is still there, since it may have already been fixed (this is why the whatsnew.txt is important, as well).

Yep, I ran into this when I was using A46 - g00r00 asked me to upgrade and retest before submitting a bug report. Again, considering his work load, this approach certainly makes sense to me.

===============================================================
TALIADON (Lee Westlake) | TALIADON BBS (taliadon.ddns.net:23)
FidoNet: 2:250/6 | fsxNet: 21:3/138 | tqwNet: 1337:1/116 ===============================================================

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: TALIADON BBS (21:3/138)