Greetings all,

I'm currently configured as a point system to my Mystic BBS v1.12 A46
using OpenXP 5.0.46. I've recently realized that Mystic has gone sideways when processing AreaFix messages received from OpenXP. I've tested using a couple recent versions of OpenXP with the samy results. My guess is that
it might be an issue with Mystic but I just tried using WinPoint to send
an AreaFix message and it gets processed correctly

From Mystic logs, I see that the arefix message is reconginized and
appears to process but with obvious issues. The AreaFix Response looks similar to the below logging

+ Nov 23 12:09:29 Importing 23120917.PKT (1:267/585.1 to 1:267/585)
+ Nov 23 12:09:29 AREAFIX received from 1:267/585.1
- Nov 23 12:09:29 AREAFIX command [
MSGID:] [1:267/585.1@FIDONET EAB000B4]
! Nov 23 12:09:29 Unknown area _� ��w�F�u� y
- Nov 23 12:09:29 AREAFIX command [
PID:] [OPENXP/5.0.42 (WIN32)]
! Nov 23 12:09:29 Unknown area _� ��w�F�u� y
- Nov 23 12:09:29 AREAFIX command [
CHRS:] [ASCII 1]
! Nov 23 12:09:29 Unknown area _� ��w�F�u� y
- Nov 23 12:09:29 AREAFIX command [
TZUTC:] [-0500]
! Nov 23 12:09:29 Unknown area _� ��w�F�u� y
- Nov 23 12:09:29 AREAFIX command [
%LIST] []
! Nov 23 12:09:29 Unknown area _� ��w�F�u� y
- Nov 23 12:09:29 AREAFIX command [
---] []
! Nov 23 12:09:29 Unknown area _� ��w�F�u� y
- Nov 23 12:09:29 AREAFIX command [
] []
! Nov 23 12:09:29 Unknown area _� ��w�F�u� y
! Nov 23 12:09:29 Import from c:\bbs\mystic\echomail\in\unsecure\
+ Nov 23 12:09:29 Bundling Messages
+ Nov 23 12:09:29 Results: 0 echo, 0 net, 0 dupes, 1 tossed in 0.11s
+ Nov 23 12:09:29 Shutdown Normal (0)

Has anyone experieinced something similar?

Thx,

-k
Salutations from Rochester, NY - (SysOp KnightMare)

--- OpenXP 5.0.46
* Origin: Point KnightMare, Rochester, NY (1:267/585.1)

Hey Oli...

** 03.12.20 - 15:49, Oli wrote to Kevin Miller:

Kevin wrote (2020-12-03):

Just an FYI... I've been working with g00r00 on this bug which he's just KM>> fixed. Will be available in Mystic a48.

What triggered the bug? And why did OpenXP trigger it and other software doesn't?

Not entirely sure but g00r00 indicated that there were some changes made
in a46 to packet handling, particularly to the areafix processor. His
guess, before the bug was fixed, that is was probably a memory leak in the code.

-k

-+-
+ Origin: (2:280/464.47)

Salutations from Rochester, NY - (SysOp KnightMare)

--- OpenXP 5.0.46
* Origin: Point KnightMare, Rochester, NY (1:267/585.1)

Hi! Kevin,

On 03 Dec 20 08:39, you wrote to me:

Just an FYI... I've been working with g00r00 on this bug which he's
just fixed. Will be available in Mystic a48.

Excellent! I've had a hankering for A47 for the longest time. ;) I haven't seen the release announcement yet.

Cheers,
Paul.

... Travelling in a fried-out kombie, On a hippy trail, head full of zombie, --- GoldED+/LNX 1.1.4.7
* Origin: Paul's other Linux ghizmo - a little more mobile (3:640/1384.125)

Hey Paul...

** 04.12.20 - 08:12, Paul Quinn wrote to Kevin Miller:

Hi! Kevin,

On 03 Dec 20 08:39, you wrote to me:

Just an FYI... I've been working with g00r00 on this bug which he's
just fixed. Will be available in Mystic a48.

Excellent! I've had a hankering for A47 for the longest time. ;) I
haven't seen the release announcement yet.

Excited to say that OpenXP is again... working as expected!

g00r00 has actually fixed the bug and compiled it into the a47 pre-alpha.
If you are willing to install a pre-alpha, you can pick it up at the below URL. I updated this morening and confirmed that both areafix and filefix requests are now working again :)

URL: http://mysticbbs.com/downloads/prealpha/

Good luck

-km

Salutations from Rochester, NY...

--- OpenXP 5.0.46
* Origin: Point KnightMare, Rochester, NY (1:267/585.1)