DB> What about a test - if the "area" after "AREA:"
is not a known
DB> valid area name, then assume it's normal message text and
DB> therefore a netmail message.

BL>   The problemn is that the writer can do it maliciously. He has access
BL> to what may be a control line in netmail if he is not a point. This
BL> only applies to a rogue sysop therefore.

No, it doesn't apply to rogue sysops, as the sysop is already
responsible for all the messages leaving his system.  It only
applies to rogue users of a system.

You really don't understand this simple concept, do you?  There
are system operators, who are responsible for the technical 
integrity of the PKTs they send to other system operators.  Then
there are BBS users who have no concerns about technical integrity,
they just log on to a BBS, type "get fucked" and anything else they
want to, and they run the SYSOP's software to generate the PKT, 
they have no input into what technology is used, they only get to
specify the user-text portion.

YOU are responsible for the software that generates PKTs, and
failure to do that successfully means you don't get to feed
mail to/from me (I get rid of the secure session).  The same
happens to me if I start sending crap to Dave, I will be told
to feed elsewhere.

DB> Netmail messages don't have "SEEN-BY" lines

BL>   Good thought, but messages from points to their boss don't have
BL> "SEEN-BY". They do have a #1FMPT line, though, so they can't type 
BL> "AREA:" in the first line.

BL>   Netmail also don't have an Tear or Origin line, but Paul has already
BL> stipulated that these are missing (SOT is present, however).

Of course they are missing from netmail.  But they can be added
by the netmail author, being normal ASCII text, as distinct from
control lines.  BFN.  Paul.
@EOT:

---