• Re: > 255 character long lines (paragraphs)

    From Ryan Fantus@1:229/2 to All on Wednesday, April 01, 2020 01:57:00
    From: nospam.Ryan.Fantus@f820.n218.z1.binkp.net

    I wonder if newer versions of Mystic cut all long lines (paragraphs)
    after 255 characters. So I'm writing some more words until I reach 256 chars to test, if this is really the case. Bla bla bla bla .... If I'm right, this line should be cut off right now. If I'm wrong, you still
    can read this.

    I don't have the /latest/ prealpha but have a relatively recent one.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Oli@1:229/2 to All on Wednesday, April 01, 2020 10:15:56
    From: nospam.Oli@p47.f464.n280.z2.binkp.net

    I wonder if newer versions of Mystic cut all long lines (paragraphs) after 255 characters. So I'm writing some more words until I reach 256 chars to test, if this is really the case. Bla bla bla bla .... If I'm right, this line should be cut off right now. If I'm wrong, you still can read this.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Tony Langdon@1:229/2 to Oli on Wednesday, April 01, 2020 21:39:00
    From: nospam.Tony.Langdon@f1.n770.z1300.fidonet.org

    On 04-01-20 10:15, Oli wrote to All <=-

    I wonder if newer versions of Mystic cut all long lines (paragraphs)
    after 255 characters. So I'm writing some more words until I reach 256 chars to test, if this is really the case. Bla bla bla bla .... If I'm right, this line should be cut off right now. If I'm wrong, you still
    can read this.


    * Origin: kakistocracy (2:280/464.47)

    Looks like it all came through. :)


    ... This tagline provided free of charge. Taxes may apply.
    === MultiMail/Win v0.51

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Oli@1:229/2 to you on Wednesday, April 01, 2020 13:17:26
    From: nospam.Oli@p47.f464.n280.z2.binkp.net

    01 Apr 20 01:57, you wrote to me:

    I wonder if newer versions of Mystic cut all long lines
    (paragraphs) after 255 characters. So I'm writing some more words
    until I reach 256 chars to test, if this is really the case. Bla
    bla bla bla .... If I'm right, this line should be cut off right
    now. If I'm wrong, you still can read this.

    I don't have the /latest/ prealpha but have a relatively recent one.

    My suspicion is that it started with 2020/03/26 and it might even be fixed in the latest pre-alpha 2020/03/29. There is one Hub in fsxnet that is running this version, the others running 2020/03/12 and are still wrapping the long lines at 79 characters.

    I'm not using Mystic, but people discovered that they receive dupes of my mails and one copy of my mails has paragraphs that are cut at character 255. I think that we tracked the problem down to the hub running 2020/03/26.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Bud Spencer@1:229/2 to Oli on Wednesday, April 01, 2020 22:29:09
    From: bud@campo.verano.it

    On Wed, 1 Apr 2020, Oli wrote:

    I wonder if newer versions of Mystic cut all long lines (paragraphs) after
    255
    characters. So I'm writing some more words until I reach 256 chars to test,
    if
    this is really the case. Bla bla bla bla .... If I'm right, this line should
    be
    cut off right now. If I'm wrong, you still can read this.

    Yeah. Happens outside of the BBS-realm:

    https://i.imgur.com/CfayWxW.png

    I have 80 x 25-and-over terminals.

    This is from Alpine running on FBSD goodness ...

    But as you see, bad behaviours is easily rehabilated just by replying :D



    /
    Bud
    /

    a1=S0
    b1=[1..2,'L0L']
    a2=2*a1
    a3=S1.4#b1
    a4=(a2,a3)
    a5=64*a4

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From mark lewis@1:229/2 to All on Wednesday, April 01, 2020 09:58:14
    From: nospam.mark.lewis@f1.n770.z842.fidonet.org

    Re: > 255 character long lines (paragraphs)
    By: Oli to All on Wed Apr 01 2020 10:15:56

    I wonder if newer versions of Mystic cut all long lines (paragraphs) after 255 characters. So I'm writing some more words until I reach 256 chars to t, if this is really the case. Bla bla bla bla .... If I'm right,
    this line should be
    cut off right now. If I'm wrong, you still can read this.

    i've not wrapped the above but yes, the long line is broken in two between "be" and "cut" as you can see above... my terminal window is 226 columns wide...


    )\/(ark

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Oli@1:229/2 to Bud Spencer on Thursday, April 02, 2020 08:02:02
    From: nospam.Oli@p47.f464.n280.z2.binkp.net

    01 Apr 20 22:29:09, Bud Spencer wrote to Oli:

    I wonder if newer versions of Mystic cut all long lines (paragraphs) after
    255
    characters. So I'm writing some more words until I reach 256 chars to test,
    if
    this is really the case. Bla bla bla bla .... If I'm right, this line should
    be
    cut off right now. If I'm wrong, you still can read this.

    Yeah. Happens outside of the BBS-realm:

    https://i.imgur.com/CfayWxW.png

    I have 80 x 25-and-over terminals.

    This is from Alpine running on FBSD goodness ...

    But as you see, bad behaviours is easily rehabilated just by replying :D

    That looks like it went through Mystic, which applies word wrapping at column 79 (adding CRs) and then the nntp gateway or alpine wraps the lines again. That is a known thing with Mystic, but it looks like something changed in the pre-alpha from 2020/03/26 and lines (=paragraphs in ftn) now get truncated after 255 characters. I'm not saying I'm 100% confident about it, it is just what our limited data suggests (we did some tests in fsxnet).

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Oli@1:229/2 to mark lewis on Thursday, April 02, 2020 10:06:10
    From: nospam.Oli@p47.f464.n280.z2.binkp.net

    01 Apr 20 09:58:14, mark lewis wrote to Oli:

    I wonder if newer versions of Mystic cut all long lines (paragraphs) after
    255 characters. So I'm
    writing some more words until I reach 256 chars to test, if this is really
    the case. Bla bla bla bla
    .... If I'm right, this line should be cut off right now. If I'm wrong, you
    still can read this.

    i've not wrapped the above but yes, the long line is broken in two between "be" and "cut" as you can
    see above... my terminal window is 226 columns wide...

    Thanks for the replies guys.

    I think I haven't provided enough informations in my mail.

    With cut after 255 characters I mean that everything from character 256 just vanishes into digital nirvana, it's not there anymore. I think truncated is the better word. It seems to happen when a mail passes through Mystic pre-alpha from 2020/03/26 and maybe versions after that (unknown).

    Everyone else who doesn't have a Mystic node with that version in their path or running that version themself should see my messages intact :).

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From g00r00@1:229/2 to All on Friday, April 03, 2020 02:13:32
    From: nospam.g00r00@f215.n129.z1.binkp.net

    My suspicion is that it started with 2020/03/26 and it might even be
    fixed in th e latest pre-alpha 2020/03/29. There is one Hub in fsxnet
    that is running this v ersion, the others running 2020/03/12 and are
    still wrapping the long lines at 7 9 characters.

    There have been two versions of the tosser one that word wraps and one that doesn't since February, so the date itself wouldn't be a factor it would
    depend on which tosser they are using.

    Sometime during A46 in March I removed the optional non-wrapping tosser and
    now its the only tosser available.

    They shouldn't be getting cut off at 256 characters, the line length is unlimited (or at least that is the intention) with the latest pre-alpha. If you find otherwise please let me know because that would be a bug.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Paul Hayton@1:229/2 to All on Saturday, April 04, 2020 14:09:33
    From: nospam.Paul.Hayton@f100.n770.z3.binkp.net

    On 03 Apr 2020 at 02:13a, g00r00 pondered and said...

    They shouldn't be getting cut off at 256 characters, the line length is unlimited (or at least that is the intention) with the latest pre-alpha. If you find otherwise please let me know because that would be a bug.

    What I'll work to do is update all three HUBs running Mystic to the latest pre-alpha so everything is on the same playing field. Then we can see what's happening and let you know. Cheers.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Al@1:229/2 to All on Friday, April 03, 2020 12:28:22
    From: nospam.Al@f757.n153.z1.binkp.net

    Hello g00r00,

    They shouldn't be getting cut off at 256 characters, the line length
    is unlimited (or at least that is the intention) with the latest pre-alpha. If you find otherwise please let me know because that
    would be a bug.

    That does seem to be the case currently. I've seen it in my own testing and it's happened to a few messages in fsxNet.

    Ttyl :-),
    Al

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Oli@1:229/2 to you on Saturday, April 04, 2020 08:14:40
    From: nospam.Oli@p47.f464.n280.z2.binkp.net

    04 Apr 20 14:09, you wrote to g00r00:

    On 03 Apr 2020 at 02:13a, g00r00 pondered and said...

    They shouldn't be getting cut off at 256 characters, the line
    length is unlimited (or at least that is the intention) with the
    latest pre-alpha. If you find otherwise please let me know
    because that would be a bug.

    What I'll work to do is update all three HUBs running Mystic to the
    latest pre-alpha so everything is on the same playing field. Then we
    can see what's happening and let you know. Cheers.

    Now everything's really messed up in fsxnet. I told you so ;)

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Oli@1:229/2 to you on Friday, April 10, 2020 17:04:23
    From: nospam.Oli@p47.f464.n280.z2.binkp.net

    10 Apr 20 14:18, you wrote to Paul Hayton:

    Hi Paul,

    On 2020-04-10 14:13:52, I wrote to you:

    @MSGID: 3:770/100 651d79ff

    @PATH: 770/100 1 317/3 229/426 292/854 261/38 801/189 188
    292/854

    Or is this a hickup on that system that shows up twice in the
    path?

    It was. I noticed there already was a message in this area with the
    above MSGID... Sorry for the noice. ;)

    Interesting. At least two nodes in fsxnet received bad packages with scrambled messages. The origin line of 292/854 were in the To, From or Subject field. There were also some empty messages in this area with 2:292/854 in the origin line, but otherwise completely empty. But how do we know that 292/384 is causing the problems? It could be 261/38 too (less likely though).

    Btw, 4:801/189, which is in the path between 2:292/854 and 2:292/854, is running an older version of Mystic that
    - writes incorrect SEEN-BY lines
    - ignores SEEN-BYs
    - modifies mails in-transit (line breaking)
    - doesn't recognized modified and unmodified mails with the same MSGID as dupes.

    Using something like this with fidoweb-style echo routing has to create some problems at some point. Like loops and dupes.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Wilfred van Velzen@1:229/2 to you on Friday, April 10, 2020 14:13:52
    From: nospam.Wilfred.van.Velzen@f464.n280.z2.binkp.net

    *** Answering a msg posted in area BAD_MSGS.

    Hi Paul,

    On 1980-01-01 00:00:00, you wrote to and:

    Hmmm... :-(

    AREA:MYSTIC
    @FMAIL BAD: Message too old (2020-04-10 14:10:26)
    @FMAIL SRC: 2:292/854
    @FMAIL DEST: 2:280/464
    @TID: Mystic BBS 1.12 A46
    @MSGID: 3:770/100 651d79ff
    @REPLY: 1:129/215 5faf9ad6
    @TZUTC: 1300
    @DATE: 00 00 03:00:00
    On 03 Apr 2020 at 02:13a, g00r00 pondered and said...

    [...]

    --- Mystic BBS v1.12 A46 2020/03/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100) SEEN-BY: 203/0 221/1 229/426 261/38 280/464 292/140 854 8125 335/364 SEEN-BY: 801/188 189 190 194 197
    @PATH: 770/100 1 317/3 229/426 292/854 261/38 801/189 188 292/854

    Or is this a hickup on that system that shows up twice in the path?

    Bye, Wilfred.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Wilfred van Velzen@1:229/2 to All on Friday, April 10, 2020 14:18:02
    From: nospam.Wilfred.van.Velzen@f464.n280.z2.binkp.net

    Hi Paul,

    On 2020-04-10 14:13:52, I wrote to you:

    @MSGID: 3:770/100 651d79ff

    @PATH: 770/100 1 317/3 229/426 292/854 261/38 801/189 188 292/854

    Or is this a hickup on that system that shows up twice in the path?

    It was. I noticed there already was a message in this area with the above MSGID... Sorry for the noice. ;)

    Bye, Wilfred.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From John Smith@1:229/2 to All on Friday, April 10, 2020 13:54:40
    From: nospam.John.Smith@f757.n153.z1.binkp.net

    Hello g00r00,

    They shouldn't be getting cut off at 256 characters, the line length
    is unlimited (or at least that is the intention) with the latest pre-alpha. If you find otherwise please let me know because that
    would be a bug.

    This is indeed the case. I did some testing yesterday with..

    Mystic BBS v1.12 A46 Linux/64 Compiled 2020/04/09 22:56:56.

    Please let us know if you would like further testing/input.

    Ttyl :-),
    Al

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Wilfred van Velzen@1:229/2 to you on Friday, April 10, 2020 18:06:08
    From: nospam.Wilfred.van.Velzen@f464.n280.z2.binkp.net

    Hi Oli,

    On 2020-04-10 17:04:23, you wrote to me:

    Interesting. At least two nodes in fsxnet received bad packages with scrambled messages. The origin line of 292/854 were in the To, From or Subject field. There were also some empty messages in this area with 2:292/854 in the origin line, but otherwise completely empty. But how do we
    know that 292/384 is causing the problems? It could be 261/38 too (less likely though).

    It happend when 2:292/854 reset his PC earlier this week when he returned from the hospital, that caused some problematic pkts to be exported from his system. Today there was another event with the same symptoms. This happend before several times when he returned from his holidays in the states for example...

    Using something like this with fidoweb-style echo routing has to
    create some problems at some point. Like loops and dupes.

    Some are caught on my system when they have an older date (like >60 days). And dupes are of course also caught. Everything else that is more or less a legit message (although from:, subject: and body are empty for instance) passes through... But this caused irex to crash on one of my downlinks.

    Bye, Wilfred.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Oli@1:229/2 to All on Saturday, April 11, 2020 08:10:29
    From: nospam.Oli@p47.f464.n280.z2.binkp.net

    This is indeed the case. I did some testing yesterday with..

    Mystic BBS v1.12 A46 Linux/64 Compiled 2020/04/09 22:56:56.

    Please let us know if you would like further testing/input.

    Ttyl :-),
    Al

    what happened to the subject and your name?

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From g00r00@1:229/2 to All on Sunday, April 12, 2020 00:04:25
    From: nospam.g00r00@f215.n129.z1.binkp.net

    This is indeed the case. I did some testing yesterday with..

    Mystic BBS v1.12 A46 Linux/64 Compiled 2020/04/09 22:56:56.

    Please let us know if you would like further testing/input.

    Thanks for letting me know.

    I have uploaded a 4/11 version which should/may address this issue. I found a function that was using an old 255 character string type, so the line of text was accidentally getting cut off when passed to that function.

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From Al@1:229/2 to All on Saturday, April 11, 2020 12:52:46
    From: nospam.Al@f757.n153.z1.binkp.net

    Hello Oli,

    what happened to the subject

    I'm not sure why suject lines get a little mixed up. It might be a slackware thing but I haven't been able to figure out why that happens.

    and your name?

    I haven't had any replies so I'm just trying to be sure my mail got through since it was in important feedback.

    Ttyl :-),
    Al

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)