1. AST bouncer
2. mail loops
3. unprintable chars on latsymb vms v5
   1. AST bouncer... intercepts at vms ast delivery code and checks
to see if it's a delete process ast for a wellknown process or its
children. If so, unqueue ast, reverse src and dest, requeue it to
the original sender. Effect is stop/id=xxxx on the protected process
amounts to stop/id on process trying to do the stop on the protected
proc.
   2. mail loops... assume decnet as follows:
node a:
address 2.1
address 2.2 name FOO
address 2.3 name BAR
address 2.1 name A

node b:
address 2.2
node 2.3 name FOO
node 2.1 name BAR
node 2.2 name B

node c:
address 2.3
node 2.1 name FOO
mode 2.2 name BAR
node 2.3 name C

now on any node have a user SET FORWARD FOO::user
   Send mail to that user & loop never stops.


3. Unprintable mail.
   LAT symbiont in VMS V5 is integrated with print symbiont. The method
of telling the lat symbiont to exit is a couple magic characters in
the data stream. Put those chars in a file and it can't be printed
since the LAT symbiont will exit. (of course, can print on non lat printers
but this could be most embarrassing.)

4. forcex on STS process
   Leave process around but with no image to handle intra-cluster lock
traffic. Result: filesystems start to rot. Sometimes VERY fast.