Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!DUKEMC!DMPM
From: DMPM@DUKEMC (James Dryfoos- PostMaster)
Newsgroups: bit.listserv.pmdf-l
Subject: More on the <not username problem.
Message-ID: <EA3ADD7D44BF00262B@dukemc>
Date: 27 Jan 90 00:25:00 GMT
Sender: PMDF Distribution List <PMDF-L@IRLEARN>
Reply-To: PMDF Distribution List <PMDF-L@IRLEARN>
Lines: 24
Approved: NETNEWS@PSUVM Gateway
Errors-to: postmast@YMIR.BITNET
Errors-to: James Dryfoos- PostMaster <DMPM@DUKEMC.BITNET>
X-Organization: Duke University Medical Center - Durham NC, USA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
Comments:     Warning -- RSCS tag indicates an origin of POSTMAST@YMIR
X-To:         ipmdf@YMIR

I have narrowed down the problem I have been having with username
in the from address being "<not"@dukemc.  Before
I installed PMDF 3.1 I created a program which uses a
homebrew channel to do some mail stuff.  My program
runs on a batch queue and sends mail on users behalf.
I used the symbol FROM the change the from address
of the mail message.  After this problem began, I reread
the doc and saw I could use the logical PMDF_FROM to
change the from address and it creates a sender: line --
I like this better.  I now do this.  Now the outgoing mail
has a From: address of what I put in PMDF_FROM and
this works fine.  However, the sender line still shows the
previous problem.  The sender: line has "<not"@DUKEMC in it.
So it seems I just moved the problem.  I have done a lot of testing
and when I do the same manually (not in a batch job), all works
correctly.  I am now suspecting that the problem is related to
my program running on the queue (this worked fine for PMDF 3.0).
The program runs on a queue and spawns a process which executes
a com file that defines pmdf_from and mail the file using vms mail.

Does anyone have any ideas?  At least I got mail going out in
an acceptable manner.

-Jim Dryfoos