Hi mark and Maurice

On 2019-04-08 11:05:16, you wrote to Sean Dennis:

@MSGID: 1:3634/12.73 5cab6502

I got this message through 2 paths (so far):

@PATH: 3634/12 154/10 280/464
@PATH: 3634/12 261/38 712/848 770/1

Both contained "long" lines, that didn't have CR inserted. So we can rule out 770/1 as the one doing the reformatting.


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

I got this message through 2 paths (so far):

@PATH: 3634/12 154/10 280/464
@PATH: 3634/12 261/38 712/848 770/1

Both contained "long" lines, that didn't have CR inserted. So we can rule out 770/1 as the one doing the reformatting.

That's good to know, I didn't think FE would do that.

Paul and I are going to do some testing, feed Mystic some input and have a look
at the output. Then we can get the facts to James.

If Mystic is doing that (and it looks like it does), I'm sure that behavior can
be changed. Mystic is designed for an 80x25 terminal, so it's something a Mystic operator would never notice. I never noticed myself since my terminal is
80x30.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 2019 Apr 08 12:11:18, you wrote to Wilfred van Velzen:

If Mystic is doing that (and it looks like it does), I'm sure that

behavior

can be changed. Mystic is designed for an 80x25 terminal, so it's

something

a Mystic operator would never notice. I never noticed myself since my terminal is 80x30.

the main thing is that no software should /ever/ modify the message text... it should only add to the seenbys and the path line... mucking about with anything
else in the message being processed before packing to other systems is BadJuJu<tm> and highly frowned upon...

software can do whatever it wants to to messages stored in its message base and
displayed to its users... rescans of these messages will result in them being different than the originals when inspected at the packet level... with this in
mind, there really is no need for software to mess about with the messages at all... let the users' terminals determine where the wrap takes place... not adding, stripping, or altering characters anywhere in a message (other than the
few specified places) is ultimately the best thing...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... May all your teeth but one fall out and from the one, eternal toothache. ---
* Origin: (1:3634/12.73)

the main thing is that no software should /ever/ modify the message text... it >should only add to the seenbys and the path line... mucking about with anythin
else in the message being processed before packing to other systems is BadJuJu<tm> and highly frowned upon...

Yep, this is the important part.

software can do whatever it wants to to messages stored in its message base an
displayed to its users... rescans of these messages will result in them being
different than the originals when inspected at the packet level... with this i
mind, there really is no need for software to mess about with the messages at all... let the users' terminals determine where the wrap takes place... not
adding, stripping, or altering characters anywhere in a message (other than th
few specified places) is ultimately the best thing...

I haven't seen James around since he released A43 a short time ago.

He is quiet when RL gets in the way but in the mean time Paul and I will try to
package the above in a quick and easy way for him to see.

I know that echomail is a priority in Mystic's development so I think he'll work on that once he learns of it.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)