AREA:FSX_BBS
I've got this message as a dupe. It is obviously also bork'd like the some other messages. Somehow the end of the message appears at the top of the message. From the path it looks like 4/100 is responsible. I doesn't look like random data corruption, it seems to follow a pattern that looks more like a specific software bug. Just a wild guess, but I'm not surprised anymore by any weird thing a Mystic system produces.
* Forwarded from BAD by Oli (21:1/151)
* Originally by: Adept (21:2/108), 13 Nov 19 14:12
* Originally to: Avon
@TID: Mystic BBS 1.12 A43
@MSGID: 21:2/108 3fa20719
@REPLY: 21:1/101 7f337a63
@TZUTC: -0800
not bork'd.)
-+- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
+ Origin: Storm BBS (21:2/108)
:)
--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
c BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
...that was interesting.
(The next message seemed to be the same thing, but not bork'd.)
-+- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
+ Origin: Storm BBS (21:2/108)
SEEN+BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 SEEN+BY: 0/116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 SEEN+BY: 0/133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 SEEN+BY: 0/149 150 151 152 153 154 155 157 158 159 160 161 162 163 164 165 SEEN+BY: 0/166 167 168 169 170 171 172 173 174 175 176 177 178 180 181 182 SEEN+BY: 0/183 184 185 186 187 188 189 190 191 192 194 195 197 199 200 201 SEEN+BY: 0/202 203 204 2/100 101 0/102 103 104 105 106 107 108 109 110 111 SEEN+BY: 0/112 113 114 115 1202 132 3/100 4/10 100 101 102 103 104 105 106 SEEN+BY: 4/107 108 110 111 112 113 114 0/156 5/100 1/151
@PATH: 2/108 100 4/100 1/100 151
--- GoldED+/LNX 1.1.5-b20180707
* Origin: 🌈 (21:1/151)