Archive-Date: Mon, 7 Feb 2000 17:33:42 -0800 Message-ID: <200002080133.UAA00289@snow.cit.cornell.edu> To: mx-list@madgoat.com CC: noon@snow.cit.cornell.edu Subject: smtp servers not starting Date: Mon, 07 Feb 2000 20:33:35 -0500 From: William Noon Reply-To: MX-List@MadGoat.com I just installed mx v5.1-a and cannot get the smtp services running. I get the following in the logs: 7-FEB-2000 20:26:34.43: MX SMTP (pid 20224717) starting %LIB-E-KEYNOTFOU, key not found in tree %TRACE-E-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC 00034D37 00034D37 0008EBE3 0008EBE3 MX_SMTP INIT 238 0000011A 00004C18 AGENT AGENT_MAIN 281 00000289 00009B4D MX_SMTP MX_SMTP 162 00000134 00004AE8 %LIB-F-KEYNOTFOU, key not found in tree %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC AGENT AGENT_MAIN 282 00000298 00009B5C MX_SMTP MX_SMTP 162 00000134 00004AE8 SYSTEM job terminated at 7-FEB-2000 20:26:35.06 Accounting information: Buffered I/O count: 50 Peak working set size: 512 Direct I/O count: 10 Peak page file size: 4410 Page faults: 638 Mounted volumes: 0 Charged CPU time: 0 00:00:00.31 Elapsed time: 0 00:00:02.33 Seems that the programs aren't linked properly or a shared lib isn't installed. Any info or help? --Bill Noon Cornell University ================================================================================ Archive-Date: Mon, 7 Feb 2000 18:20:09 -0800 Sender: madison@MadGoat.Com Date: Mon, 7 Feb 2000 18:20:04 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: noon@snow.cit.cornell.edu Message-ID: <009E5520.6AF0AE58.2@MadGoat.Com> Subject: RE: smtp servers not starting >I just installed mx v5.1-a and cannot get the smtp services running. I get >the following in the logs: > > > 7-FEB-2000 20:26:34.43: MX SMTP (pid 20224717) starting >%LIB-E-KEYNOTFOU, key not found in tree >%TRACE-E-TRACEBACK, symbolic stack dump follows [...] >Seems that the programs aren't linked properly or a shared lib isn't >installed. > >Any info or help? Looks like a problem with the NETLIB shareables or the underlying libraries provided by your TCP/IP package. Which TCP/IP are you using? You should double-check to make sure that the logical name NETLIB_SHR points to the appropriate shareable library for your TCP/IP stack. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Thu, 10 Feb 2000 10:29:28 -0800 Message-ID: <013501bf73f0$73b2b4a0$c68387c0@ulm.edu> From: "Chance Eppinette" Reply-To: MX-List@MadGoat.com To: Subject: MX and Account Flags Date: Thu, 10 Feb 2000 11:58:35 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0132_01BF73BE.28F6B2E0" This is a multi-part message in MIME format. ------=_NextPart_000_0132_01BF73BE.28F6B2E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I have been noticing for sometime that DisMail flags on our OVMS system are being overridden by incoming messages delivered by MX. Accounts on the system that have been set with a flag of DisMail can = still receive email. This has created of course a somewhat large consumption = of space due to unread messages. We are running OpenVMS V7.2-1 & MX V5.1-X Is there any fix to this problem? I don't seem to recall any past = references to this list about such a problem. Thank you, Chance Eppinette ULM Technology Support Manager Computing Center 318-342-5021 fax: 318-342-5018 ------=_NextPart_000_0132_01BF73BE.28F6B2E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
I have been noticing for sometime that = DisMail=20 flags on our OVMS system
are being overridden by incoming = messages delivered=20 by MX.
Accounts on the system that have been = set with a=20 flag of DisMail can still
receive email.  This has created = of course a=20 somewhat large consumption of
space due to unread = messages.
We are running OpenVMS V7.2-1 & MX=20 V5.1-X
Is there any fix to this problem?  = I don't=20 seem to recall any past references
to this list about such a = problem.
 
