Archive-Date: Thu, 11 Apr 2002 10:35:36 -0700 From: tfeck@frostburg.edu (Teresa Feck) Subject: No incoming mail Date: 11 Apr 2002 10:35:25 -0700 Message-ID: <421a11af.0204110935.481dca4c@posting.google.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com We are running MX V5.1-A, with OpenVMS 7.1 and TCP/IP Services for OpenVMS VAX Version V5.0. Mail is only incoming for 10 minutes after mx is restarted. When I show the mx processes all are running. A telnet to port 25 fails on this system. On all of the startup log files, it has this error message: %SET-W-NOTSET, error modifying R4C23I$DIA4: -CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device I set the debug flag on mx_smtp_debug and mx_smtp_server_debug. In the smtp_server_log files the following error occurs Send "220 fre.fsu.umd.edu (MX V5.1-A Vn4m) ESMTP server ready at Thu, 11 Apr 2002 12:17:26 -0400" 11-APR-2002 13:12:29.36 STM[3]: Error: status=022C Another log entry from the same file Send "250 2.5.0 Message received and queued." 11-APR-2002 12:14:46.57 STM[7]: Receive "QUIT" 11-APR-2002 12:14:46.58 STM[7]: Send "221 2.3.0 fre.fsu.umd.edu Service closing transmission channel" Send "220 fre.fsu.umd.edu (MX V5.1-A Vn4m) ESMTP server ready at Thu, 11 Apr 2002 12:41:02 -0400" 11-APR-2002 12:46:02.19 STM[7]: Error: status=022C Thanks in Advance for Any Help, Teresa Feck ================================================================================ Archive-Date: Thu, 11 Apr 2002 12:49:51 -0700 Message-ID: <4FA072E6B8B5D4119AE100508BAED50850879C@scmail> From: Joyce Cogar Reply-To: MX-List@MadGoat.com To: "'mx-list@madgoat.com'" Subject: smtp server log gets error 022c Date: Thu, 11 Apr 2002 15:48:41 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Hi, One of our remote sites starts mx and things run fine for about 10 minutes and then the smtp_server_log. files show the following 022c error at that point telnet site.domain 25 doesn't give ESMTP server line it gives %TELNET-E-CONNFAIL, Failed to connect to remote host -SYSTEM-F-TIMEOUT, device timeout when mx is first started you do see the ESMTP correctly on teleet site.domain 25 %TELNET-I-SESSION, Session 01, host site.domain, port 25 220 site.domain (MX V5.1-A Vn4m) ESMTP server ready at Thu, 11 Apr 2002 14:0 Here are lines from smtp_server_log Send "220 fre.fsu.umd.edu (MX V5.1-A Vn4m) ESMTP server ready at Thu, 11 Apr 2002 12:17:26 -0400" 11-APR-2002 13:12:29.36 STM[3]: Error: status=022C Another log entry from the same file Send "250 2.5.0 Message received and queued." 11-APR-2002 12:14:46.57 STM[7]: Receive "QUIT" 11-APR-2002 12:14:46.58 STM[7]: Send "221 2.3.0 fre.fsu.umd.edu Service closing transmission channel" Send "220 fre.fsu.umd.edu (MX V5.1-A Vn4m) ESMTP server ready at Thu, 11 Apr 2002 12:41:02 -0400" 11-APR-2002 12:46:02.19 STM[7]: Error: status=022C thanks in advance for your help Joyce Cogar Please note new phone numbers Joyce Cogar USM Service Center jcogar@usmsc.edu P.O. Box 530 Voice:301.809.3163 Bowie, Maryland 20718-0530 Fax: 301.809.3130 www.usmsc.edu ================================================================================ Archive-Date: Thu, 11 Apr 2002 13:58:18 -0700 Date: Thu, 11 Apr 2002 13:58:14 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: tfeck@frostburg.edu Message-ID: <00A0C4E9.6338B2ED.4@MadGoat.Com> Subject: RE: No incoming mail MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" >We are running MX V5.1-A, with OpenVMS 7.1 and TCP/IP Services for >OpenVMS VAX Version V5.0. Mail is only incoming for 10 minutes after >mx is restarted. When I show the mx processes all are running. A >telnet to port 25 fails on this system. On all of the startup log >files, it has this error message: > >%SET-W-NOTSET, error modifying R4C23I$DIA4: >-CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device This is probably just due to a SET TERMINAL command in the login command procedure that isn't checking to make sure that the running process is interactve and talking to a terminal. Are any of the MX processes dying after 10 minutes? Use MCP STATUS and make sure that the Router, SMTP, SMTP Server, and Local agents are still running. If one of them doesn't show up in the STATUS output, check its main output log file to see if it crashed. >I set the debug flag on mx_smtp_debug and mx_smtp_server_debug. In >the smtp_server_log files the following error occurs > >Send "220 fre.fsu.umd.edu (MX V5.1-A Vn4m) ESMTP server ready at Thu, >11 Apr 2002 12:17:26 -0400" >11-APR-2002 13:12:29.36 STM[3]: Error: status=022C > >Another log entry from the same file > > Send "250 2.5.0 Message received and queued." >11-APR-2002 12:14:46.57 STM[7]: Receive "QUIT" >11-APR-2002 12:14:46.58 STM[7]: Send "221 2.3.0 fre.fsu.umd.edu >Service closing transmission channel" > Send "220 fre.fsu.umd.edu (MX V5.1-A Vn4m) ESMTP server ready at Thu, >11 Apr 2002 12:41:02 -0400" >11-APR-2002 12:46:02.19 STM[7]: Error: status=022C Status 22C (hex) is a timeout error. This could be due to network connectivity issues. Are other network connections to your system working OK? -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Fri, 12 Apr 2002 06:17:09 -0700 Message-ID: <4FA072E6B8B5D4119AE100508BAED50850879E@scmail> From: Joyce Cogar Reply-To: MX-List@MadGoat.com To: "'MX-List@MadGoat.com'" Subject: RE: No incoming mail Date: Fri, 12 Apr 2002 09:15:57 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Hi, I am also working on this problem . In this situation is there a way to increase the timeout. all processes are still running here is a mcp status MCP> status PID Process name Status Agent type -------- --------------- ------------------ ----------- 00000957 MX Router Idle Router agent 00000958 MX Router#2 Idle Router agent 00000959 MX Router#3 Idle Router agent 0000095A MX Local Idle Local delivery agent 0000095B MX Local#2 Idle Local delivery agent 0000095C MX Local#3 Idle Local delivery agent 00000966 MX MLF Idle Mailing list/file server 0000095D MX SMTP Idle SMTP delivery agent 0000095E MX SMTP#2 Idle SMTP delivery agent 0000095F MX SMTP#3 Idle SMTP delivery agent 00000960 MX SMTP#4 Idle SMTP delivery agent 00000961 MX SMTP#5 Idle SMTP delivery agent 00000963 MX Site Agent Idle Site-specific delivery agent 00000964 MX Site Agent#2 Idle Site-specific delivery agent 00000962 MX SMTP Server Connected 8 SMTP server (over TCP/IP) 00000956 MX FLQ Manager Idle MX FLQ manager 00000965 MX LSV Intfc Idle Listserv interface agent the 022c code showed up in SMTP_SERVER_LOG.LOG_00000962_1 about 5 minutes after mx was started up then showed up in other SMTP_SERVER_LOG.LOG_00000962_*.logs other connectwork connections seem to be working thanks -----Original Message----- From: Matt Madison [mailto:madison@MadGoat.COM] Sent: Thursday, April 11, 2002 4:58 PM To: MX-List@MadGoat.com Cc: tfeck@frostburg.edu Subject: RE: No incoming mail >We are running MX V5.1-A, with OpenVMS 7.1 and TCP/IP Services for >OpenVMS VAX Version V5.0. Mail is only incoming for 10 minutes after >mx is restarted. When I show the mx processes all are running. A >telnet to port 25 fails on this system. On all of the startup log >files, it has this error message: > >%SET-W-NOTSET, error modifying R4C23I$DIA4: >-CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device This is probably just due to a SET TERMINAL command in the login command procedure that isn't checking to make sure that the running process is interactve and talking to a terminal. Are any of the MX processes dying after 10 minutes? Use MCP STATUS and make sure that the Router, SMTP, SMTP Server, and Local agents are still running. If one of them doesn't show up in the STATUS output, check its main output log file to see if it crashed. >I set the debug flag on mx_smtp_debug and mx_smtp_server_debug. In >the smtp_server_log files the following error occurs > >Send "220 fre.fsu.umd.edu (MX V5.1-A Vn4m) ESMTP server ready at Thu, >11 Apr 2002 12:17:26 -0400" >11-APR-2002 13:12:29.36 STM[3]: Error: status=022C > >Another log entry from the same file > > Send "250 2.5.0 Message received and queued." >11-APR-2002 12:14:46.57 STM[7]: Receive "QUIT" >11-APR-2002 12:14:46.58 STM[7]: Send "221 2.3.0 fre.fsu.umd.edu >Service closing transmission channel" > Send "220 fre.fsu.umd.edu (MX V5.1-A Vn4m) ESMTP server ready at Thu, >11 Apr 2002 12:41:02 -0400" >11-APR-2002 12:46:02.19 STM[7]: Error: status=022C Status 22C (hex) is a timeout error. This could be due to network connectivity issues. Are other network connections to your system working OK? -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Tue, 16 Apr 2002 00:32:56 -0700 Message-ID: <3CBBD3C3.68D5698D@SMTP.DeltaTel.RU> Date: Tue, 16 Apr 2002 11:33:23 +0400 From: "Ruslan R. Laishev" Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@madgoat.com Subject: SMTP auth against VMS SYSUAF and MX restricted Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Hello Matt, All, doing MX SMTP server checks VMS Right id during SMTP authentication when MX Restriction (MX mail authorization by MX_MAIL_ACCESS) is active? -- Cheers, +OpenVMS [Sys|Net] HardWorker .......................................+ Russia,Delta Telecom Inc, Cel: +7 (901) 971-3222 191119,St.Petersburg,Transportny per. 3 116-3222 +http://starlet.deltatel.ru ................. SysMan rides HailStorm +