• Grunged Messages

    From Digital Man@VERT to Alterego on Thursday, August 29, 2019 20:30:06
    Re: Grunged Messages
    By: Alterego to Digital Man on Fri Aug 30 2019 11:50 am

    Re: Grunged Messages
    By: Digital Man to Alterego on Thu Aug 29 2019 05:49 pm

    The first bytes following the 20-byte DateTime field are supposed to be the "toUserName", but in this message header first bytes are "04 00", clearly this message is totally messed up and the first
    indication (that the 20th byte of the DateTime was non-null) was a good indicator of that. Trying to parse further is just making things worse as demonstrated by my pktdump utility:

    Hmm, the 20th byte should be null? I know you've bought this up a similiar discussion like this in the FTSC echo - but for the date field I didnt think it needed to be.

    Yeah, the DateTime field has to be null-terminated too. It's a poorly written spec.

    +-----------------------+-----------------------+
    14 E | |
    ~ DateTime ~
    | 20 bytes |
    +-----------------------+-----------------------+
    34 22 | toUserName |
    ~ max 36 bytes ~
    | null terminated |
    +-----------------------+-----------------------+

    From FTSC-0001.16 "to" should be null terminated but date isnt shown that way.

    I do see earlier in that document this though:

    DateTime = (* a character string 20 characters long *)
    (* 01 Jan 86 02:34:56 *)
    DayOfMonth " " Month " " Year " "
    " " HH ":" MM ":" SS
    Null

    That "Null" there is the indicator that it's null-terminated.

    So, I assumed it wasnt null terminated. (But I didnt think that that didnt make sense, because if the date is stored as per the example it is 19 chars).

    <humble>

    Can I change my argument - the structure is not valid, so I agree it should be thrown away ;)

    And if possible, let the originating system know that they're sending back packets.

    digital man

    Synchronet/BBS Terminology Definition #24:
    DTE = Data Terminal Equipment
    Norco, CA WX: 78.4F, 63.0% humidity, 6 mph ENE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alterego@VERT/ALTERANT to Digital Man on Friday, August 30, 2019 12:44:38
    Re: Message wrapping
    By: Digital Man to Alterego on Thu Aug 29 2019 06:42 pm

    Word/line-wrapping (re-flowing) message text is a tough thing to get right in all scenarios.

    I know that it would be - but there is something "different" between that hexdump past and normal typing.

    There is also something different about the message I posted, where I pasted in from FTSC-0001. It's not being horribly wrapped on my wide UTF terminal.

    I guess
    I can test
    To see if this sentence
    Is a single sentence or over 4 lines.

    The above sentice, was posted over 4 lines, using normal typing and "return" at the end of the line. Each line starts with a capital.

    If it is wrapped, then I guess this IS a difficult problem to solve - can the auto wrapping be "turned off"?

    If it isnt wrapped, then I will ask, why the pasted in content was.
    ...*

    ... Beauty is only skin deep, but ugly goes right to the bone.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Alterego@VERT/ALTERANT to Digital Man on Friday, August 30, 2019 12:48:04
    Re: Message wrapping
    By: Alterego to Digital Man on Fri Aug 30 2019 12:44 pm

    I guess
    I can test
    To see if this sentence
    Is a single sentence or over 4 lines.

    If it isnt wrapped, then I will ask, why the pasted in content was.

    And for the record, it wasnt :)
    ...*

    ... No one can feel as helpless as the owner of a sick goldfish.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Digital Man@VERT to Alterego on Thursday, August 29, 2019 20:37:14
    Re: Message wrapping
    By: Alterego to Digital Man on Fri Aug 30 2019 12:44 pm

    Re: Message wrapping
    By: Digital Man to Alterego on Thu Aug 29 2019 06:42 pm

    Word/line-wrapping (re-flowing) message text is a tough thing to get right in all scenarios.

    I know that it would be - but there is something "different" between that hexdump past and normal typing.

    There is also something different about the message I posted, where I pasted in from FTSC-0001. It's not being horribly wrapped on my wide UTF terminal.

    "UTF" is not a factor here. It might depend on what editor you used to post the message or how you're viewing or possible the content that was posted (e.g. line-lengths).

    I guess
    I can test
    To see if this sentence
    Is a single sentence or over 4 lines.

    The above sentice, was posted over 4 lines, using normal typing and "return" at the end of the line. Each line starts with a capital.

    If it is wrapped, then I guess this IS a difficult problem to solve - can the auto wrapping be "turned off"?

    When viewing messages via the internal message reading logic in Synchronet, word-wrapping is disabled while in Raw I/O mode. Raw I/O mode is toggled with the Ctrl-Z key.

    If it isnt wrapped, then I will ask, why the pasted in content was.

    You might have to ask the of SlyEdit. A detailed comparison of the original message text versus the message text saved to the message base (e.g. viewable with smbutil) versus the message text as displayed on the BBS. Also, there's an optional message editor field (COLS/columns) which is used to indicate the width of the original terminal used to write the message and offer help to any software that may need to re-wrap the message for display. Double-check that COLS header field value.

    digital man

    Synchronet "Real Fact" #76:
    Michael Swindell still has the "Synchronet Blimp" in his possession.
    Norco, CA WX: 78.0F, 63.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From poindexter FORTRAN@VERT/REALITY to Alterego on Thursday, August 29, 2019 06:07:00
    Alterego wrote to Digital Man <=-


    So, some more feedback - I updated and re-tried the packet.

    2019-08-29 15:00:57 Kurt Weiske (618:618/1) To: (3:510/1) Exported to /opt/sbbs/data/netmail/1.msg 2019-08-29 15:00:57 Grunged message (type 21057) from 618:618/1 at offset 10844 in packet: /opt/sbbs/fido/inbound/d622a770.pkt 2019-08-29 15:00:57 Bad packet detected: /opt/sbbs/fido/inbound/d622a770.pkt


    Weird - I'm 618:300/1 and don't recall sending netmail to fido zone 3, especially not from my Micronet address?



    ... What do you think of the guests?
    --- MultiMail/XT v0.52
    Synchronet realitycheckBBS -- http://realitycheckBBS.org
  • From mark lewis@VERT to Alterego on Friday, August 30, 2019 03:17:48
    On 2019 Aug 30 08:18:20, you wrote to Digital Man:

    This was the same message that it was barfing on previously (because of
    the
    bad time "4 Feb 119").

    this date problem looks like one of the QWK y2k bugs that some software ran into... they subtract 1900 from the year value retrieved so they can get the last two digits mathematically... they do that instead of converting to a string and lopping off the first two characters... many QWK programs that have this problem also corrupt the the TO: name (IIRC) so that it has some random looking alphanumeric character prepended to it...

    on initial glance, i want to suspect a (maximus) BBS side problem since the message was written in multimail which does not have the y2k problems like bluewave and others have... it could be an unpatched squish tosser which is used a lot with maximus systems... the sources are available and i assume that sean has them at hand... he just needs to know about the problems... he routes some mail through here, too, but i've not seen anything bad from his system in a while...

    )\/(ark

    Once men turned their thinking over to machines in the hope that this would set
    them free. But that only permitted other men with machines to enslave them.
    ... Butter hardness is proportional to the softness of the bread.
    ---
    * Origin: (1:3634/12.73)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alterego@VERT/ALTERANT to poindexter FORTRAN on Friday, August 30, 2019 17:50:28
    Re: Re: Grunged Messages
    By: poindexter FORTRAN to Alterego on Thu Aug 29 2019 06:07 am

    2019-08-29 15:00:57 Kurt Weiske (618:618/1) To: (3:510/1) Exported to /opt/sbbs/data/netmail/1.msg 2019-08-29 15:00:57 Grunged message (type 21057) from 618:618/1 at offset 10844 in packet:
    /opt/sbbs/fido/inbound/d622a770.pkt 2019-08-29 15:00:57 Bad packet detected: /opt/sbbs/fido/inbound/d622a770.pkt

    Weird - I'm 618:300/1 and don't recall sending netmail to fido zone 3, especially not from my Micronet address?

    You didnt.

    I got a bad packet...
    ...*

    ... It's so true to life it's hardly true.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!