Thank you,
 
Chance Eppinette
ULM Technology = Support=20 Manager
Computing Center
318-342-5021
fax:=20 318-342-5018
------=_NextPart_000_0132_01BF73BE.28F6B2E0-- ================================================================================ Archive-Date: Mon, 14 Feb 2000 07:55:31 -0800 Date: Mon, 14 Feb 2000 10:56:52 -1300 From: system@eagle.navsses.navy.mil Reply-To: MX-List@MadGoat.com To: MX-LIST@MADGOAT.COM Message-ID: <009E5A62.A9E2EDC0.116@eagle.navsses.navy.mil> Subject: PROBLEM with MX V5.1-A Subject: MX5.1-A messages getting stuck in INPROG state I recently upgraded to MX5.1-A from MX5.1-x. At the same time I upgraded my TCP/IP stack to TCPWARE V5.4-3 (with the current DRIVERS, FTP, and NAMED patches). I am seeing a problem where SOME messages get stuck in a state like this: 103 INPROG 10932 SMTP 108 INPROG 8030 SMTP 34 INPROG 864 SMTP SMTP 51 READY 864 (waiting until 14-FEB-2000 10:28:26.48) 148 INPROG 110 SMTP 67 INPROG 1149 SMTP 72 INPROG 869 SMTP Messages 103, 108, 138, 145, 148, 67, & 72 will not be delivered unless I do an explicit QUEUE READY on them. Any Ideas? Mike Jacobi NSWCCD-SSES 96341 Shore based networking ================================================================================ Archive-Date: Mon, 14 Feb 2000 18:16:00 -0800 Message-ID: <20000215021551.4984.qmail@wwcst088.netaddress.usa.net> Date: 14 Feb 00 20:15:51 CST From: Michael Angello Reply-To: MX-List@MadGoat.com To: Subject: Error installing MX V4.2 on Alpha MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello, I need to install MX V4.2 on an AlphaServer 800 system using OVMS = 7.2-1 also DEC AXPVMS TCPIP V5.0-10, and DEC AXPVMS DECNET_OSI V7.2-1,using the= most recent version of NETLIB from MadGoat web site. It has enough free disk space to installing the software, but there is an= installation error, which I show next with the most remarkable Installati= on items at the Log display: Component Selection 1. [*] Base MX software (REQUIRED) 2. [*] NETLIB network support 3. [*] SMTP interface support 4. [ ] Jnet interface support 5. [ ] SMTP-over-DECnet support 6. [*] Site-provided interface support 7. [*] Mailing List/File Server support 8. [*] LISTSERV interface support 9. [*] Documentation 10. [*] Example files and programs 11. [*] User-contributed files and programs * Enter the MX network node name: NODEX.XXX.XXX.XXX MX Cluster Name: NODE Network Host Name: NODE.ORGANIZATION.A.B * Number of ROUTER agent processes to run [1]: 3 * Number of LOCAL agent processes to run [1]: 4 * Number of SMTP agent processes to run [1]: 8 * Number of simultaneous incoming SMTP connections to accept [4]: 16 * Number of SITE agent processes to run [1]: TCP/IP Support Selection Select the NETLIB TCP/IP support you wish to install from the menu below. An asterisk appears next to the packages that have already been selected. You can remove a package from the list by selecting it again. You may enter more than one selection by separating your choices with commas. 1. [*] DEC TCP/IP Services 2. [ ] TGV MultiNet 3. [ ] PSC TCPware 4. [ ] TWG PathWay 5. Exit * Your choice [5]: Choosing the NETLIB Directory The NETLIB libraries can be placed in any directory, as long as that directory is accessible to all users who plan to use or develop NETLIB-based applications. * Where should the NETLIB libraries be placed [SYS$COMMON:[SYSLIB]]: = Now providing the SMTP support files and images. %VMSINSTAL-I-RESTORE, Restoring product save set E ... %CREATE-I-CREATED, DKA100:[MX.SMTP] created %MX-I-LINKING, Linking image MX_SMTP... %LINK-W-MULCLUOPT, cluster multiply defined in options file NODEX$DKA0:[SYS0.SYSUPD.MX042]MX_SMTP.ALPHA_OPT;2 %VMSINSTAL-E-INSFAIL, The installation of MX V4.2 has failed. Any suggestion about some ways to fix such installation error will be appreciated! Thanks in advance! Miguel Angel ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webm= ail.netscape.com. ================================================================================ Archive-Date: Tue, 15 Feb 2000 07:06:19 -0800 Sender: madison@MadGoat.Com Date: Tue, 15 Feb 2000 07:06:14 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009E5B0B.9C60FB08.2@MadGoat.Com> Subject: RE: MX and Account Flags >I have been noticing for sometime that DisMail flags on our OVMS system >are being overridden by incoming messages delivered by MX. >Accounts on the system that have been set with a flag of DisMail can still >receive email. This has created of course a somewhat large consumption of >space due to unread messages. >We are running OpenVMS V7.2-1 & MX V5.1-X >Is there any fix to this problem? I don't seem to recall any past references >to this list about such a problem. It shouldn't be happening. MX has honored the DISMAIL flag for several years now, and should still be doing so under V7.2-1. I just ran a couple of tests on my system here (an Alpha running V7.2-1 and MX V5.1-A), and both the SMTP server and the LOCAL agent correctly rejected delivery of messages to a DISMAIL'ed account. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Tue, 15 Feb 2000 07:08:28 -0800 Sender: madison@MadGoat.Com Date: Tue, 15 Feb 2000 07:08:23 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009E5B0B.E90F3154.22@MadGoat.Com> Subject: RE: PROBLEM with MX V5.1-A >I recently upgraded to MX5.1-A from MX5.1-x. At the same time I upgraded my >TCP/IP stack to TCPWARE V5.4-3 (with the current DRIVERS, FTP, and NAMED >patches). I am seeing a problem where SOME messages get stuck in a state like >this: > > 103 INPROG 10932 SMTP [...] >Messages 103, 108, 138, 145, 148, 67, & 72 will not be delivered unless I do an >explicit QUEUE READY on them. Any Ideas? Take a look in the SMTP server and Router log files... is either of those processes dying and restarting? If so, that could leave some dangling IN-PROGRESS messages behind. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Tue, 15 Feb 2000 07:15:31 -0800 Date: Tue, 15 Feb 2000 10:16:53 -0400 From: system@eagle.navsses.navy.mil Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: system@eagle.navsses.navy.mil Message-ID: <009E5B26.3E3218C0.111@eagle.navsses.navy.mil> Subject: RE: PROBLEM with MX V5.1-A >>I recently upgraded to MX5.1-A from MX5.1-x. At the same time I upgraded my >>TCP/IP stack to TCPWARE V5.4-3 (with the current DRIVERS, FTP, and NAMED >>patches). I am seeing a problem where SOME messages get stuck in a state like >>this: >> >> 103 INPROG 10932 SMTP >[...] >>Messages 103, 108, 138, 145, 148, 67, & 72 will not be delivered unless I do an >>explicit QUEUE READY on them. Any Ideas? > >Take a look in the SMTP server and Router log files... is either of those >processes dying and restarting? If so, that could leave some dangling >IN-PROGRESS messages behind. > >-Matt I have backed out both my recent MX and TCPWARE upgrades. I was seeing some SERVRE problems with TCPWARE V5.4-3 - along the lines of some of my nodes were unable to start an outbound connection at the TCP level. The SYNs were either not getting out or the SYN/ACKs were not getting back. Going back to TCPWARE V5.3-3 fixed that!!?!??? Mike Jacobi NSWCCD-SSES 96341 Shore Based Networking ================================================================================ Archive-Date: Sat, 19 Feb 2000 09:29:29 -0800 Message-ID: <3.0.6.32.20000219172908.007d49b0@pop3.colloquium.co.uk> Date: Sat, 19 Feb 2000 17:29:08 +0000 To: MX-List@MadGoat.com From: Colloquium Internet Technical Support Reply-To: MX-List@MadGoat.com Subject: Insufficient disk space MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hello; We are an ISP using a VAX cluster running MX V5.1 for our SMTP services. Recently, whenever anyone has tried to sent a message, they get the following SMTP error :- 452 4.3.4 Insufficient storage for any message right now. There is plenty of storage on all the drives in the cluster, but the error message keeps appearing. We have tried restarting MX and all the boxes in the cluster, but the error persists. Does anyone know why this error might be produced when in fact there is plenty of disk space available ? Thank you; Colloquium Internet Technical Support. ----------------------------------------------------------------------- Colloquium Internet Technical Support (World Wide Web : http://www.colloquium.co.uk Electronic Mail : support@colloquium.co.uk 101 Abercorn Street Colloquium Internet Paisley PA3 4AT Telephone : 0541 555 576 (in the United Kingdom) +44 (0) 141 889 8080 Facsimile : +44 (0) 141 849 0414 ----------------------------------------------------------------------- Colloquium Sales Department (World Wide Web : http://www.colloquium.co.uk Electronic Mail : sales@colloquium.co.uk 101 Abercorn Street Colloquium Internet Paisley PA3 4AT Telephone : +44 (0) 141 849 0849 Facsimile : +44 (0) 141 849 0414 ----------------------------------------------------------------------- Colloquium Internet Secure Online Transactions - Secure, Safe and Easy! https://ssl.colloquium.co.uk/ Why Not Signup Today!!! ----------------------------------------------------------------------- ================================================================================ Archive-Date: Sat, 19 Feb 2000 09:52:51 -0800 Subject: Re: PROBLEM with MX V5.1-A From: eplan@kapsch.net (Peter LANGSTOEGER) Reply-To: MX-List@MadGoat.com Message-ID: <38aed2c8$1@news.kapsch.co.at> Date: 19 Feb 2000 18:28:40 +0100 To: MX-List@LISTS.WKU.EDU In article <009E5A62.A9E2EDC0.116@eagle.navsses.navy.mil>, system@eagle.navsses.navy.mil writes: >Subject: MX5.1-A messages getting stuck in INPROG state > >I recently upgraded to MX5.1-A from MX5.1-x. At the same time I upgraded my >TCP/IP stack to TCPWARE V5.4-3 (with the current DRIVERS, FTP, and NAMED >patches). I am seeing a problem where SOME messages get stuck in a state like >this: >[snip] >Messages 103, 108, 138, 145, 148, 67, & 72 will not be delivered unless I do an >explicit QUEUE READY on them. Any Ideas? It's TCPware V5.4-3. At least at our site. I have (/had ?) the same problems after upgrading TCPware from V5.3-3 to V5.4-3 (weeks/months after upgrading to MX 5.1-A). So far I was unable to nail it down and the problem seems to not escalate but instead lower the frequency of occurence... Surprised ? Me too. It did not happen on my test system (which is of course not the main mail server)... -- Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services E-mail eplan@kapsch.net <<< KAPSCH AG Wagenseilgasse 1 PSImail PSI%(0232)281001141::EPLAN A-1121 VIENNA AUSTRIA "I'm not a pessimist, I'm a realist" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Sat, 19 Feb 2000 10:10:03 -0800 Subject: Re: Error installing MX V4.2 on Alpha From: eplan@kapsch.net (Peter LANGSTOEGER) Reply-To: MX-List@MadGoat.com Message-ID: <38aed51b$1@news.kapsch.co.at> Date: 19 Feb 2000 18:38:35 +0100 To: MX-List@LISTS.WKU.EDU In article <20000215021551.4984.qmail@wwcst088.netaddress.usa.net>, Michael Angello writes: >Hello, I need to install MX V4.2 on an AlphaServer 800 system using OVMS 7.2-1 >also DEC AXPVMS TCPIP V5.0-10, and DEC AXPVMS DECNET_OSI V7.2-1,using the most >recent version of NETLIB from MadGoat web site. >It has enough free disk space to installing the software, but there is an >installation error, which I show next with the most remarkable Installation >items at the Log display: > > Component Selection > > 1. [*] Base MX software (REQUIRED) > 2. [*] NETLIB network support > 3. [*] SMTP interface support Point 2 is a problem. The NETLIB packaged with MX V4.2 was current at the time, MX V4.2 was current. It is way old now and will NOT run with TCPIP V5. Get the current version at ftp://ftp.madgoat.com/madgoat/netlib022-g.zip So, after installing and configuring VMS, OSI and TCPIP, install NETLIB on its own. Then install MX V4.2, but WITHOUT NETLIB support. btw: Don't forget the V4.3 patch EXEs. Note: I haven't tried it and I can't comment if MX V4.2 will run on V7.2[-1] at all. I use MX V5.1-A on V7.1 (with UCX V4.2 ECO3 & TCPware V5.4-3). HIH -- Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services E-mail eplan@kapsch.net <<< KAPSCH AG Wagenseilgasse 1 PSImail PSI%(0232)281001141::EPLAN A-1121 VIENNA AUSTRIA "I'm not a pessimist, I'm a realist" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Sat, 19 Feb 2000 10:26:09 -0800 Subject: Re: Insufficient disk space From: eplan@kapsch.net (Peter LANGSTOEGER) Reply-To: MX-List@MadGoat.com Message-ID: <38aedfe8$1@news.kapsch.co.at> Date: 19 Feb 2000 19:24:40 +0100 To: MX-List@LISTS.WKU.EDU In article <3.0.6.32.20000219172908.007d49b0@pop3.colloquium.co.uk>, Colloquium Internet Technical Support writes: >We are an ISP using a VAX cluster running MX V5.1 for our SMTP services. >Recently, whenever anyone has tried to sent a message, they get the >following SMTP error :- > >452 4.3.4 Insufficient storage for any message right now. > >There is plenty of storage on all the drives in the cluster, but the error >message keeps appearing. We have tried restarting MX and all the boxes in >the cluster, but the error persists. Does anyone know why this error might >be produced when in fact there is plenty of disk space available ? Define "plenty" and you will get a hint ;-) Now this is becoming a FAQ entry... The limit of what part of the disk must be free to get a mail accepted is controlled by the logicals MX_FLQ_DISK_FREE_ABSOLUTE blocks MX_FLQ_DISK_FREE_RESERVED percentage They are (not really good) documented in the MX install guide. If both of them are not defined, the default is MX_FLQ_DISK_FREE_RESERVED = 10 which means that 10% of the disk must be free or the mails will be rejected. So, define (/sys/exe) MX_FLQ_DISK_FREE_ABSOLUTE 2000 and you can fill up the disk until only 2000 Blocks are free/available... -- Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services E-mail eplan@kapsch.net <<< KAPSCH AG Wagenseilgasse 1 PSImail PSI%(0232)281001141::EPLAN A-1121 VIENNA AUSTRIA "I'm not a pessimist, I'm a realist" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Mon, 21 Feb 2000 07:04:58 -0800 Date: Mon, 21 Feb 2000 10:06:22 -1300 From: system@eagle.navsses.navy.mil Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: system@eagle.navsses.navy.mil Message-ID: <009E5FDB.C4B29C80.112@eagle.navsses.navy.mil> Subject: Re: PROBLEM with MX V5.1-A I also have had some problems with TCPWARE 5.4-3. On some of my systems I could not generate an outbound TCP connection. Ping would work! HMMMmmmm.... mike jacobi