🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

2 total messages Started by pat Tue, 29 Dec 1992 17:22
"error in device name" message on MX 3.1
#353
Author: pat
Date: Tue, 29 Dec 1992 17:22
37 lines
2714 bytes
I've long been running MX 2.0 on a Vaxcluster, all seven of whose nodes are
currently running VMS 5.5 and CMU-TEK version 6.6-5.  I haven't upgraded MX
for two reasons:  1) "If it ain't broke, don't fix it" and  2) A couple of
previous attempts to upgrade to 3.1 have been unsuccessful.  However, a recent
lack of success on my users' part in sending messages to the CERN particle
accelerator site in Europe (addresses ending in .CH, e.g., joe@foo.bar.ch; the
messages simply vanish and no bounced mail messages are received) is forcing
me to confront this upgrade (to 3.1; unless somebody advises me otherwise,
I'll get 3.1 working first and then worry about 3.1C or whatever is the
current revision) and conquer it by any means necessary, in hopes that the
newer version will have less trouble sending to CERN.

Here's my problem:  I've customized the 3.1 installation for our site (the
ROUTER, LOCAL, and MLF processes all run on 3 of the 7 nodes; SMTP runs on
these 3 plus one other node; and SMTP_SERVER runs on all 7 nodes).  As best
I can tell, I've modified it so it should be configured just as it has been
to successfully run MX 2.0.  I start up MX and all the appropriate processes
start up, and will run until I stop them myself.  However, as soon as I try
to send an outgoing message, I receive the following error:

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

I've checked all of the appropriate logicals I'm aware of (SHOW LOGICAL *MX*
and SHOW LOGICAL *NETLIB*), and as best I can tell they're all defined
properly; i.e., all logicals defined to point to directories or files do so
successfully and MX_INET_HOST, MX_NODE_NAME, MX_SMTP_DEFAULT_ROUTER and
MX_VMSMAIL_LOCALHOST all point to the correct machines.  Does anybody have
any idea what could be wrong here?  Apologies if this is a beginner's question;
I've recently taken over MX duties from the guru who set up 2.0 on this site
and am still on the learning curve.  Also, please let me know if I can supply
additional useful information.  Many thanks in advance.

- Patrick Walsh
  University of Virginia Department of Physics
  pw@virginia.bitnet, pw@virginia.edu, pat@gomez.phys.virginia.edu
Re: "error in device name" message on MX 3.1
#356
Author: Carl J Lydick
Date: Thu, 31 Dec 1992 18:04
41 lines
2681 bytes
In article <00965cfc.5c2d8740.2806@gomez.phys.virginia.edu>, pat@che.phys.Virginia.EDU writes:
>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
>
>I've checked all of the appropriate logicals I'm aware of (SHOW LOGICAL *MX*
>and SHOW LOGICAL *NETLIB*), and as best I can tell they're all defined
>properly; i.e., all logicals defined to point to directories or files do so
>successfully and MX_INET_HOST, MX_NODE_NAME, MX_SMTP_DEFAULT_ROUTER and
>MX_VMSMAIL_LOCALHOST all point to the correct machines.  Does anybody have
>any idea what could be wrong here?  Apologies if this is a beginner's question;
>I've recently taken over MX duties from the guru who set up 2.0 on this site
>and am still on the learning curve.  Also, please let me know if I can supply
>additional useful information.  Many thanks in advance.

Here are the MX-related files my process has open after answering the
"To:	" prompt with an MX address, after I get the "Cc:	" prompt:
	DUD0:[MX.EXE]MX_MAILSHR.EXE
	DUD0:[MX.EXE]FLQ_SHR.EXE
	DUD0:[MX.EXE]MX_SHR.EXE
	DUD0:[MX.EXE]MX_MAILSHRP.EXE
	DUD0:[MX.QUEUE]SYSTEM_QUEUE.FLQ_CTL
	DUD0:[MX.QUEUE]6796.SRC_INFO
	DUD0:[MX.QUEUE]6796.HDR_INFO
	DUD0:[MX.QUEUE]6796.MSG_TEXT
	DUD0:[MX.EXE]MX_MSG.EXE
These involve the logical names:
	MX_MAILSHR
	MX_EXE
	MX_MAILSHRP
	FLQ_DIR
and any further logical names involved in translating them.  I'd check the
definitions of those logical names, if I were you.  Good luck.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads