HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"cvm@NAUVAX.UCC.NAU.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 18 Nov 92 20:54:05 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Bad return address
Newsgroups: bit.listserv.pmdf-l

> I have a problem with MS-Mail not using the correct address when
> replying to a message from a POP3 client whose mail address is on our
> VAX.  I have a copy of the queued message on the VAX before it gets sent
> to the MS-Mail system.  All other machines that the POP client sends to,
> reply to CVM@NAUVAX.UCC.NAU.EDU.  The MS-Mail system replies to
> CVM@PC19.UCC.NAU.EDU.  Before I go to Microsoft or the MS-Mail
> discussion list, I need to know is what the first line in this file is
> used for.  That is the line that says:
>
> m;cvm@pc19.ucc.nau.edu

This first line is the envelope From: address.  The lines immediately following
it up until the control A's are the envelope To: addresses.  In the SMTP session
this information is used in the MAIL FROM and RCPT TO commands; e.g.,

  HELO xxxx
  MAIL FROM:<cvm@pc19.ucc.nau.edu>
  RCPT TO:<cvm@msmail.ucc.nau.edu>

> What does PMDF use this for when communicating with the MS-Mail
> SMTP gateway?  Here is the queued message that causes the problem:

Now, I have no idea what MS-Mail is doing with the envelope From: address.  I
could conjecture all sorts of things, but they'd be merely conjectures.  You
need to find out from the MS-Mail discussion list what MS-Mail uses for a
reply address.  It probably has some sort of precedence list (i.e., first
choice is Resent-reply-to:, second choice Resent-From:, third Reply-to:, etc.)
I've seen all sorts of behavior: some just plain wrong (e.g., using the
envelope From: address as the reply address; building a Reply-to: address out
of the envelope From: address) and others not as black-and-white wrong but
certainly not in alignment with common practice (e.g., using a Return-path:
address preferentially over a From: address; the Return-path: address is
built by the final transport system which delivers the mail to the recipient;
it is usually built from the envelope From: address).

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SUE@A1.PSUPEN.PSU.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 14:51:32 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Errors in MAILSERV command processing
Newsgroups: bit.listserv.pmdf-l

This is almost certainly a problem with the definition of the
PMDF_MAILSERV_MAIL_DIR logical name. Check the definition and make sure
it points at a valid directory containing the .DIS files for your various
mailing lists. You should also enable master_debug and check out the
processing log for the mailserv channel to track these sorts of things
down more precisely.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Native address: <MAILMAIN@EMDUAM11.BITNET>
Date:         Mon, 23 Nov 92 12:33:29 HOE
From:         "Postmaster de la UAM." <MAILMAIN@VM1.SDI.UAM.ES>
Subject:      Help with Pmdf vers. 4.0
Newsgroups: bit.listserv.pmdf-l

  My name is Jesus Barreiro and I work as Postmaster in the UAM.ES domain.
We have recently upgraded our Pmdf version to 4.0 and I have a problem with
modifying the Return batch job.
  As default Pmdf sends notices to mails that are 3,6,9 and 12 days old. In
previous version it was quite easy to modify the return.com to change it to ano
ther set-up but in this version I haven't found where to change this set-up.
     Does anybody know where I can modify this ?
 Thank you very much in advance
              yours faithfully
                        Jesus Barreiro

*----------------------------------------------------------------------
*|                   --------------------                             |
*|                   |The UAM Postmaster|                             |
*|                   |postmaster@uam.es |                             |
*|                   --------------------                             |
*|                                                                    |
*|  Centro de Calculo / Servicio de Informatica                       |
*|  Universidad Autonoma de Madrid / E-28049 Cantoblanco. (SPAIN)     |
*|  Phone: +34-1-397.5153 / FAX: +34-1-397.3914                       |
*|  e-mail: mailmain@vm1.sdi.uam.es (native:mailmain@emduam11.bitnet) |
*----------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 16 Nov 92 17:03:22 -0500
From:         SKIPPER@MEDCOLPA.BITNET
Subject:      Logging feature missing?
Newsgroups: bit.listserv.pmdf-l

Probably something very simple I am overlooking.

