Archive-Date: Sat, 01 Oct 1994 00:03:32 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 01 Oct 1994 00:03:18 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <00985448.4E64AAFE.260@WKUVX1.WKU.EDU> Subject: MX-LIST Administrivia: Monthly Post Posting statistics for list MX-LIST during September 1994 Total number of posts: 141 Total number of posters: 58 Total number of subscribers: 243 Total number of digest subscribers: 43 Last modified: 7-JUL-1994 10:04 (Updated version info) Welcome to MX-List@WKUVX1.WKU.EDU, an electronic mailing list established for the discussion of the Message Exchange mail software. This is a routine posting you will see from time to time on MX-List. MX-List postings are also available in a daily digest format. To subscribe to the digest, send the following command in the body of a mail message to MXserver@WKUVX1.WKU.EDU: SUBSCRIBE MX-List-Digest "Your real name here" The MX-List archives are maintained at ARCHIVES@WKUVX1.WKU.EDU. To get a copy of any month's postings, send an e-mail message with the body SEND MX-List.yyyy-mm to ARCHIVES@WKUVX1.WKU.EDU, where "yyyy" is the year and "mm" is the numeric representation of the month. For example, the message SENDME MX-List.1992-04 will send the archives for April 1992. MX itself is available via anonymous ftp from ftp.spc.edu in [.MX.MX041]. You can also get it via e-mail by sending the commands SEND MX and SEND FILESERV_TOOLS on separate lines in the body of a mail message to FILESERV@WKUVX1.WKU.EDU. To remove yourself from the mailing list, send the following command to MXserver@WKUVX1.WKU.EDU: SIGNOFF MX-List MXserver supports a few other commands for your convenience. The following commands can be handled automatically by the list processor: SIGNOFF MX-List - to remove yourself from the list REVIEW MX-List - to get a list of subscribers QUERY MX-List - to get the status of your entry on the list SET MX-List NOMAIL - to remain on the list but not receive mail SET MX-List MAIL - to resume receiving mail from the list SET MX-List CONCEAL - to not report your address in a REVIEW SET MX-List NOCONCEAL - to report your address in a REVIEW SET MX-List REPRO - to receive posts you make to MX-List SET MX-List NOREPRO - to not receive posts you make to MX-List LIST - to get a list of mailing lists served by WKUVX1 HELP - to receive a help file By default, subscriptions are set to MAIL, REPRO, NOCONCEAL. If you have any questions, comments, or suggestions about MX-List, please contact the list owner at the address below. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Hunter Goatley, VAX Systems Programmer goathunter@WKUVX1.WKU.EDU Western Kentucky University Academic Computing, STH 226 (502) 745-5251 Bowling Green, KY 42101 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ================================================================================ Archive-Date: Sat, 01 Oct 1994 06:57:00 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 01 Oct 1994 06:56:39 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00985482.0CDCD10D.3@ALPHA.WKU.EDU> Subject: RE: multiple node in mx_startup_info "Michael H. Spence, Eastman Chemical" writes: > >I need to add some nodes to run mx processes in the mx_startup_info.dat file. >However, right now I only have one node defined. What is the syntax for adding >processes on additional nodes? > >001NETLIB:* >002FLQ_MGR:STD150 >002ROUTER:STD150=1 >003LOCAL:STD150=1 >004SMTP:STD150=1 >004SMTP_SERVER:STD150 Just tack on additional nodes, where "*" is "all nodes": 004SMTP:STD150=1,NODE2=4,NODE3=2 etc. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Sat, 01 Oct 1994 12:31:11 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: jspinnow@netcom.com (John Stewart Pinnow) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX 4.1 SMTP Server Dying... Message-ID: Date: Sat, 1 Oct 1994 15:31:27 GMT To: MX-List@WKUVX1.WKU.EDU It seems to work for awhile and then quits. It has happend since umm we upgraded to UCX 3.1. My theory is that UCX Smtp isn't fully disabled. I just don't have enuf access to find out. I would like any help so I can tell the person that does have such access to fix it given this. -- ____________________________________________________________________________ Tmoh Research Internet: jspinnow@netcom.com Phone: (414) 761-1537 John S. Pinnow jspinnow@world.std.com Disclaim: Opinions==Mine ================================================================================ Archive-Date: Sat, 01 Oct 1994 19:43:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: stevea48@aol.com (SteveA48) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX 4.1 Install fails creating the system message queues OVMS 6.1 Date: 1 Oct 1994 20:26:09 -0400 Message-ID: <36kun1$5d@newsbf01.news.aol.com> To: MX-List@WKUVX1.WKU.EDU Hi, I'm having problem installing MX 4.1 on and alpha running VMS 6.1. It is in a cluster with non AXP machines. I'm running UCX 3.1. The drive where I 'm install MX on has 1.5 million free blocks on it. The error during install is as follows: %MCP-E-QCVTFAIL. error creating new system message queue -RMS-F-DEV, error in device name or inappropriate device type for operation I'm not typeing an incorrect name. There are no error on the device I've entered the drive name a couple of different ways,both the logical and and node$devie way. I get the same error with both. Any help would be greatly apreciated. --steve anich@sicdes.dnet.etn.com ================================================================================ Archive-Date: Sun, 02 Oct 1994 18:05:49 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: hunt@blade.wcc.govt.nz (Martin D. Hunt) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX processes die Date: Mon, 3 Oct 94 11:13:52 +1200 Message-ID: <36nbbm$dsj@golem.wcc.govt.nz> To: MX-List@WKUVX1.WKU.EDU I have found over the last few weeks that MX processes keep on dying, after about half an hour up. The main ones affected are MX Local and MX SMTP. I suspect the problem may have started when an additional node (an Alpha) started running MX. The exit status in the log files is 1000000C, which translates to access violation (see below): 30-SEP-1994 23:26:43.49: MX SMTP (pid 27019A1E) starting 1-OCT-1994 00:09:35.43: MX SMTP (pid 27019A1E) exiting, status = 1000000C I also find that a status command done on a VAX shows processes running on the Alphas as having a status of "Unknown" (no such problem running the same command from an Alpha). In the following display, the Alpha is Quatar (MX has been shut down on the other Alpha) and MX_STARTUP has just been run on Mecca, so not all processes will be running on the other nodes: PID Node Process name Status Agent type -------- ------ --------------- ------------------ ------------ 2580801D HAVEN MX Router Idle Router agent 25C0266F METIS MX Router Idle Router agent 25E01368 QUATAR MX Router Unknown Router agent 26C03E99 MECCA MX Router Idle Router agent 26E05ED7 NOMAD MX Router Idle Router agent 2701512B BLADE MX Router Idle Router agent 2580641E HAVEN MX Local Idle Local delivery agent 25C02C70 METIS MX Local Idle Local delivery agent 25E01969 QUATAR MX Local Unknown Local delivery agent 26C0409A MECCA MX Local Idle Local delivery agent 26E05ED8 NOMAD MX Local Idle Local delivery agent 2701392C BLADE MX Local Idle Local delivery agent 2580720F HAVEN MX MLF Idle Mailing list/file server 25C0246A METIS MX MLF Idle Mailing list/file server 26C044DB MECCA MX MLF Idle Mailing list/file server 26E04459 NOMAD MX MLF Idle Mailing list/file server 27015220 BLADE MX MLF Idle Mailing list/file server 25804C22 HAVEN MX SMTP Idle SMTP delivery agent 25C02A9E METIS MX SMTP Idle SMTP delivery agent 25E030E7 QUATAR MX SMTP Unknown SMTP delivery agent 26C03E9B MECCA MX SMTP Idle SMTP delivery agent 26E060D9 NOMAD MX SMTP Idle SMTP delivery agent 27015131 BLADE MX SMTP Idle SMTP delivery agent 25807A0E HAVEN MX SMTP Server Idle SMTP server (over TCP/IP) 25C02469 METIS MX SMTP Server Idle SMTP server (over TCP/IP) 25E0196C QUATAR MX SMTP Server Unknown SMTP server (over TCP/IP) 26C03ADA MECCA MX SMTP Server Idle SMTP server (over TCP/IP) 26E04E58 NOMAD MX SMTP Server Idle SMTP server (over TCP/IP) 27014A1F BLADE MX SMTP Server Idle SMTP server (over TCP/IP) 2580820A HAVEN MX FLQ Manager Idle MX FLQ manager 25C02465 METIS MX FLQ Manager Idle MX FLQ manager 26C03AD6 MECCA MX FLQ Manager Idle MX FLQ manager 26E05E54 NOMAD MX FLQ Manager Idle MX FLQ manager 2701521B BLADE MX FLQ Manager Idle MX FLQ manager So, what is the reason for the Unknown status, and how do I stop things dying? ----------------------------------------------------------------------------- Martin D. Hunt This space contains nothing important Systems Administrator because I can't think of what to put. Wellington City Council hunt@wcc.govt.nz ================================================================================ Archive-Date: Mon, 03 Oct 1994 11:33:14 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: desroches@aspen.uml.edu (Dick Desroches, ACC Systems Manager) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MLF: ADD failed: insufficient privileg Date: 3 Oct 94 12:28:21 -0500 Message-ID: <1994Oct3.122821.1@aspen.uml.edu> To: MX-List@WKUVX1.WKU.EDU I'm trying to set up a mailing list under MX 4.1 for the very first time (ever). I've followed everything in the mailing list manual but I can't seem to manage the list. I created a list named "Provost" and named myself as the owner as shown below: DEFINE LIST/nocase "Provost"- /OWNER="desroches@woods.uml.edu"- /ERRORS_TO="desroches@woods"- /DESCRIPTION="Members of Provost Council"- /NOARCHIVE- /PROTECTION=(S:RWED,O:RWED,G:W,W) However, when I try to add users to the list via MXSERVER using this command: ADD Provost user1, user2, ... usern I get the message ADD failed: insufficient privilege. What did I do wrong? Dick Desroches ================================================================================ Archive-Date: Mon, 03 Oct 1994 12:47:54 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 03 Oct 1994 13:47:35 EDT From: Bob Roklan Office B112/7 x7824 Lab b127 x3886 Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: roklan@ptf1.npt.nuwc.navy.mil Message-ID: <0098564D.C9B25D80.1@ptf1.npt.nuwc.navy.mil> Subject: Outgoing mail hangs, SMTP dies Outgoing mail hangs, SMTP dies I upgraded MX from v3.3 to v4.1 on July 19 and have had problems since. The outgoing mail hangs every so often - once or twice a week recently. The incoming mail still gets through. Neither using mcp reset, nor shutting down and restart of mx and cmu/ip help. The only thing that does is to reboot the system. (gasp!) VMS is V5.5-3 and TCP/IP is CMU V6.6-5A. The log file mx_smtp_ptf1.log shows : 28-SEP-1994 10:35:08.56: MX SMTP (pid 000000A7) starting 30-SEP-1994 11:05:27.85: MX SMTP (pid 000000A7) exiting, status = 1000000C The log files otherwise do not show anything alarming. I have looked in the archives of mx-list and didnt find an answer. There is a mention of rewrite rules - we are not using them, and assigning $ define /sys /exec mx_smtp_debug true which I just did. I thought that maybe it happens when a message with a bad address is processed, but I am not sure. Any help would slow my insanity! Bob Roklan roklan@ptf1.npt.nuwc.navy.mil ================================================================================ Archive-Date: Mon, 03 Oct 1994 13:23:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 03 Oct 1994 12:16:06 MDT From: Ask me about Star Stare '95 Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: m_frazier@borgil.cxo.dec.com Message-ID: <00985641.022594A0.1@borgil.cxo.dec.com> Subject: RE: MLF: ADD failed: insufficient privileg |>From: desroches@aspen.uml.edu (Dick Desroches, ACC Systems Manager) _^^^^^_ |> /OWNER="desroches@woods.uml.edu"- _^^^^^_ Could it be that your message is comming from ASPEN when you /OWNER says it is supposed to be WOODS (A cluster alias maybe?) ? Mike ================================================================================ Archive-Date: Wed, 05 Oct 1994 06:27:44 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: 5 Oct 94 07:18:00 EST From: "WRIGHT" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: Outgoing mail hangs, SMTP dies To: "MX-List" Bob Roklan wrote: >Outgoing mail hangs, SMTP dies >I upgraded MX from v3.3 to v4.1 on July 19 and have had problems since. The >outgoing mail hangs every so often - once or twice a week recently. The >incoming mail still gets through. Neither using mcp reset, nor shutting down and >restart of mx and cmu/ip help. The only thing that does is to reboot the >system. (gasp!) VMS is V5.5-3 and TCP/IP is CMU V6.6-5A. >The log file mx_smtp_ptf1.log shows : > 28-SEP-1994 10:35:08.56: MX SMTP (pid 000000A7) starting > 30-SEP-1994 11:05:27.85: MX SMTP (pid 000000A7) exiting, status = 1000000C >The log files otherwise do not show anything alarming. I have looked in the >archives of mx-list and didnt find an answer. There is a mention of rewrite >rules - we are not using them, and assigning $ define /sys /exec mx_smtp_debug true >which I just did. I thought that maybe it happens when a message with a bad >address is processed, but I am not sure. Any help would slow my insanity! It happens to me too. We recently upgraded to 4.1. We're using VMS 5.5.3 and UCX. Yesterday, all of my SMTP processes on two separate nodes in a cluster failed within seconds of each other. All had a status of of 1000000C (access violation). They had been running about six days. After restarting the SMTP processes, they started delivering mail. The other processes were there, but not doing anything. The router did not respond to a shutdown and had to be stopped manually. Mike Wright University of Florida mcw@pine.circa.ufl.edu ================================================================================ Archive-Date: Wed, 05 Oct 1994 09:06:00 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: numrich@abmx.rz.rwth-aachen.de Subject: MX V4.1 installing story. Help needed :) Date: 5 Oct 1994 13:33:51 GMT Message-ID: <36u9vv$338@urmel.informatik.rwth-aachen.de> Reply-To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: MX-List@WKUVX1.WKU.EDU Hi I recently installed version V4.1 of message exchange. Here is my story .. i hope someone can help ... I'm not very familiar with VMS and i'm my own system manager unfortunately :) I'm running VMS V5.3-1 and UCX V1.3 on a Microvax II The installation ran very well all seemed to work. But i could only recieve mail. Nothing wanted to leave my computer ... mcp> queu sh /full gave Entry: 1, origin: [Local] .... Status: IN-PROGRESS, size ... Created: ... ... SMTP entry #2, status: READY ... ... I noticed that the MX SMTP process was deleted right after installation ... Is this right ??? And sh sys gave : VAX/VMS V5.3-1 on node Unknown 4-OCT-1994 13:16:13.98 Uptime 0 01:24:00 Pid Process Name State Pri I/O CPU Page flts Ph.Mem ... 0000004F MX Router HIB 5 260 0 00:00:03.52 358 700 00000050 MX Local HIB 5 64 0 00:00:01.28 275 433 00000051 MX Site Agent HIB 6 142 0 00:00:02.60 370 370 00000055 MX SMTP Server HIB 6 19 0 00:00:00.81 297 447 00000056 MX LSV Intfc HIB 4 52 0 00:00:00.96 245 309 0000005A MX MLF HIB 5 104 0 00:00:01.16 245 392 ... The .log file only contained 3-OCT-1994 15:27:25.19: MX SMTP (pid 00000052) starting No error message. I didnt know what to do, so i decided to play with MX a little bit. I splitted the log-file for SMTP in mx_start.com into two different files. One for output one for errors ... And voila ... NOW the "error-log.file" contained an error .... :)) %SYSTEM-F-NOLOGNAM, no logical name match %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC MX_SMTP MX_SMTP 32 00000044 000020A4 I dumped over mx_smtp.exe and found several logical names bound to nothing. There was one, that is nowhere documented: mx_inet_host Well, i defined it ... because i didnt know what it is for it containes now my domain ... and the improbable event happened ! The process MX SMTP is living ! :) no errors ... But now it's vice versa ... I can send mail but not recieving ... ----------- Here are some things that might help : I installed: 1. [*] Base MX software 2. [*] NETLIB network support 3. [*] SMTP interface support . [ ] ... 8. [*] Site-provided interface support 9. [*] Mailing List/File Server support 10. [*] Documentation 11. [*] Example files and programs 12. [*] User-contributed files and programs TCP/IP package ... 4. [*] DEC UCX V1.3 or TCP/IP Services for VMS V2.0 or later ... $sh log mx* "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "DUA0:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "SYS$SYSDEVICE:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "CISSY" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_INET_HOST" = "cissy.gia.rwth-aachen.de" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_LSV_DIR" = "MX_ROOT:[LSV]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "cissy.gia.rwth-aachen.de" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DIR" = "MX_ROOT:[SITE]" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DEBUG" = "TRUE" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_SMTP_SERVER_THREADS" = "4" "MX_VMSMAIL_LOCALHOST" = "@cissy.gia.rwth-aachen.de" mcp> show path Domain-to-path mappings: Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP, Route="novell.gia.rwth-aachen.de" ----- Can anyone help ? if u need further information please contact me. Thanx in advance ... Nummi ---------------------- numrich@rwth-aachen.de ================================================================================ Archive-Date: Wed, 05 Oct 1994 10:51:39 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 05 Oct 1994 16:49:37 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009857F9.8CB762CE.102@uni-lj.si> Subject: RE: Outgoing mail hangs, SMTP dies > >Outgoing mail hangs, SMTP dies > > ... > > It happens to me too. We recently upgraded to 4.1. We're using VMS > 5.5.3 and UCX. Yesterday, all of my SMTP processes on two separate > nodes in a cluster failed within seconds of each other. All had > a status of of 1000000C (access violation). They had been running about > six days. > ... Agents usually die if .MSG_TEXT of an entry is missing in the queue directories. Such entry is useless; you just cancel it. I noticed Router dies if some user's personal name is too long. Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 168 6439 61000 Ljubljana fax: +386 61 168 6358 Slovenia ================================================================================ Archive-Date: Wed, 05 Oct 1994 12:37:12 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 05 Oct 1994 12:37:12 CDT From: "Alan J. Canellis" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009857D6.4932BEE0.1@APACHE.BROOKS.AF.MIL> Subject: RE: MX V4.1 installing story. Help needed :) Nummi, Check to see if your UCX data files are corupted! +-------------------------------+----------------------------------------------+ | Alan J. Canellis | Disclaimer: Who, What, When, Where??? | | Senior Systems Analyst +----------------------------------------------+ | Armstrong Laboratory | | | Brooks AFB, Tx | | | Voice: (210) 536-2683 | This space intentionally left blank | | (210) 536-2336 | | | Fax: (210) 536-3004 | | +-------------------------------+---------------------+------------------------+ | INTERnet: canellis@kiowas.brooks.af.mil | +-----------------------------------------------------+ ================================================================================ Archive-Date: Thu, 06 Oct 1994 01:32:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 06 Oct 1994 01:31:54 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00985842.82A66804.19@ALPHA.WKU.EDU> Subject: RE: MX V4.1 installing story. Help needed :) numrich@abmx.rz.rwth-aachen.de writes: > [...] >I'm running VMS V5.3-1 and UCX V1.3 on a Microvax II [...] >And voila ... NOW the "error-log.file" contained an error .... :)) > > %SYSTEM-F-NOLOGNAM, no logical name match > %TRACE-F-TRACEBACK, symbolic stack dump follows > module name routine name line rel PC abs PC > MX_SMTP MX_SMTP 32 00000044 000020A4 > >I dumped over mx_smtp.exe and found several logical names bound to nothing. >There was one, that is nowhere documented: mx_inet_host > Make sure that both UCX$INET_HOST and UCX$INET_DOMAIN are both defined. If not, you should define them in your system startup. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Thu, 06 Oct 1994 02:35:26 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: Pathway Runtime/Access and UCX Emulation - MX 3.3 Failing Message-ID: <1994Oct6.113802.973@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.WKU.EDU Date: 6 Oct 94 11:38:02 +1000 To: MX-List@WKUVX1.WKU.EDU We're having some problems with Pathway Runtime(v1.1.1)/Access(v1.0.1). We're trying to run MX v3.3, Teamlinks TLC v2.1 (under All-In-1 3.0a) and Teamlinks via All-In-1 3.1 in UCX emulation. They are running under VAX/VMS 5.5-2 on a 7610, 3900 and a 4000vlc. (MX is on the 4000vlc) In MX the Router fails with an ACCVIO and in Teamlinks the AIDA server fails with a "Network Shutdown", "Unable to Initialize Transport Layer". The FILECAB server seems to run (don't know if it's accepting logons though). In MX, only the Router fails. MX SMTP runs and will accept connections and work properly. Are there problems and/or incompatabilities with Pathway's UCX Emulation? Has anyone had these sort of problems before? We've gone back to UCX v3.1 on the machine that runs MX to keep it running but doing that for the Teamlinks machines is not really an option. Carl. BTW this article is crossposted to vmsnet.networks.tcpip.wintcp and vmsnet.mail.mx so please adjust your replies accordingly. -- Carl Makin (VK1KCM) "Speaking for myself only!" makinc@hhcs.gov.au 'Work +61 6 289 8443' Canberra, Australia 'The best book on programming for the layman is "Alice in Wonderland"; but that's because it's the best book on anything for the layman.' ================================================================================ Archive-Date: Thu, 06 Oct 1994 03:11:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 6 Oct 1994 09:12:10 +0000 To: MX-List@WKUVX1.WKU.EDU From: mjb@gemini.ci.uc.pt ( =?iso-8859-1?Q?M=E1rio?= Bernardes) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX Processes die I have been following the discussion about MX processes that die without any obvious reason. I am having the same problem with MX Local since I installed MX 4.1 on an AXP 7610 running VMS 1.5. Regards, -- Mario Bernardes System and Network Manager Centro de Informatica da Univ. Coimbra PORTUGAL ================================================================================ Archive-Date: Thu, 06 Oct 1994 03:18:33 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 06 Oct 1994 03:18:21 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00985851.61E697D3.6@ALPHA.WKU.EDU> Subject: RE: MX Processes die mjb@gemini.ci.uc.pt ( =?iso-8859-1?Q?M=E1rio?= Bernardes) writes: > >I have been following the discussion about MX processes that die without >any obvious reason. These have been known to happen when the queue is corrupted, you have an entry in the queue that's missing its files due to a disk filling up, and because of a bug in MX V4.1 that can be triggered by CANCELling an INPROG SMTP entry. >I am having the same problem with MX Local since I installed MX 4.1 on >an AXP 7610 running VMS 1.5. > If you are running 1.5-H1 or have applied the security patch 2, that's what your problem is. You must be running the MAILSHR, MAILSHRP, and SECURESHRP from a plain-vanilla V1.5---the others have bugs in them that cause the MX Local process (or any other that uses callable mail repeatedly) to die. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Thu, 06 Oct 1994 08:07:06 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 06 Oct 1994 08:45:38 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: uunet!WKUVX1.WKU.EDU!mx-list@esseye.si.com CC: makinc@hhcs.gov.au Message-ID: <0098587F.1A276520.33@swdev.si.com> Subject: RE: Pathway Runtime/Access and UCX Emulation - MX 3.3 Failing Carl Makin (makinc@hhcs.gov.au) writes: >We're trying to run MX v3.3, Teamlinks TLC v2.1 (under All-In-1 >3.0a) and Teamlinks via All-In-1 3.1 in UCX emulation. The most recent verion of Pathway Runtime is 1.1.1.1 and I know that there are patches available for the UCX emulation. I have a question, though: why not use NETLIB V1.6 (or the current version of MX [V4.1] which includes NETLIB V1.6) and use the Pathway native mode? The current NETLIB supports Pathway directly. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Thu, 06 Oct 1994 10:29:32 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: numrich@abmx.rz.rwth-aachen.de Subject: MX V4.1 installation story - Part 2 Date: 6 Oct 1994 15:06:44 GMT Message-ID: <3713q4$2h6@urmel.informatik.rwth-aachen.de> Reply-To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: MX-List@WKUVX1.WKU.EDU A few additions to my first posting ( #4450 ! ) First of all thanks to Alan and Hunter :) Alan> Check to see if your UCX data files are corupted. Nothing strange there but i ran UCX%CONFIG again and it installed a new process: UCX$INET-ROUTED Hunter> Make sure that both UCX$INET_HOST and UCX$INET_DOMAIN are both Hunter> defined. If not, you should define them in your system startup. YES ! UCX$INET_DOMAIN was NOT defined. After defining it i removed mx_inet_host and the process MX SMTP is still alive :) $sh log ucx$* "UCX$BIND_DOMAIN" = "rwth-aachen.de" "UCX$BIND_SERVER" = "........" "UCX$BIND_SERVER000" = "134.130.1.253" "UCX$BIND_STATE" = "...." "UCX$DEVICE" = "BG0:" "UCX$EXPORT" = "SYS$COMMON:[SYSEXE]UCX$EXPORT.DAT;1" "UCX$FTP_EXTLOG" = "1" "UCX$FTP_IMBX" = "MBA18:" "UCX$FTP_LOWER_CASE" = "1" "UCX$FTP_NO_VERSION" = "1" "UCX$FTP_RMBX" = "MBA17:" "UCX$FTP_TMBX" = "MBA19:" "UCX$FTP_WNDSIZ" = "9216" "UCX$HOST" = "SYS$COMMON:[SYSEXE]UCX$HOST.DAT;1" "UCX$INET_DOMAIN" = "gia.rwth-aachen.de" "UCX$INET_HOST" [user] = "cissy.gia.rwth-aachen.de" "UCX$INET_HOST" [exec] = "cissy.gia.rwth-aachen.de" "UCX$NETWORK" = "SYS$COMMON:[SYSEXE]UCX$NETWORK.DAT;1" "UCX$PROXY" = "SYS$COMMON:[SYSEXE]UCX$PROXY.DAT;1" "UCX$RLOGIN_MAX_SES" = "10" "UCX$RLOGIN_RCV_QUOTA" = "3000" "UCX$RLOGIN_SND_QUOTA" = "3000" "UCX$ROUTE" = "SYS$COMMON:[SYSEXE]UCX$ROUTE.DAT;1" "UCX$TELNET_FREE_BUF" = "5" "UCX$TELNET_FREE_IRP" = "3" "UCX$TELNET_FREE_UCB" = "4" "UCX$TELNET_MAX_SES" = "10" "UCX$TELNET_NON_BURST" = "FALSE" "UCX$TELNET_RCV_QUOTA" = "3000" "UCX$TELNET_SND_QUOTA" = "3000" anything strange here ? A queue entry looks like the following now: mcp> que sh /fu Entry: 7, Origin: [SMTP] Status: IN-PROGRESS, size: 22 bytes Created: 6-OCT-1994 11:09:41.13, expires 5-NOV-1994 11:09:41.13 Last modified 6-OCT-1994 12:40:31.43 SMTP entry #8, status: READY, size: 22 bytes, waiting for retry until 6-OCT-1994 13:10:35.46 Created: 6-OCT-1994 11:09:42.59, expires 5-NOV-1994 11:09:41.13 Last modified 6-OCT-1994 12:40:35.49 Recipient #1: , Route=novell.gia.rwth-aachen.de Error count=1 Last error: %MX-E-PROTOERR, protocol error? During this problems i learned a lot about VMS but not enough to help myself unfortunately ... Are there any further ideas outside ???? with best regards and many thanks in advance Nummi ---------------------- numrich@rwth-aachen.de ================================================================================ Archive-Date: Thu, 06 Oct 1994 20:27:38 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: kevin@ins.infonet.net (Kevin Houle) Subject: MX Local generating NON-FATAL BUGCHECKS Date: 7 Oct 1994 01:03:22 GMT Message-ID: <3726oq$cae@insosf1.infonet.net> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Platform: AXP 3000-500S, OpenVMS 1.5 We are seeing non-fatal bugchecks being generated soon after the time stamp in the system error log. The MX Local process is being named as the cause, as witnessed below : ERROR SEQUENCE 17160. LOGGED ON: CPU_TYPE 00000002 DATE/TIME 6-OCT-1994 01:09:51.91 SYS_TYPE 00000004 SYSTEM UPTIME: 15 DAYS 00:29:35 SCS NODE: VMS V1.5 HW_MODEL: 00000409 Hardware Model = 1033. TIME STAMP KN15 DEC 3000 MODEL 500W V M S SYSTEM ERROR REPORT COMPILED 6-OCT-1994 17:53:16 PAGE 1. ******************************* ENTRY 2262. ******************************* ERROR SEQUENCE 17161. LOGGED ON: CPU_TYPE 00000002 DATE/TIME 6-OCT-1994 01:16:20.39 SYS_TYPE 00000004 SYSTEM UPTIME: 15 DAYS 00:36:03 SCS NODE: VMS V1.5 HW_MODEL: 00000409 Hardware Model = 1033. NON-FATAL BUGCHECK KN15 DEC 3000 MODEL 500W SSRVEXCEPT, Unexpected system service exception PROCESS NAME MX Local PROCESS ID 035D001E ERROR PC FFFFFFFF 839142D0 Process Status = 00000000 00000009, SW = 01, Previous Mode = EXECUTIVE System State = 00, Current Mode = EXECUTIVE VMM = 00 IPL = 0, SP Alignment = 0 STACK POINTERS KSP 00000000 7FF96000 ESP 00000000 7FF998D8 SSP 00000000 7FFA2000 USP 00000000 7FF48650 GENERAL REGISTERS R0 00000000 0000000C R1 00000000 7FF99AE8 R2 00000000 00235820 R3 00000000 7FF99E50 R4 00000000 7FF99CF0 R5 00000000 7FF99EF8 R6 00000000 7FF99E54 R7 00000000 00244008 R8 00000000 00000002 R9 00000000 00000004 R10 FFFFFFFF 80431400 R11 00000000 00000000 R12 00000000 0064E428 R13 FFFFFFFF 8086CBB8 R14 00000000 002A6000 R15 00000000 0064E56C R16 00000000 000003C0 R17 00000000 7FF99980 R18 00000000 000005A0 R19 FFFFFFFF 80428200 R20 00000000 00000000 R21 00000000 007E001A R22 FFFFFFFF 8086C000 R23 00000000 7FF9A000 R24 00000000 7FFF0028 R25 00000000 00000002 R26 FFFFFFFF 83913D4C R27 FFFFFFFF 8086CBB8 R28 00000000 000005AC FP 00000000 7FF998E0 SP 007E001A 00000000 PC FFFFFFFF 839142D0 PS 00000000 00000009 Any ideas why that happens? -- Kevin Houle kevin@ins.infonet.net ================================================================================ Archive-Date: Fri, 07 Oct 1994 10:15:16 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 07 Oct 1994 10:41:50 EDT From: Bob Roklan Office B112/7 x7824 Lab b127 x3886 Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: roklan@ptf1.npt.nuwc.navy.mil Message-ID: <00985958.805B9760.3@ptf1.npt.nuwc.navy.mil> Subject: RE: MX Processes die RE: MX Processes die >>I have been following the discussion about MX processes that die without >>any obvious reason. > >These have been known to happen when the queue is corrupted, you have >an entry in the queue that's missing its files due to a disk filling >up, and because of a bug in MX V4.1 that can be triggered by >CANCELling an INPROG SMTP entry. > >Hunter Goatley, VMS Systems Programmer, Western Kentucky University >goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) In my case disks are not full and entries have not been canceled. How can a queue become corrupted? Bob Roklan roklan@ptf1.npt.nuwc.navy.mil ================================================================================ Archive-Date: Fri, 07 Oct 1994 17:06:39 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 07 Oct 1994 15:05:23 EDT From: Scot Bishop-Walker - DEC PC Integration Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: scot@vmpyr.wro.dec.com, m_frazier@borgil.cxo.dec.com Message-ID: <0098597D.51856360.14@vmpyr.wro.dec.com> Subject: What's on the wish list? Hunter... could you post a reply with a list of things that are on the wish list for MX? We're curious about what you'll be working on (as time permits, of course), and don't want to send in things that are already on the list. Thanks! - Scot Bishop-Walker Digital Equipment Corporation Santa Clara, CA ================================================================================ Archive-Date: Mon, 10 Oct 1994 22:54:41 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: tillman@swdev.si.com (Brian Tillman) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: Pathway Runtime/Access and UCX Emulation - MX 3.3 Failing Message-ID: <10OCT94.12174087@swdev.si.com> Date: Mon, 10 Oct 1994 12:17:40 GMT To: MX-List@WKUVX1.WKU.EDU Carl Makin (makinc@hhcs.gov.au) writes: >We're trying to run MX v3.3, Teamlinks TLC v2.1 (under All-In-1 >3.0a) and Teamlinks via All-In-1 3.1 in UCX emulation. .. >In MX the Router fails with an ACCVIO and in Teamlinks the AIDA Get V4.1 of MX. It supports Pathway natively. No need to run UCX emulation. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Mon, 10 Oct 1994 23:43:43 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 11 Oct 1994 10:37:21 +1000 Message-ID: <199410110037.KAA24846@sserve.cc.adfa.oz.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: uunet!si.com!tillman_brian@uunet.uu.net, uunet!esseye.si.com!uunet!WKUVX1.WKU.EDU!mx-list@uunet.uu.net From: esseye!uunet!hhcs.gov.au!makinc@uunet.uu.net (Carl Makin) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: Pathway Runtime/Access and UCX Emulation - MX 3.3 Failing Hi Brian, At 8:45 AM 6/10/94 -0400, Brian Tillman wrote: > The most recent verion of Pathway Runtime is 1.1.1.1 and I know that there >are > patches available for the UCX emulation. I'll hunt up those patches. Thanks. > I have a question, though: why not >use > NETLIB V1.6 (or the current version of MX [V4.1] which includes NETLIB V1.6) >and > use the Pathway native mode? The current NETLIB supports Pathway directly. I'm going to however my only direct link to the Internet is a 14.4Kb PPP dial-up. Each time I try to collect it the damn link dies. :-( I'll be trying again this week. Thanks for the help. Carl. -- Carl Makin (VK1KCM) "Speaking for myself only!" makinc@hhcs.gov.au 'Work +61 6 289 8443' Canberra, Australia 'The best book on programming for the layman is "Alice in Wonderland"; but that's because it's the best book on anything for the layman.' ================================================================================ Archive-Date: Tue, 11 Oct 1994 09:13:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 11 Oct 1994 10:17:11 EDT From: kamrul@ycvax.york.cuny.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00985C79.B85FBD20.3878@ycvax.york.cuny.edu> Subject: Insufficient priv to add Pleae help me with this problem. I am running MX 3.3 with VMS 5.5 and the TCP/IP transport is UCX 2.0D. When the owner of the list tries to add someone to the list it give the insufficient privilege error. But the users can add themselves. Through MCP I checked the list and found that owner is listed there. I also did RESET/CLUSTE MLF,ROUTER. It did not work. I have also tried to add users to the list using system account; that did give the same 'insufficient priv' error. Thank you for any help. Kamrul Ahsan York College, CUNY New York. Voice: 718-262-2754 ================================================================================ Archive-Date: Tue, 11 Oct 1994 23:19:35 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 11 Oct 1994 23:19:19 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00985CE6.FBCB8EAF.35@ALPHA.WKU.EDU> Subject: RE: Insufficient priv to add kamrul@ycvax.york.cuny.edu writes: > >Pleae help me with this problem. >I am running MX 3.3 with VMS 5.5 and the TCP/IP transport is UCX >2.0D. > >When the owner of the list tries to add someone to the list it >give the insufficient privilege error. But the users can add >themselves. > First, MX V4.1 is the current version---MX V3.3 is not supported. Secondly, the problem is most likely caused by a case mismatch in the defined /OWNER name and the case of the address in the actual From: line (for example, it's defined a "x@XYZ" but comes in as from "X@XYZ"). Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Wed, 12 Oct 1994 07:47:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: nilsson@plasma.kth.se (Bengt H. Nilsson, Plasma Physics, KTH, Stockholm) Subject: Selecting SMTP delivery agent Date: 12 Oct 1994 08:05:19 GMT Message-ID: <37g5bv$5s4@news.kth.se> Reply-To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit To: MX-List@WKUVX1.WKU.EDU I need to be able to control from which node in a VMScluster outgoing SMTP mail is delivered. The background is that we will connect one of the nodes in our VMScluster to a second Ethernet. Only this node will see this second net. This means as I understand it that SMTP mail to this second net must be delivered by a delivery agent running on this node. But the MX Router doesn't seem to know about the different environments the SMTP agents are seeing, so it routes the mail to an agent according to its own decision. My question is: can I set up MX so that mail to the second net is certain to be delivered by a SMTP agent on the right node? We are running MX V4.1 in our VMScluster including among other things one VAX 6610 and one DECstation 3000-400. It is to the Alpha we will connect the second Ethernet. The main part of the MX agents are running on the VAX. We run VMS V5.5-2 and V1.5 respectively, soon to be upgraded to V6.1, and we use UCX V3.1. Bengt H. ------------------------------------------------------------------------- Bengt H. Nilsson Internet: nilsson@plasma.kth.se Division of Plasma Physics SPAN: PLAFYS::NILSSON Alfve'n Laboratory Bitnet: bhn@sekth Royal Institute of Technology Phone: +46 8 790 7693 S-100 44 Stockholm, Sweden Fax: +46 8 24 54 31 ================================================================================ Archive-Date: Wed, 12 Oct 1994 10:47:10 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 12 Oct 1994 11:43:15 PDT From: Spencer Yost Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <00985D4E.E911A660.1308@ledger.co.forsyth.nc.us> Subject: Mailing list server questions I am new to this list, so if this is old ground I am covering, please forgive me. I currently manage a fair sized mailing list using MX 3.3, and in the process of upgrading to 4.1. Two requests came in recently from subscribers that seemed quite reasonable. Here is a quick rundown of what they wanted: 1 One fellow wanted the archive files (which I then include in my gopher server) to confirm to RFC 934, which apparently dictates how archives are created, in order to allow bursting and what not. 2 Another subscriber wanted the list software to preface all subject lines with some type of "tag". This will allow mail software that supports "rules" to do some automatic forwarding/filing. I have no idea what he meant by that other than he wants his email package to separate out the list traffic from the rest of his email. My questions are: 1: Are these things to be implemented any time in the near future? 2: If not, has someone done this locally and would like to share code/ideas with me? Many thanks ahead of time for your assistance! +================================+====================================+ | Spencer William Yost | Mis Department | | Vax/VMS Systems Manager | Forsyth County Government | | Yost@ledger.co.forsyth.nc.us | 200 N. Main St Room 603 | | | Hall Of Justice | | | Winston-Salem NC 27101 | +=====================================================================+ ================================================================================ Archive-Date: Wed, 12 Oct 1994 14:39:44 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 12 Oct 1994 15:38:36 EDT From: "Green eggs and ham." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <00985D6F.C960E472.13@vax6.drc.com> Subject: Running MX on a second cluster node. I am running MX (very successfully) on one node of a two node cluster. The other node uses the common system disk, but has a separate IP address. I want to run MX on the second node now, also, but don't want to have to install it from scratch again. The second node already runs the Netlib software and the MadGoat FTP program using the TCPWare Internet software. Aside from just running the startup from the second node, what else must I do to configure MX so it will run correctly on that node. Dan Graham ================================================================================ Archive-Date: Wed, 12 Oct 1994 16:43:09 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 12 Oct 1994 17:33:33 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: uunet!WKUVX1.WKU.EDU!mx-list@esseye.si.com CC: uunet!vax6.drc.com!graham@esseye.si.com Message-ID: <00985D7F.D8B6AD20.2@swdev.si.com> Subject: RE: Running MX on a second cluster node. Dan Graham (graham@vax6.drc.com) writes: >Aside from just running the startup from the second node, what else must I >do to configure MX so it will run correctly on that node. When I wanted to do what you are seeking to do, I simply edited the MX_DIR:MX_STARTUP_INFO.DAT file to add the nodes I wanted. Here's what I had: 001NETLIB:* 002FLQ_MGR:HURON 002ROUTER:BARRY=1,ZEQOLL=1 003LOCAL:BARRY=1,ZEQOLL=1 004SMTP:BARRY=1,ZEQOLL=1 004SMTP_SERVER:BARRY,ZEQOLL I wanted to run the SMTP Server on all the nodes in my cluster, so I merely changed the last line above to this: 004SMTP_SERVER:* I then shut MX down and executed SYS$STARTUP:MX_STARTUP.COM with SYSMAN, selecting the cluster as my environment. I wasn't running NETLIB on all nodes and I use three different TCP/IPs in our cluster, so I had to update SYS$STARTUP:NETLIB_STARTUP.COM, but you apparently don't have that requirement. -- Brian Tillman tillman_brian@si.com ================================================================================ Archive-Date: Thu, 13 Oct 1994 06:02:29 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 13 Oct 1994 12:55 GMT+3 From: SYSTEM@GRGBOX.FORTHNET.GR Reply-To: MX-List@WKUVX1.WKU.EDU Subject: BSMTP is not working (mx 4.1) To: MX-List@WKUVX1.WKU.EDU CC: skapetis@forthnet.gr Message-ID: <01HI88JTA56800002V@GRGBOX.FORTHNET.GR> Hello, I have installed and configured MX 4.1 on a system (VMS 5.4, Jnet 3.5, Multinet 2.2) and everything seems to work ok except the BSMTP gateway, though MX Jnet Deamon is running, so all the BSMTP mail is send to the SYSTEM account without being processed. Prior to MX the system was running PMDF 4.0 and it worked fine. Does anyone know what might be wrong? I get no errors in the log files at all. I suspect that it is something with the delivery logicals/executables in lmd.com but i don't know what. Here is my config.mcp: DEFINE PATH "grgbox.forthnet.gr" LOCAL DEFINE PATH "139.91.1.11" LOCAL DEFINE PATH *.UUCP SMTP/ROUTE="pythia.forthnet.gr" DEFINE PATH "GRGBOX" LOCAL DEFINE PATH "GRGBOX.BITNET" LOCAL DEFINE PATH *.BITNET Jnet SET JNET/LENIENT/username=mailer/accounting DEFINE PATH * SMTP SET SMTP /accounting DEFINE ALIAS "Postmaster" "system@grgbox.forthnet.gr " DEFINE ALIAS "POSTMAST" "system@grgbox.forthnet.gr " thanks in advance Lefteris ================================================================================ Archive-Date: Thu, 13 Oct 1994 08:24:51 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 13 Oct 1994 09:24:35 EDT From: "The bard of Seville." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <00985E04.B4129B2A.1@vax6.drc.com> Subject: Re: Running MX on a second cluster node. Thanks Brian, that seems fairly streightforward, one more thing, though. When I do an mcp show path, it names the primary node's address. Do I need to be concerned about that when I bring up the second node using the same config information? Dan Graham ================================================================================ Archive-Date: Thu, 13 Oct 1994 14:14:30 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 13 Oct 1994 15:13:49 EDT From: "UFO's are real, the Air Force doesn't exist." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <00985E35.7D75F63A.28@vax6.drc.com> Subject: Re: Adding a second cluster node to the existing MX system. Hi again, Well, I tried to configure the second node and there were no errors. I added it to the proper lines in the mx_startup_info file and ran the startup procedure and all processes are sitting there, waiting for input. (Need input! remind you of a movie?) Anyway, the two nodes are a cluster, they are VAX6 and oasys. VAX6 has been running MX for several weeks with no problems. I added oasys today. Oasys sends mail now just fine, but I cannot send mail to it. It does have a separate Internet address from VAX6. Here are the error lines from the error notification message sent back to VAX6 when I attempted to send mail to myself on oasys. If anyone can help me figure this out, I'd be very grateful. Dan Graham --> Error description: Error-For: GRAHAM@OASYS.DRC.COM Error-Code: 2 Error-Text: %MX_SMTP-F-TRANSACTION_FAI, transaction failed -(Via OASYS.DRC.COM) -Transcript: -Rcvd: 220 OASYS.DRC.COM MX V4.1 VAX SMTP server ready at Thu, 13 Oct 1994 15:07:04 EDT -Sent: HELO VAX6.DRC.COM -Rcvd: 250 Hello, VAX6.DRC.COM -Sent: MAIL FROM: -Rcvd: 250 MAIL command accepted. -Sent: RCPT TO: -Rcvd: 250 Recipient okay (at least in form) -Sent: DATA -Rcvd: 354 Start mail input; end with . -Rcvd: 554 Received too many times by this host. -Sent: QUIT -Rcvd: 221 OASYS.DRC.COM Service closing transmission channel ================================================================================ Archive-Date: Fri, 14 Oct 1994 03:37:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Adding a second cluster node to the existing MX system. Date: 14 Oct 1994 08:22:34 GMT Message-ID: <37lf4a$bgi@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <00985E35.7D75F63A.28@vax6.drc.com>, "UFO's are real, the Air Force doesn't exist." writes: =Hi again, = =Well, I tried to configure the second node and there were no errors. I =added it to the proper lines in the mx_startup_info file and ran the =startup procedure and all processes are sitting there, waiting for =input. (Need input! remind you of a movie?) = =Anyway, the two nodes are a cluster, they are VAX6 and oasys. VAX6 has =been running MX for several weeks with no problems. I added oasys today. =Oasys sends mail now just fine, but I cannot send mail to it. It does have =a separate Internet address from VAX6. Here are the error lines from the =error notification message sent back to VAX6 when I attempted to send mail =to myself on oasys. If anyone can help me figure this out, I'd be very =grateful. = =Dan Graham = =--> Error description: = =Error-For: GRAHAM@OASYS.DRC.COM =Error-Code: 2 =Error-Text: %MX_SMTP-F-TRANSACTION_FAI, transaction failed = -(Via OASYS.DRC.COM) = -Transcript: = -Rcvd: 220 OASYS.DRC.COM MX V4.1 VAX SMTP server ready at Thu, 13 Oct 1994 15:07:04 EDT = -Sent: HELO VAX6.DRC.COM = -Rcvd: 250 Hello, VAX6.DRC.COM = -Sent: MAIL FROM: = -Rcvd: 250 MAIL command accepted. = -Sent: RCPT TO: = -Rcvd: 250 Recipient okay (at least in form) = -Sent: DATA = -Rcvd: 354 Start mail input; end with . = -Rcvd: 554 Received too many times by this host. = -Sent: QUIT = -Rcvd: 221 OASYS.DRC.COM Service closing transmission channel Looks like you haven't told MX that OASYS is a local node. -------------------------------------------------------------------------------- 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. ================================================================================ Archive-Date: Fri, 14 Oct 1994 15:22:21 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: larry@eco.twg.com (Lawrence B. Henry III) Subject: Re: Pathway Runtime/Access and UCX Emulation - MX 3.3 Failing Date: 14 Oct 1994 20:07:28 GMT Message-ID: <37moe0$8ha@scoop.eco.twg.com> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <1994Oct6.113802.973@hhcs.gov.au>, Carl Makin writes: |> |>We're having some problems with Pathway Runtime(v1.1.1)/Access(v1.0.1). |> |>We're trying to run MX v3.3, Teamlinks TLC v2.1 (under All-In-1 |>3.0a) and Teamlinks via All-In-1 3.1 in UCX emulation. |> |>They are running under VAX/VMS 5.5-2 on a 7610, 3900 and a 4000vlc. |>(MX is on the 4000vlc) |> |>In MX the Router fails with an ACCVIO and in Teamlinks the AIDA |>server fails with a "Network Shutdown", "Unable to Initialize Transport |>Layer". The FILECAB server seems to run (don't know if it's accepting |>logons though). |> |>In MX, only the Router fails. MX SMTP runs and will accept connections |>and work properly. |> |>Are there problems and/or incompatabilities with Pathway's UCX Emulation? |> |>Has anyone had these sort of problems before? |> |>We've gone back to UCX v3.1 on the machine that runs MX to keep it |>running but doing that for the Teamlinks machines is not really an |>option. |> |> |>Carl. |>BTW this article is crossposted to vmsnet.networks.tcpip.wintcp and |>vmsnet.mail.mx so please adjust your replies accordingly. |>-- Carl, Please open a support call. We have recently fixed some incompatibility issues with Teamlinks. -Larry. The Wollongong Group. ================================================================================ Archive-Date: Mon, 17 Oct 1994 04:49:29 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 17 Oct 1994 10:54:13 -0100 To: From: Robertini@sns.it (Marco Robertini) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: SMTP process dies Hi all, I'm still using MX 3.3 so my question may be "obsoleta". When I try to send a mail to zane@MERCURY.MATH.UKANS.EDU this is what I find in MX_SMTP_LOG.LOG 17-OCT-1994 10:20:28.23 Processing queue entry number 24209 on node VAXSNS 17-OCT-1994 10:20:28.54 Recipient: , route=mercurcy.math.ukans.edu 17-OCT-1994 10:20:28.54 SMTP_SEND: looking up host name mercury.math.ukans.edu [EOB] This is the finger test $ finger zane@MERCURY.MATH.UKANS.EDU [mercury.math.ukans.edu] Login name: zane In real life: Omar Zane Directory: /home/zane Shell: /bin/csh Never logged in. <======================================!!! Mail last read Fri Oct 14 11:24:37 1994 No Plan. $ Is "never logged in" a black hole for SMTP process? Trying with a Mac with LeeMail I receive this answer: Date: Mon, 17 Oct 94 04:40:58 CDT From: Mailer-Daemon@titania.math.ukans.edu (Mail Delivery Subsystem) Subject: Returned mail: Service unavailable Message-Id: <9410170940.AB02278@titania.math.ukans.edu> To: ----- Transcript of session follows ----- Connected to mercury: >>> HELO titania.math.ukans.edu <<< 553 titania.math.ukans.edu host name configuration error 554 ... Service unavailable ----- Unsent message follows ----- Return-Path: Received: from CED.sns.it by titania.math.ukans.edu (4.1/SMI-4.1) id AA02276; Mon, 17 Oct 94 04:40:58 CDT Date: Mon, 17 Oct 94 10:45:51 EST From: Marco Robertini Subject: Test To: zane@MERCURY.math.ukans.edu X-Mailer: LeeMail 2.0.3 Message-Id: test Marco Robertini +39 050 509268 In this case LeeMail brings out a lot of informations. Someone who explains me the situation?!?!? ++++++++++++++++++++++++++++++++++++++++++++++++++++ + Marco Robertini +39 50 509268 + + Fax +39 50 563513 + + Lan manager - Scuola Normale Superiore di Pisa + ++++++++++++++++++++++++++++++++++++++++++++++++++++ ================================================================================ Archive-Date: Mon, 17 Oct 1994 05:06:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: numrich@abmx.rz.rwth-aachen.de Subject: Installation story not ended Date: 17 Oct 1994 09:56:11 GMT Message-ID: <37thns$ik0@urmel.informatik.rwth-aachen.de> Reply-To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: MX-List@WKUVX1.WKU.EDU Hi again ... I hope someone can remember my problems, they are still unresolved ... I learned a lot about VMS during this but unfortunately not enough to help myself at this point ... I noticed that my newsserver deleted my old postings already (?), every day i get only the last 3 or 4 postings in this group, so i give a short :) summary here ... VMS V5.3 - 1 , UCX V1.3 , MX V4.1 Sending mail is OK but incoming mail only reaches the queue Here's what queue show /full gives : -------------------- Status: FINISHED, size: 9 bytes Entry: 2, Origin: [SMTP] Status: IN-PROGRESS, size: 14 bytes Created: 13-OCT-1994 10:12:49.50, expires 12-NOV-1994 10:12:49.50 Last modified 13-OCT-1994 10:12:52.13 SMTP entry #4, status: IN-PROGRESS, size: 14 bytes Created: 13-OCT-1994 10:12:50.90, expires 12-NOV-1994 10:12:49.50 Last modified 13-OCT-1994 10:12:51.75 Recipient #1: , Route=cissy.gia.rwth-aachen.de Entry: 6, Origin unknown Status: IN-PROGRESS, size: 0 bytes Created: 13-OCT-1994 10:12:54.00, expires 12-NOV-1994 10:12:54.00 Last modified 13-OCT-1994 10:12:54.00 ------------------------ Status: FINISHED, size: 9 bytes Entry: 6, Origin: [SMTP] Status: IN-PROGRESS, size: 14 bytes Created: 13-OCT-1994 10:12:54.00, expires 12-NOV-1994 10:12:54.00 Last modified 13-OCT-1994 10:12:57.28 SMTP entry #8, status: IN-PROGRESS, size: 14 bytes Created: 13-OCT-1994 10:12:56.21, expires 12-NOV-1994 10:12:54.00 Last modified 13-OCT-1994 10:12:57.01 Recipient #1: , Route=cissy.gia.rwth-aachen.de Entry: 9, Origin: [SMTP] Status: IN-PROGRESS, size: 0 bytes Created: 13-OCT-1994 10:12:59.01, expires 12-NOV-1994 10:12:59.01 Last modified 13-OCT-1994 10:12:59.01 Recipient #1: ------------------------------------------------------------------ This is the error message sent back from Postmaster : From Thu Oct 13 10:12:19 1994 Message-Id: <9410130912.AA11802@otto.gia.rwth-aachen.de> Date: Thu, 13 Oct 1994 10:13:11 EDT From: SMTP delivery agent To: Subject: SMTP delivery error X-Report-Type: Nondelivery; boundary="> Error description:" Note: this message was generated automatically. An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: NUMMI@cissy.gia.rwth-aachen.de Error-Code: 2 Error-Text: %MX_SMTP-F-TRANSACTION_FAI, transaction failed -(Via cissy.gia.rwth-aachen.de) -Transcript: -Rcvd: 220 cissy.gia.rwth-aachen.de MX V4.1 VAX SMTP server ready at Thu, 13 Oct 1994 10:13:08 EDT -Sent: HELO cissy.gia.rwth-aachen.de -Rcvd: 250 Hello, cissy.gia.rwth-aachen.de -Sent: MAIL FROM: -Rcvd: 250 MAIL command accepted. -Sent: RCPT TO: -Rcvd: 250 Recipient okay (at least in form) -Sent: DATA -Rcvd: 354 Start mail input; end with . -Rcvd: 554 Received too many times by this host. -Sent: QUIT -Rcvd: 221 cissy.gia.rwth-aachen.de Service closing transmission channel Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ Received: from cissy.gia.rwth-aachen.de by cissy.gia.rwth-aachen.de (MX V4.1 VAX) with SMTP; ... Received: from cissy.gia.rwth-aachen.de by cissy.gia.rwth-aachen.de (MX V4.1 VAX) with SMTP; ... Received: from cissy.gia.rwth-aachen.de by cissy.gia.rwth-aachen.de (MX V4.1 VAX) with SMTP; ... Received: from otto.gia.rwth-aachen.de by cissy.gia.rwth-aachen.de (MX V4.1 VAX) with SMTP; ... Received: by otto.gia.rwth-aachen.de; id AA11798; Thu, 13 Oct 1994 10:11:44 +0100 Date: Thu, 13 Oct 1994 10:11:44 +0100 From: Ralf Numrich Message-ID: <9410130911.AA11798@otto.gia.rwth-aachen.de> Apparently-To: NUMMI@cissy.gia.RWTH-Aachen.de otto -> cissy ------------------------------------------- Hope that someone can help ... Below there is some additional information that might help With best regards and thanks in advance Nummi ---------------------- numrich@rwth-aachen.de ---------------------------- $ show sys VAX/VMS V5.3-1 on node Unknown 13-OCT-1994 10:45:31.54 Uptime 2 21:28:19 Pid Process Name State Pri I/O CPU Page flts Ph.Mem 00000021 SWAPPER HIB 16 0 0 00:01:23.18 0 0 00000026 ERRFMT HIB 8 2217 0 00:00:24.57 94 140 00000027 JOB_CONTROL HIB 9 526 0 00:00:04.26 173 389 00000028 CONFIGURE HIBO 8 -- swapped out -- 148 00000029 SYMBIONT_0001 HIBO 4 -- swapped out -- 105 0000002A INET_ACP HIB 9 2713 0 00:00:39.07 257 294 0000002B UCX$INET_ROUTED LEF 6 43 0 00:00:01.98 325 386 S 0000002C UCX$FTPD LEF 9 716 0 00:00:05.72 417 500 0000002D MX Router HIB 5 18283 0 00:02:37.52 592 568 0000002E MX Local HIBO 5 -- swapped out -- 379 0000002F MX Site Agent HIB 6 56 0 00:00:02.04 376 481 00000030 MX SMTP HIB 5 3863 0 00:00:40.41 952 783 00000031 MX SMTP Server HIB 5 2406 0 00:00:32.01 541 441 00000032 VWS$DISPLAYMGR HIB 7 969 0 00:00:40.60 910 390 000000F4 WTA1:NUMMI HIB 4 7195 0 00:01:13.98 2146 737 000000F5 WTA2:BABYLON HIB 4 618 0 00:00:18.09 1847 4033 000000F6 WTA3:NUMMI LEF 4 4707 0 00:00:38.01 2239 368 000000F9 WTA4:SYSTEM CUR 4 295 0 00:00:07.43 1010 733 ------------------------- show log mx* "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "DUA0:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "SYS$SYSDEVICE:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "Unknown" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "cissy.gia.rwth-aachen.de" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DIR" = "MX_ROOT:[SITE]" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_SMTP_SERVER_THREADS" = "4" "MX_VMSMAIL_LOCALHOST" = "@cissy.gia.rwth-aachen.de" ---------------------------- $ sh log ucx* "UCX$BIND_DOMAIN" = "gia.rwth-aachen.de" "UCX$BIND_SERVER" = "........" "UCX$BIND_SERVER000" = "134.130.1.253" "UCX$BIND_STATE" = "...." "UCX$DEVICE" = "BG0:" "UCX$EXPORT" = "SYS$COMMON:[SYSEXE]UCX$EXPORT.DAT;1" "UCX$FTP_EXTLOG" = "1" "UCX$FTP_IMBX" = "MBA12:" "UCX$FTP_LOWER_CASE" = "1" "UCX$FTP_NO_VERSION" = "1" "UCX$FTP_RMBX" = "MBA11:" "UCX$FTP_TMBX" = "MBA13:" "UCX$FTP_WNDSIZ" = "9216" "UCX$HOST" = "SYS$COMMON:[SYSEXE]UCX$HOST.DAT;1" "UCX$INET_DOMAIN" = "gia.rwth-aachen.de" "UCX$INET_HOST" = "cissy.gia.rwth-aachen.de" "UCX$NETWORK" = "SYS$COMMON:[SYSEXE]UCX$NETWORK.DAT;1" "UCX$PROXY" = "SYS$COMMON:[SYSEXE]UCX$PROXY.DAT;1" "UCX$RLOGIN_MAX_SES" = "10" "UCX$RLOGIN_RCV_QUOTA" = "3000" "UCX$RLOGIN_SND_QUOTA" = "3000" "UCX$ROUTE" = "SYS$COMMON:[SYSEXE]UCX$ROUTE.DAT;1" "UCX$TELNET_FREE_BUF" = "5" "UCX$TELNET_FREE_IRP" = "3" "UCX$TELNET_FREE_UCB" = "4" "UCX$TELNET_MAX_SES" = "10" "UCX$TELNET_NON_BURST" = "FALSE" "UCX$TELNET_RCV_QUOTA" = "3000" "UCX$TELNET_SND_QUOTA" = "3000" (DECW$LOGICAL_NAMES) --------------------- mcp> sh path Domain-to-path mappings: Domain="cissy.gia.rwth-aachen", Path=Local Domain="cissy", Path=Local Domain="*.gia.rwth-aachen.de", Path=SMTP Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP ---------------------- ================================================================================ Archive-Date: Mon, 17 Oct 1994 07:57:19 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 17 Oct 1994 13:56:54 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0098614F.68D5F10E.349@uni-lj.si> Subject: RE: Installation story not ended > I hope someone can remember my problems, they are still unresolved ... > ... > Here's what queue show /full gives : > > Entry: 2, Origin: [SMTP] > Status: IN-PROGRESS, size: 14 bytes > Created: 13-OCT-1994 10:12:49.50, expires 12-NOV-1994 10:12:49.50 > Last modified 13-OCT-1994 10:12:52.13 > SMTP entry #4, status: IN-PROGRESS, size: 14 bytes > Created: 13-OCT-1994 10:12:50.90, expires 12-NOV-1994 10:12:49.50 > Last modified 13-OCT-1994 10:12:51.75 > Recipient #1: , Route=cissy.gia.rwth-aachen.de ************************ > ... > mcp> sh path > > Domain-to-path mappings: > Domain="cissy.gia.rwth-aachen", Path=Local ********************* > ... cissy.gia.rwth-aachen is local, but cissy.gia.rwth-aachen.de is not! So add .de to your path definition! Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 168 6439 61000 Ljubljana fax: +386 61 168 6358 Slovenia ================================================================================ Archive-Date: Mon, 17 Oct 1994 08:02:33 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 17 Oct 1994 08:47:44 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: uunet!WKUVX1.WKU.EDU!mx-list@esseye.si.com CC: numrich@rwth-aachen.de Message-ID: <00986124.380FDBA0.5@swdev.si.com> Subject: RE: Installation story not ended Nummi (numrich@rwth-aachen.de) writes: > -Rcvd: 554 Received too many times by this host. and > Domain="cissy.gia.rwth-aachen", Path=Local These lines say it all. You've not told MX that cissy.gia.rwth-aachen.de is a local node. You need a line in CONFIG.MCP that says: DEFINE PATH "cissy.gia.rwth-aachen.de" local You've left off the ".de" in your config. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Mon, 17 Oct 1994 09:46:27 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 17 Oct 1994 15:45:18 GMTDT From: Erdosi Peter Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: perdosi@tigris.klte.hu Message-ID: <0098615E.8D7B2E20.36@tigris.klte.hu> Subject: MCP QUE SHO /BRIEF crashes with MX V4.1, as well... Hi, MX-gurus, Pasztor Miklos wrote (08 Aug 1994): All of a sudden I experience the following when I do an MCP QUE SHOW/BR: $mcp que show/br SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=0260B344, PC =0000CAE9, PSL=03C00000 Improperly handled condition, image exit forced. Signal arguments Stack contents Number = 00000005 00000000 Name = 0000000C 00000000 00000001 00000000 0260B344 2FFC0000 0000CAE9 7FF09060 03C00000 00000000 20FC0000 7FF09060 7FF09024 0000C2C9 Register dump R0 = 00982764 R1 = 00000000 R2 = 7FF08FDC R3 = 7FF08DD0 R4 = 000381F0 R5 = 000015B4 R6 = 0002DCE0 R7 = 0002DEF8 R8 = 00000000 R9 = 00000000 R10= 00000000 R11= 00000000 AP = 7FF08D00 FP = 7FF08CC0 SP = 7FF08D3C PC = 0000CAE9 PSL= 03C00000 MCP QUE SHOW, MCP QUE SHOW/ALL and all other MCP and MX operations seem to work normally. Note: This error was made by MX V4.0. ------------------------------------------------------------------------ My problem is similar, after this command I see the following: %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=02616588, PC =0000CAE9, PSL=03C00000 Improperly handled condition, image exit forced. Signal arguments Stack contents Number = 00000005 00000000 Name = 0000000C 00000000 00000001 00000000 02616588 2FFC0000 0000CAE9 7FE70060 03C00000 00000000 20FC0000 7FE70060 7FE70024 0000C2C9 Register dump R0 = 009853F5 R1 = 00000000 R2 = 7FE6FFDC R3 = 7FE6FDD0 R4 = 000381F0 R5 = 000015B4 R6 = 0002ECE0 R7 = 0002EEF8 R8 = 00000000 R9 = 00000000 R10= 00000000 R11= 00000000 AP = 7FE6FD00 FP = 7FE6FCC0 SP = 7FE6FD3C PC = 0000CAE9 PSL= 03C00000 What's wrong in THIS version, too? The counters seem to be normally: %MCP-I-QSTATUS, total entries: 76/25000 (0%) Highest entry used: 8364 (33%) Best regards, Peter Erdosi Erdosi Peter Universitas of Debrecen Debreceni Universitas University of Lajos Kossuth Kossuth Lajos Tudomanyegyetem Center of Informatics and Computing Informatikai es Szamito Kozpont Section of VMS Systems VMS rendszerek osztalya H4010 Debrecen, P.O.B.:58 4010 Debrecen, Pf.:58 Hungary E-mail: PERDOSI@TIGRIS.KLTE.HU ================================================================================ Archive-Date: Mon, 17 Oct 1994 12:33:22 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 17 Oct 1994 12:20:42 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: uunet!WKUVX1.WKU.EDU!mx-list@esseye.si.com CC: perdosi@tigris.klte.hu Message-ID: <00986141.F848AA60.23@swdev.si.com> Subject: RE: MCP QUE SHO /BRIEF crashes with MX V4.1, as well... Peter Erdosi( PERDOSI@TIGRIS.KLTE.HU) writes: >My problem is similar, after this command I see the following: > >%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=02616588, Sounds like your file is corrupt. Try recreating it. /sig ================================================================================ Archive-Date: Mon, 17 Oct 1994 18:22:20 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: EREYES@ccr.dsi.uanl.mx (Ernesto Reyes Dorado) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: %MAIL-E-NOSUCHUSR Message-ID: Date: Mon, 17 Oct 1994 23:00:43 GMT To: MX-List@WKUVX1.WKU.EDU Every user we add to the system is unable to receibe mx mail and MX returs a message to the sender like this: --> Error description: Error-For: cgower@ccr.dsi.uanl.mx Error-Code: 2 Error-Text: Error in (forward) delivery to user CGOWER %MAIL-E-NOSUCHUSR, no such user CGOWER Error-End: 1 error detected Of course, the user exists. He can log in and I can send normal VMS mail to him, but can't receive Internet mail. All the older users are receiving MX normally, but all new user doesn't. Some MX quota exceeded? We have 600 registred users on the UAF. We are running MX4.1 on a MicroVAX 3100 with VMS5.1-2 and UCX. Any idea? ================================================================================ Archive-Date: Tue, 18 Oct 1994 08:01:09 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 18 Oct 1994 08:45:14 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: uunet!WKUVX1.WKU.EDU!mx-list@esseye.si.com CC: EREYES@ccr.dsi.uanl.mx Message-ID: <009861ED.093A9F80.1@swdev.si.com> Subject: RE: %MAIL-E-NOSUCHUSR Ernesto Reyes Dorado writes: >Every user we add to the system is unable to receibe mx mail >and MX returs a message to the sender like this: > >--> Error description: >Error-For: cgower@ccr.dsi.uanl.mx >Error-Code: 2 >Error-Text: Error in (forward) delivery to user CGOWER > %MAIL-E-NOSUCHUSR, no such user CGOWER >Error-End: 1 error detected > >Of course, the user exists. He can log in and I can send normal >VMS mail to him, but can't receive Internet mail. > >All the older users are receiving MX normally, but all new >user doesn't. Sounds like it might be a protection problem with VMSMAIL_PROFILE.DATA. -- Brian Tillman ================================================================================ Archive-Date: Tue, 18 Oct 1994 14:33:12 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: numrich@abmx.rz.rwth-aachen.de Subject: Installation stor not ended Date: 18 Oct 1994 09:33:09 GMT Message-ID: <3804ol$h5a@urmel.informatik.rwth-aachen.de> Reply-To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: MX-List@WKUVX1.WKU.EDU > > -Rcvd: 554 Received too many times by this host. > > and > > > Domain="cissy.gia.rwth-aachen", Path=Local > > These lines say it all. You've not told MX that cissy.gia.rwth-aachen.de is a > local node. > ... > You've left off the ".de" in your config. I changed it ... but ... i don't dare to say it .... now i get: Last error: %MX-E-PROTOERR, protocol error? as the errormessage :( I think i give it up now .. too many days gone already Nevertheless thanks to brian and Rok .. Nummi ---------------------- numrich@rwth-aachen.de ================================================================================ Archive-Date: Tue, 18 Oct 1994 15:43:02 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 18 Oct 1994 16:26:11 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: uunet!WKUVX1.WKU.EDU!mx-list@esseye.si.com CC: numrich@rwth-aachen.de Message-ID: <0098622D.6DDA67A0.5@swdev.si.com> Subject: RE: Installation stor not ended Nummi (numrich@rwth-aachen.de) writes: > I think i give it up now .. too many days gone already Don't give up yet! Include the contents of the debug file from your latest attempt. This error seems to indicate that the other system isn't answering with the correct SMTP responses. -- Brian tillman_brian@si.com ================================================================================ Archive-Date: Tue, 18 Oct 1994 22:21:11 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: dunnett@mala.bc.ca (Malcolm Dunnett) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Question about MX and MAIL FROM: commands Message-ID: <1994Oct18.161553.5167@mallrc.mala.bc.ca> Date: 18 Oct 94 16:15:53 -0700 To: MX-List@WKUVX1.WKU.EDU I had a complaint from another site about MX rejecting mail messages from there. Turns out that the problem was that the messages were originating in uucp and their mailer was putting "bang path" notation in the MAIL FROM: SMTP command. MX rejects the message at this point, with a 501 error and the session closes. Presumably MX is demanding the address given here conform to RFC 822. While this is arguably the right thing to do it's apparently more restrictive than other mailers, such as sendmail, which seem to accept any random string here. It's quite possible that the rest of the message is fine ( eg contains a replyable "from:" address ) and that it is reasonable to accept this message. Since MX is only checking the address for correct syntax there's no guarantee that it is a valid return path anyway. What would the impact be of having MX accept messages under these circumstances? -- ============================================================================= Malcolm Dunnett Malaspina University-College Email: dunnett@mala.bc.ca Computer Services Nanaimo, B.C. CANADA V9R 5S5 Tel: (604)755-8738 ================================================================================ Archive-Date: Wed, 19 Oct 1994 02:22:00 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: wing@tgv.com ("Dan Wing") Subject: Re: %MAIL-E-NOSUCHUSR Date: 18 Oct 1994 16:56:38 GMT Message-ID: <380uo6$kak@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article , EREYES@ccr.dsi.uanl.mx (Ernesto Reyes Dorado) writes: #Every user we add to the system is unable to receibe mx mail #and MX returs a message to the sender like this: # #--> Error description: #Error-For: cgower@ccr.dsi.uanl.mx #Error-Code: 2 #Error-Text: Error in (forward) delivery to user CGOWER # %MAIL-E-NOSUCHUSR, no such user CGOWER #Error-End: 1 error detected # #Of course, the user exists. He can log in and I can send normal #VMS mail to him, but can't receive Internet mail. # #All the older users are receiving MX normally, but all new #user doesn't. # #Some MX quota exceeded? We have 600 registred users on the UAF. # #We are running MX4.1 on a MicroVAX 3100 with VMS5.1-2 and UCX. # #Any idea? It says "Error in (forward) delivery ...". Does user CGOWER have a forwarding record? $ SET PROCESS/PRIVILEGE=SYSNAM $ MAIL MAIL> SHOW FORWARD/USER=CGOWER Also, turn on Local debugging (see MX_DOC:MX_MGMT_GUIDE.TXT for information), which will show more information as well. -Dan Wing, wing@tgv.com ================================================================================ Archive-Date: Wed, 19 Oct 1994 02:22:05 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: EREYES@ccr.dsi.uanl.mx (Ernesto Reyes Dorado) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: %MAIL-E-NOSUCHUSR Message-ID: Date: Tue, 18 Oct 1994 17:01:01 GMT To: MX-List@WKUVX1.WKU.EDU In EREYES@ccr.dsi.uanl.mx writes: > Every user we add to the system is unable to receibe mx mail > and MX returs a message to the sender like this: > > --> Error description: > Error-For: cgower@ccr.dsi.uanl.mx > Error-Code: 2 > Error-Text: Error in (forward) delivery to user CGOWER > %MAIL-E-NOSUCHUSR, no such user CGOWER > Error-End: 1 error detected > > Of course, the user exists. He can log in and I can send normal > VMS mail to him, but can't receive Internet mail. > > All the older users are receiving MX normally, but all new > user doesn't. > > Some MX quota exceeded? We have 600 registred users on the UAF. > > We are running MX4.1 on a MicroVAX 3100 with VMS5.1-2 and UCX. > > Any idea? > Good news: we found the solution! Before the problem, I recreate with CONVERT the SYSUAF.DAT file to avoid file fragmentation. This generate version two of SYSUAF.DAT. But version one still exists. I think VMS was using version two of the SYSUAF and MX was using version one. I delete version one and rename version two as version one. It works! Thanks for your colaboration! ================================================================================ Archive-Date: Wed, 19 Oct 1994 03:47:29 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 19 Oct 1994 09:47:16 EDT From: Brian A McMillan (44) 505 702030 Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009862BE.DDFBE180.1@cosmos.colloquium.co.uk> Subject: Changing Reply-To: field?? Is it possible to set the Reply-To: field to have a different value to the host name? We have users sending mail from individual workstations, e.g. cosmos.colloquium.co.uk, but we want mail to return to colloquium.co.uk. many thanks in advance, Brian =============================================================================== Brian A McMillan | Colloquium | Telephone: FDS Ltd | Email and Conferencing | 6/7 Steeple Square | "Knowledge today is *power* tomorrow" | 01505 702030 Kilbarchan PA10 2JD | | Scotland | MCMILLAN@cosmos.COLLOQUIUM.CO.UK | =============================================================================== ================================================================================ Archive-Date: Wed, 19 Oct 1994 05:41:52 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 19 Oct 1994 11:41:22 WET From: Hubert Ulliac - Universite de Haute Bretagne Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009862CE.CE59A96C.15@mailhost.uhb.fr> Subject: RE : Changing Reply-To: field?? >Is it possible to set the Reply-To: field to have a different value to >the host name? We have users sending mail from individual workstations, >e.g. cosmos.colloquium.co.uk, but we want mail to return to >colloquium.co.uk. I use for that the contrib NAME_CONVERSION ------------------------------------------------------------------------------- Hubert ULLIAC ! Téléphone: (33) 99 33 52 77 Université de Haute Bretagne ! Télécopie: (33) 99 33 52 73 Service Informatique ! pour la Recherche ! et l'Enseignement ! 6 Avenue Gaston Berger ! F-35043 RENNES Cedex ! E-Mail : Hubert.Ulliac@Uhb.Fr ------------------------------------------------------------------------------- ================================================================================ Archive-Date: Wed, 19 Oct 1994 08:08:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 19 Oct 1994 08:57:06 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: uunet!WKUVX1.WKU.EDU!mx-list@esseye.si.com Message-ID: <009862B7.DBBAA840.21@swdev.si.com> Subject: RE: Question about MX and MAIL FROM: commands Malcolm Dunnett (dunnett@mala.bc.ca) writes: > Turns out that the problem was that the messages were originating in >uucp and their mailer was putting "bang path" notation in the >MAIL FROM: SMTP command. MX rejects the message at this point, with a >501 error and the session closes. Presumably MX is demanding the address >given here conform to RFC 822. ... > What would the impact be of having MX accept messages under these >circumstances? We, too, receive mail via UUNET and we get bang paths as well. However, our UUNET internal router, named esseye, is a Sun running Smail3.1.28.1 #29. We've modified it to tack on "@esseye.si.com" on the end of all the bang paths (except for Reply-To, which we believe should never be modified). Perhaps you could do something similar. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Wed, 19 Oct 1994 13:38:20 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 19 Oct 1994 11:34:00 PDT From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: mcmillan@cosmos.colloquium.co.uk, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <009862CD.C6CF1EA0.31418@CCVAX.CCS.CSUS.EDU> Subject: RE: Changing Reply-To: field?? > Is it possible to set the Reply-To: field to have a different value to > the host name? If you have the co-operation of your users, have them place in their login.com files the command: $ DEFINE MX_REPLY_TO "appropriate_user_name@colloquium.co.uk" if the appropriate username is always the actual account name, you can use the generic: $ DEFINE MX_REPLY_TO - "''F$EDIT(F$GETJPI("","USERNAME"),"COLLAPSE")'@colloquium.co.uk" Of course, I assume that colloquium.co.uk knows how to get the mail back to the intended recipient... John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu "Just an invisible cog in a huge wheel" ================================================================================ Archive-Date: Wed, 19 Oct 1994 14:11:40 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: hlaufman@magnus.acs.ohio-state.edu (Harry B Laufman) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Newbie mx questions... Date: 19 Oct 1994 15:17:51 GMT Message-ID: <383dav$fne@charm.magnus.acs.ohio-state.edu> To: MX-List@WKUVX1.WKU.EDU Hello, Some fundamental questions from a new VAX manager. MX 3.3 is already installed on this VMS 5.4.3 VAX 4300. We have some 80 mailing lists in action. Can I / should I run MLF_CONFIG.COM? I have been creating Mailing lists from the mcp prompt with DEFINEs and MODIFYs. Is anything lost or gained by running MLF_CONFIG.COM? Should I run it to re-define SYSTEM_USERS? I have changed these from the mcp prompt. After making changes from the mcp prompt, I was told to command RESET, which prompts that such and such is being notified. I find in the manual the following: $ MCP MCP> @MLF_CONFIG.MCP MCP> SAVE MCP> RESET So, do I need the SAVE and RESET after a DEFINE or MODIFY? And, some LIST /OWNERs have gotten "insufficient privileges" messages when addressing LISTSERV with ADDs and REMOVEs. It seems that this happens when they are using one of the POP clients (NUPOP, EUDORA, etc) rather than their interactive login accounts. I vaguely remember being told of this difficulty. Are these clients non-complient with some RFC? I do intend to upgrade to 4.1 of MX as soon as I feel a little more comfortable with our system. How difficult is this upgrade process? Thanks for any and all help. Harry Laufman I'd like to be able to explain it coherently to our users. ================================================================================ Archive-Date: Wed, 19 Oct 1994 14:12:01 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: madison@tgv.com (Matt Madison) Subject: Re: Question about MX and MAIL FROM: commands Date: 19 Oct 1994 15:36:42 GMT Message-ID: <383eeg$49q@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <1994Oct18.161553.5167@mallrc.mala.bc.ca>, dunnett@mala.bc.ca (Malcolm Dunnett) writes: & I had a complaint from another site about MX rejecting mail messages & from there. & & Turns out that the problem was that the messages were originating in & uucp and their mailer was putting "bang path" notation in the & MAIL FROM: SMTP command. MX rejects the message at this point, with a & 501 error and the session closes. Presumably MX is demanding the address & given here conform to RFC 822. & & While this is arguably the right thing to do it's apparently more & restrictive than other mailers, such as sendmail, which seem to accept & any random string here. It's quite possible that the rest of the message & is fine ( eg contains a replyable "from:" address ) and that it is & reasonable to accept this message. Since MX is only checking the address & for correct syntax there's no guarantee that it is a valid return path & anyway. Yes, but if it is syntactically correct, MX at least stands a chance of being able to get an error message back to the sender in the event that the message cannot be delivered. & What would the impact be of having MX accept messages under these & circumstances? If the message was mis-addressed, or for whatever reason could not be delivered, the sender would never get any bounce message back. Maybe that's not so bad, but if the sending site is on the Internet, the least they could do is to minimally conform to the protocol specs. -Matt -- Matthew Madison | madison@tgv.com | +1 408 457 5390 TGV, Inc. | 101 Cooper Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Wed, 19 Oct 1994 14:12:34 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: denholm@conmat.phys.soton.ac.uk Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: Changing Reply-To: field?? Message-ID: <0FMTBS5P@math.fu-berlin.de> Date: Wed, 19 Oct 1994 17:16:01 GMT To: MX-List@WKUVX1.WKU.EDU In Article <009862BE.DDFBE180.1@cosmos.colloquium.co.uk> Brian A McMillan (44) 505 702030 writes: >Is it possible to set the Reply-To: field to have a different value to >the host name? We have users sending mail from individual workstations, >e.g. cosmos.colloquium.co.uk, but we want mail to return to >colloquium.co.uk. > you can define reply-to on a per-user basis to anything you like. ($ define mx_reply_to or something like that) but you can also set mx up to stamp the mail as from the common name. Here, I have nodes soton{a|b|c}.phys.soton.ac.uk Our mail address is conmat.phys.soton.ac.uk (This is an mx-entry mapping to sotona, I think) so I have $ sh log mx* ! output edited... "MX_NODE_NAME" = "sotona.phys.soton.ac.uk" "MX_VMSMAIL_FROM_FORMAT" = "" "MX_VMSMAIL_LOCALHOST" = "@conmat.phys.soton.ac.uk" this seems to do what I think it ought to - mail is stamped from user@conmat.phys... But in the smtp-transaction, the HELO and 'received-by' stuff use mx_node_name, ie the actual node involved, which I assume is the correct thing to do..? Actually, no, I think they bypass mx_node_name and use actual ip name, since I have mx_node_name set to sotona on all 3 nodes, for some reason, yet both sotona and b run smtp process, and seem to mark the email correctly... perhaps mx_node_name is used only as second param in mx_vmsmail_localhost format string ? I think I got all this by trial and error - docs didn't suggest setting things up in this way. (so I hope I'm not breaking any smtp rules) dd -- David Denholm 'official' : D.R.Denholm@southampton.ac.uk Physics dept. preferred : denholm@conmat.phys.soton.ac.uk Southampton University Tel : (0703) 592104 [work] (0489) 576733 [home] uk SO17 1BJ Fax : (0703) 585813 ================================================================================ Archive-Date: Wed, 19 Oct 1994 16:09:14 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 Oct 1994 16:08:52 -0400 To: MX-List@WKUVX1.WKU.EDU From: Dolan@Bible.acu.edu (Tom Dolan) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: AOL.com Anyone else notice mail is not reaching AOL.COM today? Tom Dolan Dolan@Bible.acu.edu Systems Manager College of Biblical and Family Studies Abilene Christian University ================================================================================ Archive-Date: Wed, 19 Oct 1994 21:18:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: jgostl@panix.com (Jack Gostl) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: VMS to Unix mail Date: 19 Oct 1994 22:17:16 -0400 Message-ID: <384jvc$666@panix.com> To: MX-List@WKUVX1.WKU.EDU I'm trying to find out what is involved in connecting VMS mail to Unix mail. Nothing fancy. Just two machines on the same new. Not even any domains involved. Can anyone help me out. (Would appreciate response via e-mail.) ================================================================================ Archive-Date: Wed, 19 Oct 1994 22:18:50 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: leebp@iscs.nus.sg Date: Thu, 20 Oct 1994 11:16:38 SST Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00986394.84225915.325@dec7000.iscs.nus.sg> Subject: Random mail errors under MX4.1 and VMS 6.1 Hi guys .. I wonder if you have seen the following. I have MX4.1 running on a cluster of Vax and Axp VMS6.1 with a common MX root and mail queue. I received the following errors (rarely): 1) ...... Error-Code: 2 Error-Text: Error in delivery to user xxxxx error sending to user !AS I assume the following occurs becoz there maybe be something wrong with the mail files. I checked and tested with mails and found it was not the case. The next error which I have seen reports a DUP key in the mail file (or something to that effect as I have not saved a copy of the erroneous mails *sigh*). Would I be right to presume it's related to a bug with VMSmail on the VMS 6.1 (Axp or Vax)? I have seen a patch mentioned with regards to VMSmail and hope it's related .. I would appreciate pointers .... Thanks a lot ... Paul ================================================================================ Archive-Date: Thu, 20 Oct 1994 03:45:41 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 20 Oct 1994 09:45:16 EDT From: "Mario Meyer, Phys.-Techn. Bundesanstalt" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: mmeyer@ChbRB.Berlin.PTB.De Message-ID: <00986387.C0E399E3.5@ChbRB.Berlin.PTB.De> Subject: for wishlist: route handling I use MX as gateway for incoming mails to UNIX hosts. Therefore I added MX records at the nameserver pointing to the VAXes running MX. I had to define appropriate paths for every UNIX host pointing on its IP address in MX. But I don't want to spend too much time copying nameserver information to MX path definitions and maintaining consistency. Therefore my suggestion: Is it possible to introduce a qualifier (/directly) that causes SMTP routing to the hosts IP address instead of the nameservers mx record target ? Example: MCP> define path "shiva.Berlin.PTB.De" SMTP /directly instead of: MCP> define path "shiva.Berlin.PTB.De" SMTP /route=192.53.103.111 A path definition Domain="shiva.Berlin.PTB.De", Path=SMTP now means the same as Domain="shiva.Berlin.PTB.De", Path=SMTP, Route="shiva.Berlin.PTB.De" . Both will route mails acoordingly to the nameservers mx records. Wouldn't It it be better to use the latter for a direct routing to the host ? Thanks to Hunter for a fine piece of software. May DEC learn from him ! --,------------------------------------------------------.------------------ | Mario Meyer Physikalisch-Technische Bundesanstalt | . , | ............. Institut Berlin Labor 10.42 | _QQ__ | : wide area : Abbestr. 2-12, D - 10587 Berlin | __( U, )__ | : networker : tel. (+49 30) 3481 442, fax. ... 490 | /// `---' \\\ | SMTP MMeyer@ChbRB.Berlin.PTB.De, BITNET MMeyer@PTBIB | /||\ /||\ --| X.400 S=Meyer;OU=AM;OU=10-42;O=PTB;P=PTB;A=d400;C=De |------------------ `------------------------------------------------------' ================================================================================ Archive-Date: Thu, 20 Oct 1994 06:12:27 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 20 Oct 1994 07:08:37 EST From: Spencer Yost Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986371.DE9FF960.1@ledger.co.forsyth.nc.us> Subject: RE: Newbie mx questions... > Hello, > > Some fundamental questions from a new VAX manager. MX 3.3 is > already installed on this VMS 5.4.3 VAX 4300. We have some 80 mailing > lists in action. > Up until last week I was running this configuration on vms 5.5-2 > Can I / should I run MLF_CONFIG.COM? I have been creating Mailing lists from > the mcp prompt with DEFINEs and MODIFYs. Is anything lost or gained by running > MLF_CONFIG.COM? Should I run it to re-define SYSTEM_USERS? I have changed > these from the mcp prompt. > I have never seen an advantage to MLF_CONFIG. I have made changes manually. > After making changes from the mcp prompt, I was told to command RESET, which > prompts that such and such is being notified. I find in the manual the > following: > > $ MCP > MCP> @MLF_CONFIG.MCP > MCP> SAVE > MCP> RESET > > So, do I need the SAVE and RESET after a DEFINE or MODIFY? > Yes, because reset forces all the agents to re-read their configuration information. Therefore you need to save what you just finished, then reset. Until I happened across the save command, I was exiting, then re-entering or "$mcp reset" to do the reset. By the way, this save command can take a {file-name} parameter, enabling you to save the config off to the side before you make any changes you are unsure off. > And, some LIST /OWNERs have gotten "insufficient privileges" messages when > addressing LISTSERV with ADDs and REMOVEs. It seems that this happens when I have had that problem too and I was using my VAX account (I am owner of a list), but I just started using MLFAKE as a work-around, and never investigated. I am now at MX 4.1 and have not tried the add and remove yet. > I do intend to upgrade to 4.1 of MX as soon as I feel a little more > comfortable with our system. How difficult is this upgrade process? > > Thanks for any and all help. > Upgrade was a cinch, I was able to support a rolling upgrade(one node is still at 3.3) and nothing special had to be done. A couple of notes of interest: -Any messages currently in the queues pending delivery will be gone. -Save your configuration file as a command file (the installation notes explain well) -The LISTSERV mail stop has been deimplemented, and I had to set up an alias. If you are using MX's mailing list processor, alot of your lists' users are probably used to using it and this is something you will have to do. -Take advantage of the multiple processes available. This has dramatically improved list performance (I have 6 SMTP processes running). > I'd like to be able to explain it coherently to our users. "It's magic" works for me (-:% +================================+====================================+ | Spencer William Yost | Mis Department | | Vax/VMS Systems Manager | Forsyth County Government | | Yost@ledger.co.forsyth.nc.us | 200 N. Main St Room 603 | | | Hall Of Justice | | | Winston-Salem NC 27101 | +=====================================================================+ ================================================================================ Archive-Date: Thu, 20 Oct 1994 06:15:19 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 20 Oct 1994 07:11:56 EST From: Spencer Yost Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986372.55248CE0.27@ledger.co.forsyth.nc.us> Subject: RE: AOL.com > Anyone else notice mail is not reaching AOL.COM today? I have problems periodically with mail addressed to them, but usually it is AOL's fault and they are back on-line before the retry limit is exceeded and the postmaster gets a message. PRODIGY, however is a different matter .... Wow I have been able to contribute twice today! I'm exhausted ..... (-;% +================================+====================================+ | Spencer William Yost | Mis Department | | Vax/VMS Systems Manager | Forsyth County Government | | Yost@ledger.co.forsyth.nc.us | 200 N. Main St Room 603 | | | Hall Of Justice | | | Winston-Salem NC 27101 | +=====================================================================+ ================================================================================ Archive-Date: Thu, 20 Oct 1994 07:37:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: cooper@utsph.sph.uth.tmc.edu Subject: ..Unsent mail messages...how to get them back into the queue Date: 19 Oct 1994 19:05:22 GMT Message-ID: <383qli$ipb@oac4.hsc.uth.tmc.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU For some unknown reason our MX server quit sending mail messages. There were about 400 backlogged...so I stopped the server and re-started it. a few of the messages were sent...but it was very slow. I then did a compress of the queue using the command QUEUE COMPRESS/MAX=5000 which moved all of the messages to [.old_x] subdirectories. Now mail appears to be working fine...that is new mail...but all of the old messages that were backup appear to have never been sent. Is there some easy way to re-add these messages to the queue file in order to get the messages out...there are too many to try to do by hand. Thanks for any help you can provide Charlie cooper@utsph.sph.uth.tmc.edu ================================================================================ Archive-Date: Thu, 20 Oct 1994 12:44:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <9410201730.AA00203@us3rmc.pa.dec.com> Date: Thu, 20 Oct 94 10:30:05 PDT From: Scot Bishop-Walker - DEC PC Integration 20-Oct-1994 1031 Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Subject: RE: Newbie mx questions... >> And, some LIST /OWNERs have gotten "insufficient privileges" messages when >> addressing LISTSERV with ADDs and REMOVEs. It seems that this happens when > I have had that problem too and I was using my VAX account (I am owner of a > list), but I just started using MLFAKE as a work-around, and never > investigated. I am now at MX 4.1 and have not tried the add and remove > yet. I've run into this problem (usually on a newly-created list) on a regular basis. The only solution I've found is to remove the list, and reDEFINE it. Make sure you have backup copies of your subscriber list files, though...just in case. Once the list has been reDEFINEd, I don't have any problems. Hunter - any ideas why this happens? - Scot Bishop-Walker Digital Equipment Corporation Northern California PC Integration Services ================================================================================ Archive-Date: Thu, 20 Oct 1994 12:46:45 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 20 Oct 1994 12:46:10 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009863A1.05FD1A95.30@ALPHA.WKU.EDU> Subject: RE: Newbie mx questions... Scot Bishop-Walker - DEC PC Integration 20-Oct-1994 1031 writes: > >I've run into this problem (usually on a newly-created list) on a regular basis. > >The only solution I've found is to remove the list, and reDEFINE it. Make sure >you have backup copies of your subscriber list files, though...just in case. > >Once the list has been reDEFINEd, I don't have any problems. > >Hunter - any ideas why this happens? > The only reason I know of that can cause that is mismatched case on the /OWNER address---the case of that address must match the case of the received message *exactly*. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Thu, 20 Oct 1994 15:14:31 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: wing@tgv.com ("Dan Wing") Subject: Re: VMS to Unix mail Date: 20 Oct 1994 15:41:59 GMT Message-ID: <38634d$hgf@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <384jvc$666@panix.com>, jgostl@panix.com (Jack Gostl) writes: #I'm trying to find out what is involved in connecting VMS mail to Unix mail. #Nothing fancy. Just two machines on the same new. Not even any domains #involved. # #Can anyone help me out. # #(Would appreciate response via e-mail.) You need TCP/IP and SMTP on both nodes. -Dan Wing, wing@tgv.com ================================================================================ Archive-Date: Thu, 20 Oct 1994 15:15:10 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: system@hal.datalife.com Subject: SMTP send pblm - error code 08638162 Message-ID: <1994Oct20.095715.77@hal.datalife.com> Date: 20 Oct 94 09:57:15 -0400 Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU This morning our outbound SMTP mail is getting hung up. All entries in the MX queue are failing with status code 08638162. I stopped and restarted MX (V3.3) and CMU IP (V6.6). The errors persist. Here is an entry from MCP QUEUE SHOW/FULL: Entry: 19656, Origin: [Local] Status: IN-PROGRESS, size: 2236 bytes Created: 19-OCT-1994 22:04:27.41, expires 18-NOV-1994 22:04:27.41 Last modified 20-OCT-1994 09:28:28.65 SMTP entry #19657, status: READY, size: 2236 bytes, waiting for retry until 20-OCT-1994 09:59:47.05 Created: 19-OCT-1994 22:06:41.14, expires 18-NOV-1994 22:04:27.41 Last modified 20-OCT-1994 09:29:47.05 Recipient #1: , Route=delphi.com Error count=21 Last error: %NONAME-E-NOMSG, Message number 08638162 I turned on router and smtp debugging. Here are the log files: MX_ROUTER.LOG: 20-OCT-1994 09:26:14.36 %PROCESS, Processing entry number 19657 20-OCT-1994 09:26:14.47 %PROCESS, Status from READ_INFO was 00000001 20-OCT-1994 09:26:14.47 %PROCESS, Recipient #0: 20-OCT-1994 09:26:14.47 %REWRITE, No rewrite rules matched 20-OCT-1994 09:27:06.53 %FINDPATH, Site-spec expand on delphi.com err=08638162 20-OCT-1994 09:27:06.53 %FINDPATH, domain name DELPHI.COM matched path pattern * 20-OCT-1994 09:27:06.53 %PROCESS, Rewrote as - next hop delphi.com, path 2 20-OCT-1994 09:27:06.73 %PROCESS, Adding to SMTP path: . 20-OCT-1994 09:27:06.94 %PROCESS, Path SMTP gets 1 rcpts, entry number 19685 MX_SMTP.LOG: 20-OCT-1994 09:28:28.47 Processing queue entry number 19657 on node HAL 20-OCT-1994 09:28:28.73 Recipient: , route=delphi.com 20-OCT-1994 09:28:28.73 SMTP_SEND: looking up host name delphi.com 20-OCT-1994 09:29:46.73 SMTP_SEND: Failed, sts=08638162 20-OCT-1994 09:29:46.73 SMTP send failed, sts=0C27804A, sts2=08638162 20-OCT-1994 09:29:46.73 Recipient status=0C27804A for 20-OCT-1994 09:29:47.05 1 rcpts need retry, next try 20-OCT-1994 09:59:47.05 20-OCT-1994 09:29:47.08 *** End of processing pass *** Our internet connection is up and we can access our name servers. If I use the NSQUERY utility to lookup delphi.com I get valid results: QUERY #1: QName=DELPHI.COM., QType=255, QClass=1 ANSWER #1: DELPHI.COM., NS, INTERNET, 1 23:28:40, NS=NIC.NEAR.NET. ANSWER #2: DELPHI.COM., NS, INTERNET, 1 23:28:40, NS=BU.EDU. ANSWER #3: DELPHI.COM., A, INTERNET, 0 01:35:46, Addr=192.80.63.1 ANSWER #4: DELPHI.COM., A, INTERNET, 0 01:35:46, Addr=192.80.63.2 ANSWER #5: DELPHI.COM., A, INTERNET, 0 01:35:46, Addr=192.80.63.4 ANSWER #6: DELPHI.COM., A, INTERNET, 0 01:35:46, Addr=192.80.63.8 ANSWER #7: DELPHI.COM., A, INTERNET, 0 01:35:46, Addr=192.80.63.6 ANSWER #8: DELPHI.COM., A, INTERNET, 0 01:35:46, Addr=192.80.63.9 ANSWER #9: DELPHI.COM., A, INTERNET, 0 01:35:46, Addr=192.80.63.7 ANSWER #10: DELPHI.COM., A, INTERNET, 0 01:35:46, Addr=192.80.63.5 ANSWER #11: DELPHI.COM., MX, INTERNET, 0 01:35:46, Pref=5, Exch=bos1h.delphi.com. ANSWER #12: DELPHI.COM., MX, INTERNET, 0 01:35:46, Pref=20, Exch=delphi.com. AUTHOR #1: delphi.com., NS, INTERNET, 1 23:28:40, NS=NIC.NEAR.NET. AUTHOR #2: delphi.com., NS, INTERNET, 1 23:28:40, NS=BU.EDU. ADDTNL #1: NIC.NEAR.NET., A, INTERNET, 1 23:59:52, Addr=192.52.71.4 ADDTNL #2: BU.EDU., A, INTERNET, 1 23:59:52, Addr=128.197.27.7 ADDTNL #3: bos1h.delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.10 ADDTNL #4: delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.1 ADDTNL #5: delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.2 ADDTNL #6: delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.4 ADDTNL #7: delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.8 ADDTNL #8: delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.6 ADDTNL #9: delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.9 ADDTNL #10: delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.7 ADDTNL #11: delphi.com., A, INTERNET, 0 01:35:46, Addr=192.80.63.5 The same error occurs on mail to aol.com, ibmmail.com, and vnet.ibm.com. Can anyone shed some light on this problem? Thanks in advance. ...Chris -- Chris Wysocki Data Life Associates wysocki@datalife.com +1 201 239 7500 x232 ================================================================================ Archive-Date: Thu, 20 Oct 1994 16:09:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <9410202101.AA16020@us3rmc.pa.dec.com> Date: Thu, 20 Oct 94 14:01:55 PDT From: Scot Bishop-Walker - DEC PC Integration 20-Oct-1994 1403 Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Subject: RE: Newbie mx questions... >> I've run into this problem (usually on a newly-created list) on a regular >> basis. >> >> The only solution I've found is to remove the list, and reDEFINE it. Make >> sure you have backup copies of your subscriber list files, though...just >> in case. >> >> Once the list has been reDEFINEd, I don't have any problems. > The only reason I know of that can cause that is mismatched case on > the /OWNER address---the case of that address must match the case of > the received message *exactly*. I've added the user id in upper case and lower case, both, so the /OWNER list shows the address both ways. I've also had the same problem sending commands from the SYSTEM account. MX didn't recognize the SYSTEM account as having privileges, although I've defined SYSTEM and my user account (both upper and lower case) as system users. As I said, though, if I remove the list and redefine it, everything works like it should. - Scot ================================================================================ Archive-Date: Thu, 20 Oct 1994 16:09:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 20 Oct 1994 16:09:58 CDT From: system@BEAVER.Bemidji.MSUS.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009863BD.7EE49CA0.22@BEAVER.Bemidji.MSUS.edu> Subject: RE: Newbie mx questions... Hunter wrote ... > The only reason I know of that can cause that is mismatched case on > the /OWNER address---the case of that address must match the case of > the received message *exactly*. I second that. I tried to use an IP alias to didle with the list ... it was rejected. //----------\|/------\\ Dave Miller. || /\ -X- || Professor, Computer Science. || / \ /|/\ || || / \ / \ || DMILLER@BEAVER.Bemidji.MSUS.EDU || / \ \ || || /________\____\ || 1500 Birchmont Dr. NE || || || || Bemidji State University \\------|| -------// Bemidji MN, 56601 ================================================================================ Archive-Date: Thu, 20 Oct 1994 16:21:00 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 20 Oct 1994 17:10:21 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: Robertini@sns.it, hardis@garnet.nist.gov Message-ID: <009863C5.EDFCE220.25503@garnet.nist.gov> Subject: RE: SMTP process dies > Is "never logged in" a black hole for SMTP process? No. ================================================================================ Archive-Date: Fri, 21 Oct 1994 12:03:47 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 21 Oct 1994 18:04:39 EDT From: Paul Warwicker - GDS Customer Service Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU CC: paulw@uk.gdscorp.com Message-ID: <00986496.AEC4476B.1@gdssup.uk.gdscorp.com> subscribe mx-list Paul Warwicker ================================================================================ Archive-Date: Fri, 21 Oct 1994 15:42:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: Current version of MX? Message-ID: <1994Oct21.130314@cam1> From: henderson@mln.com (Javier Henderson) Reply-To: MX-List@WKUVX1.WKU.EDU Date: 21 Oct 94 13:03:14 PDT To: MX-List@WKUVX1.WKU.EDU Hello, I ftp'd MX 4.1 from ftp.spc.edu, installed it (upgraded from 4.0 beta actually) and it all works great, except that during the installation the product was identified as 4.1T and the mail headers still say 4.1-beta-1. Is there a 'final' release available, or is this as final as it gets? Thanks! -- Javier Henderson (JH21) henderson@mln.com ================================================================================ Archive-Date: Fri, 21 Oct 1994 17:12:55 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 21 Oct 1994 17:12:14 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0098648F.5BD57B35.39@ALPHA.WKU.EDU> Subject: RE: Current version of MX? henderson@mln.com (Javier Henderson) writes: > >Hello, > >I ftp'd MX 4.1 from ftp.spc.edu, installed it (upgraded from 4.0 beta actually) >and it all works great, except that during the installation the product was >identified as 4.1T and the mail headers still say 4.1-beta-1. > >Is there a 'final' release available, or is this as final as it gets? > I can't check ftp.spc.edu right now, as we're having Internet troubles upstream from us. I did check the .ZIP file on ftp.wku.edu and saw no such problems: MCP> sho vers MX version id is: MX V4.1 VAX MCP> The installation identifying it as T4.1 is a bug in VMSINSTAL in OpenVMS AXP V6.1---this was documented in the addendum to the release notes for V6.1. The file on ftp.spc.edu should be identical to the one on ftp.wku.edu, and it does indeed appear to be so.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Sat, 22 Oct 1994 08:36:33 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 22 Oct 1994 14:21:33 EDT From: Paul Warwicker - GDS Customer Service Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: paulw@uk.gdscorp.com Message-ID: <00986540.AE5EF4AB.1@gdssup.uk.gdscorp.com> Subject: A question on name conversion. Could someone offer me some advice. I've only had about a day's involvement with MX, so keep it simple! All our internet mail is sent via a seperate cluster (hello PaulH) and we want to use a generic mail address. Unfortunately the accounts on both clusters don't match so that replies to mail originating from paul on one cluster bounced on the hub. I've succeded in converting mail to/from paul on one cluster to be sent to paulw via the hub so replies now work. However I still have two nigling problems. The first is merely cosmetic. The Return-Path (not the Reply-To) is still incorrect. And secondly any replies coming via the hub has the cluster alias prefixed (i.e. ARC::MX%"MX-List@WKUVX1.WKU.EDU"). Is there a way to fix either of these? tia paul -- Paul Warwicker (Senior Technical Specialist) Graphic Data Systems Ltd Internet: paulw@uk.gdscorp.com Wellington House, East Rd Camb, CB1 1BH Voice: +44(0)1223 300113, Fax: +44(0)1223 371926 England -- ================================================================================ Archive-Date: Mon, 24 Oct 1994 07:10:22 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 24 Oct 1994 08:10:04 EDT From: "Friend of Odin." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0098669F.1E0C5EAF.10@vax6.drc.com> Subject: The queue entries just sit there. I'm running MX 4.1 and I notice that some, not all, but some inbound and outbound mail entries just sit in the queue. Their status is in progress and ready, but they don't go anywhere. They are not requeued for a future time, they just sit there and do absolutely nothing. If I do a reset, they disappear, but are not delivered. If I do a queue ready on them, they continue to sit there and are not delivered. I have the processes operating on a 15 minute instead of a 30 minute interrval, but don't think this is the problem. Help? Please? Dan Graham ================================================================================ Archive-Date: Mon, 24 Oct 1994 10:12:45 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 24 Oct 1994 11:12:17 EDT From: "Friend of Odin." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <009866B8.921E2F67.3@vax6.drc.com> Subject: More on mail messages that just sit in the queue. I wrote a little while ago about my problem with MX 4.1 where inbound and outbound mail, seemingly at random, just sits in the queue not moving, not erroring, just sitting there doing nothing. This morning, I have observed several instances where a mail message was just sitting there, just one mwssage. When another came along, both were properly dispatched, but it seemed to take another message to "boot" the one just sitting in the queue to action. Any thoughts? Dan Graham ================================================================================ Archive-Date: Mon, 24 Oct 1994 11:07:46 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 24 Oct 1994 16:07:40 GMT From: "Andy Harper, KCL Systems Manager" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: udaa055@bay.cc.kcl.ac.uk Message-ID: <009866E1.D63CC000.14@bay.cc.kcl.ac.uk> Subject: RE: More on mail messages that just sit in the queue. >I wrote a little while ago about my problem with MX 4.1 where inbound and >outbound mail, seemingly at random, just sits in the queue not moving, not >erroring, just sitting there doing nothing. This morning, I have observed >several instances where a mail message was just sitting there, just one >mwssage. When another came along, both were properly dispatched, but it >seemed to take another message to "boot" the one just sitting in the queue >to action. Any thoughts? I've seen this quite a lot too. I found that a reset/cluster from MCP would usually force them to be processed. Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Mon, 24 Oct 1994 12:05:55 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 24 Oct 1994 12:55:31 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: graham@vax6.drc.com, hardis@garnet.nist.gov Message-ID: <009866C6.FE4C7100.25841@garnet.nist.gov> Subject: RE: More on mail messages that just sit in the queue. > I wrote a little while ago about my problem with MX 4.1 where inbound and > outbound mail, seemingly at random, just sits in the queue not moving... > Any thoughts? I think you ought to enable the debugging flags to see what's really happening. ================================================================================ Archive-Date: Tue, 25 Oct 1994 07:56:59 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 25 Oct 1994 16:20:44 -0330 From: SAEED KHADEMI Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <009867AC.D405B780.469@IREARN.BITNET> Subject: problem with finished mails... Dear Hunter, I'm using mx 4.1 and I've enabled auto purging. It looks like there is a problem with it's function. When I use MCP QUE SH/ALL, I see that finished mailes disapear from queue ( so this means that auto purging works very well ), but when I get directory listing of queue subdirectories ( 0-9 ) I see that there are a lot of files there. Again when I want to see inside queue by MCP command, I see that none of these files are in queue. What is the problem? Any comment will help me. Thanks in Advance. Regards, Saeed. ================================================================================ Archive-Date: Tue, 25 Oct 1994 08:15:08 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 25 Oct 1994 09:16:21 EDT From: hone@ouvaxa.cats.ohiou.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <00986771.8ADCA0E0.33@ouvaxa.cats.ohiou.edu> Subject: MX V4.1 & MR V3.3A problem Ohio University Electronic Communication Date: 25-Oct-1994 09:13am EST To: Remote Addressee ( _MX%"MX-List@WKUVX1.WKU.EDU" ) From: Donald Hone Dept: CaTS HONE Tel No: 614-593-0247 Subject: MX V4.1 & MR V3.3A problem We are an ALL-IN-1 system and recently upgraded from Message Router and MR VMS Mail Gateway (V3.2) to the newest release V3.3A. Since then the sender field is blank. This is the sender's full name field within ALL-IN-1. There were no other changes with our system. For example: Sender: MX%"MX-List@WKUVX1.WKU.EDU"@MRGATE@OUVAX Senders Full Name: These messages are replyable :-) but our users cannot see who internet messages are from without reading them. Has anyone else updated the MailBus packages to these versions? (PMDF is a solution I know). There is a new feature within MR Gate about including the VMS Username. "Do you want to include the VMS user name of the message sender in the message?" I have tried "Y" and "N" but not "NONE" with no change. Any feedback is appreciated. Thanks in advance. Received: 25-Oct-1994 09:16am ================================================================================ Archive-Date: Tue, 25 Oct 1994 11:28:33 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 25 Oct 1994 11:28:39 EDT From: Bob Christenson Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <00986784.06380BA0.3@fcstc1.frco.com> Subject: QUERY QUERY mx-list ================================================================================ Archive-Date: Tue, 25 Oct 1994 22:44:21 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: Single Quote Nightmares Message-ID: <1994Oct25.145624.6543@kcvax1> From: oursler@kenyon.edu (Miles) Reply-To: MX-List@WKUVX1.WKU.EDU Date: 25 Oct 94 14:56:24 EST To: MX-List@WKUVX1.WKU.EDU Hullo, I hope this is simple... We've got a user who received mail from the following address John_O'Connell@brown.edu Try as we might, we can't seem to get mail to accept this address. The single quote throws it for a loop. I've tried enclosing the quote in quotes and even quoted those quotes. But alas, no luck. MXALIAS also can't deal with it Any suggestions... - Miles - ================================================================================ Archive-Date: Tue, 25 Oct 1994 22:54:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: leebp@iscs.nus.sg Date: Wed, 26 Oct 1994 11:53:15 SST Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00986850.A0824591.460@dec7000.iscs.nus.sg> Subject: REMOVE ALIAS * ? Hi guys ... Is there a quick and dirty way to flush or remove all user aliases from the MX4.1 configuration file? Something possibly along the line of REMOVE ALIAS * ? Thanks .. Paul ================================================================================ Archive-Date: Wed, 26 Oct 1994 11:45:08 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 26 Oct 1994 10:41:06 MDT From: Mark Tarka Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00986846.8C1670A0.11@earth.oscs.montana.edu> Subject: Mail forwarding I had said: #Return-Path: #Received: from MVB.SAIC.COM by earth.oscs.montana.edu (MX V4.1 VAX) with SMTP; # Wed, 26 Oct 1994 10:19:41 MDT #From: Mark Tarka [Header material deleted] #In article <1994Oct25.082117.1@slacvx.slac.stanford.edu>, #fairfield@slacvx.slac.stanford.edu writes: # #[NB Quote symbol is ">" for the current message.] #>In article <1994Oct25.092137@sable.adelphi.edu>, #> cheryl@sable.adelphi.edu (Cheryl L. Kay) writes: #> #>> Is there a way to have mail forwarded to a different address and still #>> keep a copy within VMS???? #[text deleted...] #> I keep thinking that MX allows this also, but I have not direct #> experience with MX. # #Does. Just did it with this post. Uh...well I thought so, but now I'm unsure. I presumed that MX 4.1 forwards the message, and now note the "with SMTP" qualifier in the "Received" field above. Could someone supply a simple explanation of how the two (MX and SMTP), if there are two (i.e. MX not using SMTP within its "shell"(?)), interact? Mark ichjsmt@earth.oscs.montana.edu ================================================================================ Archive-Date: Wed, 26 Oct 1994 15:28:27 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 26 Oct 1994 15:27:59 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0098686E.9FA06540.94@uwwvax.uww.edu> Subject: local process dying Right after LOCAL starts local#1, there are four, dies with a status of 10018294 If I am correct that is "no file found" later local #4 dies with the same message. Mean while the two other are working. What file is it looking for or do I have the wrong message. Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Wed, 26 Oct 1994 17:43:55 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 26 Oct 1994 18:43:00 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: ichjsmt@earth.oscs.montana.edu, hardis@garnet.nist.gov Message-ID: <00986889.DDE99220.26207@garnet.nist.gov> Subject: RE: Mail forwarding Simplifying the previous question: > Is there a way to have mail forwarded to a different address and still > keep a copy within VMS? Which MAIL command do you mean, FORWARD or SET FORWARD? If FORWARD, use the /SELF qualifier. If SET FORWARD, not that I know of. > Could someone supply a simple explanation of how the two (MX and SMTP) > ... interact? SMTP is an acronym of Simple Message Transfer Protocol, a defined method for sending EMail over an IP network (i.e., the Internet). MX is software that provides an implementation of SMTP on the VAX. One component of MX receives EMail from the Internet, and another passes it on to VAX Mail. A third component of MX receives messages composed in VAX Mail, while a fourth transmits it (if required) using SMTP on the network. - Jonathan ================================================================================ Archive-Date: Thu, 27 Oct 1994 07:22:30 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 27 Oct 1994 07:14:11 EST From: Spencer Yost Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009868F2.CE6F6180.5@ledger.co.forsyth.nc.us> Subject: RE: local process dying > Right after LOCAL starts local#1, there are four, dies with a status of 10018294 > If I am correct that is "no file found" > later local #4 dies with the same message. Mean while the two other are > working. > What file is it looking for or do I have the wrong message. > Lyle Hunter > Computer Center > University Wisconsin-Whitewater > hunterl@uwwvax.uww.edu I have had this problem before in the past, though I have not run across it since I upgraded to 4.1 If you look in your queue(/full), there should be some entries whose disposition reads something like "no local_info". I seem to remember that there was literally a {msg_number}.local_info file that was missing. Anyways, irregardless of the my memoruy on the file, it was these types of entries occasionally torpedo the local process. Other times they saeemd to be harmless. I never did research how those entries came to be created, but they seemed to be tied to aborted editing sessions within VMSmail. I just had either a watchdog process or an operator keep an eye out for dying processes and restart them. I had a problem with 3.3 where a specific machine was killing the SMTP server process, so I already had this type of infrastructure set up. This may be too manual for your needs. Hope I helped, +================================+====================================+ | Spencer William Yost | Mis Department | | Vax/VMS Systems Manager | Forsyth County Government | | Yost@ledger.co.forsyth.nc.us | 200 N. Main St Room 603 | | | Hall Of Justice | | | Winston-Salem NC 27101 | +=====================================================================+ ================================================================================ Archive-Date: Thu, 27 Oct 1994 08:28:04 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 27 Oct 1994 09:29:18 EDT From: HONE@ouvaxa.cats.ohiou.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986905.AEE1B440.2@ouvaxa.cats.ohiou.edu> Subject: RE: local process dying From: NAME: Donald Hone FUNC: CaTS TEL: 614-593-0247 To: MX%"MX-List@WKUVX1.WKU.EDU"@MRGATE@OUVAX >Right after LOCAL starts local#1, there are four, dies with a status of >10018294 >If I am correct that is "no file found" I had the exact same problem. Since the problem deteriorated, my solution was to do MCP QUEUE COMPRESS (after SHUTDOWN) however I believe that messages were lost. After that the MCP QUEUE STATUS command showed total entries as incorrect. There haven't been any failures since then (3 days ago). Details are: mx 4.1, vms 5.5-2, ucx 3.1 ================================================================================ Archive-Date: Thu, 27 Oct 1994 10:47:36 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 27 Oct 1994 11:44:43 EDT From: "Friend of Odin." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <00986918.99C0AB2F.3@vax6.drc.com> Subject: Entry sits in queue after its time. We are running MX 4.1 and see a problem that just started last evening. I came in to four queue entries that were waiting for a retry time ... but the time was many hours in the past. I readied each entry and they flew as normal. Just now, I discovered two more entries that were supposed to run at 11:22, and I fuond them still sitting there, waiting for 11:22, when it was 11:37 ... and yes, the VAX clock is correctly set. Any ideas? Dan Graham ================================================================================ Archive-Date: Thu, 27 Oct 1994 10:52:10 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 27 Oct 1994 10:51:48 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986911.3545C651.35@ALPHA.WKU.EDU> Subject: RE: Entry sits in queue after its time. "Friend of Odin." writes: > >We are running MX 4.1 and see a problem that just started last evening. I >came in to four queue entries that were waiting for a retry time ... but >the time was many hours in the past. I readied each entry and they flew >as normal. Just now, I discovered two more entries that were supposed to >run at 11:22, and I fuond them still sitting there, waiting for 11:22, when >it was 11:37 ... and yes, the VAX clock is correctly set. > I, too, have seen this a couple of times. I believe this is related to the bug that can cause the MX SMTP agents to do with a "bad block address" error. I've not had time to try to fix it yet. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Thu, 27 Oct 1994 13:23:40 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: dunnett@mala.bc.ca (Malcolm Dunnett) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Problem with Local agent creating mail files Message-ID: <1994Oct27.110023.5286@malasp.mala.bc.ca> Date: 27 Oct 94 11:00:23 -0700 To: MX-List@WKUVX1.WKU.EDU Had a problem with the LOCAL agent the other day ( MX V4.1, running on AXP V6.1 ). Every message it tried to deliver would fail with a "MAIL-E-OPENOUT, error opening !AS for output" error. The temp file would be retained in the MX_ROOT:[LOCAL] directory. I checked for obvious things like quota problems or full disk or index file, but found nothing unusual. Another LOCAL agent in the cluster (running on VMS V5.5-2) continued on with no problem (processing files in the same directories ). A RESET didn't seem to fix the problem, deleting the MX_LOCAL process and re-running the startup procedure ( to restart the LOCAL agent ) fixed the problem. Has anyone else had this happen? If I see this again I'll try turning on debug to see if I get any more information. -- ============================================================================= Malcolm Dunnett Malaspina University-College Email: dunnett@mala.bc.ca Computer Services Nanaimo, B.C. CANADA V9R 5S5 Tel: (604)755-8738 ================================================================================ Archive-Date: Fri, 28 Oct 1994 10:56:04 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 28 Oct 1994 10:56:04 CDT From: system@BEAVER.Bemidji.MSUS.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <009869DA.F843CE40.2@BEAVER.Bemidji.MSUS.edu> Subject: SMTP delivery agent not starting Experts and gurus. Here is the situation; some (not all) SMTP delivery agents aren't starting. 1. The log for the agent sez it started. 2. I get a message telling me the PID. 3. but when I MCP STAT, it isn't there. SH SYS doesn't show it either. MX is working fine otherwise. This only happens on two nodes in my cluster; the other two nodes work fine. I'm assuming I'm running out of some kinda quota, but I don't have any messages to guide me. What is the next step, please? //----------\|/------\\ Dave Miller. || /\ -X- || Professor, Computer Science. || / \ /|/\ || || / \ / \ || DMILLER@BEAVER.Bemidji.MSUS.EDU || / \ \ || || /________\____\ || 1500 Birchmont Dr. NE || || || || Bemidji State University \\------|| -------// Bemidji MN, 56601 ================================================================================ Archive-Date: Fri, 28 Oct 1994 11:13:59 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 28 Oct 1994 16:08:26 +0200 From: Leyrat@criuc.unicaen.fr Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@criuc.unicaen.fr CC: Leyrat@criuc.unicaen.fr Message-ID: <00986A06.9B28A560.11@caen1.unicaen.fr> Subject: MIME QP characters Hi, Responding an answer of Herve Gilibert on this list, Hunter wrote: > MX V4.0-1 will automatically decode MIME Quoted-Printable if the > headers say that's what it is. Application/VMS-RMS applies only to > binaries, not quoted-printable. Specifically, the following headers > must be present: > > Content-Transfer-Encoding: QUOTED-PRINTABLE > Content-Type: TEXT/PLAIN[...] > Hox can MX send MIME Quoted Printable messages ? Thanks. *********************************************************************** Jacques LEYRAT ! Tel: (33-)31-45-55-08 Centre de Ressources Informatiques (C.R.I.U.C) ! Universite de Caen ! Fax: (33-)31-44-58-54 14032 Caen Cedex ! FRANCE !e-mail: Leyrat@criuc.unicaen.fr *********************************************************************** ================================================================================ Archive-Date: Fri, 28 Oct 1994 11:51:06 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <9410281643.AA28906@us3rmc.pa.dec.com> Date: Fri, 28 Oct 94 09:43:48 PDT From: Scot Bishop-Walker - DEC PC Integration 28-Oct-1994 0945 Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: scot@vmpyr.enet.dec.com Subject: CRISIS! SMTP delivery errors on only one list... I'm getting SMTP delivery errors...but only on ONE of my distribution lists. If anyone can help, I'd appreciate it...I've got about 350 people who haven't gotten any mail for over a week now. Note that the digest is going out just fine, and all my otehr mailing lists and digests are going out fine. Thanks for any help. - Scot Bishop-Walker Digital Equipment Corporation Northern California PC Integration <----------------------------------------------------------------------------> Here's a sample of the error I'm getting: <----------------------------------------------------------------------------> From @@Pa.dec.com Fri Oct 28 01:36:44 1994 Message-Id: <9410280834.AA02553@inet-gw-2.pa.dec.com> Date: Fri, 28 Oct 1994 01:35:18 EDT From: SMTP delivery agent To: Subject: SMTP delivery error X-Report-Type: Nondelivery; boundary="> Error description:" Note: this message was generated automatically. An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: amedrano@EUCLID.UCSD.EDU Error-Code: 2 Error-Text: %MX-E-PROTOERR, protocol error? -Retry count exceeded -(Via relay.dec.com) Error-For: Chuck_A._Filanosky@FOURD.COM Error-Code: 2 Error-Text: %MX-E-PROTOERR, protocol error? -Retry count exceeded -(Via relay.dec.com) <...snip...> Error-For: hemken@UX1.CSO.UIUC.EDU Error-Code: 2 Error-Text: %MX-E-PROTOERR, protocol error? -Retry count exceeded -(Via relay.dec.com) Error-For: lmorse@MIGHTY.RIV.EDU Error-Code: 2 Error-Text: %MX-E-PROTOERR, protocol error? -Retry count exceeded -(Via relay.dec.com) -Transcript: -Rcvd: 220 inet-gw-2.pa.dec.com King James Sendmail 5.65/10Aug94 ready at Fri, 28 Oct 94 01:28:48 -0700 -Sent: HELO vmpyr.wro.dec.com -Rcvd: 250 Hello vmpyr.wro.dec.com, pleased to meet you -Sent: MAIL FROM: -Rcvd: 250 ... Sender ok -Sent: RCPT TO: -Rcvd: 250 ... Recipient ok -Sent: RCPT TO: -Rcvd: 250 ... Recipient ok -Sent: RCPT TO: -Rcvd: 250 ... Recipient ok <...snip...> -Sent: RCPT TO: -Rcvd: Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ X-ListName: "Models, Inc. discussion list" Warnings-To: <> Errors-To: owner-models-inc@vmpyr.wro.dec.com Sender: owner-models-inc@vmpyr.wro.dec.com Received: from inet-gw-1.pa.dec.com by vmpyr.wro.dec.com (MX V4.1 VAX) with SMTP; Tue, 25 Oct 1994 15:42:32 EDT Received: from ucsd.edu by inet-gw-1.pa.dec.com (5.65/10Aug94) id AA00562; Tue, 25 Oct 94 15:36:31 -0700 Received: from euclid by ucsd.edu; id PAA05062 sendmail 8.6.9/UCSD-2.2-sun via SMTP Tue, 25 Oct 1994 15:35:11 -0700 for Received: by euclid (4.1/UCSDPSEUDO.2) id AA10122 for models-inc@vmpyr.wro.dec.com; Tue, 25 Oct 94 15:35:10 PDT From: amedrano@euclid.ucsd.edu (Archie Medrano) Reply-To: amedrano@euclid.ucsd.edu (Archie Medrano) Message-ID: <9410252235.AA10122@euclid> Subject: TEST To: models-inc@vmpyr.wro.dec.com Date: Tue, 25 Oct 94 15:35:10 PDT <----------------------------------------------------------------------------> Here's my .CFG file: <----------------------------------------------------------------------------> MCP> sho all Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;44 MX version id is: MX V4.1 VAX System (privileged) users: "SCOT@VMPYR.WRO.DEC.COM" "SYSTEM@VMPYR.WRO.DEC.COM" Mailing lists: Name: MODELS-INC-DIGEST Owner: "AMEDRANO@EUCLID.UCSD.EDU" "SCOT@VMPYR.WRO.DEC.COM" "SYSTEM@VMPYR.WRO.DEC.COM" Reply-to: NOList, NOSender Add message: MODELS-INC-DIGEST_ADD.TXT Remove message: MODELS-INC-DIGEST_REMOVE.TXT Errors-to: AMEDRANO@EUCLID.UCSD.EDU Strip header: NOReceived, Other Private list: No Case sensitive: No Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RED,WORLD:ED) Name: MODELS-INC Owner: "amedrano@EUCLID.UCSD.EDU" "scot@VMPYR.WRO.DEC.COM" Reply-to: NOList, Sender Add message: MODELS-INC_ADD.TXT Remove message: MODELS-INC_REMOVE.TXT Description: Models Inc. discussion list Errors-to: amedrano@EUCLID.UCSD.EDU Strip header: NOReceived, Other Private list: No Case sensitive: No Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RED) Address-rewriting rules: Rewrite "<{u}@DIGEST.SITE>" => "<{u}@DIGEST.SITE>" Domain-to-path mappings: Domain="vmpyr.wro.dec.com", Path=Local Domain="[16.60.64.92]", Path=Local Domain="DIGEST.SITE", Path=Site, Route="DIGEST" Domain="vmpyr", Path=Local Domain="*.dec.com", Path=SMTP Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP, Route="relay.dec.com" Aliases: LocalName="Postmaster", Address="scot@vmpyr.wro.dec.com" LocalName="POSTMAST", Address="scot@vmpyr.wro.dec.com" LocalName="LISTSERV", Address="MXSERVER@VMPYR.WRO.DEC.COM" LocalName="LISTADMIN", Address="MXSERVER@VMPYR.WRO.DEC.COM" SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Number of DNS failure retries: 12 Accounting: disabled Default router: (none) LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. Multiple VMS Mail From: addresses allowed. Local delivery errors are not CC'ed to local Postmaster. Delivery to MultiNet MM disallowed. Top headers: FROM,IN_REPLY_TO,DATE Bottom headers: SUBJECT,REPLY_TO,RECEIVED ROUTER agent settings: Automatic percent-hack handling: enabled Sender header for outgoing VMS Mail messages: included if necessary JNET agent settings: Automatic percent-hack handling: enabled BSMTP replies: disabled Accounting: disable ================================================================================ Archive-Date: Fri, 28 Oct 1994 12:31:10 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 28 Oct 1994 12:31:00 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009869E8.3AFB6605.12@ALPHA.WKU.EDU> Subject: RE: MIME QP characters Leyrat@criuc.unicaen.fr writes: > >Hox can MX send MIME Quoted Printable messages ? It can't. Unless you want to hack up something using MX SITE. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Fri, 28 Oct 1994 19:04:55 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 28 Oct 1994 19:05:01 CDT From: system@BEAVER.Bemidji.MSUS.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00986A1F.46994540.7@BEAVER.Bemidji.MSUS.edu> Subject: Re: SMTP agents not starting. Earlier today I asked .... >Here is the situation; some (not all) SMTP delivery agents aren't starting. >1. The log for the agent sez it started. >2. I get a message telling me the PID. >3. but when I MCP STAT, it isn't there. SH SYS doesn't show it either. Greg Koenig responded with a personal note: > When this happens to me, I do an MCP SHUTDOWN/CLUSTER and verify that all > agents stop. Next, I start the agents on the nodes that SMTP dies on and > verify that the SMTP delivery agents stay running. (Note that they can't > really process much because I don't have any Local agents running anywhere > yet, but at least the SMTP agents are up and stable.) Finally, I start the > remaining agents throughout the cluster and verify that everything stays > running. > > I'm not sure why this works for me, but I'd be interested in hearing if this > helps you out at all. Or, alternatively, what you do to fix the problem > eventually. Well, I tried Greg's suggestion ... no luck. I even turned on diagnostics: $ DEF/SYS/EXE MX_SMTP_DEBUG TRUE but MX_SMTP_LOON.LOG (LOON is the name of the node) had only one line in it: 28-OCT-1994 18:38:14.77: MX SMTP (pid 202002E4) starting Anyone have any other suggestions? dave. ================================================================================ Archive-Date: Sun, 30 Oct 1994 04:21:36 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: SMTP agents not starting. Date: 29 Oct 1994 16:44:15 GMT Message-ID: <38tu4v$4eo@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <00986A1F.46994540.7@BEAVER.Bemidji.MSUS.edu>, system@BEAVER.Bemidji.MSUS.edu writes: =Earlier today I asked .... = =>Here is the situation; some (not all) SMTP delivery agents aren't starting. = =>1. The log for the agent sez it started. =>2. I get a message telling me the PID. =>3. but when I MCP STAT, it isn't there. SH SYS doesn't show it either. =but MX_SMTP_LOON.LOG (LOON is the name of the node) had only one line in it: = = 28-OCT-1994 18:38:14.77: MX SMTP (pid 202002E4) starting = =Anyone have any other suggestions? Next step: Enable process accounting (if you haven't already done so) and use the ACCOUNTING facility to find the final exit status of the MX SMTP process next time you try to start it. -------------------------------------------------------------------------------- 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. ================================================================================ Archive-Date: Sun, 30 Oct 1994 07:24:21 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sun, 30 Oct 1994 14:24:12 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986B8A.6042838C.9@uni-lj.si> Subject: Re: SMTP agents not starting. >In article <00986A1F.46994540.7@BEAVER.Bemidji.MSUS.edu>, system@BEAVER.Bemidji.MSUS.edu writes: >=Earlier today I asked .... >= >=>Here is the situation; some (not all) SMTP delivery agents aren't starting. >= >=>1. The log for the agent sez it started. >=>2. I get a message telling me the PID. >=>3. but when I MCP STAT, it isn't there. SH SYS doesn't show it either. > >=but MX_SMTP_LOON.LOG (LOON is the name of the node) had only one line in it: >= >= 28-OCT-1994 18:38:14.77: MX SMTP (pid 202002E4) starting >= >=Anyone have any other suggestions? > > Next step: Enable process accounting (if you haven't already done so) and use > the ACCOUNTING facility to find the final exit status of the MX SMTP process > next time you try to start it. Or just $ RUN MX_EXE:MX_SMTP from appropriate username and watch it die before your wery eyes. Before you run MX_SMTP you can even $ SET WATCH FILES/CLASS=MAJOR to see which files are looked up. Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 168 6439 61000 Ljubljana fax: +386 61 168 6358 Slovenia ================================================================================ Archive-Date: Sun, 30 Oct 1994 07:25:09 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sun, 30 Oct 1994 07:25:27 CST From: system@BEAVER.Bemidji.MSUS.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986B4F.E0B0EEE0.1@BEAVER.Bemidji.MSUS.edu> Subject: Re: SMTP agents not starting. Previously I asked if any could tell me why SMTP agents weren't starting on some satellite nodes. Carl suggested that I capture the situation with ACCOUNTING. Here is a brief summary of that message and the ACCOUNTING listing. ... snip snip ... > =but MX_SMTP_LOON.LOG (LOON is the name of the node) had only one line in it: > = > = 28-OCT-1994 18:38:14.77: MX SMTP (pid 202002E4) starting > = > =Anyone have any other suggestions? > > Next step: Enable process accounting (if you haven't already done so) and use > the ACCOUNTING facility to find the final exit status of the MX SMTP process > next time you try to start it. MX_SMTP Image Termination ------------------------- Username: SYSTEM UIC: [SYSTEM] Account: SYSTEM Finish time: 29-OCT-1994 17:35:42.89 Process ID: 402000A2 Start time: 29-OCT-1994 17:35:39.63 Owner ID: Elapsed time: 0 00:00:03.26 Terminal name: Processor time: 0 00:00:00.86 Remote node addr: Priority: 4 Remote node name: Privilege <31-00>: FFFFFFFF Remote ID: Privilege <63-32>: FFFFFFFF Remote full name: Queue entry: Final status code: 100001BC Queue name: Job name: Final status text: %SYSTEM-F-NOLOGNAM, no logical name match Page faults: 174 Direct IO: 6 Page fault reads: 17 Buffered IO: 14 Peak working set: 376 Volumes mounted: 0 Peak page file: 1265 Images executed: 0 Image name: BEAVER$DKA0:[MX.][EXE]MX_SMTP.EXE DETACHED Process Termination ---------------------------- Username: SYSTEM UIC: [SYSTEM] Account: SYSTEM Finish time: 29-OCT-1994 17:35:43.44 Process ID: 402000A2 Start time: 29-OCT-1994 17:35:38.71 Owner ID: Elapsed time: 0 00:00:04.73 Terminal name: Processor time: 0 00:00:01.43 Remote node addr: Priority: 4 Remote node name: Privilege <31-00>: FFFFFFFF Remote ID: Privilege <63-32>: FFFFFFFF Remote full name: Queue entry: Final status code: 100001BC Queue name: Job name: Final status text: %SYSTEM-F-NOLOGNAM, no logical name match Page faults: 249 Direct IO: 6 Page fault reads: 24 Buffered IO: 26 Peak working set: 376 Volumes mounted: 0 Peak page file: 2206 Images executed: 1 $ SHO LOG MX* (LNM$PROCESS_TABLE) (LNM$JOB_80654280) (LNM$GROUP_000001) (LNM$SYSTEM_TABLE) "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "BEAVER$DKA0:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DNSMTP_DIR" = "MX_ROOT:[DNSMTP]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "SYS$SYSDEVICE:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "BEAVER" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "BEAVER.Bemidji.MSUS.edu" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_SMTP_SERVER_THREADS" = "4" "MX_TZ_PREFIX" = "C" "MX_VMSMAIL_LOCALHOST" = "@BEAVER.Bemidji.MSUS.edu" $ SH LOG UCX* (LNM$PROCESS_TABLE) (LNM$JOB_80654280) (LNM$GROUP_000001) (LNM$SYSTEM_TABLE) "UCX$BIND_STATE" = "........" "UCX$CONFIGURATION" = "SYS$COMMON:[SYSEXE]UCX$CONFIGURATION.DAT;2" "UCX$DEVICE" = "BG0:" "UCX$EXAMPLES" = "SYS$COMMON:[SYSHLP.EXAMPLES.UCX]" "UCX$EXPORT" = "SYS$COMMON:[SYSEXE]UCX$EXPORT.DAT;1" "UCX$HOST" = "SYS$COMMON:[SYSEXE]UCX$HOST.DAT;1" "UCX$INET_HOST" = "LOON.Bemidji.MSUS.edu" "UCX$INET_HOSTADDR" = "199.17.178.6" "UCX$INTERNET_SERVICES" = "SYS$LOADABLE_IMAGES:UCX$INTERNET_SERVICES_V6.EXE" "UCX$NETWORK" = "SYS$COMMON:[SYSEXE]UCX$NETWORK.DAT;1" "UCX$PROXY" = "SYS$COMMON:[SYSEXE]UCX$PROXY.DAT;2" "UCX$ROUTE" = "SYS$COMMON:[SYSEXE]UCX$ROUTE.DAT;2" "UCX$SERVICE" = "SYS$COMMON:[SYSEXE]UCX$SERVICE.DAT;1" "UCX$TDF" = "-6" "UCX$TZ" = "CST6CDT5,M4.1.0,M10.5.0" ================================================================================ Archive-Date: Sun, 30 Oct 1994 07:49:02 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sun, 30 Oct 1994 07:49:04 CST From: system@BEAVER.Bemidji.MSUS.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986B53.2DA40040.4@BEAVER.Bemidji.MSUS.edu> Subject: Re: SMTP agents not starting. MX Sluths: I discovered my own problem, thanks to Carl's prompting. The executive summary is that UCX (I *love* that package!) forgot to define one logical, namely UCX$INET_DOMAIN This upsets the SMTP Agent. When DOMAIN is defined properly, everything works fine. FYI, the thread follows ... > In article <00986A1F.46994540.7@BEAVER.Bemidji.MSUS.edu>, system@BEAVER.Bemidji.MSUS.edu writes: > =Earlier today I asked .... > = > =>Here is the situation; some (not all) SMTP delivery agents aren't starting. > = > =>1. The log for the agent sez it started. > =>2. I get a message telling me the PID. > =>3. but when I MCP STAT, it isn't there. SH SYS doesn't show it either. > > =but MX_SMTP_LOON.LOG (LOON is the name of the node) had only one line in it: > = > = 28-OCT-1994 18:38:14.77: MX SMTP (pid 202002E4) starting > = > =Anyone have any other suggestions? > > Carl J Lydick suggested ... > > Next step: Enable process accounting (if you haven't already done so) and use > the ACCOUNTING facility to find the final exit status of the MX SMTP process > next time you try to start it. ================================================================================ Archive-Date: Mon, 31 Oct 1994 07:56:40 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 31 Oct 1994 13:56:35 GMT From: "Andy Harper, KCL Systems Manager" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wku.edu CC: udaa055@bay.cc.kcl.ac.uk Message-ID: <00986C4F.AF702C00.7@bay.cc.kcl.ac.uk> Subject: mx rewrite rules We use another mailer here that generates FROM lines in a peculiar way. For example: CBS%UK.AC.KCL.CC.BAY::UDAA055 (my address!) What I want to achieve is that REPLYing to this address results in: (a) MX being activated (b) The address being rewritten into the more usual format (user@site) The first stage is easy: define MAIL$PROTOCOL_CBS MX_MAILSHR The second stage however is not. I have tried various combinations of rewrite rules to deal with this and it appears that MX (or VMS MAIL?) cannot correctly deal with :: which are NOT inside quotes (I.E. exactly my above example) What ROUTER debugging shows me is that an address of the form: CBS%system::user is converted to: user@localsystem before the rewrite rules have even come into play. That is, everything from the beginning up to and including the :: is removed first, then the local system name is added. If the whole address is quoted: CBS%"system::user" then a rewrite rules of this form will match successfully: define rewrite - "<""{system}::{user}""@{localsystem}>" - "<{user}@{system}>" Since I can't modify the headers that my other mailer generates, in order to force inclusion of the quotes, I would appear to be stuck. I would be grateful if anyone has an explanation (or a solution!) as to why :: outside of quotes should be treated specially. Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Mon, 31 Oct 1994 08:43:48 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: kismet@trantor.cc.umb.edu (Ted Corning) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: SMTP Server exiting, status = 10248074 Date: 31 Oct 1994 14:20:32 GMT Message-ID: <392ufg$5oa@anchor.cc.umb.edu> To: MX-List@WKUVX1.WKU.EDU Hi, Over the weekend we had a problem with the SMTP Servers on our cluster exiting with status 10248074, which translates to %STR-F-STRTOOLON, string is too long (greater than 65535) I understand that the reason both servers died is that the remote host tried again once its connection timed out. I have seen this problem before, and posted about it. It was caused by the incoming message having an extremely large "To:" field (of several hundred addresses) I had thought that this problem was fixed in V4.0/V4.1. I have restarted my SMTP Servers, and have not been hit by the problem again. If it is still queued on the remote site, I will see it within a few hours. When that happens, I'll re-post with the SMTP Log. Until then, any information is appreciated. Ted -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Mon, 31 Oct 1994 08:45:46 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 31 Oct 1994 08:44:48 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00986C24.20F6FE20.4@uwwvax.uww.edu> Subject: smtp_server terminating I have coming mail that casuses smtp_server to die with the error message #10248074 String is too long (>65535) The same sender keeps reproducing the error pepsi@netcom.com How is this possible? Am, I mis-reading the situation? The process is dying every 5 to 10 minutes. What can be done? Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Mon, 31 Oct 1994 10:10:22 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 31 Oct 1994 15:58:15 GMT From: "John Hill, Cavendish Lab, Cambridge Univ. (01223-337243)" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986C60.AE701051.8@hep.phy.cam.ac.uk> Subject: RE: SMTP Server exiting, status = 10248074 > Over the weekend we had a problem with the SMTP Servers on our cluster > exiting with status 10248074, which translates to > %STR-F-STRTOOLON, string is too long (greater than 65535) > > I understand that the reason both servers died is that the remote host > tried again once its connection timed out. > > I have seen this problem before, and posted about it. It was caused by > the incoming message having an extremely large "To:" field (of several > hundred addresses) I had thought that this problem was fixed in V4.0/V4.1. > > I have restarted my SMTP Servers, and have not been hit by the problem > again. If it is still queued on the remote site, I will see it within a > few hours. When that happens, I'll re-post with the SMTP Log. > > Until then, any information is appreciated. > >Ted Strange, but we had exactly the same problem over the weekend - though this is the first time I'd seen it. We tracked the problem to a specific mail from netcom.com (I can give the user if necessary). In the end we had to ask our local mail hub to cancel the mail as every retry killed the STMP server processes. All has been OK since then. The recipient claims he wasn't expecting a mail from this source - is this a junk mailshot?? John Hill -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Mon, 31 Oct 1994 10:35:01 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 31 Oct 1994 10:34:42 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986C33.7AE761CC.9@ALPHA.WKU.EDU> Subject: RE: SMTP Server exiting, status = 10248074 kismet@trantor.cc.umb.edu (Ted Corning) writes: > >Hi, > > Over the weekend we had a problem with the SMTP Servers on our cluster > exiting with status 10248074, which translates to > %STR-F-STRTOOLON, string is too long (greater than 65535) > Me too! > I have seen this problem before, and posted about it. It was caused by > the incoming message having an extremely large "To:" field (of several > hundred addresses) I had thought that this problem was fixed in V4.0/V4.1. > Me too! > I have restarted my SMTP Servers, and have not been hit by the problem > again. If it is still queued on the remote site, I will see it within a > few hours. When that happens, I'll re-post with the SMTP Log. > That'd be good. Thanks. > Until then, any information is appreciated. > I'll look into that again for MX V4.2. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Mon, 31 Oct 1994 11:43:51 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 31 Oct 1994 17:12:29 GMT From: "Andy Harper, KCL Systems Manager" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: udaa055@bay.cc.kcl.ac.uk Message-ID: <00986C6B.0D582280.95@bay.cc.kcl.ac.uk> Subject: RE: SMTP Server exiting, status = 10248074 >> Over the weekend we had a problem with the SMTP Servers on our cluster >> exiting with status 10248074, which translates to >> %STR-F-STRTOOLON, string is too long (greater than 65535) Me too! Looks like a combination of SMTP_server bug plus a duff message to me. Andy Harper Kings College London ================================================================================ Archive-Date: Mon, 31 Oct 1994 13:40:44 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: wing@tgv.com ("Dan Wing") Subject: Re: smtp_server terminating Date: 31 Oct 1994 19:31:53 GMT Message-ID: <393gn9$6ka@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <00986C24.20F6FE20.4@uwwvax.uww.edu>, hunterl@uwwvax.uww.edu writes: #I have coming mail that casuses smtp_server to die with the error #message #10248074 String is too long (>65535) #The same sender keeps reproducing the error pepsi@netcom.com #How is this possible? Am, I mis-reading the situation? #The process is dying every 5 to 10 minutes. What can be done? It would appear to be related to this. -dan ----- Path: ames!haven.umd.edu!umd5.umd.edu!mojo.eng.umd.edu!bloom-beacon.mit.edu!satisfied.elf.com!news.mathworks.com!news.alpha.net!mvb.saic.com!info-pmdf From: Ned Freed Newsgroups: vmsnet.mail.pmdf Subject: Problems with "drug legalization" messages from netcom.com Message-ID: <01HIW412YJPI8Y53F5@SIGURD.INNOSOFT.COM> Date: Sun, 30 Oct 1994 14:26:43 +1300 Organization: Info-Pmdf<==>Vmsnet.Mail.Pmdf Gateway Lines: 96 Someone apparently saw fit to send a massive number of copies of a "drug legalization" message from netcom.com this weekend. Now, by itself this would not be anything other than annoying junk mail, but at least some of the copies of this message contain truly massive header lines -- the ones I've seen list over 4000 recipient addresses! This causes problems with PMDF for the following reasons: (1) PMDF has no intrinsic limit on header length -- it will try to process anything it can fit into memory. (2) PMDF applies rewriting to all known headers and thus has to parse their contents. (3) The parser is fast enough but not very efficient in its use of memory. (4) Even when things are reasonably efficient rewriting takes time, especially if you have complex rewriting rules. The net result is that SMTP server processes suck up a lot of memory, start page faulting like crazy and really slow your system down. You may even think PMDF is in an infinite loop. Not so. But for all intents and purposes it *is* in a loop if processing takes longer than the other side of the connection is willing to wait (usually five minutes or so). The other side disconnects before PMDF is finished and tries again a few minutes later. Meanwhile PMDF finishes processing (this is one of SMTP's little problems) the original message and then accepts a new connection. You end up with multiple copies of the message, all your SMTP server slots are jammed up, and so on. Successfully receiving the message doesn't help much either. I was able to successfully receive one of these messages in a little over 3 elapsed minutes (this on an unloaded 4000 model 90A with lots of memory). However, when I routed the thing on to Message Router it took 4 CPU minutes to reformat the header into Message Router formats, 6 CPU minutes for Message Router to accept the resulting message, heaven knows how long for it to wind through Message Router and MailWorks (I cooked and ate my dinner while waiting for it) and almost five CPU minutes for ALL-IN-1 mail to complete a SHOW HEADER command! And the amount of memory involved is equally scary -- we're talking 10,000 pages at a minimum here. In other words, receiving this message is fairly problematic. However, I've tried to put together a bunch of possible solutions sites can adopt if they so desire. They are the following: (1) Disable all incoming SMTP from netcom.com. (There are a lot of hosts involved so I'd recommend disabling 192.100.81.*.) This sort of disabling is a function of the TCP/IP package you happen to be using, not of PMDF itself. This will cause all the mail to pile up back at netcom.com, where it will be continually retried until it times out or someone gets rid of it manually. (2) Bounce all messages from netcom.com with a SEND_ACCESS mapping of the form: SEND_ACCESS *tcp_*|*@*netcom.com|*|* $NDisabled$ because$ of$ problem$ messages For those of you unfamiliar with PMDF mappings, they go in the file PMDF_TABLE:MAPPINGS. If you already have a mappings file these three lines (including the blank line between) can go at the end, separated from any existing mappings by at least one additional blank line. If you already have a SEND_ACCESS mapping you will have to add the new rule to your existing mapping. As always, if you have a compiled configuration you will have to recompile with PMDF CNBUILD and reinstall with INSTALL REPLACE PMDF_CONFIG_DATA. (3) Upgrade to the most recent (i.e. this afternoon's) PMDFSHR.EXE (available via anonomous FTP from innosoft.com in the directory [.PMDF_43_PATCHES.VAX] or [.PMDF_43_PATCHES.ALPHA]). Please follow the directions in the [.PMDF_43_PATCHES]AA_PMDFSHR_PATCHES.TXT file when installing this image. Once you have obtained and installed this new version, you can make use of the new "maxprocchars" channel keyword. When placed on your TCP/IP channel, this keyword will limit the size of header line PMDF will even bother to try to rewrite and otherwise process. For example, I now have the following in my PMDF.CNF file here: mtcp_local nox_env_to single_sys smtp maxprocchars 10000 MTCP-DAEMON Application to other channels is straightforward. Note that this does NOT block the message. However, it will be very slow to process by any channel that has to convert the contents of headers to other formats, e.g. mr_local, and it may be *very* slow to come up in some user agents. Finally, if receive any of these messages please send a copy of them to me. I'm trying to build up a list of specific originator addresses so the SEND_ACCESS mapping can be further refined. However, it looks like different copies originate from completely different mailboxes, so it isn't clear that this will be very successful. Ned ================================================================================ Archive-Date: Mon, 31 Oct 1994 14:26:27 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: laidlaw@draco.rutgers.edu Subject: MX smtp server dieing. Date: 31 Oct 1994 19:57:54 GMT Message-ID: <393i82$c69@newark-news.rutgers.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU My smtp server process keeps dieing. From vms accounting the final exit is: %STR-F-STRTOOLON, string is too long (greater then 65535) From the smtp_server_log.log file it looks like the to: address of one particular message is too big (>65535 bytes!). MX version is 4.1 Below is an excerpt from the smtp_server_log.log file: STM[4]: Send "220 draco.rutgers.edu MX V4.1 VAX SMTP server ready at Mon, 31 Oct 1994 13:40:28 EST" STM[4]: Receive "HELO netcom7.netcom.com" STM[4]: Send "250 Hello, netcom7.netcom.com" STM[4]: Receive "MAIL From:" STM[4]: Send "250 MAIL command accepted." STM[4]: Receive "RCPT To:" STM[4]: Send "250 Recipient okay (at least in form)" STM[4]: Receive "DATA" STM[4]: Send "354 Start mail input; end with ." STM[4]: Receive "Received: by netcom7.netcom.com (8.6.9/Netcom)" STM[4]: Receive " id MAA02493; Fri, 28 Oct 1994 12:13:49 -0700" STM[4]: Receive "Date: Fri, 28 Oct 1994 12:13:49 -0700" STM[4]: Receive "Message-Id: <199410281913.MAA02493@netcom7.netcom.com>" STM[4]: Receive "To: jokerman@netcom.com, jokir@netcom.com, jolanne@netcom.com," STM[4]: Receive " jolcott@netcom.com, joler@netcom.com, jolie@netcom.com," (and so on for ~1100 more lines! then the last line is:) STM[4]: Receive " macman@netcom.com, macnevin@netcom.com, macnexus@netcom.com," Does anyone have any suggestions on what to do, about this message that helpfully keeps getting resent because it wasn't delivered, and anything that can be done to keep mx from chokeing on such things in the future? Angus Laidlaw laidlaw@draco.rutger.edu ================================================================================ Archive-Date: Mon, 31 Oct 1994 14:34:31 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 31 Oct 1994 14:33:52 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00986C54.E49CB77C.97@ALPHA.WKU.EDU> Subject: RE: MX smtp server dieing. laidlaw@draco.rutgers.edu writes: > > My smtp server process keeps dieing. From vms accounting the >final exit is: %STR-F-STRTOOLON, string is too long (greater then 65535) >From the smtp_server_log.log file it looks like the to: address of >one particular message is too big (>65535 bytes!). MX version is 4.1 >Below is an excerpt from the smtp_server_log.log file: > One other note on this---the maximum size of a string supported by string descriptors is 65535, so this limitation would affect lots of other applications, not just MX. In any case, MX SMTP Server shouldn't actually die with that error---that's what I hope to address in V4.2. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Mon, 31 Oct 1994 23:59:14 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 01 Nov 1994 16:59:07 +1000 From: Powell HEUER Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: powell@syd.dwt.csiro.au Message-ID: <00986D32.59A1FB80.2@syd.dwt.CSIRO.AU> Subject: Bug in naming log files in MX_START.COM I'm running MX V4.1 VAX. I've recently noticed that the log files for MLF and SMTP_SERVER don't include the node name in the name, ie the log files are MX_DEVICE:[MX.SMTP]SMTP_SERVER.LOG and MX_DEVICE:[MX.MLF]MX_MLF.LOG without including the name of the node running the component. The log files for the other components I run (LOCAL, SMTP and ROUTER) do include the node name as expected. I've looked at MX_START.COM (in MX_ROOT:[EXE]). The problem seems to be that the code that creates the symbol FILEID which is appended to other strings to create each log file name seems to be inside a conditional block (starting soon after the label LOOP) that is only executed for components that can have multiple instances. If I'm right this would mean that the log file for FLQ_MGR (which I don't run) would also not include the node name. I must confess that I haven't modified the command file to trace its execution to confirm this. I really don't want to face the screams of my users if I get it wrong and stop MX working. MX works very well here and everyone is used to it working all the time! Would someone like to check and confirm: 1. Am I right that the log file name doesn't include the node name for these components (or did I don something wrong when I upgraded form V3.3) 2. The error is due to this part of MX_START.COM. Thanks to all involved for this great piece of software. Regards Powell Heuer --------------------------------------------------------------------- Powell Heuer E-Mail: P.Heuer@syd.dwt.csiro.au CSIRO Division of Wool Technology Phone : +61 2 809 9444 PO Box 7 Fax : +61 2 809 9476 Ryde NSW 2112 AUSTRALIA