TIP: Click on subject to list as thread! ANSI
echo: msged_echo
to: Ronald Hoekstra
from: andrew clarke
date: 1997-02-18 00:27:16
subject: schema

14 Feb 97 13:07, Ronald Hoekstra wrote to Paul Edwards:

 > At Feb 12 you wrote about "schema" a.o.:

 >> {at}PID: Msged/2 4.2.b1
 >> {at}SOT:
 >> {at}EOT:

 > Seems to me that there's a minor problem with some kludges... Your 
 > message starts with the PID, than the SOT, immediately followed by an 
 > EOT?

It appeared here as follows:

{at}PID: Msged/2 4.2.b1
{at}SOT:
Does anyone have a schema to match the old default colours?  BFN.  Paul. {at}EOT:

---
SEEN+BY: 50/99 54/99 270/101 620/243 632/360 635/544 728 670/218 711/401
SEEN+BY: 711/413 430 934 712/407 505 517 623 624 713/317 714/906 800/1
{at}PATH: 711/934 712/624 50/99 635/728

What you're experiencing is normally attributed to storing your messages in
JAM format, but since Msged doesn't currently support JAM message bases
that pretty much rules that theory out.  I can only assume Paul's message
was damaged in-transit.  A rescan of a JAM base could have caused this, or
perhaps a broken packet sorter or mail processor.

Regards
Andrew

-- randy{at}zws.com

--- Msged/2 4.20 beta 2

--- Squish/386 v1.11
* Origin: X (3:711/934.9)
* Origin: Blizzard of Ozz, Melbourne, Australia (3:635/728.4{at}fidonet)
* Origin: Blizzard of Ozz, Melbourne, Australia (3:635/728.4)
SEEN-BY: 50/99 54/99 270/101 620/243 632/360 635/544 728 670/218 711/401 413
SEEN-BY: 711/430 934 712/407 505 517 623 624 713/317 714/906 800/1
@PATH: 635/728 50/99 712/624 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.