HDTenEightyP/NetNews huggingface dataset:
From: sys_hjk@LIFRA.LIF.DE (Hans-Joachim Koch)
Newsgroups: vmsnet.mail.mx
Subject: RE: "opcode reserved to DIGITAL fault" still killing SMTP
Date: 9 Jan 93 15:16:33 GMT
Reply-To: koch@lifra.lif.de
Organization: Lahmeyer International GmbH, Frankfurt/Main, Germany

In article <009664C6.FF4C6FA0.13173@WKUVX1.BITNET>, goathunter@WKUVX1.BITNET (Hunter Goatley) writes:
>pat@che.phys.Virginia.EDU writes:
>>
>>Well, I've just tried reinstalling MX 3.1 from scratch, creating a new
>>CONFIG.MCP, etc., and I'm getting the same "opcode reserved to DIGITAL fault"
>>error.  Any ideas?  Any more information I can supply?  Thanks.

Just a hint, because I had the same situation two days ago (with an own 
program, not with MX). Your problem may have other reasons.

I have a ci-cluster and made a new version of a shared library on one
node and installed it there. My small program used an entry from that 
library. It worked on one node, but gave the above error message, when 
executed on the other node.

The solution: (after a lot of gray hair) I installed the sharable 
library on the other node.

I think the above message is some sort of all-purpose message... :-(

Hans.
-- 
Hans-Joachim Koch, Computer department of Lahmeyer International
Lyoner Strasse 22, POB 71 06 51, D-6000 Frankfurt (Main) 71, Germany
Phone: +49 69 6677-642, Fax: +49 69 6677-571, Tx: 413478 li d
EUnet: koch@lifra.lif.de, AMPRnet: dk9om@db0lj.ampr.org
From: pat@che.phys.Virginia.EDU
Newsgroups: vmsnet.mail.mx
Subject: Followup to: "error in device name" message on MX 3.1
Date: Mon, 04 Jan 1993 11:55:24 EST
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

Thanks to Hunter Goatley and Carl Lydick, both of whom correctly suggested
that I had a problem with the definition of FLQ_DIR which was causing me to
encounter the following error whenever I tried to SEND using MX 3.1:

>MAIL> send
>To:     mx%"user@site.edu"                 ! dummy user and site, of course
>%RMS-F-DEV, error in device name or inappropriate device type for operation

It turns out that I had defined FLQ_DIR in a nonstandard way which was
perfectly legal as far as VMS is concerned, but unacceptable to MX; thus
DCL commands like $ DIR FLQ_DIR worked normally, leaving me with the false
impression that everything was set up properly.  (I set up the faulty
definition of FLQ_DIR some weeks back, and I'm afraid I can't remember why
I was using a nonstandard definition; it was probably just part of a trial-
and-error process.)

Now I have a new question:  my SMTP process is dying on me as soon as I try
to SEND.  The appropriate *.HDR_INFO, *.MSG_TEXT, *.SRC_INFO and *.SMTP_INFO
files are being created in the (now correctly-defined) FLQ_DIR directory,
but they all end up stranded there because SMTP has died.  The VMS accounting
utility tells me that SMTP is dying with status code 1000043C,

%SYSTEM-F-OPCDEC, opcode reserved to DIGITAL fault at PC=!XL

Does this ring a bell with anyone?  A bug in MX 3.1 (i.e., "Try 3.1C, dummy!),
or am I still doing something wrong?

(A review of my MX environment:  7-node Vaxcluster, all nodes running VMS 5.5
 and CMU-TEK 6.6-5.  MX 2.0 currently running successfully on all nodes with
 the exception of occasional failures to deliver, particularly to CERN in
 Europe (addresses ending in .CH).  ROUTER, LOCAL and MLF run on 3 of the
 7 nodes; SMTP runs on these 3 plus 1 other node, and all 7 nodes run
 SMTP Server.)

- Patrick Walsh
  University of Virginia Department of Physics
  pw@virginia.bitnet, pw@virginia.edu, pat@gomez.phys.virginia.edu
From: lewisc@elcsci.com (Chuck Lewis)
Newsgroups: vmsnet.mail.mx
Subject: Queue entries stuck in READY state
Date: 4 Jan 93 23:04:55 GMT
Organization: Electro Scientific Industries, Portland OR

I recently managed to get my MX components hung up while attempting to update
the MX logicals to match my new registered domain name. I noticed there was a
problem when I discovered that my messages to  test the new address were not
being delivered. A STATUS command to MCP resulted in the error  'no such agent
processes are running',  while a show system did show that the MX processes
existed. Attempting to restart the MX components resulted in errors such as

	%MX-F-AGENTALRDY, agent MX_UUCP is already running
	-SYSTEM-F-IVBUFLEN, invalid buffer length

Restoring MX_logicals.dat to its original state solved the above
problem. However, messages posted during the time that MX was not
running correctly now appear in my queue in a READY state and have
for several days. Other messages posted after I got MX running again
are delivered correctly and promptly.

What steps should I perform to cause these pending entries to be 
delivered. I can find nothing in the trace logs that indicates any
MX component is attempting to process these entries.

I have attempted a QUEUE READY command to no affect.
 
Thanks for any helpful hints.


MCP>show version
MX version is is: MX V3.1C
MCP>que show /all/full

Entry: 577, Origin: [VMSmail] CAMPBELLL    "Laura @Forty Two Ten"
  Status: READY, size: 1498 bytes
  Created: 11-DEC-1992 16:05:45.16, expires 10-JAN-1993 16:05:45.16
  Last modified 15-DEC-1992 16:21:29.57
    Recipient #1: <joeys@esipdx>

Entry: 578, Origin: [VMSmail] RONNINGK    
  Status: READY, size: 254 bytes
  Created: 14-DEC-1992 09:02:15.11, expires 13-JAN-1993 09:02:15.11
  Last modified 15-DEC-1992 16:32:18.49
    Recipient #1: <dougk@esipdx>


Chuck Lewis                         |  UUCP        esimis!lewisc
Electro Scientific Ind.             |              lewisc@elcsci.com
13900 NW Science Park, Portland Or  |  Compuserve  71140,2271
Xref: sparky vmsnet.mail.misc:95 vmsnet.sysmgt:429 vmsnet.tcp.multinet:5
From: rsaigal@jade.tufts.edu (Ranjani Saigal)
Newsgroups: vmsnet.mail.misc,vmsnet.sysmgt,vmsnet.tcp.multinet
Subject: Distribution Lists on Internet
Date: 8 Jan 93 17:06:14 GMT
Organization: Tufts University - Medford, MA


	Is there a way to send messages using a VMS distribution list so
that the header does not contain the names of all the people it is sent
to, but has just a list name? The list will contain INTERNET addresses.
We are using Multinet Tcp/ip. Please E-mail the response to me.


			-Thanks

				Ranjani
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Using BITNET (NJE) style address on outbound Email to BITNET
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 04 Jan 1993 14:04:01 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 04 Jan 1993 14:04:01 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GT4GE8GAYQ90OJNS@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SKIPPER%MEDCOLPA.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> We are a BITNET only site, but are also registerred with the NIC as
> MEDCOLPA.EDU.  Using PMDF, I have our address being rewritten to read
> user@ccc.medcolpa.edu.  This has been working quite well (after a few
> changes to the way we were registerred), until I tried to renew some
> AFD to NETSERV@PUCC.  Since NETSERV is a NJE only server, it will only
> accept mail addresses with NJE syntax (user@medcolpa) and NOT domain style
> addresses.  Is there a way to make PMDF forward a BITNET style return
> address if the outgoing mail is sent to a BITNET only site or server and
> domain style to all others.  It seems that I have seen or read something
> addressing this matter before.  If so, I would be more than willing in
> reading the manual if directed to the appropriate location.

Well, CONFIGURE.COM usually sets things up correctly.  However, you may not
have ever used CONFIGURE.COM.  (Nothing wrong with that; most ancient PMDF
sites have never had cause to run that procedure.)

Anyhow, check to see if there is a local alias on your bit_local channel;
e.g., see if it looks something like

   bit_local ...
   JNET-DAEMON  MEDCOLPA
                ^local alias


If the "MEDCOLPA.BITNET" is missing, then go ahead and add it.  Also, check
your file PMDF_ROOT:[TABLE]BITNET_DOMAINS_DRIVER.COM file (or whatever you use
to drive PMDF_ROOT:[EXE]BITNET_DOMAINS.COM) and see if you define a
BITNET_ALIAS symbol; e.g.,

   $ bitnet_alias = "MEDCOLPA"

After making any changes, be sure to recompile and reinstall your configuration
(assuming that you use a compiled configuration) and restart BN_SLAVE with the
command PMDF RESTART BN_SLAVE.

Now, if both of these items looks okay, then it might have something to do with
your entry in DOMAIN.NAMES or XMAILER.NAMES....  Let us know if this is the
case and we'll take it from there.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Files as recipients
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 06 Jan 1993 11:29:28 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Jan 1993 11:29:28 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GT73KB4Y5E90OVWF@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"RAMSEY@CUA.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> Is it possible to specify a file as a mail recipient?  what I'd like
> to do is set up an entry in a personal (or system) alias database that
> points to one or more addresses plus a file on the local system for
> archiving.  Can I do this without using DELIVER?  I couldn't seem to
> find any info about this in the manual (but perhaps I'm blind).

Yes, use an address of the form

   "+device:[directory]filename"@local-host

as the address in the alias file.  For instance,

   "+disk1:[mail_archives]info-pmdf.txt"@innosoft.com

Now, you have to do a couple of things first:

  (1) If you do not have PMDF-FAX, then create a PMDF_USER account which
      has no privileges and is in a UIC group all of its own (and is not
      in an implicitly privileged UIC group either).  The account name need
      not be PMDF_USER.  The account should be disusered, disnewmailed,
      captive, restricted, etc., etc.

  (2) Define the system-wide logical PMDF_USER_USERNAME whose translation
      value is the name of the PMDF_USER account; e.g.,

         $ define/system PMDF_USER_USERNAME "PMDF_USER"

      Add this logical definition to your system startup.  Next time you
      install PMDF, elect to create a PMDF_USER account.  By doing this,
      the account will properly be created and the definition of the
      PMDF_USER_USERNAME logical will be added to your PMDF_STARTUP
      command procedure.

  (3) Create the archive file; e.g.,

         $ create disk1:[mail_archives]info-pmdf.txt
         ^Z
         $

      Make sure that the PMDF_USER account has write access to this file.

The whole point behind the PMDF_USER account is to create a safe context for
use by PMDF when appending messages to files.  You don't want people casually
appending DCL commands to, say, your system startup procedure or system login
command procedures.  PMDF will only perform the append operation to files which
the PMDF_USER account has write access.

By the way, the address format to use from withing VMS MAIL would be

   in%"'+disk:[device]filename'@local-host"

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: Using BITNET (NJE) style address on outbound Email to BITNET sites...
From: skipper%medcolpa.bitnet@ymir.claremont.edu
Date: 04 Jan 1993 16:09:09 -0500
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 04 Jan 1993 16:09:09 -0500
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GT4EI2X5V690OJ21@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Hopefully this is NOT a FAQ.

Anyway,

We are a BITNET only site, but are also registerred with the NIC as
MEDCOLPA.EDU.  Using PMDF, I have our address being rewritten to read
user@ccc.medcolpa.edu.  This has been working quite well (after a few
changes to the way we were registerred), until I tried to renew some
AFD to NETSERV@PUCC.  Since NETSERV is a NJE only server, it will only
accept mail addresses with NJE syntax (user@medcolpa) and NOT domain style
addresses.  Is there a way to make PMDF forward a BITNET style return
address if the outgoing mail is sent to a BITNET only site or server and
domain style to all others.  It seems that I have seen or read something
addressing this matter before.  If so, I would be more than willing in
reading the manual if directed to the appropriate location.

Thanks in advance.

/tom

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
L. Thomas Skipper (Tom)                             M     M   CCCCCC  PPPPPPP
VAX Systems & Networking Manager                    MM   MM  C        P      P
Medical College of Pennsylvania                     M M M M  C        P      P
College Computer Center                             M  M  M  C        PPPPPPP
2900 Queen Lane                                     M     M  C        P
Philadelphia, Pennsylvania 19129                    M     M   CCCCCC  P

BITNET:  SKIPPER@MEDCOLPA  Internet: SKIPPER@CCC.MEDCOLPA.EDU
PHONE:   (215)991-8180          -OR- SKIPPER@SINGER.ASRI.EDU
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Newsgroups: vmsnet.mail.pmdf
Subject: running bitnet_domains.com for current xmailer and domain names files
From: "Anna Tomecka, x7733" <anna%clarku.bitnet@ymir.claremont.edu>
Date: 07 Jan 1993 14:18 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 07 Jan 1993 14:18 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GT8HQZ3Y9U90OT4U@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.bitnet"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Hi,

I just tried to run the bitnet_domains.com after having loaded new
xmailer.names and domain.names files.  The procedure finished fine, but it did
not create a new tcpip.rules file.  The new file is empty.  Have I missed
something and shouldn't be using xmailer and domain names files anymore?  Can
anybody help, please?  Thanks in advance.

Anna Tomecka
Systems Manager, Clark University
Newsgroups: vmsnet.mail.pmdf
Subject: pmdf-mr
From: Cheri Weaver - 845-9430 ext 2153 <cheri.weaver@sheridanc.on.ca>
Date: 07 Jan 1993 17:30 -0400 (EDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 07 Jan 1993 17:30 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GT8O71CNN690P2XT@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@ymir.claremont.edu"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I am running PMDF v.4 and PMDF-MR.  I can send mail from Allin1
to an Ultrix machine (TCP/IP Services for VMS) and it gets delivered
with no problems.  Unfortunatley I cannot reply to the message.
I am using sendmail on the ultrix machine and the first "from" in the
header seems to have the replyable address but the second "from:"
is being used and it is full of, I believe, x400 gobblygook and
returns an error.  I can send mail from the Ultrix machine to the
Allin1 account using what shows up on the from line.

I would appreciate it if someone can give me any ideas as to how I
should be solving the problem or point me to the right place.

Thanks
Cheri
Newsgroups: vmsnet.mail.pmdf
Subject: RE: immediate vs. periodic
From: Ned Freed <ned@innosoft.com>
Date: 12 Jan 1993 09:39:29 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Jan 1993 09:39:29 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTFDHGPL4Y8WWDGU@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"JOHNSON@northeastern.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

There is at least one oversight in the immediate job creation logic that
can cause messages to slip into the queue without getting processed by
an immedate job. This was discussed earlier this month on info-pmdf;
please check the original messages on this subject for details. This
will be fixed in the next release.

It is also possible that your immediate jobs are dying without doing any
processing; you'd have to examine your logs to see if this is happening. It
is also possible that processing is happening but for some reason the
user's mail files are temporarily unavailable. This is a very frequent
event on some systems. Again, you'll have to check the logs to tell the
specifics. You can usually tell whether or not a message has received
some attention by the file name: names beginning with ZZ have not been
processed; names beginning with ZY have had one delivery attempt; names
beginning with ZX have had two, and so on.

You can always increase the frequency of periodic processing if you want
to try to push messages through faster. This is done with the
PMDF_POST_INTERVAL logical. I would not recommend decreasing the interval
to anything less than one hour, however. You can always use the period
setting to service some channels more often than others.

In summary, PMDF provides ample means for gettng just as much delivery
processing as you need. The problem is making sure that the processing you
ask for is actually efficacious; for example, frequent reprocessing of
SMTP channels is largely a waste of resources since unreachable systems
tend to remain unreachable for periods measured in hours if not days.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: Empty MAILSERV list causes error message
From: rollo.ross@levels.unisa.edu.au
Date: 12 Jan 1993 16:51:46 +1030
Organization: University of South Australia
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Jan 1993 16:51:46 +1030
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTEPT1Y6VM8WWB57@YMIR.CLAREMONT.EDU>
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

	I've just noticed that an empty local MAILSERV distribution list
causes PMDF to return an error message to anyone who sends a message to it.
The error message says, for example:

>The message could not be delivered to:
>
>Addressee: PACS-L-FORWARD
>Reason:
>  Illegal host/domain in address "PACS-L-EXPAND"
>  no addressees in

	While I can see some value in warning a human that a distribution
list is empty, in this case the distribution list was a redistribution of
an overseas list. It seems a bit risky to send error messages back to a
list server just because the normal ebb and flow of subscriptions to our
own list had resulted in it being empty at the time. Some list maintainers
can be trigger-happy when it comes to dropping entries from their lists!

	Our local list was set up as:

PACS-L: PACS-L-FORWARD
PACS-L-EXPAND: <PMDF_MAILSERV_MAIL_DIR:PACS-L.DIS, PACS-L-ERROR
PACS-L-REQUEST: MAILSERV
PACS-L-ERROR: POSTMASTER

	Is there some way of arranging that only the local postmaster
gets the error message in this special case of an empty MAILSERV list?
Or do I have to put a dummy address in each DIS file to make sure it
never becomes empty?

                                    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
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Another question
From: ned@sigurd.innosoft.com
Date: 11 Jan 1993 17:35:47 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Jan 1993 17:35:47 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@SIGURD.INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTEFT44E5E95MT1Z@SIGURD.INNOSOFT.COM>
X-Vms-To: IN%"xu@neuro.psycha.upenn.edu"
X-Vms-Cc: IN%"ipmdf@SIGURD.INNOSOFT.COM"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

This log isn't sufficiently detailed to track down the specifics of the
problem. All it says is that the attempt to open the connection failed with
some sort of temporary error. This could be a problem on the remote host, a
problem with the network, a nameserver problem, or a local host configuration
problem.

You can get more information into the log by enabling master_debug on the
utcp_local channel. You can also test your network connectivity to the
destination host by other means (like telnet, for instance).

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: Where can I find DECUS UUCP?
From: Jody Glasser <glasser@tdycont.com>
Date: 08 Jan 1993 14:21:46 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 08 Jan 1993 14:21:46 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTA6I6OEDE8WVYV4@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@ymir.claremont.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Does anyone know of an anonymous FTP site where I can get DECUS UUCP?

Jody Glasser

----------------------------------------------------------------------
##                            |\-=
## Jody Glasser          |\   ||\-=      Internet: glasser@tdycont.com
## Teledyne Controls    <)))))))))))))        CIS: 76220,2260
## Director,             |/   ||/-=         Voice: (310)820-4616 x2630
## Software Engineering       |/-=            FAX: (310)820-0183
----------------------------------------------------------------------
Newsgroups: vmsnet.mail.pmdf
Subject: RE: immediate vs. periodic
From: John C Klensin <klensin@infoods.mit.edu>
Date: 12 Jan 1993 21:31:54 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Jan 1993 21:31:54 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: JOHNSON@NORTHEASTERN.EDU, IPMDF@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTFW3U0ALU8WWH89@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"NED@INNOSOFT.COM"
X-Vms-Cc: IN%"JOHNSON@NORTHEASTERN.EDU", IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Mail-System-Version: <MultiNet-MM(335)+TOPSLIB(156)+PMDF(4.1)@INFOODS.UNU.EDU>

>ask for is actually efficacious; for example, frequent reprocessing of
>SMTP channels is largely a waste of resources since unreachable systems
>tend to remain unreachable for periods measured in hours if not days.

Ned,
  It is worth adding to this that HR (RFC1123) prohibits setting
reprocessing of SMTP channels at intervals of less than, if I recall, 30
minutes.  The rationale for that was general concern about network
resources but also recognition of the tendency you mention-- i.e., it is
a waste of resources and can cause congestion on busy systems and it
rarely accomplishes much anyway.
    john
Newsgroups: vmsnet.mail.pmdf
Subject: RE: running bitnet_domains.com for current xmailer and domain names
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 07 Jan 1993 11:44:57 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 07 Jan 1993 11:44:57 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GT8IEPN70Y90P2SZ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ANNA%CLARKU.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> I just tried to run the bitnet_domains.com after having loaded new
> xmailer.names and domain.names files.  The procedure finished fine, but it did
> not create a new tcpip.rules file.  The new file is empty.  Have I missed
> something and shouldn't be using xmailer and domain names files anymore?  Can
> anybody help, please?  Thanks in advance.

You should not run bitnet_domains.com.  Instead, you should be running a
shell procedure which sets the appropriate DCL symbols and then invokes
bitnet_domains.com.  Check to see if you have any such procedure
(e.g., BITNET_DOMAINS_DRIVER.COM) in your PMDF_ROOT:[TABLE] directory.
You should be running that procedure and not BITNET_DOMAINS.COM.

Dan