MSGID: 1:267/585.1@fidonet eab4d149
REPLY: 2:221/360.0 5fbc29ec
PID: OpenXP/5.0.46 (Win32)
CHRS: ASCII 1
TZUTC: -0500
Thx for the response Paul...

I've been leaning to this being an issue with Mystic, but I haven't sent  
an areafix request to the BBS in some months and a couple version  
upgrades. Not sure at which version it broke but it worked briliiantly at  
one point

I've posted to the Mystic echo but crickets so far... I'll continue to  
search.

-k

** 23.11.20 - 23:30, Paul Quinn wrote to Kevin Miller:

> Hi! Kevin,

> On 11/24/2020 05:00 AM, you wrote to All:

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

> [chopped]

>> Has anyone experieinced something similar?

> Yes, with my own Mystic A46.  I just thought it was a contamination from my
> current situation, with Mystic not being the primary receiving agent as it's
> aligned _behind_ a regular tosser.

> I suggest that you persist with the matter in the Mystic echo...

Salutations from Rochester, NY - (SysOp KnightMare)

--- OpenXP 5.0.46
 * Origin: Point KnightMare, Rochester, NY (1:267/585.1)
SEEN-BY: 1/123 57/0 90/1 105/81 120/340 123/131 124/5016 153/250 154/10
SEEN-BY: 203/0 220/70 221/0 226/17 30 227/114 702 229/101 424 426
SEEN-BY: 229/664 1016 240/2100 5138 5411 5832 5853 249/206 317 400
SEEN-BY: 267/800 280/464 5003 288/100 292/854 8125 310/31 317/3 320/219
SEEN-BY: 322/757 340/1000 342/200 396/45 423/120 712/848 770/0 1 100
SEEN-BY: 770/330 340 772/0 1 220 230 2432/390 2452/250 2454/119
PATH: 267/585 800 770/1 280/464 240/5832 229/426