HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: in%"info-pmdf@innosoft.com"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 16 Dec 92 12:23:01 GMT
From:         Anders Rolff <ROLFF@ENTERPRISE.EUROKOM.IE>
Subject:      PX25_master hangs (PMDF 4.0)
Newsgroups: bit.listserv.pmdf-l

Hello!

I have noticed several times that the PX25_master program hangs (for hours).
As an effect of this, that particular channel is blocked so no messages
will be delivered. When I manually kill the process, and manually re-run
the queue it works fine.

Is there a known workaround for this problem?

Thanks,

Anders.
From: Dan@TOE.TOWSON.EDU
Newsgroups: bit.listserv.pmdf-l
Subject: RE: PMDF V4.1 and Jnet V3.6
Date: 16 Dec 92 14:15:25 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"D.Nash@utexas.edu"
X-VMS-Cc: ipmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Comments:     Warning -- original Sender: tag was E7OPDAN@TOE.TOWSON.EDU

We upgraded to Jnet V3.6 using 3 DNANJE links and 1 BSC/370 link last Friday.
As Jack Pernice said, the new install does not replace your lmd.com.  Along with

other user-configurable procedures, they give you a template file and tell you
to merge your local modifications into it.

For LMD.COM, I just left the Jnet template alone and used the LMD.COM from PMDF
V4.1.  We've had no problems since then (related to Jnet, that is - but that's
another story :-).

Dan

   Daniel A. Dinkin
   Network Services Manager                   BITNET: dan@towsonvx.bitnet
   IR Academic Computing                    Internet: dan@toe.towson.edu
   Towson State University                            dan@midget.towson.edu
   Towson, Maryland 21204                UMSA DECnet: toe::e7opdan
   (410)830-3320

     Any thoughts in this message are purely random and my employer had
           nothing to do with them... especially if I was right.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: in%"info-pmdf@innosoft.com"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 21 Dec 92 04:27:31 GMT
Comments:     Warning -- original Sender: tag was TINKELMAN@DECUS.ORG
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      Using [auth_list] positional parameter
Newsgroups: bit.listserv.pmdf-l

I'm trying to use the [auth_ilst] positional parameter to restrict
posting to a list.

From the alias file:

> ! Mailing_List.Aliases
> !
> comcom-l:             comcom-list
> comcom-list:          comcom-forward
> comcom-x:             <pmdf_mailserv_mail_dir:comcom-list.dis,\
>                       [auth_list] pmdf_mailserv_mail_dir:comcom-list.dis,\
>                       comcom-l-owner,*,*,comcom-l-owner
> comcom-owner:         postmaster,comcom-sec
> comcom-sec:           gerland

VMSmail forwarding addresses:
        comcom-x -> in%comcom-x
        comcom-forward -> in%comcom-x

Mail that is sent from an address not in the named file is not delivered
to the list, as expected.  However, it's not bounced to the originator
either.  It just sits in the queue and gets retried laster.  The log file
shows:

> $   mail/protocol=pmdf_mailshr
> %PMDF-E-HOST, Illegal host/domain in address "COMCOM-X"
> -PMDF-I-TEXT, you are not allowed to use this list: COMCOM-X@DECUS.Org

I don't remember what version of PMDF was first supposed to support this
feature.  Should this work under 4.1-11?

If the PMDF version is not the problem, what do you suggest I look at to
figure out the problem?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"kraftjoel@bvc.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 14 Dec 92 20:47:30 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Second l channel?
Newsgroups: bit.listserv.pmdf-l

> In order to make mail look "nicer" for our users, we currently use the
> "headeromit" keyword on our l channel.  I have recently found the need to have
> headers on mail sent to some accounts (most notably the account that receives
> mail that is to be posted to news).  I would like to set up an additional
> "l" channel that is identical to normal l except that the headers are included
> on messages.  I have tried to make a new channel using the MAIL_ prefix name o
   n
