[bit.listserv.pmdf-l] More on the <not username problem.

DMPM@DUKEMC (James Dryfoos- PostMaster) (01/27/90)

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

NED@HMCVAX.CLAREMONT.EDU (Ned Freed, Postmaster) (01/27/90)

I still cannot narrow down the problem here. It has to be something corrupting
the envelope From: address PMDF is getting from VMS MAIL. Failing that, it
would have to be a rewrite rule problem -- perhaps the rule that would apply
to the correct From: address on these messages is not correct.

I would suggest enabling master_debug on the local channel and trying your
batch job and then looking at the log. Warning -- when master_debug is
enabled all users of VMS MAIL will get a lot of crap tracing out on their
screens as messages are sent. So be careful about leaving it enabled for
long periods of time (I usually do it on a separate machine that uses
a separate configuration file, but then again I have resources to work on
problems like this...).

The sender address is directly extracted from the From: line PMDF gets from
VMS MAIL. There's a messy rewrite processes these addresses undergo; I suppose
it is possible that is messed up. But why would it only happen on this special
channel? That is hard to figure.

Hope this helps (but it probably won't help much).

                        Ned