Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!VCUVAX.BITNET!LANGFORD
From: LANGFORD@VCUVAX.BITNET (Bob Langford)
Newsgroups: comp.os.vms
Subject: VMS Mail from DECNET task
Message-ID: <8705020504.AA01063@ucbvax.Berkeley.EDU>
Date: Wed, 29-Apr-87 16:00:00 EDT
Article-I.D.: ucbvax.8705020504.AA01063
Posted: Wed Apr 29 16:00:00 1987
Date-Received: Sun, 3-May-87 04:33:34 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 13

I think the "problem" is MAIL; it behaves differently when in NETWORK mode.

The MAIL program checks to see if it is being run as a network task; if so, it
assumes that it is supposed to deliver a message to the machine it's on from a
remote system.  It then copies the message sent from the originating system,
and does the delivery.  This is a tricky way of not having two images for MAIL.
If you read the source code for mail, you'll see several references to things
like this, including the /PROTOCOL qualifier, whose effect I haven't figured
out yet.

If you copied something TO the task you have been testing with, you might find
it MAILed to some place on the receiving system, but probably not unless you
got the format of the data just right....