-={ 2016-11-20 02:13:11.216738384+00:00 }=-

Hey Fearless!

This should be an old school fidonet msg with an interesting twist ...
or so the story goes. If it works out and finds it's way past any and
all {cripple,abandon}ware between here and here then there should be a
space at the end of the so-called end of lines except where we actually
want an end of line and in that case there should be no space.

Here is a second paragraph ... or is and will be a second paragraph to
a text editor that is capable of proper word wrapping.

We shall soon see.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.4.0(1)-release (x86_64-silvermont-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice,

On 20 Nov 16 02:13, Maurice Kinal wrote to Fearless Lee:

@MSGID: 1:153/7001 583106b7
-={ 2016-11-20 02:13:11.216738384+00:00 }=-

Hey Fearless!

This should be an old school fidonet msg with an interesting twist ...
or so the story goes. If it works out and finds it's way past any
and all {cripple,abandon}ware between here and here then there should
be a space at the end of the so-called end of lines except where we actually want an end of line and in that case there should be no
space.

Here is a second paragraph ... or is and will be a second paragraph to
a text editor that is capable of proper word wrapping.

We shall soon see.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.4.0(1)-release (x86_64-silvermont-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001) SEEN-BY: 123/500 153/7001 154/10 30 700 203/0 221/6 227/201 280/464 340/800
@PATH: 154/10

Looks okay, but you seem to have sent this one directly through my system. Are you hard wrapping in this original message? If not, something on my end is altering it.

I can't see this as possible, though.. as Mark Lewis's messages are arriving here without any kind of hard wrapping, and I am not doing any specific hard wrapping here either on what I type. My current putty window's width is 160, and while your message seemed to be formatted in less than 80 columns, what I'm
writing right now is using all 160. Every message that I read from Mark is also
using all 160 columns.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

-={ 2016-11-20 10:13:46.072466282-06:00 }=-

Hey Nicholas!

Are you hard wrapping in this original message?

The one you are replying to yes. I thought I'd try it to see if I recieved it with the special spaces intact at this end. Unfortunetly it never made it and is still MIA along with many others. :-/

Anyhow I don't think it is you that is causing the oddball hard wraps I see in the messages that do make it through. Beats me where it is happening and I am giving up trying to figure out a proper 'fix' for it.

For the record this reply is via the 'normal' channel and isn't being wrapped.
All paragraphs are unbounded as per specs for packed messages.

Life is good,
Maurice

... Wiþ swiþe mænige biternesse is gemenged seo swetnes þisse worulde.
With much bitterness is mingled the sweetness of this world.
--- GNU bash, version 4.4.0(1)-release (x86_64-atom-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice,

On 20 Nov 16 16:13, Maurice Kinal wrote to Nicholas Boel:

The one you are replying to yes. I thought I'd try it to see if I recieved it with the special spaces intact at this end. Unfortunetly
it never made it and is still MIA along with many others. :-/

Anyhow I don't think it is you that is causing the oddball hard wraps
I see in the messages that do make it through. Beats me where it is happening and I am giving up trying to figure out a proper 'fix' for
it.

For the record this reply is via the 'normal' channel and isn't being wrapped. All paragraphs are unbounded as per specs for packed
messages.

@PATH: 153/7001 7715 250 770/1 280/464 154/10

This one arrived here hardwrapped. I'm fairly certain 770/1 (FastEcho) is not doing this, and am certain it's not 280/464 (FMail) or 154/10 (me, HPT), so you
have 2 other prospects. You may want to try your direct uplink (153/7715, or maybe even 153/250) and see what BBS software package they're using (In my experience with this, it's usually an old BBS software that does this, unless a
tosser is specifically configured to do so).

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

-={ 2016-11-20 12:09:56.225151751-06:00 }=-

Hey Nicholas!

This one arrived here hardwrapped.

Yep. I double checked the original and it is unwrapped as it should be. It is
being altered somewhere in between here and there. :-/

Life is good,
Maurice

... Yldo beoð on eorðan æghwæs cræftig.
Old age has power over everything on earth.
--- GNU bash, version 4.4.0(1)-release (x86_64-atom-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice,

On 20 Nov 16 18:09, Maurice Kinal wrote to Nicholas Boel:

This one arrived here hardwrapped.

Yep. I double checked the original and it is unwrapped as it should
be. It is being altered somewhere in between here and there. :-/

I mentioned elsewhere who the culprits most likely are, as I've had many dealings with the other three systems involved and haven't seen that problem before. If you care enough to do so, I'm sure you can get it all squared away.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

20 Nov 16 16:13, you wrote to Nicholas Boel:

@MSGID: 1:153/7001.0@fidonet 5831cbba
@REPLY: 1:154/10 5831c532
-={ 2016-11-20 10:13:46.072466282-06:00 }=-

Hey Nicholas!

Are you hard wrapping in this original message?

The one you are replying to yes. I thought I'd try it to see if I

recieved

it with the special spaces intact at this end. Unfortunetly it never made it and is still MIA along with many others. :-/

it is possible that your post was added to another packet that had messages from a system that is not setting the packed messages datetime stamp properly..
it was setting them to all nulls and some tossers were stopping processing the packet at that point... valid messages after the malformed one were just left behind lost in the bucket...

Anyhow I don't think it is you that is causing the oddball hard wraps
I see in the messages that do make it through. Beats me where it is happening and I am giving up trying to figure out a proper 'fix' for
it.

it can be an interesting exercise... especially when you also get involved with
systems that use and recognise the "softCR" character (0x8d)... that character has real meaning in other languages and is generally ignored... it may also be followed by linefeeds but since linefeeds are ignored they shouldn't really matter... in fact, FTS-0001 says that systems which display message text should
wrap long lines to suit the application... basically, even hard wrapped posts can be "unwrapped" so the text can be displayed taking the full width of the application's display viewport...

For the record this reply is via the 'normal' channel and isn't being wrapped. All paragraphs are unbounded as per specs for packed messages.

something in the path below wrapped it in transmission, then... it arrived here
hard wrapped to fit an 80 column viewport :(

Life is good,
Maurice

... Wiþ swiþe mænige biternesse is gemenged seo swetnes þisse worulde.
With much bitterness is mingled the sweetness of this world.
--- GNU bash, version 4.4.0(1)-release (x86_64-atom-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001) SEEN-BY: 1/10 146 11/0 1 25/8 57/0 1 73/0 1 100/200 111/1 120/229 301 323 SEEN-BY: 120/419 481 544 545 546 640 123/57 500 130/505 153/250 154/10 199/0
SEEN-BY: 199/1 200/1 203/0 220/10 226/70 301 350 227/51 60 400 240/1661 SEEN-BY: 249/303 250/3 280/464 5003 310/31 317/2 340/200 352/0 3 393/68 SEEN-BY: 712/848 770/0 1 100 340 772/0 1 777/7 863/100 101 902/508 2215/15 SEEN-BY: 2215/300 2320/100 3634/12 15 22 24 27 50 4975/301 5075/35
@PATH: 153/7001 7715 250 770/1 280/464 227/51 120/544 3634/15 12

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... My new Special Friend... @FN@!
---
* Origin: (1:3634/12.73)

-={ 2016-11-20 13:31:12.928982824-06:00 }=-

Hey Nicholas!

I mentioned elsewhere who the culprits most likely are

Yes you did.

I have no plans to try and get whomever to alter their system.

I do have plans to alter mine very soon.

Life is good,
Maurice

... Wyrd bið ful aræd.
Fate is greatly fixed.
--- GNU bash, version 4.4.0(1)-release (x86_64-atom-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

-={ 2016-11-20 14:42:40.765342696-05:00 }=-

Hey mark!

something in the path below wrapped it in transmission

Yes.

Life is good,
Maurice

... Cyning sceal on healle beagas dælan.
A king in the hall should deal out rings.
--- GNU bash, version 4.4.0(1)-release (x86_64-atom-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)