Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!SLACTWGM.BITNET!ESMP09
From: ESMP09@SLACTWGM.BITNET (Ed Miller SLAC x3291 or [415]854-1055)
Newsgroups: comp.os.vms
Subject: Re: Sending mail from a remote DECnet task (Problems)
Message-ID: <8704291847.AA15479@jade.berkeley.edu>
Date: Wed, 29-Apr-87 14:41:00 EDT
Article-I.D.: jade.8704291847.AA15479
Posted: Wed Apr 29 14:41:00 1987
Date-Received: Sun, 3-May-87 04:30:36 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 23

Ian MacPhedran inquires about the following problem:

> I have a DECnet task running asynchronously which I would like to
> monitor indirectly (i.e. not typing NETSERVER.LOG to see if it's
> one yet, or SHOW PROC, etc.) by having it send me mail. However,
> the mail message does not come through, nor is an error generated.

I believe that the cause of your difficulty is that MAIL.EXE,
when it sees that it is running as a network job, assumes that
its mission is to support requests from remote nodes to deliver
mail to addresses on the local node.  See, for instance,
SYS$SYSTEM:MAIL.COM, which supports this mode of operation.

I too encountered this problem.  The only work-around I found
was to replace the MAIL command in my similar network task with
a SPAWN command which executed the desired MAIL command.
The specific format of the command I use is

  $ SPAWN/NOLOG/NOSYMBOLS/NOLOGICAL/INPUT=NLA0:/OUTPUT=NLA0:  -
     MAIL/SUBJ="subject text" nla0: address

                                Ed Miller
                                ESMP09@SLACTWGM.BITNET