Hi James,

I think I may have found a small bug. I was typing a reply when I was disconnected for some reason. No worries, luckily Mystic saved my message as a draft.

I logged back in and resumed my message & hit send. I then noticed that
there was no @REPLY kludge on the message, just he usual @MSGID & TZUTC.

I haven't tested whether this only happens if you're disconnected or if it would also happen if you /F to purposely save as a draft.


Thanks,
Jay

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

Hello Jay!

On 29 Dec 2020, Jay Harris said the following...

I think I may have found a small bug. I was typing a reply when I was disconnected for some reason. No worries, luckily Mystic saved my
message as adraft.

I logged back in and resumed my message & hit send. I then noticed that there was no @REPLY kludge on the message, just he usual @MSGID & TZUTC.

I stumbled across something similar a while ago on some earlier 1.12 A46 or A47, although in my case I got no Origin: line on the outgoing echomail message. Haven't had it happen again after that, though. But it was after a disconnect and resuming the message. If I come across it again, I'll let you all know.

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hi James,

I think I may have found a small bug. I was typing a reply when I was disconnected for some reason. No worries, luckily Mystic saved my
message as a draft.

I logged back in and resumed my message & hit send. I then noticed that there was no @REPLY kludge on the message, just he usual @MSGID & TZUTC.

Thanks this seems to also happen when saving a draft message as well. I've made a note of it in the TODO list to get this fixed.

--- Mystic BBS v1.12 A47 2020/12/21 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)