On 11 Aug 2020, alterego said the following...
@TZUTC: 1000
@MSGID: 41276.fsx_gen@21:2/116 2397d9be
@REPLY: 21:3/107 a2442386
@PID: Synchronet 3.18a-Linux Aug 2 2020 GCC 8.3.0
@TID: SBBSecho 3.11-Linux r3.176 Aug 2 2020 GCC 8.3.0
@CHRS: ASCII 1
@NOTE: SlyEdit 1.73 (2020-03-31) (ICE style)
@SEEN-BY: 1/100 2/100 116 3/100 101 102 103 105 106 108 109 110 111 112 113 114
@SEEN-BY: 3/116 117 118 119 4/100
@SEEN-BY: 1/100 2/100 116 3/100 101 102 103 105 106 107 108 109 110 111 112 113
@SEEN-BY: 3/114 116 117 118 119 4/100
@PATH: 2/116 3/100
Re: Re: Test Message
By: Nazferiti to tonic on Mon Aug 10 2020 09:13 pm
Hey Mike,
I was curious by this message of yours - since when it imported for me,
it appeared to come from the hub (which I know it didnt):
#--# BEGIN MESSAGE #--#
ŚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄśśśś
³ Subj: Re: Test Message
³ To : tonic
³ From: Nazferiti (21:3/100)
³ Date: Mon Aug 10 2020 09:13 pm UTC-4:00 (1.0 hours ago) ĄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄśśśśśś
On 10 Aug 2020, tonic said the following...
#--# END MESSAGE #--#
When I tracked it, it came from you (3/107) - but it was a bad packet (that hpt
partially tossed). Curious if there is any logging on your side as to
why it was created bad.
It seems to me that there are 8 nulls in the middle of the packet (which I'm guessing are not right):
00000100 30 32 30 2c 20 74 6f 6e 69 63 20 73 61 69 64 20 0, tonic
said | 00000110 74 68 65 20 66 6f 6c 6c 6f 77 69 6e 67 2e 2e 2e |the following...| 00000120 0d 20 0d 20 74 6f 3e 20 0d 20 74 6f 3e 20 00 00 |. . to> . to> ..| 00000130 00 00 00 00 00 00 54 65 73 74 20 6d 65 73
73 61 |......Test messa| 00000140 67 65 3f 0d 20 74 6f 3e 20 0d 20 74 6f 3e 20 2d |ge?. to> . to> -| 00000150 2d 2d 20 45 4e 69 47 4d 41 20 31 2f 32 20 76 30 |-- ENiGMA 1/2 v0|
This is the message:
X-FTN-TID Mystic BBS 1.12 A46
X-FTN-MSGID 21:3/107 a2442386
X-FTN-REPLY 260870.fsx_gen@21:1/121 40f2031a
...ėīåļ
... I can't promise anything but I can promise 100%.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
I don't see anything in the log that would tell me why there would be a problem, however, I did upgrade to the newest build of A46 last night from A45. My initial run of the BBS after the upgrade gave some errors at login (which I have since fixed) so it's possible I responded to some messages
during this time. I'll keep an eye on things.
- Mike
--- Mystic BBS v1.12 A46 2020/08/10 (Linux/64)
* Origin: Arcadia BBS | Connecticut USA | bbs.arcadiabbs.com (21:3/107)