@MSGID: 1:3634/12.73 5cab6502
@PATH: 3634/12 154/10 280/464
@PATH: 3634/12 261/38 712/848 770/1
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.
If Mystic is doing that (and it looks like it does), I'm sure thatbehavior
can be changed. Mystic is designed for an 80x25 terminal, so it'ssomething
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 anythin
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 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...
Sysop: | Ruben Figueroa |
---|---|
Location: | Mesquite, Tx |
Users: | 3 |
Nodes: | 4 (0 / 4) |
Uptime: | 169:39:56 |
Calls: | 77 |
Files: | 50 |
Messages: | 72,826 |