Article View: vmsnet.mail.mx
Article #356Re: "error in device name" message on MX 3.1
From: Carl J Lydick
Date: Thu, 31 Dec 1992 18:04
Date: Thu, 31 Dec 1992 18:04
41 lines
2681 bytes
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.
Technical Details
Message-ID:
<1hvcmlINNfdu@gap.caltech.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!usc!elroy.jpl.nasa.gov!news.claremont.edu!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARLReferences:
<00965cfc.5c2d8740.2806@gomez.phys.virginia.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!usc!elroy.jpl.nasa.gov!news.claremont.edu!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Newsgroups: vmsnet.mail.mx Subject: Re: "error in device name" message on MX 3.1 Date: 31 Dec 1992 18:04:05 GMT Organization: HST Wide Field/Planetary Camera Lines: 41 Distribution: world Message-ID: <1hvcmlINNfdu@gap.caltech.edu> References: <00965cfc.5c2d8740.2806@gomez.phys.virginia.edu> Reply-To: carl@SOL1.GPS.CALTECH.EDU NNTP-Posting-Host: sol1.gps.caltech.edu