Anyway, my MAIL.LOG file in the PMDF_ROOT:[LOG] directory has
no entries since 09-NOV-1992.  I didn't notice this until I
noticed that the MAIL.LOG_CURRENT was 0 blocks in size and, of
course, MAIL.LOG_YESTERDAY was also.  I have changed our
configuration a few times (Thanks to KVC for the help) and I'm sure
these changes coincide with the missing MAIL.LOG entries.  I do
NOT have the "logging" keyword on the individual channels but it
is on the Defaults channel.  My Defaults channel is...

defaults postheadonly logging

What am I overlooking or NOT considering?  If more information is
needed it will certainly be provided.

Thanks in advance.

/tom
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IPMDF@YMIR.CLAREMONT.EDU
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 20:51:41 GMT
From:         Greg Isett <GWI@ICF.HRB.COM>
Subject:      MAILSHR.EXE patch for VMS 5.5-2?
Newsgroups: bit.listserv.pmdf-l

I have been using a widely available patch for MAILSHR.EXE that allows
it to accept most rfc822 type mail addresses and surround them by IN%"".
This patch worked up to VMS 5.5-1.  After we installed VMS 5.5-2 this
patch no longer works.  I suspect the internal addressing of MAILSHR have
changed.

Has anyone gotten this to work on 5.5-2?

-------------------------------------------------------------------------------
Greg Isett                              Internet: gwi@icf.hrb.com
HRB Systems                             FAX     : (814)234-7720
300 Science Park Road                   Voice   : (814)238-4311
State College, Pa. USA 16804-0060
-------------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SKIPPER%MEDCOLPA.BITNET@ymir.claremont.edu"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 09:23:46 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: strange Return address...
Newsgroups: bit.listserv.pmdf-l

> From: "NAME = Hayne Margulies\\"" <"mcplib::margulies"@shrsys.hslc.org>

The other system generated that, I have no idea why, though I suspect it
is due to weird characters in a VMS MAIL personal name.  The doubled-up
backshlashes look wrong to me (isn't it supposed to be a single backslash
to quote the double-quote that follows that is inside of the matching pair
of double-quotes?

>  IN%"'NAME = Hayne Margulies\\\\'' <'mcplib::margulies'@shrsys.hslc.org>"

Anyway, PMDF saw that horrible thing and quoted it up still further for
VMS MAIL.  If you quote the double-quote that's inside the matching pair
of quotes with a single backslash, like this:

   IN%"'NAME = Hayne Margulies\'' <'mcplib::margulies'@shrsys.hslc.org>"

then PMDF seems to like it.  I suspect MX botched it when it tried
to quote up the funny-looking personal name field.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"PMDF-L@IRLEARN.BITNET"
X-VMS-Cc: MEADE
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Date:         Mon, 16 Nov 92 20:57:49 GMT
From:         "Shawn L. Meade ** Systems Manager" <MEADE@NKUVAX.BITNET>
Subject:      Reverse mapping using the PMDF_MAPPING_FILE
Newsgroups: bit.listserv.pmdf-l

I have a VAXcluster running PMDF, PMDF-MR, and JNET.  I have a VAXstation 3100,
not part of the cluster, running Message Router and All-in-one Mail.  I wish to
use the PMDF_MAPPING_FILE, (which is currently set to MAPPINGS.), to change all
reverse pointing addresses to the form username@NKUVAX.BITNET.

On the VAXstation 3100 (node name MAILBX), I have one mailbox for PMDF, named
appropriately PMDF, for which I have used the MRMAN utility to set the
/NOTIFY=PMDF_MR_NOTIFY option.

On the VAXcluster, I am using the PMDF Process Symbiont. I have three execution
queues on each of the two nodes, (setup according to the examples of PMDF_1 and
PMDF_2 on page 4-2 of the PMDF 4.1 manual), and a generic queue pointing at all
six of the execution queues.  I have created a file in PMDF_ROOT:[TABLE] called
MAPPINGS. to which the appropriate logical points.  There are only two lines in
this file and they are the following in the following format:
REVERSE
        *@AM.MAILBX.NKU.EDU     $0@NKUVAX.BITNET$Y
I have also modified the PMDF option file (OPTION.DAT) such that the
USE_REVERSE_DATABASE line is as follows:
USE_REVERSE_DATABASE=5

Everything seems to be working extremely well except that the reverse mapping
is not taking place.  I sent a message using an A1MAIL account to my VMS
account and the address was the same as before I modified the MAPPINGS. file.
I am sure I am leaving something simple out but I cannot seem to find it.

I appreciate any and all help.
Thank You
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ Shawn L. Meade                !       Northern Kentucky University           ~
~ Systems Manager               !       Academic Computing                     ~
~ BITNET: MEADE@NKUVAX.BITNET   !       Highland Heights, KY  41099-6127       ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~   Any statements made by myself are from myself alone and not my employer.   ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@INNOSOFT.COM"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 02:14:34 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Alias, reply address problem.
Newsgroups: bit.listserv.pmdf-l

> Below is an error I got replying to a message I received. I realize why I got
> the error.  In PMDF on our vax (DUKEMC) I have put in an alias for dryfo001 an
   d
> pointed it to dryfo001@deneb.mc.duke.edu (my workstation).
>
> This has worked fine for some time.  However, just found a case where it does
> not.  Someone sent me mail from a Bitnet node (DUKEMVS) to dryfo001@dukemc.  M
   y
> alias forward sent it to me at deneb.mc.duke.edu, but the return address was
> setup so that it would only work we replying through the PMDF system (which it
> was not) -- i.e. user@node.bitnet.  Normal SMTP internet mail works fine as my
> reply goes directly to the sender and not through PMDF.  I suspect I need a
> rewrite rule or something to prevent this?  Am I doing something I am not
> supposed to? On systems connected to the PMDF system, I want replies to go
> through our Bitnet connection, but for cirumstances such as this, we need to g
   o
> through an SMTP/Bitnet gateway or back through the PMDF system?

The problem, as I see it, is that the machine you sent the message to doesn't
know what to do with the host name "dukevms.bitnet".  What's the alternative?
Send it "dukevms"?  That's not the correct either in this case.  The best
solution is to configure deneb.mc.duke.edu to know what to do with addresses of
the form user@node.bitnet.  If deneb.mc.duke.edu is on BITNET then it needs to
send it out BITNET.  If it isn't on BITNET then it needs to gateway the mail
through a machine which is on BITNET.  While you can work around this instance
of the problem with PMDF on DUKEMC, it will not fix the problem for when mail
arrives on deneb.mc.duke.edu from other hosts.

To "fix" things via PMDF on DUKEMC, you can add a second wtcp_ channel on
DUKEMC which will force routes into addresses and thereby produce return
addresses of the form user%host@mc.duke.edu.  However, this will be done to
_all_ of your mail from DUKEMC to deneb.mc.duke.edu.  This may, for all I know,
be desireable to you as it will put your workstation's mail load onto DUKEMC.
However, the cleanest solution would be to train sendmail on deneb.mc.duke.edu
to know what to do with BITNET addresses.

Add the rewrite rule

    deneb.mc.duke.edu     $U%deneb.mc.duke.edu@WTCP-ROUTE

and then add the channel block

    wtcp_route smtp single_sys exproute nox_env_to
    WTCP-ROUTE

The key thing here is the "exproute" keyword which causes the local host to get
stuffed into the address as a route.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"TERRY@spcvxa.spc.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 24 Nov 92 05:12:42 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Missing message parts lately>
Newsgroups: bit.listserv.pmdf-l

The message you cite was damaged because it was in RFC1154 format, and
a bug in PMDF causes such messages to be incorrectly processed. This
problem was fixed in V4.1-13. However, the damage was done before the
message reached your system, so there's nothing you can do about it.

I have no idea what caused your problem with a previous message. All I can
say is that the example you cite has nothing to do with your configuration.

                                Ned
From: gomide@FPSP.FAPESP.BR
Newsgroups: bit.listserv.pmdf-l
Subject: PMDF 3.2 - job enqueue error
Date: 18 Nov 92 19:43:56 GMT
Reply-To: gomide@BRFAPQ.BITNET
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir.bitnet"
X-VMS-Cc: GOMIDE
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Comments:     @FAPQ.FAPESP.BR - @FAPQ%FPSP.HEPNET - @BRFAPQ.BITNET - .BR
              gateway
Comments:     Warning -- original Sender: tag was GOMIDE@BRFAPQ

Dear Sirs,

I'm running pmdf 3.2 with VMS 5.4-2. When a new mail arrives, pmdf
enqueues another job on the corresponding queue, without recognizing
that there are already other jobs for the same channel pending on that
queue. This creates a big overhead of JOB CONTROL. Is there a patch to
correct this? For reasons not stated here I can not install pmdf 4.x
right now.

Yours,
--
Alberto Courrege Gomide | Fundacao de Amparo `a Pesquisa - (11)831-3357
Software Supervisor     | Rua Pio XI, 1500 - CEP 05468-901 - Sao Paulo
<gomide@fapq.fapesp.br> | FAX (11)261-4167 Telex (11)82014 - Brazil
(ACG8) - .BR Domain Technical Contact. |        [this space for rent]
--
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"S.ROSS@CGNET.COM"
X-VMS-Cc: info-pmdf, in%"service@tgv.com"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 21 Nov 92 07:36:05 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: Multinet TCP/IP parameter settings
Newsgroups: bit.listserv.pmdf-l

You probably want to increase both maxservers and backlog.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"cvm@NAUVAX.UCC.NAU.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 17 Nov 92 05:25:38 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: forwarding mail for testing
Newsgroups: bit.listserv.pmdf-l

>>> I am trying to evaluate MS-Mail.  To help do this I would like to have
>>> all mail that is sent to my VMS mail account also sent to my MS-Mail
>>> account. I am currently using the W action of deliver to do this, but it
>>> does not keep the original headers intact.  Any suggestions on how I can
>>> accomplish this?  I use deliver for other purposes also.  Could I
>>> eliminate the W action in my MAIL.DELIVERY file, change my forwarding
>>> address in VMS mail to be: in%"~cvm,cvm@msmail.ucc.nau.edu" and still
>>> have deliver work?
>>
>>Use the P action instead of W or F.  The problem with W and F is that they
>>use VMS MAIL to forward the message and this is too much of a disruption to
>>the headers.  If you use the P action, then PMDF SEND will be used instead
>>of VMS MAIL:
>>
>>  * * * A P "cvm@msmail.ucc.nau.edu"
>>
>>Dan
>
> The P action keeps the headers intact but it does not leave the
> originator of the message as the sender.  What I really need is a an
> action that uses PMDF SEND to send the mail and makes the From: field be
> the original sender of ther message.

You might consider making cvm into an alias by adding the following to
pmdf_root:[table]aliases.;

   cvm: _cvm,cvm@msmail.ucc.nau.edu

and not bother with DELIVER.  If you have a compiled configuration, then
you will have to recompile it and re-install it before this change will
take effect.  You might also make cvm in VMS MAIL forward to IN%CVM


   MAIL> set forward/user=cvm in%cvm

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"PMDF-L@IRLEARN.BITNET"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 23:34:10 GMT
From:         "Stephen LaBelle - MSCD" <LABELLES@MSCD.BITNET>
Subject:      Re: Incoming notification From: prefix = SMTP%
Newsgroups: bit.listserv.pmdf-l

SETH@SPEECH.MIT.EDU WRITES:

> Hi,
>         A while back I posted a note concerning occasional file
> create errors of the following form:
>
> %MAIL-E-SENDERR, error sending to user audiodev@cbgrle.mit.edu at
> -PMDF-E-FCRT, File create error, Pascal status = 2, VMS statuses = 99684 and 0
> -PMDF-I-TEXT, cannot create channel queue entry
>
>         It turned out that we were mixing IN% and SMTP% protocols
> in a given MAIL session. Simply requiring the use of only one
> of these form solved the problem, but in hindsight brings up an
> interesting question.
>
>         Why would all incoming mail on a machine newly updated
> from CMU TCP/IP to Multinet suddenly start using the SMTP prefix
> on ALL incoming Internet mail? I don't seem able to determine the
> cause of this change. As far as I know, it was nothing I did during
> the switch from CMU to TGV code, at least knowingly... :-)
>

The prefix change to SMTP% was setup when you installed MultiNet by its
installation procedure. That is the mail transport prefix used by MultiNet.
If you have MultiNet and PMDF you need to setup the TGV MultiNet Channels
used to interface PMDF to TGV MultiNet. This replaces the SMTP componant in
TGV MultiNet.

You should look at section 9.9 in your PMDF manual and make sure you have
done the steps neccessary to setup the Channel.

                                                        Steve

##############################################################################
# Stephen LaBelle                        # Internet : labelles@zeno.mscd.edu #
# Systems Programmer                     #            labelles@clem.mscd.edu #
# Metropolitan State College of Denver   #####################################
# Denver, Colorado  USA                  # Bitnet   : LABELLES@MSCD.BITNET   #
##############################################################################
# DISCLAIMER: The opinions expressed are mine and in no way, shape or form   #
# neccessarily reflect those of Metropolitan State College of Denver.        #
##############################################################################
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-VMS-To: IN%"PMDF-L%IRLEARN.bitnet"
X-VMS-Cc: MALLETTN
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Date:         Fri, 20 Nov 92 16:08:44 GMT
From:         "Nigel Mallett, ISD,
              Radio Free Europe x2723" <MALLETTN@ADMINA.RFERL.ORG>
Subject:      deliver
Newsgroups: bit.listserv.pmdf-l

Hi,
	I am using deliver to auto file certain incoming messages, these
	are put into folders in a seperate mail file. What I would like
	is to still get the new mail message at my terminal so that I
	know things are arriving. Can anything short of writing a procedure
	to reply or some such to me be done?

	Nigel

+=========================================+===================================+
|                                         |                                   |
|	Nigel Mallett,                    |   Internet: Mallettn@RFERL.ORG    |
|	System Manager,                   |                                   |
|	Radio Free Euorope/ Radio Liberty,|   Phone: int+ 49 89 2102 3723     |
|	8000 Munich 22                    |                                   |
|	Germany                           |   FAX:   int+ 49 89 2102 3752     |
|                                         |                                   |
+ ============================================================================+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 18 Nov 92 11:59:14 -0500
From:         SKIPPER@MEDCOLPA.BITNET
Subject:      strange Return address...
Newsgroups: bit.listserv.pmdf-l

Hopefully someone can look at the Return address in the following
headers and give me an idea as to what is happening.  The software
particulars are as follows...

        medcolpa.edu    VMS 5.5-1, PMDF 4.1, JNET 3.5
        shrsys.hslc.org  VMS 5.?, MX (3.0 perhaps)

Of course, this is NOT replyable from VMSMail.

Thanks,
/tom
**************************************************************************

From:   IN%"'NAME = Hayne Margulies\\\\'' <'mcplib::margulies'@shrsys.hslc.org>"
    18-NOV-1992 11:36:00.52
To:     IN%"skipper@medcolpa.edu"
CC:
Subj:   vax symbols

Return-path: <"mcplib::margulies"@shrsys.hslc.org>
Received: from CUNYVM.BITNET (MAILER@CUNYVMV2) by medcolpa.edu (PMDF #2945 ) id
 <01GRANHVRQ6O90MU5R@medcolpa.edu>; Wed, 18 Nov 1992 11:35:54 -0500
Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.08) with BSMTP id 2791; Wed,
 18 Nov 92 11:35:15 EST
Received: from SHRSYS.HSLC.ORG by CUNYVM.CUNY.EDU (IBM VM SMTP V2R2) with TCP;
 Wed, 18 Nov 92 11:35:12 EST
Received: by shrsys.hslc.org (MX V3.1) id 5263; Wed, 18 Nov 1992 11:35:56 EST
Date: 18 Nov 1992 11:35:36 -0500 (EST)
From: "NAME = Hayne Margulies\\"" <"mcplib::margulies"@shrsys.hslc.org>
Subject: vax symbols
To: skipper@medcolpa.edu
Message-id: <00963CBE.072DE720.5263@shrsys.hslc.org>
Content-transfer-encoding: 7BIT
X-MX-Warning:   Warning -- Invalid "From" header.
X-VMSmail-To: SHRSYS::MX%"skipper@medcolpa.bitnet"
X-VMSmail-CC: MARGULIES