> the channel, but any delivery on that channel crashes with this error:

Use a d or dn_ channel for a second local channel.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: University of Minnesota CIS
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf-newsgate@mccall.UUCP"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 16 Dec 92 02:02:40 GMT
Comments:     Warning -- original Sender: tag was daven@MCCALL.UUCP
From:         David Nieters <daven@VX.CIS.UMN.EDU>
Subject:      Using customer-supplied routine substitutions
Newsgroups: bit.listserv.pmdf-l

I am trying to use a customer-supplied routine substitution as described
in section 3.2.4.7.3 on page 3-15 of the 4.1 PMDF managers manual.

I'm able to get my routine called just fine, and I print out the argument,
and what I am returning, but when I try to do a
        PMDF TEST/REWRITE/CONFIG=xxx.cnf
it seems to completely ignore the string that I return and just use
whatever it sent me.  I AM returning a -1 when I want it to do the
substitution.  Has anyone had any success with this?  If so, can I
look at your source?  Or am I doing something obviously wrong?

David Nieters
University of Minnesota
daven@vx.acs.umn.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ccvj@misty.latrobe.edu.au"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 11 Dec 92 19:13:51 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: DELIVER query - return message to sender
Newsgroups: bit.listserv.pmdf-l

> I'd like to have a message automatically forwarded to people when I am
> away.  I have come up with the following rather unwieldly interpretation
> of DELIVER - is there a better way of doing it?  I fiddled with QFROM
> and QQFROM but went crosseyed with """s.   Have I missed an obvious flag
> for replying?

Use

   $ mail/subject="I am on holiday" hols.txt "''QFROM'"

Also, a word of warning.  You need to somehow log each address you
automatically send a message to and then ensure that you do not subsequently
send another automatic message to that address.  Otherwise, you may find
yourself generating a mail loop or two.  (E.g., you get a message from a
mailing list, you post hols.txt to the list, you get you're posting back, you
post hols.txt to the list, etc.)

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"D.Nash@utexas.EDU"
X-VMS-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 15 Dec 92 00:32:03 GMT
From:         Jack Pernice <PERN@DB1.CC.ROCHESTER.EDU>
Subject:      RE: PMDF V4.1 and Jnet V3.6
Newsgroups: bit.listserv.pmdf-l


We installed JNET V3.6, and TCPNJE V1.2 (WIN driver) on an 8 node cluster
on 12/12/92.  We're running PMDF V4.1-12.  The JNET V3.6 installation does
not replace LMD.COM.  We're using LMD.COM that came with PMDF and all seems
to be just fine.

We have quite a bit of mail traffic through our system.  If there were any
problems, I think we would have encountered them by now.

----------
Jack Pernice                             BitNet:    PERN@UORDBV
VMS Systems                              InterNet:  pern@db1.cc.rochester.edu
University of Rochester                  Voice:     (716) 275-7160
Rochester, NY  14620
USA
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Buena Vista College
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"KVC@SUMMER.INNOSOFT.COM"
X-VMS-Cc: IN%"info-pmdf@ymir.claremont.edu"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 15 Dec 92 06:14:27 GMT
From:         "Joel D. Kraft" <KRAFTJOEL@BVC.EDU>
Subject:      RE: Second l channel?
Newsgroups: bit.listserv.pmdf-l

>Don't use a dn_ channel, that will not run the correct channel program.  You
>need to use a "d" or "d_" channel for this.  A "d" channel is normally used to
>support DECnet MAIL-11 for remote DECnet nodes that do not have PMDF.  It turns
>out that PMDF supports remote DECnet MAIL-11 nodes simply by handing the
>message
>to VMS MAIL, which makes the network connection and does the transfer.  If
>the address has no remote node then this devolves to being the same as a local
>VMS MAIL delivery -- hence the use of a "d" channel for alternate local
>delivery.

>If you are already using a "d" channel and you don't want its configuration to
>change for this purpose, go ahead and create a "d_headers" or something channel
>(everything after the "d_" can be whatever you like).

Okay, this is close, but when trying this I see that the "d" channels parse
the user@host format in its entirety interpreting the host as a decnet node
name, while the "l" channel will strip off the "@host" portion.  What is
the best way to set up the rewrite rules in our homogeneous cluster (which
shares the PMDF configuration) to get the decnet hostname to work properly.
I'd prefer not to write a rule for each node to get it to work out
properly.

May I also suggest adding support for multiple "l" channels...

Thanks,
Joel D. Kraft
System Manager
Buena Vista College
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"bthomas@drifter.uwyo.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 15 Dec 92 21:47:24 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Address reversal data base
Newsgroups: bit.listserv.pmdf-l

> How does one go about getting a default reversal mapping in the
> reversal data base similar to the "*" mapping in the directory
> data base. I would like not to have to put all users on other systems
> using PMDF as a mail forwarder into the reversal file if I can help it.
> I get the idea from the manual this is done with the REVERSE keyword
> but I have tried several varations on using it and none have worked.

The address reversal database does not support wild card operations; it's too
much of a performance lose in that situation.  (The directory channel can be
argued to support them since use of the directory channel in the first place
is an implicit statement that performance is not an issue.)

The reverse keyword is not what you need to be using; it merely controls
whether or not the reversal mechansims are used for a particular channel.
What you need to be looking at is the REVERSE mapping.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@ymir.bitnet"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 17 Dec 92 16:45:46 GMT
From:         Daphne Yang <OPERATOR@WFEB2.BITNET>
Subject:      Help: How to get mail deliver messages for internet nodes?
Newsgroups: bit.listserv.pmdf-l


We are on both Bitnet and Internet.  Before we joined Internet last month, we
can receive messages dislayed on the screen shown where the mail has been
delivered.  After I adding a channel and installing the slave program
PMDF_ROOT:[EXE]MTCP_SLAVE.EXE to act as TGV MultiNet's SMTP server, now I can
receive deliver messages only when the mail's destination is a BITNET node.
Some of my users REALLY sit in front of the terminal until they saw their mails
been delivered to the destination.  That feature is very important to them.
Can anyone tell me if it is possible to get the deliver messages for all the
addresses(not only Bitnet)?  Is there some kind of switch I need to set?
Thank you very much for your help.



Daphne Yang
System Manager
Worcester Foundation
222 Maple Ave,
Shrewsbury, MA

operator@wfeb2.bitnet
operator@sci.wfeb.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: NYU Medical Center, 550 First Ave., New York, 10016
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: in%"ipmdf@ymir.bitnet"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 17 Dec 92 13:46:03 GMT
From:         SMITH@NYUMED.BITNET
Subject:      Encrypted mail
Newsgroups: bit.listserv.pmdf-l

A couple of years ago I got a program called ENCRYPT from Wesleyan and have
had it here for a while.  It hasn't been used much until now, but we recently
had a user who wnated to mail encrypted text and asked if this could be built
in directly into mail.  ENCRYPT generates mail-like headers, which potentially
allows decryption on the fly, and might lend itself to incorporation into a
mail package.

Any thoughts on whether this might be something you would consider for the
PMDF user agent, or whether other mailers might support encryption (or
security-enhanced mail, as ENCRYPT calls it).
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%INFO-PMDF
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 15 Dec 92 17:19:38 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      Stuck msgs in queue for local channel
Newsgroups: bit.listserv.pmdf-l

We converted a very large VMSmail distribution list (one with 100s of
entries) into a PMDF list by defining a PMDF alias that pointed to
an the existing file.  [It's maintained by a complex set of programs
that I didn't want to touch.]  The mailing list consists of single
lines of the format node::usename.

A mail msg to this list hung for over 24 hours.  When we killed the
job the last lines were
        $   mail /protocol=pmdf_mailshr
        %MAIL-E-NOSUCHUSR, no such user XXXXX at node XXXXX
(with actual user name and node)

First Question:

A dump of the queued msg shows lots of envelope destination addresses
of the form node::user.  This surprised me.  Is it an indication that
I did something wrong in setting up the list?

Second Question:

I know there is a bug in the Mail-11 protocol which gets triggered
when distinct distribution list entries (distinct on the local node)
getting collapsed into common addresses based on forwarding at
destination nodes.  Could this bug explain the msg getting hung?
If so, is there a recommended method to avoid the problem or at least
reduce the likelyhood of its occurance?  Finally, is there someway to
place a timeout on delivery through VMSmail?  I'd be willing to take
responsibility for maintaining the value of a locally specified
time-out value if that would be appropriate.
--
Bob Tinkelman <bob@camb.com>
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"BYRD@mscf.med.upenn.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 17 Dec 92 22:28:24 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Addressing confusion
Newsgroups: bit.listserv.pmdf-l

This behavior is entirely expected and consistent. In general, PMDF only
know about the addresses VMS MAIL passes directly to it. Other addresses
on the VMS MAIL To: and Cc: lines that are passed to other agents are not
part of the information that's passed to PMDF. While PMDF can and does get
copies of the actual To: and Cc: headers from VMS MAIL, there's no way for
PMDF to convert the information it sees on those lines into usable RFC822
addresses. The problem is fundamental; there's too much hidden logic both
in VMS MAIL and in whatever other foreign protocols you happen to use for
PMDF to duplicate it all accurately.

PMDF does scan and reexpand the To: and Cc: lines so it can attempt to match
the RFC822 addresses it has in hand with the headers. This is done so that
there's a chance the addresses will end up on the right header. (VMS MAIL
does not tell PMDF what header a given address came from.) This is all a
very complex process involving close to 1000 lines of code. There are
numerous assumptions and heuristics built into it all where PMDF simply has
no way of duplicating a particular chunk of processing someone else does. As
such, it works fairly well but it isn't perfect by any means.

There is an undocumented channel keyword that tells PMDF to take the
results of the reexpansion of the To: and Cc: headers and attempt to build
reasonable RFC822 addresses from the parts that didn't match PMDF addresses.
This is UNSUPPORTED; it is known to have numerous problems; all of which have
been found to be unfixable. However, if you want to try it, the keyword to
use is addlineaddrs.

In summary, it isn't possible for PMDF to build RFC822 headers that
accurately reflect all the information that was in the original VMS MAIL
headers. This is largely due to the fact that VMS MAIL provides no information
to PMDF other than the original header lines and PMDF-specific addresses
extraced from these headers. We have attempted to duplicate the logic that
is used in an effort to provide this information, but we have found numerous
problems with this approach that are simply intractable. If you want to
use the results of the reexpansion you can do so, but this usage is
unsupported by Innosoft.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: ipmdf
X-VMS-Cc: joe,sam
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 11 Dec 92 20:13:11 GMT
Comments:     Warning -- original Sender: tag was E7OPDAN@TOE.TOWSON.EDU
From:         Dan@TOE.TOWSON.EDU
Subject:      default routing in Jnet V3.6
Newsgroups: bit.listserv.pmdf-l

I just upgraded to Jnet V3.6.  However, before I institute the new default
routing can anyone tell me what its effects on BN_MASTER are?  If I tell TOWSON2

that the default Jnet router is TOWSON1 and then bring up Jnet on TOWSON2
without a JANROUTES.JCP file, what happens when PMDF tries to process a message
destined for BN_MASTER on TOWSON2?

I am assuming, since I haven't seen any warnings on this list about this being a

problem, this should be OK.  I'd like to see it in writing, though, before I go
and install it.

Many thanks.

Dan

P.S. - Effective 12/16, I am leaving Towson State University for a new position
at University of MD Baltimore County.  Though they currently use PMDF on their
administrative but not their academic system - where I am going - I'm afraid I
will be leaving the list (at least until I can convince them they can't live
without PMDF :-).  My account at TSU will still exist for a while so if you wish

to send me email after 12/16, you can still send it here.

   Daniel A. Dinkin
   Network Services Manager                   BITNET: dan@towsonvx.bitnet
   IR Academic Computing                    Internet: dan@toe.towson.edu
   Towson State University                            dan@midget.towson.edu
   Towson, Maryland 21204                UMSA DECnet: toe::e7opdan
   (410)830-3320

     Any thoughts in this message are purely random and my employer had
           nothing to do with them... especially if I was right.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"92636828s%csghsg5a.bitnet@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 11 Dec 92 18:30:03 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: mail without sender?
Newsgroups: bit.listserv.pmdf-l

>       Is it possible to send an email with VMS Mail without the
>        email-address of the sender being included in that mail?

Well, there's two things you might be asking for here: the ability to send mail
anonymously or the ability to have a mailing list which supports anonymous
postings.  The latter is something we've thought about adding support for
but it has never made it high enough on our priority list.  (Just let us know
and we'll look more seriously into implementing it.)  The former, the ability
to anonymously send mail, is violates all sorts of standards and spirits of the
standards and I do not see us ever supporting it.

Dan
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"
X-VMS-Cc: AE
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 17 Dec 92 10:46:24 -0400
From:         Aidan Evans <AE@AC.DAL.CA>
Subject:      Did a rewritten "From:" make a message appear forged?
Newsgroups: bit.listserv.pmdf-l

  One of our users (ECH) got a message that said in the VMS MAIL "From:" line:

        From:   IN%"hannon@ac.dal.ca" 16-DEC-1992 11:55:18.99

and replied to that message.  When user "hannon" got the reply she was
surprised, because she hadn't sent the original message.  She was worried that
someone was forging mail.
  We got ECH to send us the original message he replied to.  The headers,
including VMS MAIL's, looked like this:

From:   IN%"hannon@ac.dal.ca" 16-DEC-1992 11:55:18.99
To:     IN%"ECH@ac.dal.ca"
CC:
Subj:   Beer compatible solder

Return-path: <hannon@sparc3303.cacd.cr.rockwell.com>
Received: from sparc3303.cacd.cr.rockwell.c (sparc3303.cacd.cr.rockwell.com) by
 AC.DAL.CA (PMDF #2545 ) id <01GSDREERFN4001Z65@AC.DAL.CA>; Wed,
 16 Dec 1992 11:28:35 -0400
Received: from pc234sun2601.cacd.cr.rockwell.com ([131.198.60.234]) by
 sparc3303.cacd.cr.rockwell.com (4.0/SMI-4.0) id AA15863; Wed,
 16 Dec 92 09:27:56 CST
Date: 16 Dec 1992 09:25:20 +0000
From: hannon@ac.dal.ca (<hannon@sparc3303.cacd.cr.rockwell.com>)
Subject: Beer compatible solder
To: ECH@ac.dal.ca
Message-id: <QB2F4A61@pc234sun2601>
Content-transfer-encoding: 7BIT

  My theory, based on the domain name "pc234sun2601.cacd.cr.rockwell.com" in
one of the "Received:" lines, is that a badly written PC mail program wrote
the original "From:" line like

        From: hannon (<hannon@sparc3303.cacd.cr.rockwell.com>)

and that PMDF rewrote "hannon" to "hannon@ac.dal.ca".  Is this possible? If
so, is there any way to prevent PMDF from doing this?  I can see it might be
difficult, given that mapping my theoretical "From:" line to VMS MAIL might
produce ``From: IN%"hannon"'' which is not much better than what was done in
the first place.

Aidan Evans (AE@AC.Dal.CA), Computer Facilities & Operations,
University Computing & Information Services, Dalhousie University,
Halifax, N.S., Canada, B3H 4H8
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU