HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%PMDF
X-VMS-Cc: MWILDER
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 22 Jul 92 15:08:33 GMT
From:         MIKE WILDER <MWILDER@FRMNVAX1>
Subject:      Problem with TMP files and security
Newsgroups: bit.listserv.pmdf-l

I have what I know is probably a real simple problem, but I can't for the life
of me find the solution.  I don't think it's a PMDF problem but rather a
VMSMail problem (I know it's hard to believe :-).  The problem seems to be that
temporary files created on SYS$SCRATCH are being created with SYSTEM as the
owner instead of the user.  When VMSMail tries to open the file (as in a
FORWARD or REPLY) or tries to delete it upon exiting, a security violation
obviously occurs.  I've watched the files as they get created and sometimes
they are created with correct owner and sometimes not; I don't see a pattern.

One solution I've pondered is to define SYS$SCRATCH to SYS$LOGIN, but we use
disk quotas on the users' drive and not on the system drive where SYS$SCRATCH
is defined to be.  Doing this could very quickly lead to quota overruns.  Even
then, I don't know if it will cure the ownershipproblem.

If there's any information that I can provide that will help, please let me
know.  Like I said, this is not a PMDF problem; I'm asking here because all you
folks are so good about helping and I'm a new sys mgr who needs help with a
simple problem.

____________________________________________________________________________
Mike Wilder
Postmaster, TechRep
Furman University Computer Center
Greenville, SC
BITNET: MWILDER@FRMNVAX1
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.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Original_To:  BITNET%"ipmdf@ymir"
Date:         Tue, 21 Jul 92 21:26:04 GMT
From:         "Scott J. Mitchell" <MITCHELL@UTHSCSA>
Subject:      VMS MAIL_SERVER and undeleted temp files
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

We recently discovered a large number (10,000s) of uncataloged MAIL.TXT
files on the system disk of one of our Vaxes.  DEC acknowledges that
MAIL_SERVER.EXE is creating these temp files and failing to delete them
properly, but at the same time they're pointing an ambiguous finger at
"non-DEC protocols," suggesting that the problem is more likely to occur
when the delivering system is something other than VMSmail.  A timestamp
comparison suggests that the problem is indeed associated with deliveries
relayed by our primary mail host using PMDF.

I'm absolutely not suggesting that PMDF has any relationship to this problem,
particularly in a causal sense.  Just wondering if anyone can shed additional
light on the subject.  We were caught asleep at the switch and had some
difficulty recovering the disk because of a hosed INDEXF.SYS.

Scott Mitchell
University of Texas Health Science Center at San Antonio
mitchell@uthscsa.edu
mitchell@uthscsa.bitnet
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@innosoft.com"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 30 Jul 92 23:27:24 GMT
From:         Stephen Tihor 212 998 3052 <TIHOR@ACFCLUSTER.NYU.EDU>
Subject:      Bizaro mail message headers:
X-To:         info-pmdf@INNOSOFT.COM
Newsgroups: bit.listserv.pmdf-l


From:   IN%"Ron Frank                                      RIFRANK  at YKTVMH 8-
   863-7636 (914)784-7636 FAX 7455 H2-B06 IBM TJW Research Box 704 Yorktown Heig
   hts NY 10598 rifrank @ watson.ibm.com" 30-JUL-1992 16:11:50.86
To:     IN%"TIHOR@ACFcluster.NYU.EDU"
CC:
Subj:   Whom do I contact about NYU student use of networking?

Return-path: <>
Received: from Jnet-DAEMON by ACFcluster.NYU.EDU (PMDF #2323 ) id
 <01GMZ4UHLSMO8YA35C@ACFcluster.NYU.EDU>; Thu, 30 Jul 1992 16:11:27 EDT
Received: From YKTVMH(RIFRANK) by NYUACF7 with Jnet id 2886 for TIHOR@NYUACF;
 Thu, 30 Jul 1992 16:11 EDT
Date: 30 July 1992, 16:09:58 EDT
From: Ron Frank                                      RIFRANK  at YKTVMH
 8-863-7636 (914)784-7636 FAX 7455 H2-B06 IBM TJW Research Box 704 Yorktown
 Heights NY 10598 rifrank @ watson.ibm.com
Subject: Whom do I contact about NYU student use of networking?
To: TIHOR@ACFcluster.NYU.EDU
Message-id: <01GMZUS4S2C88YA35C@ACFcluster.NYU.EDU>
Content-transfer-encoding: 7BIT

 +-----------------------------------------------------------+
 | Ron Frank                  | | (914) 784-7636  8-863-     |
 | H2-B06                     | | FAX 914 784-7455           |
 | IBM TJW Research Center    | |                            |
 +----------------------------| |----------------------------+
 | Box 704                    | | RIFRANK  at YKTVMH         |
 | Yorktown Heights, NY 10598 | | rifrank @ watson.ibm.com   |
 +-----------------------------------------------------------+
 | 30 Saw Mill River Rd.      \     For FEDEX etc.           |
 | Hawthorne, NY 10532         \                             |
 +-----------------------------------------------------------+
 | Current Assignment - Education Technology Research        |
 +-----------------------------------------------------------+
 | The opinions are mine, only media access is my company's. |
 +-----------------------------------------------------------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: University of South Australia
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@ymir.claremont.edu"
X-VMS-Cc: CCAJR
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 27 Jul 92 02:07:11 +0930
Comments:     Warning -- original Sender: tag was CCAJR@LEVELS.UNISA.EDU.AU
From:         Rollo.Ross@LEVELS.UNISA.EDU.AU
Subject:      Problem with timezone names
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

        PMDF_STARTUP (in 4.1) overrides the site's specification for
PMDF_TIMEZONE if MULTINET_TIMEZONE is defined:

$ if f$logical("MULTINET_TIMEZONE") .nes. "" then -
  pmdf_define/exec/nolog pmdf_timezone "''f$logical("MULTINET_TIMEZONE")'"

        (Similarly for JAN_TIME_ZONE.) Unfortunately, it then makes
unwarranted assumptions about what MULTINET_TIMEZONE means. In South
Australia, the appropriate value for MULTINET_TIMEZONE is "CST". PMDF
assumes that this means -0600, and constructs a Date header like this:

Date: 27 Jul 1992 01:07:54 -0600 (CST)

        However, in this country CST means +0930. Could PMDF_STARTUP please be
changed so that it only uses the value of MULTINET_TIMEZONE if PMDF_TIMEZONE
is not defined? Then our carefully-chosen *unambiguous* timezone will not be
overidden.

                                    Rollo Ross, Network Manager (CLW campuses)

Computer Centre,  University of South Australia, The Levels, SA 5095, Australia
Ph +61 8 302 3158 Fax 302 3385 DTE 505282622004  Rollo.Ross@Levels.UniSA.Edu.Au
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"KNEZEVICH@NOAAPMEL.GOV"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 21 Jul 92 20:42:39 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: PMDF 4.0, Multinet 3.0, and VMS 5.5
X-To:         KNEZEVICH@NOAAPMEL.GOV, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

I cannot speak to Multinet V3.0, but PMDF V4.0 works fine on VMS 5.5.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"IMHW400@INDYVAX.IUPUI.EDU"
X-VMS-Cc: IPMDF
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 21 Jul 92 23:28:04 GMT
From:         "Daniel C. Newman" <DAN@HMCVAX.CLAREMONT.EDU>
Subject:      RE: Problem with vmsnet.mail.pmdf gateway?
X-To:         IMHW400@INDYVAX.IUPUI.EDU, INFO-PMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> Is there some sort of problem with the gateway between IPMDF and the
> vmsnet.mail.pmdf newsgroup?  Or has this list really been silent since
> 6-Jul-1992?

info-pmdf itself has not been silent.  We do not know where the info-pmdf
to vmsnet.mail.pmdf feed is and thus cannot comment or rectify any problem
related to that feed.

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.CLAREMONT.EDU"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 31 Jul 92 01:38:34 GMT
From:         "Pete Kanaitis (412) 359-1516" <KANAITIS@SINGER.ASRI.EDU>
Subject:      VAX Notes channel
X-To:         IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Hello.

   I've upgraded to PMDF V4.1, and thought I'd try out the VAX NOTES
channel.  Seems to work pretty well keeping messages that have the
same subject as "replies" to the original message.  One question
that I have is:  Is there a simple way to strip out most of the headers
(except possibly for the basic to/from/date/subject) from the body of the
note?

   Another thing about NOTES, is that there are a few send-mail-into-notes
programs out there (such as the PMDF NOTES channel), but are there any
notes-back-into-mail type of programs?  Typically, if you use NOTES to
receive Internet mailing lists, you have to set the notes to read-only,
so that users do try to reply locally... This doesn't make it that great
of a tool if you participate in these discussions, rather than just
read them.  It would be nice if a WRITE or REPLY command from
within NOTES could fire something back to the mailing list...

Pete Kanaitis
Manager, Computational Resources
Allegheny-Singer Research Institute
KANAITIS@ASRI.EDU
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: State University of New York, Stony Brook
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:         Sun, 26 Jul 92 19:48:15 GMT
Reply-To:     Sanjay Kapur <skapur@SBCCMAIL>
From:         Sanjay Kapur <SKAPUR@SBCCMAIL>
Subject:      RFC 822 and 821.
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

I do not remember if this has been mentioned before but the tenth anniversery
of these standards is coming up soon.  RFC 822 has a date of August 13, 1982
and RFC 821 just says August 1982.



  Sanjay Kapur    (SK54)              |Internet:    Sanjay.Kapur@sunysb.edu
  Systems Staff, Computing Services,  |Bitnet:      SKAPUR@USB
  State University of New York,       |SPAN/HEPnet: 44132::SKAPUR
  Stony Brook, NY 11794-2400        |Phone:+1-516 632 8029, FAX:+1-516 632 8046
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: University of Northern Iowa
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, 22 Jul 92 12:25:47 -0500
Comments:     Warning -- original Sender: tag was NETNEWS@AMERICAN.EDU
From:         Ken Connelly <connelly@ISCSVAX.UNI.EDU>
Subject:      RE: Problem with vmsnet.mail.pmdf gateway?
X-To:         ipmdf-newsgate@mccall.UUCP
Newsgroups: bit.listserv.pmdf-l

In article <01GMLP43SGCI985EO2@YMIR.CLAREMONT.EDU>, "Mark H. Wood"
<IMHW400@INDYVAX.IUPUI.EDU> writes:
> Is there some sort of problem with the gateway between IPMDF and the
> vmsnet.mail.pmdf newsgroup?  Or has this list really been silent since
> 6-Jul-1992?

Apparently not.  I normally read this group as bit.listserv.pmdf-l because
it seems to get the same messages more quickly than vmsnet.mail.pmdf.
However, both newsgroups are roughly equivalent on my system as far as
items received.  Your question appears in both groups!

Therefore, it would seem that the problem lies in your feed for v.m.p (or
vmsnet in its entirety?)
--
===========================================================================
Ken Connelly, Systems/Operations Manager         Internet: connelly@uni.edu
Information Systems and Computing Services
University of Northern Iowa                       USWestNet: (319) 273-2357
Cedar Falls, IA  50614-0121                             FAX: (319) 273-3509
As time goes on, it becomes more and more apparent that elected officials
should be required to pass a competency test.  Then we wouldn't have any,
and all would be right with the world!
===========================================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"MITCHELL%UTHSCSA.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 21 Jul 92 22:43:19 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: VMS MAIL_SERVER and undeleted temp files
X-To:         MITCHELL@UTHSCSA, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

There are two cases where MAIL_SERVER is used. One is with PMDF's incoming
message processing. The other is with incoming DECnet mail. I suspect that
the latter is more of an issue; if experience is any indication the use of
MAIL_SERVER in this way can lead to lots of these files left lying about.

PMDF has no direct involvement; these files are created (and deleted) entirely
on the whim of MAIL_SERVER. It would seem that a decent exit handler would
eliminate them unconditionally, but unfortunately this approach is not used
as far as I know.

In short, this is a problem which, even if some abnormal condition in PMDF
was the cause (this is totally hypothetical mind you), is totally the
responsibility of VMS MAIL to clean up properly. Given the fact that these
are pure scratch files not entered into any directory there is no way for
PMDF to get a handle on the file even if it wanted to.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Indiana University - Purdue University at Indianapolis
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"IPMDF@YMIR.CLAREMONT.EDU"
X-VMS-Cc: IMHW400
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 20 Jul 92 14:07:24 -0500
From:         "Mark H. Wood" <IMHW400@INDYVAX.IUPUI.EDU>
Subject:      Problem with vmsnet.mail.pmdf gateway?
X-To:         IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Is there some sort of problem with the gateway between IPMDF and the
vmsnet.mail.pmdf newsgroup?  Or has this list really been silent since
6-Jul-1992?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"Rollo.Ross@Levels.UniSA.Edu.Au"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 26 Jul 92 19:32:19 GMT
From:         "Ned Freed (Postmaster)" <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Problem with timezone names
X-To:         Rollo.Ross@Levels.UniSA.Edu.Au, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

The logic for getting values from MULTINET_TIMEZONE should, in practice,
never be used. This is because PMDF should always be started prior to
starting Multinet. See the documentation on startup ordering in the
PMDF installation guide for details. In essence, PMDF should be started
prior to starting any networking software PMDF interacts with. (In other
words, run PMDF_STARTUP very early during startup.) PMDF_SUBMIT_JOBS
should then be run only after ALL networking software has started. (And
after you have made all appropriate logical name assignments and other
changes that would affect PMDF or other networking software you use.)

Since the logic for setting PMDF_TIMEZONE via the other logicals is, in
practice, useless, we plan to get rid of it entirely in the next release.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"C.Chaundy@its.unimelb.EDU.AU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 22 Jul 92 17:14:47 GMT
From:         "Ned Freed (Postmaster)" <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Repeating messages on info-pmdf list
X-To:         C.Chaundy@its.unimelb.EDU.AU, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

The problem was caused by disk errors on ymir.claremont.edu. It should
be fixed now.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"TIHOR@ACFcluster.NYU.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 27 Jul 92 22:02:15 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Mail lists and large queues
X-To:         TIHOR@ACFcluster.NYU.EDU, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

One additional point. While it is true that list traffic can flood the
queues in some cases, it is also true that in most cases regular mail
will get jobs queued just to process it. As such, the list expansion already
tends to happen in a somewhat independent fashion. For example, we expand
several very large lists on ymir.claremont.edu, several of which see heavy
traffic, and in most cases this has virtually no effect on the initial
delivery attempt for regular mail.

Immediate delivery jobs for messages only "see" messages that they were
queued to process -- specifically, messages that appeared after some
time. This means that if mail from a list is already expanding in the
background the immediate job does not see it.

There is only one limitation with this approach. If your queues are so
narrow that there are always jobs pending you may not get additional
immediate jobs queued in some cases. The simple solution in this case is
to use a wider queue that supports more simultaneous delivery jobs at
once. I recommend at least six and possibly even eight job slots if you're
serious about expanding large lists to many channels. Note that
prioritization helps but cannot solve this problem -- if you use up all
your job slots on expansion of lists there is simply no place for
immediate message operations to go. Once prioritization of list messages is
available you can set things up so that these messages don't create
immediate jobs, but that's about all you can do. A job, once created,
is not the sort of thing that can change its mind about what it is
doing. The VMS batch system is not flexible enough to suspend a running
job to let a later job start running.

The big problem comes with periodic delivery. Although periodic jobs try
to process messages with the fewest number of delivery attempts first, it
is far from certain that this simple criteria suffices to correctlyu
prioritize list traffic. This is the place where handling of jobs in
priority order is a real benefit. If a list expands but sees lots of
temporary delivery failures it can really wedge up periodic delivery.
This is the case that prioritization really fixes.

                                Ned
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"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 21 Jul 92 22:33:33 GMT
From:         Rick Pim <RICK@QUCDNEE>
Subject:      stuck message in bit_gateway channel
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

i just came back from holiday (inevitably) to find a message stuck in
my bit_gateway channel. this channel has been working (with no problems
that i'm aware of) for many months; i've never seen anything like this
before.

the file in pmdf_root:[queue.bit_gateway] is as follows:

m;EPMDF@YMIR.BITNET
smtpuser@bitnet-gateway

Received: from JNET-DAEMON by qucdnee.ee.QueensU.CA (PMDF #12466) id
 <01GMC8K32TL09ZLDWK@qucdnee.ee.QueensU.CA>; Mon, 13 Jul 1992 18:26 EST
Received: From YMIR(EPMDF) by QUCDNEE with Jnet id 1796 for SMTPUSER@QUCDNEE;
 Mon, 13 Jul 1992 18:26 EST
Date: Mon, 13 Jul 1992 18:26 EST
Date-warning: Date header was inserted by qucdnee.ee.QueensU.CA
From: EPMDF@YMIR.BITNET
To: SMTPUSER@QUCDNEE.EE.QUEENSU.CA
Message-id: <01GMC8K32TL09ZLDWK@qucdnee.ee.QueensU.CA>
X-Envelope-to: smtpuser@bitnet-gateway
PMDF-Warning: To line inserted; none found in original message header.

HELO YMIR.BITNET
TICK 0001
MAIL FROM:<epmdf@YMIR.BITNET>
RCPT TO:<RICK@QUCDNEE.BITNET>
DATA
Received: from YMIR.CLAREMONT.EDU by YMIR.CLAREMONT.EDU (PMDF #2326 ) id
 <01GMBY2G8YV0984O20@YMIR.CLAREMONT.EDU>; Mon, 13 Jul 1992 13:27:33 PDT
Received: from THOR.INNOSOFT.COM by YMIR.CLAREMONT.EDU (PMDF #2326 ) id
 <01GMBWE38SMO984N5C@YMIR.CLAREMONT.EDU>; Mon, 13 Jul 1992 12:38:29 PDT
Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF #1336 ) id
 <01GMBWD8T6LC8WW3AJ@INNOSOFT.COM>; Mon, 13 Jul 1992 12:37:41 PDT
Date: 13 Jul 1992 12:37:41 -0700 (PDT)
From: "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject: RE: Internet mail through DECnet routing
To: OZMINSKI@MSUKBS.BITNET, IPMDF@YMIR.BITNET
Errors-to: epmdf@YMIR.BITNET
Resent-message-id: <01GMBY2GPD4U984O20@YMIR.CLAREMONT.EDU>
Message-id: <01GMBWD8TG8I8WW3AJ@INNOSOFT.COM>
X-Envelope-to: RICK@QUCDNEE.BITNET
X-VMS-To: IN%"OZMINSKI%MSUKBS.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Fruit-of-the-day: appl
Fruit-of-the-day-warning: Fruit is not valid

(body of message deleted)

QUIT
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.claremont.edu"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 25 Jul 92 07:11:22 GMT
From:         Jeremy Begg <JEREMY@VSM.COM.AU>
Subject:      RE: Request for minor changes to installation procedure
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

From Ned:
>The proper approach is to put these things collectively into a site-specific
>startup file. This file should then be run immediately after PMDF_STARTUP is
>run. This eliminates the possibility that these settings will be lost after an
>upgrade. It also eliminates the possibility that we'll lose your changes, and
>it eliminates the need to scan the old startup looking for changes.

So how about built-in support for something like SYS$STARTUP:PMDF_SYSTARTUP.COM?

Regards,

        Jeremy Begg

  +----------------------------------------------------------+
  | VSM Software Services,  |  E-Mail:  jeremy@vsm.com.au    |
  | P.O.Box 801, Unley,     |   Phone:  +61 8 4145074 (pager)|
  | South Australia 5061    |     FAX:  +61 8 3734911        |
  +----------------------------------------------------------+

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU