Archive-Date: Tue, 03 Mar 1992 02:57:12 EST Sender: Date: Tue, 03 Mar 1992 08:54:48 EST From: mxlist@zmboot.zdv.uni-tuebingen.de Reply-To: mxlist@zmboot.zdv.uni-tuebingen.de To: mx-list@vms.ecs.rpi.edu Message-ID: <00957058.7D1BE1E0.81@zmboot.zdv.uni-tuebingen.de> Subject: signoff SIGNOFF mx-list ================================================================================ Archive-Date: Tue, 03 Mar 1992 15:31:52 EST To: mx-list@vms.ecs.rpi.edu Date: Tue, 03 Mar 92 19:51:26 GMT From: lwhays@cancer.unm.edu (Larry 'Purple' Hays) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <00957079.8B575D40@cancer.unm.edu> Reply-To: lwhays@cancer.unm.edu (Larry 'Purple' Hays) Subject: MX on Heterogenous clusters I've installed MX version 3.0-A and as usual, I'm very happy with it. (VMS 5.4-3, UCX 1.3) I do have some configuration questions that I'm unsure about. We have a LAVC of two nodes, each of which I'd like to run MX on, but the cluster is not homogenous - each has tasks and users that the other doesn't, so we don't want to use cluster aliasing or any of the other cluster goodies. They shouldn't really even be clustered, but budget restrictions at this point leave us no choice. Since they are, in effect, separate nodes sharing a system disk, I'd like both to run the same copy on MX, but with separate configuration files. We had this working with MX version 2.X, through the use of the MX_CONFIG logical name, but the new package doesn't seem to want to use this logical name, and each node's configuration breaks the other node, understandably. It looks to me like what I need defined separately are the MCP configuration file and the logical names definition file, but I can't find anything in the documentation about what logicals I need to be using, or indeed anything about heterogeneous clusters in general except that they are supported. I have the sinking feeling I've missed something obvious - what am I overlooking? Larry ================================================================================ Archive-Date: Tue, 03 Mar 1992 20:48:37 EST To: mx-list@vms.ecs.rpi.edu Date: 3 Mar 92 10:11:50 PST From: goppelt@scfb.nwc.navy.mil (dave goppelt) Reply-To: goppelt@scfb.nwc.navy.mil (dave goppelt) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar3.101151.56@scfb.nwc.navy.mil> Subject: Invalid From: address The Configuration: {Remote} DECnet {Mail } Internet {Gateway} DECnet {Final } {Node }-----------{Node }--------------{Node }------------{Destination} {PERS::} {SCFE::} { } {Node } The "Mail Node" (SCFE::) is running MX V3.0A, VMS V5.4 and UCX V1.3A. The "Gateway Node" is running some unknown version of Ultrix. Both remote and final nodes are running VMS V5.4-n. The Problem: Mail sent by a user on the "Remote Node" (PERS::) to a person on the "Final Destination Node" (FDN) cannot be replied to by a person on the FDN. The mail message From: line looks like: From: GATEWY::"""pers::user""@scfe.nwc.navy.mil" which mail will choke on with the error message : %MAIL-E-USERSPEC, invalid user specification '"pers::user""@scfe.nwc.navy.mil"' when the user tries the REPLY command. The From: in the MX header (not the VMS MAIL From: line) is : From: "pers::user"@SCFE.NWC.NAVY.MIL I have the following relevant rewrite rules in effect : DEFINE REWRITE_RULE - "<{user}%{host}.decnet@scfe.nwc.navy.mil>" - "<""{host}::{user}""@scfe.nwc.navy.mil>" This allows people to address messages like : user%pers.decnet@scfe.nwc.navy.mil and the messages will be delivered. The Question (finally!): Is there a way to control the MX From: line to specify something on the order of : user%pers.decnet@scfe.nwc.navy.mil where applicable, so that a return address does not have the extra (or rather *any*) quotes? (Note that I only have control of MX and not the gateway or remote nodes. I'm hoping that I modify the MX configuration to get this to work...but then again, I'm a dreamer... :-) ) I have looked at the MX_VMSMAIL_FROM_FORMAT logical name, but this may not do what I want. Would trying to run DECnet_SMTP on the remote nodes (on my side of the Internet) help? Mail will be properly delivered to the FDN system (i.e., with a "%pers.decnet" address) using other mailers (Wollongong V5.2, Sun stations). I just want MX to do it as well... Any ideas or help is appreciated... thanks, dave ----- David S. Goppelt Internet: goppelt@scfe.nwc.navy.mil goppelt@scfb.nwc.navy.mil ================================================================================ Archive-Date: Wed, 04 Mar 1992 10:20:41 EST Sender: Date: Wed, 04 Mar 1992 09:18:55 CST From: hunterl@uwwvax.uww.edu Reply-To: hunterl@uwwvax.uww.edu To: mx-list@vms.ecs.rpi.edu Message-ID: <00957125.05D8A320.15410@uwwvax.uww.edu> Subject: Is list still active? I have beening to mail from MX-LIST for over a week. Is there a problem? Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Wed, 04 Mar 1992 17:55:28 EST To: mx-list@vms.ecs.rpi.edu Date: 4 Mar 92 17:24:29 EST From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar4.172429.2067@dayton.saic.com> References: <1992Mar3.101151.56@scfb.nwc.navy.mil> Subject: Re: Invalid From: address In article <1992Mar3.101151.56@scfb.nwc.navy.mil>, goppelt@scfb.nwc.navy.mil (dave goppelt) writes: > The Configuration: > > {Remote} DECnet {Mail } Internet {Gateway} DECnet {Final } > {Node }-----------{Node }--------------{Node }------------{Destination} > {PERS::} {SCFE::} { } {Node } > > The "Mail Node" (SCFE::) is running MX V3.0A, VMS V5.4 and UCX V1.3A. The > "Gateway Node" is running some unknown version of Ultrix. Both remote and > final nodes are running VMS V5.4-n. > > The Problem: > > Mail sent by a user on the "Remote Node" (PERS::) to a person on the "Final > Destination Node" (FDN) cannot be replied to by a person on the FDN. The mail > message From: line looks like: > > From: GATEWY::"""pers::user""@scfe.nwc.navy.mil" > Is there a way to control the MX From: line to specify something on the order > of : > > user%pers.decnet@scfe.nwc.navy.mil Yes, there is. I wrote a modified name_conversion program to take the ugly address and turn it into user%node.dnet. It is in the contrib directory on Matt's machine and also in the contrib saveset if you installed that portion of MX. > where applicable, so that a return address does not have the extra (or rather > *any*) quotes? (Note that I only have control of MX and not the gateway or > remote nodes. I'm hoping that I modify the MX configuration to get this to > work...but then again, I'm a dreamer... :-) ) I have looked at the > MX_VMSMAIL_FROM_FORMAT logical name, but this may not do what I want. Would > trying to run DECnet_SMTP on the remote nodes (on my side of the Internet) > help? Yes, DECnet_SMTP would help. You could then setup PERS as a fully qualified domain name. Mail from that node would have a return address as user@pers.nwc.navy.mil. This would be the best bet if you could install MX on the PERS node. E-mail me directly if you have problems with this. I have installed it and can give advice. -Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Thu, 05 Mar 1992 10:14:49 EST Sender: Date: Thu, 05 Mar 1992 09:12:13 CST From: "David Harrold, MSOE" Reply-To: "David Harrold, MSOE" To: mx-list@vms.ecs.rpi.edu CC: harrold@kirk.msoe.edu Message-ID: <009571ED.40BB6AE0.3587@kirk.msoe.edu> Subject: SYSTEM_QUEUE.FLQ_CTL File Corruption on VMS 5.4-3 I am having a problem with the SYSTEM_QUEUE.FLQ_CTL file getting corrupted by VMS convert/reclaim. According to the release notes for VMS, convert/reclaim is a known bug. I am running MX V3.0A with UCX V1.3A. About every two weeks or so, the queue file seems to be completely fried, causing MCP SHOW QUEUE to die a horrible death (stack and register dumps). I found the logical (FLQ_RECLAIM_WAIT) to set the time between reclaims, but I haven't set it. (Why this problem only occurs every 2 weeks, I don't know). My question is, How can I disable the reclaim completely???? ( At least until DEC fixes the bug in convert/reclaim). Thanks for your help, David Harrold ............................................................................... David Harrold harrold@kirk.msoe.edu Milwaukee School Of Engineering Phone: 414-277-7286 Academic Computing Services FAX: 414-277-7465 P.O. Box 644, 1025 N. Milwaukee St., Milwaukee, WI 53201-0644 "It's not a bug, it's a feature !" ............................................................................... ================================================================================ Archive-Date: Thu, 05 Mar 1992 17:15:04 EST Sender: Date: Thu, 05 Mar 1992 14:10:56 PST From: "John F. Sandhoff" Reply-To: sandhoff@csus.edu To: mx-list@vms.ecs.rpi.edu CC: syssand@CCVAX.CCS.CSUS.EDU Message-ID: <00957216.FBE7B0C0.30504@CCVAX.CCS.CSUS.EDU> Subject: re: Queue file corruption According to the release notes for VMS, convert/reclaim is a known bug. YOUCH! Is this a bug *only* in 5.4-3 or is it also in 5.5?!?? John F. Sandhoff, Network Support California State University, Sacramento sandhoff@csus.edu ================================================================================ Archive-Date: Fri, 06 Mar 1992 00:06:46 EST To: mx-list@vms.ecs.rpi.edu Date: Fri, 06 Mar 92 04:25:07 GMT From: lwhays@cancer.unm.edu (Larry 'Purple' Hays) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <00957253.A3644FC0@cancer.unm.edu> References: <00957079.8B575D40@cancer.unm.edu> Reply-To: lwhays@cancer.unm.edu (Larry 'Purple' Hays) Subject: Re: MX on Heterogenous clusters In article <00957079.8B575D40@cancer.unm.edu>, lwhays@cancer.unm.edu (Larry 'Purple' Hays) writes: > > [How does one run MX separately on each node in a cluster as though > each node were a standalone system without having multiple copies of > the software on the shared system disk?] > >I have the sinking feeling I've missed something obvious - what am I >overlooking? Configuration: MX030A, UCX 1.3, VMS 5.4-3 The suggestion I got in email was to define the MX_root logical name as a searchlist and keep things that differ like the logical names and configuration files separately and make sure each node finds only its own files. (I should've though of that). Ok, I modified mx_root:[exe]mx___startup.com as follows: [...] $ PRC = F$ENVIRONMENT ("PROCEDURE") $ DEV = F$PARSE (PRC,,, "DEVICE", "NO_CONCEAL") $ DIR = F$PARSE (PRC,,, "DIRECTORY", "NO_CONCEAL") - "][" - "EXE]" $ NODE = F$GETSYI("NODENAME") ! Added for non-homogeneous cluster LWH 3/5/92 $! $ DEFINE/NOLOG/SYSTEM/EXEC MX_ROOT 'DEV'['NODE'.MX.],'DEV''DIR'] - /TRANSLATION=CONCEALED ! Non-homogeneous cluster LWH 3/5/92 $! DEFINE/NOLOG/SYSTEM/EXEC MX_ROOT 'DEV''DIR']/TRANSLATION=CONCEALED ! Orig [...] Therefore, MX_ROOT becomes: "MX_ROOT" = "CANCER$DUB0:[CANCER.MX.]" (LNM$SYSTEM_TABLE) = "CANCER$DUB0:[MX.]" On node CANCER and: "MX_ROOT" = "CANCER$DUB0:[M44.MX.]" (LNM$SYSTEM_TABLE) = "CANCER$DUB0:[MX.]" On node M44. At this point I moved the configuration file and logical_names.dat file for cancer into the cancer searchtree. I shut down and restarted MX and it seemed to work fine. Not too awfully surprising, as cancer is the node I had running before. It still seems to be fine after all my fiddling... On to the other node (m44). After running MXCONFIG on node M44 and moving the configuration and logical names files into M44's private search tree, I tried to start MX and had problems. I even reinstalled the base, SMTP and NETLIB modules, restored my changes to MX___STARTUP.COM, re-ran MXCONFIG and tried again. No joy. The SMTP server process starts, but none of the others do. Here are the contents of the log files: CANCER$DUB0:[M44.MX.LOCAL]MX_LOCAL_M44.LOG;4 %RMS-F-FNF, file not found %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC MX_LOCAL MX_LOCAL 30 0000004C 0000124C CANCER$DUB0:[M44.MX.ROUTER]MX_ROUTER_M44.LOG;4 %RMS-F-FNF, file not found %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC MX_ROUTER MX_ROUTER 101 00000062 00001A62 CANCER$DUB0:[M44.MX.SMTP]MX_SMTP_M44.LOG;4 %RMS-F-FNF, file not found %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC MX_SMTP MX_SMTP 31 0000004C 00001AB0 CANCER$DUB0:[M44.MX.SMTP]SMTP_SERVER_M44.LOG;4 I've checked to make sure that both search lists have the same list of all files, and they do. I ftp'd the Source saveset and started poking around there, but I'm severely Bliss-impaired, so that didn't net me much. Anybody know what files MX_LOCAL wants on line 30, MX_ROUTER on line 101 and MX_SMTP on line 31? Is there a problem with my searchlist definition? Is this in fact the wrong approach to attempt? Thanks, Larry ================================================================================ Archive-Date: Fri, 06 Mar 1992 08:54:28 EST To: mx-list@vms.ecs.rpi.edu Date: Fri, 6 Mar 1992 13:52:12 GMT From: madison@mdmvs.ecs.rpi.edu (Matt Madison) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: References: <009571ED.40BB6AE0.3587@kirk.msoe.edu> Reply-To: madison@vms.ecs.rpi.edu Subject: Re: SYSTEM_QUEUE.FLQ_CTL File Corruption on VMS 5.4-3 In article <009571ED.40BB6AE0.3587@kirk.msoe.edu>, harrold@kirk.msoe.edu (David Harrold, MSOE) writes: > I am having a problem with the SYSTEM_QUEUE.FLQ_CTL file getting > corrupted by VMS convert/reclaim. According to the release notes > for VMS, convert/reclaim is a known bug. I am running MX V3.0A with > UCX V1.3A. I read the release notes, and neither of the cases quoted there apply to the MX queue control file.... the file does not have index compression enabled, nor does it have multiple indices. I thought we were safe -- and in fact, I've been running MX on VMS V5.4-3 on several systems here without incident. > About every two weeks or so, the queue file seems to be completely > fried, causing MCP SHOW QUEUE to die a horrible death (stack and > register dumps). I found the logical (FLQ_RECLAIM_WAIT) to set the > time between reclaims, but I haven't set it. (Why this problem only > occurs every 2 weeks, I don't know). > > My question is, How can I disable the reclaim completely???? ( At > least until DEC fixes the bug in convert/reclaim). You can't... at least not without patching the image. You could increase the length of time between reclaim passes - since the problem seems to occur after two weeks, that's 14 passes (using the default of one per day). You could set FLQ_RECLAIM_WAIT to "365 00:00:00", which should effectively prevent the Router from performing a reclaim. However, if you do this, you should periodically do a manual CONVERT on the queue control file to prevent MX performance from going down the tubes (which it will, over time). You must shut down all MX processes before doing this, then restart them all afterwards. -Matt -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Fri, 06 Mar 1992 16:41:54 EST Sender: Date: Fri, 06 Mar 1992 16:39:44 EST From: "Reuben D. Molloy" Reply-To: "Reuben D. Molloy" To: mx-list@vms.ecs.rpi.edu Message-ID: <009572F4.EF88E2C0.8520@auvax1.adelphi.edu> Subject: the NETLIB_DOMAIN logical Hi, I am running MX3.0A under VMS 5.4-3 on a 6420. I have been experiencing some strange behavior related to the NETLIB logical NETLIB_DOMAIN. All outgoing SMTP mail were first going through our domain nameserver, an Ultrix system. I wanted to prevent that from happening so I start doing some snooping. I noticed that I didn't have the logical NETLIB_DOMAIN defined. I then defined the logical as follows: DEFINE/SYSTEM NETLIB_DOMAIN "adelphi.edu,ADELPHI.EDU". To my surprise, email over SMTP no longer passed through ADX, the Ultrix machine. I then noticed that I had incorrectly, or so I thought, defined the logical. What I meant to do was: DEFINE/SYSTEM "adelphi.edu","ADELPHI.EDU". When I changed the logical, the mail again went through ADX. I thought it could be because of the redundancy in the domain name since VMS is not case sensitive. I then changed the logical to just "adelphi.edu". Mail still when through ADX. I changed the logical back to "adelphi.edu,ADELPHI.EDU" and got the results I wanted. Could anyone explain what is going on? Thanks in advanced. ================================================================================ Archive-Date: Sat, 07 Mar 1992 14:20:43 EST Date: Sat, 7 Mar 92 13:12:48 EST Message-ID: <009573A1314AC3C0.00002646@acad.wit.edu> From: "Richard Chonak" Reply-To: "Richard Chonak" Subject: problem setting up MX with UUCP To: mit-eddie!vms.ecs.rpi.edu!MX-List@EDDIE.MIT.EDU I'm trying to set up MX on my system for the first time, integrating V3.0A with DECUS uucp V1.3A. But the following error happens when I try to send myself a message: --- [MX.UUCP]MX_UUCP_LOG.LOG [time stamps abbreviated] 21.97 Processing queue entry number 24. 23.08 DELIVER: Delivering to "system@acad.wit.edu" 23.08 DELIVER_FILE: Command: MAIL/PROTOCOL=UUCP_MAILSHR MX_UUCP_0000034E.TMP;1 "system@acad.wit.edu" 24.03 DELIVER_FILE: Subprocess says: MAIL/PROTOCOL=UUCP_MAILSHR MX_UUCP_00000 34E.TMP;1 "system@acad.wit.edu" 24.03 DELIVER_FILE: Subprocess says: %MAIL-E-NOMSG, Message number 007E829A 24.05 DELIVER_FILE: Subprocess says: %STR-F-ILLSTRCLA, illegal string class 24.07 DELIVER_FILE: Subprocess says: %STR-F-ILLSTRCLA, illegal string class 24.26 DELIVER_FILE: Subprocess says: WRITE SYS$OUTPUT F$FAO("EXIT:!XL",F$INTE GER($STATUS)) 24.28 DELIVER_FILE: Subprocess says: EXIT:00248054 Can you good folks experienced in MX-&-UUCP give me a clue or two about what's happening? Any other advice (on the general subject) would be welcome. --Richard Chonak, sysmgr, Wentworth Institute, Boston system@acad.wit.edu ================================================================================ Archive-Date: Mon, 09 Mar 1992 11:37:01 EST Sender: Date: Mon, 09 Mar 1992 17:33:27 MET From: Eckart Meyer Reply-To: Eckart Meyer To: MX-LIST@VMS.ECS.RPI.EDU Message-ID: <00957557.EFEED8E0.2227@ifn.ing.tu-bs.de> Subject: MCP SHUTDOWN always for entire cluster? MX V3.0, VMS V5.5, CMU-TEK TCP/IP V6.5 When I use MCP SHUTDOWN SMTP_SERVER on one node in a cluster in which two nodes run SMTP_SERVER, the process is stopped on *both* nodes. It seems impossible to shut it down only on a specific node. I understand that MCP would shutdown all processes only if the qualifier /ALL is specified. Any comments? Eckart ----------------------------------------------------------------------------- Eckart Meyer Address: Schleinitzstr. 23 Inst. f. Nachrichtentechnik 3300 Braunschweig Technical University of Braunschweig Germany Phone: +49 531 391 2454 E-Mail: meyer@ifn.ing.tu-bs.de FAX: +49 531 391 5192 I7100501@DBSTU1.BITNET (not preferred) VMSmail: PSI%+26245050351130::MEYER (DATEX-P) ----------------------------------------------------------------------------- ================================================================================ Archive-Date: Mon, 09 Mar 1992 12:09:11 EST Sender: Date: Mon, 09 Mar 1992 12:08:03 EST From: Matt Madison Reply-To: madison@vms.ecs.rpi.edu To: meyer@ifn.ing.tu-bs.de CC: mx-list@vms.ecs.rpi.edu Message-ID: <0095752A.7A7A4F40.15651@mdmvs.ecs.rpi.edu> Subject: RE: MCP SHUTDOWN always for entire cluster? > When I use MCP SHUTDOWN SMTP_SERVER on one node in a cluster in > which two nodes run SMTP_SERVER, the process is stopped on > *both* nodes. It seems impossible to shut it down only on a > specific node. I understand that MCP would shutdown all > processes only if the qualifier /ALL is specified. > Any comments? This inconsistency in the behaviour of the SHUTDOWN command will be fixed in MX V3.1. -Matt -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Mon, 09 Mar 1992 12:43:46 EST To: mx-list@vms.ecs.rpi.edu Date: 9 Mar 92 14:14:12 GMT From: ferriby@perot.com Reply-To: ferriby@perot.com Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar9.091412.6687@perot.com> Subject: SMTP Accounting Trouble Has anyone experienced serious trouble using the SMTP accounting? No matter what I do (yes, I've checked file protections...) the SMTP acccounting data file does not get created. The local accounting file works fine, but the SMTP accounting file does not work at all at the moment. I'm using MX 3.0A with TGV Multinet 3.0. -- John Ferriby Perot Systems Corporation Telephone: +1-313-641-3660 4555 Corporate Drive Internet: ferriby@perot.com Troy, MI 48098-6353 UUCP: {uunet,decwrl,sun}!perot!ferriby ================================================================================ Archive-Date: Mon, 09 Mar 1992 14:24:02 EST Sender: Date: Mon, 09 Mar 1992 11:41:44 MST From: "Russ Wilton, Systems Manager" Reply-To: "Russ Wilton, Systems Manager" To: mx-list@vms.ecs.rpi.edu CC: wilton@hg.uleth.ca Message-ID: <00957526.CDF6D340.579@hg.uleth.ca> Subject: Local delivery problem - solution? Hi: About three weeks ago I sent a note describing a problem I was having with local delivery, where the mail would not be delivered and no non-delivery notice was sent to anyone. I recieved a grand total of ONE response, so I take it this is not a common problem. :-) Herve Gilibert in France suggested that the problem might be with the quotas of the MAILER account I am using. On checking my MAILER account UAF record, I found that all of the quotas and privileges mentioned in section 1.5 of the Installation manual as being important, had been set up properly. Some of the other quotas, however, were significantly lower than those shown in the example account. Specifically, BYTLM, ASTLM and ENQLM were quite a bit lower. I modified my MAILER UAF record to meet or exceed the quotas shown in the example, and I haven't had a recurrance of the problem. I hope it's gone permanently. :-) Perhaps a minor change to the Installation manual to strongly suggest that quotas on the MAILER account should meet or exceed those in the example, would be in order. Russ #===============================================================# # Russell D Wilton E Mail: WILTON@HG.ULeth.CA # # Systems and Comm Manager Voice: (403) 329-2525 # # Computing Services FAX: (403) 329-2022 # # University of Lethbridge # # 4401 University Drive Lethbridge, Alberta, CANADA T1K 3M4 # #===============================================================# ================================================================================ Archive-Date: Tue, 10 Mar 1992 10:12:47 EST Date: Tue, 10 Mar 1992 09:06:40 CST From: Mike Frohme Reply-To: Mike Frohme To: MX-List@vms.ecs.rpi.edu Message-ID: <009575DA.4EC45DE0.11272@bilbo.memst.edu> Subject: Problem: ACCVIO in SMTP, MX 2.3 -------------------------------------------------------------------------------- Michael K. Frohme Internet: frohme@bilbo.memst.edu Center for Earthquake Research & Information Bitnet: frohmemk@memstvx1 Memphis State University PhoneNet: 901/678-2007 "... I suppose we *could* network a few tricorders together..." - Geordi ================================================================================ Archive-Date: Tue, 10 Mar 1992 11:06:21 EST Date: Tue, 10 Mar 1992 10:00:47 CST From: Mike Frohme Reply-To: Mike Frohme To: mxlist@bilbo.memst.edu Message-ID: <009575E1.DDA72D60.11284@bilbo.memst.edu> Subject: Problem (again): ACCVIO MX_SMTP v2.3 Hi all, Well, the first one didn't go, so let's run this one again... I have a problem with the MX_SMTP process going away on occasion. The condition is reproducable, but (as far as I presently know) it only happens when someone sends mail to the INFO-VAX mailing list :-(. MX is running on the cluster (785 - logicals only, 2 VS3100's each running all processes). Eventually, the MX_SMTP process dies with an ACCVIO on both outgoing mail nodes. The MX_SMTP_LOG and MX_SMTP_BILBO debug log files are included below, as well as the MCP config output. Any ideas or suggestions would be appreciated. I'm planning to upgrade to 3.x later this month. Thanks in advance. Mike Frohme -------------------------------------------------------------------------------- Host BILBO, Vaxstation 3100, MX V2.3, UCX 1.3B, VMS 5.3-1 ROUTER and SMTP debug turned on From MX_SMTP_LOG.LOG 10-MAR-1992 08:38:48.83 Processing queue entry number 11265 on node BILBO 10-MAR-1992 08:38:49.76 Recipient: 10-MAR-1992 08:38:49.77 Identified next hop as KL.SRI.COM 10-MAR-1992 08:38:49.77 SMTP_SEND: looking up host name KL.SRI.COM 10-MAR-1992 08:39:02.56 SMTP_SEND: Attempting to start session with CRVAX.SRI.COM. 10-MAR-1992 08:39:02.88 SMTP_SEND: Connected 10-MAR-1992 08:39:04.29 SMTP_SEND: Rcvd: 220-VMS/SRI SMTP V1.2 Send Bugs/Gripes to Postmaster@CRVAX.SRI.COM -------------------------------------------------------------------------------- From MX_SMTP_BILBO.LOG %SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000002, PC=00054475, PSL=03C00004 %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC 00054475 00054475 0002C2E5 0002C2E5 SMTP_OUT GET_REPLY 650 00000089 00003AD8 SMTP_OUT SMTP_SEND 281 000002F5 00003395 PROCESS PROCESS 283 00000365 000025C8 MX_SMTP MX_SMTP 31 0000020D 00001C71 -------------------------------------------------------------------------------- Current configuration: ! Configuration file: MX_ROOT:[000000]MX_CONFIG.MXCFG;18 DEFINE SYSTEM_USERS - "frohme@BILBO.MEMST.EDU",- "brewer@BILBO.MEMST.EDU" DEFINE REWRITE_RULE - "<@{route}:{user}@{host}.UUCP>" - "<@{route}:{user}@{host}.UUCP>" DEFINE REWRITE_RULE - "<{user}@{host}.UUCP>" - "<@uunet.uu.net:{user}@{host}>" DEFINE REWRITE_RULE - "<@{route}:{user}@{host}.CSNET>" - "<@{route}:{user}@{host}.CSNET>" DEFINE REWRITE_RULE - "<{user}@{host}.CSNET>" - "<@relay.cs.net:{user}@{host}.CSNET>" DEFINE REWRITE_RULE - "<@{route}:{user}@{host}.BITNET>" - "<@{route}:{user}@{host}.BITNET>" DEFINE REWRITE_RULE - "<{user}@{host}.BITNET>" - "<@cunyvm.cuny.edu:{user}@{host}.BITNET>" DEFINE REWRITE_RULE - "<{user}@{host}.TAIWAN>" - "<@cunyvm.cuny.edu:{user}@{host}.AS.TW>" DEFINE PATH "bilbo" Local DEFINE PATH "bilbo.memst.edu" Local DEFINE PATH "[141.225.56.13]" Local DEFINE PATH "frodo" Local DEFINE PATH "frodo.memst.edu" Local DEFINE PATH "[141.225.56.12]" Local DEFINE PATH "thorin" Local DEFINE PATH "thorin.memst.edu" Local DEFINE PATH "[141.225.56.11]" Local DEFINE PATH "*" SMTP DEFINE ALIAS "Postmaster" "frohme@bilbo.memst.edu" SET SMTP/ACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 /DNS_RETRIES=12 SET LOCAL/ACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96/HEADERS=(TOP=(- FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID,- RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT,- ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM,- RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER), BOTTOM=(- RECEIVED,RETURN_PATH)) SET ROUTER/PERCENT_HACK SET JNET/PERCENT_HACK/NOBSMTP_REPLY/NOACCOUNTING -------------------------------------------------------------------------------- Michael K. Frohme Internet: frohme@bilbo.memst.edu Center for Earthquake Research & Information Bitnet: frohmemk@memstvx1 Memphis State University PhoneNet: 901/678-2007 "... I suppose we *could* network a few tricorders together..." - Geordi ================================================================================ Archive-Date: Tue, 10 Mar 1992 12:53:10 EST To: mx-list@vms.ecs.rpi.edu Date: 10 Mar 92 17:25:41 GMT From: rbr4@uhura.cc.rochester.edu (Roland Roberts) Reply-To: rbr4@uhura.cc.rochester.edu (Roland Roberts) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar10.172541.10906@galileo.cc.rochester.edu> Subject: Rewrite rule to make jnet the default We're trying to find a way to make MX act as though .BITNET was appended onto any addresses that lack a domain, e.g., joe@sbnp --> joe@sbnp.bitnet karla@uordbv --> karla@uordbv.bitnet fred@uornsrl.bitnet --> fred@uornsrl.bitnet (unchanged) mike@ifa.hawaii.edu --> mike@ifa.hawaii.edu (unchanged) So far, the only thing we can come up with involves a rewrite for every host. Is there a better way? roland -- Roland Blaine Roberts University of Rochester roberts@uornsrl.bitnet Nuclear Structure Research Laboratory roberts@nsrl31.nsrl.rocester.edu 271 East River Road rbr4@uhura.cc.rochester.edu Rochester, NY 14627 (716) 275-8962 -- Fight `Look and Feel' copyrights and Software Patents. Join the League for Programming Freedom, info from league@prep.ai.mit.edu ================================================================================ Archive-Date: Tue, 10 Mar 1992 16:45:48 EST To: mx-list@vms.ecs.rpi.edu Date: 10 Mar 92 21:30:53 GMT From: frohme@bilbo.memst.edu Reply-To: frohme@bilbo.memst.edu Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar10.153053.1@bilbo.memst.edu> References: <009575E1.DDA72D60.11284@bilbo.memst.edu> Subject: Problem Solved: ACCVIO MX_SMTP v2.3 In article <009575E1.DDA72D60.11284@bilbo.memst.edu>, frohme@bilbo.memst.edu (Mike Frohme) writes: > > Hi all, > > I have a problem with the MX_SMTP process going away on occasion. > The condition is reproducable, but (as far as I presently know) it > only happens when someone sends mail to the INFO-VAX mailing list :-(. > MX is running on the cluster (785 - logicals only, 2 VS3100's each > running all processes). Eventually, the MX_SMTP process dies with > an ACCVIO on both outgoing mail nodes. The MX_SMTP_LOG and > MX_SMTP_BILBO debug log files are included below, as well as the > MCP config output. > Matt responded immediately that it was a bug in the NETLIB version I was running. Version 1.5 of NETLIB cleared up the problem right away after restarting MX. Thanks for a great product, Matt. 8-). Mike Frohme ================================================================================ Archive-Date: Tue, 10 Mar 1992 16:53:35 EST To: mx-list@vms.ecs.rpi.edu Date: 10 Mar 92 16:03:42 EST From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar10.160342.5943@dayton.saic.com> References: <1992Mar10.172541.10906@galileo.cc.rochester.edu> Subject: Re: Rewrite rule to make jnet the default In article <1992Mar10.172541.10906@galileo.cc.rochester.edu>, rbr4@uhura.cc.rochester.edu (Roland Roberts) writes: > > We're trying to find a way to make MX act as though .BITNET was > appended onto any addresses that lack a domain, e.g., > > joe@sbnp --> joe@sbnp.bitnet > karla@uordbv --> karla@uordbv.bitnet > fred@uornsrl.bitnet --> fred@uornsrl.bitnet (unchanged) > mike@ifa.hawaii.edu --> mike@ifa.hawaii.edu (unchanged) > > So far, the only thing we can come up with involves a rewrite for > every host. Is there a better way? If you have both BITNET and SMTP connections, you could pass everything with a period in the hostname to SMTP and everything else to JNET. DEFINE PATH "*.*" SMTP DEFINE PATH "*" JNET You could also define a rewrite as well but be careful how you use it. DEFINE REWRITE_RULE - "<{user}@{host}.{something}>" - "<{user}@{host}.{something}>" DEFINE REWRITE_RULE - "<{user}@{host}>" - "<{user}@{host}.bitnet>" The order IS IMPORTANT! This means that any address of the form user@host.domain would trip on the first rewrite rules and user@host would get the ".bitnet" appended to it. Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Tue, 10 Mar 1992 17:46:26 EST Sender: Date: Tue, 10 Mar 1992 13:34:19 PST From: "John F. Sandhoff" Reply-To: sandhoff@csus.edu To: rbr4@uhura.cc.rochester.edu CC: mx-list@vms.ecs.rpi.edu, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <009575FF.B1F32520.1915@CCVAX.CCS.CSUS.EDU> Subject: re: rewrite rule to make jnet the default > We're trying to find a way to make MX act as though .BITNET was > appended onto any addresses that lack a domain Digging thru the archives I found this solution that came from Carl J Lydick (and that Earle Ake whopped me aside the head when I said it wouldn't work): > DEFINE PATH *.BITNET Jnet > DEFINE PATH *.* SMTP > DEFINE PATH * Jnet This of course assumes that you're a BITnet node are are running JNET. It also assumes that you AREN'T using UUCP (or at least that you don't have a comflict with "I'm sending to foo@bar. Now should that be bar.bitnet or bar.uucp?"). My guess is that you're just trying to rewrite an address of "foo@bar" so that it is converted to a BITnet address but DELIVERED via SMTP. I haven't tried this (hey, all my users are smart enough to know when to append .BITnet :-). Uh huh, sure....). I HAVEN'T TRIED IT, but maybe the following would work?...: define rewrite define rewrite {user}@{host1}.{host2} => {user}@{host1}.{host2} define rewrite {user}@{host} => {user}@{host}.BITnet The idea here is one and only one rewrite rule applies. (at least, I *think* that's thr rule). So anything with a dot gets rewritten to match its original address. Anything left over couldn't have had a dot so append .BITnet As I say, I HAVEN'T TRIED THIS! My mailer is too active to risk it. I'm certain Matt will sadly shake his head ("why did I *ever* let people like John get ahold of my workmanship? What a KLUDGE!") but let us know if it works! John F. Sandhoff, Network Support California State University, Sacramento sandhoff@csus.edu ================================================================================ Archive-Date: Tue, 10 Mar 1992 17:46:47 EST Sender: Date: Tue, 10 Mar 1992 13:34:19 PST From: "John F. Sandhoff" Reply-To: sandhoff@csus.edu To: rbr4@uhura.cc.rochester.edu CC: mx-list@vms.ecs.rpi.edu, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <009575FF.B1F32520.1915@CCVAX.CCS.CSUS.EDU> Subject: re: rewrite rule to make jnet the default > We're trying to find a way to make MX act as though .BITNET was > appended onto any addresses that lack a domain Digging thru the archives I found this solution that came from Carl J Lydick (and that Earle Ake whopped me aside the head when I said it wouldn't work): > DEFINE PATH *.BITNET Jnet > DEFINE PATH *.* SMTP > DEFINE PATH * Jnet This of course assumes that you're a BITnet node are are running JNET. It also assumes that you AREN'T using UUCP (or at least that you don't have a comflict with "I'm sending to foo@bar. Now should that be bar.bitnet or bar.uucp?"). My guess is that you're just trying to rewrite an address of "foo@bar" so that it is converted to a BITnet address but DELIVERED via SMTP. I haven't tried this (hey, all my users are smart enough to know when to append .BITnet :-). Uh huh, sure....). I HAVEN'T TRIED IT, but maybe the following would work?...: define rewrite define rewrite {user}@{host1}.{host2} => {user}@{host1}.{host2} define rewrite {user}@{host} => {user}@{host}.BITnet The idea here is one and only one rewrite rule applies. (at least, I *think* that's thr rule). So anything with a dot gets rewritten to match its original address. Anything left over couldn't have had a dot so append .BITnet As I say, I HAVEN'T TRIED THIS! My mailer is too active to risk it. I'm certain Matt will sadly shake his head ("why did I *ever* let people like John get ahold of my workmanship? What a KLUDGE!") but let us know if it works! John F. Sandhoff, Network Support California State University, Sacramento sandhoff@csus.edu ================================================================================ Archive-Date: Tue, 10 Mar 1992 17:49:13 EST Sender: Date: Tue, 10 Mar 1992 13:34:19 PST From: "John F. Sandhoff" Reply-To: sandhoff@csus.edu To: rbr4@uhura.cc.rochester.edu CC: mx-list@vms.ecs.rpi.edu, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <009575FF.B1F32520.1915@CCVAX.CCS.CSUS.EDU> Subject: re: rewrite rule to make jnet the default > We're trying to find a way to make MX act as though .BITNET was > appended onto any addresses that lack a domain Digging thru the archives I found this solution that came from Carl J Lydick (and that Earle Ake whopped me aside the head when I said it wouldn't work): > DEFINE PATH *.BITNET Jnet > DEFINE PATH *.* SMTP > DEFINE PATH * Jnet This of course assumes that you're a BITnet node are are running JNET. It also assumes that you AREN'T using UUCP (or at least that you don't have a comflict with "I'm sending to foo@bar. Now should that be bar.bitnet or bar.uucp?"). My guess is that you're just trying to rewrite an address of "foo@bar" so that it is converted to a BITnet address but DELIVERED via SMTP. I haven't tried this (hey, all my users are smart enough to know when to append .BITnet :-). Uh huh, sure....). I HAVEN'T TRIED IT, but maybe the following would work?...: define rewrite define rewrite {user}@{host1}.{host2} => {user}@{host1}.{host2} define rewrite {user}@{host} => {user}@{host}.BITnet The idea here is one and only one rewrite rule applies. (at least, I *think* that's thr rule). So anything with a dot gets rewritten to match its original address. Anything left over couldn't have had a dot so append .BITnet As I say, I HAVEN'T TRIED THIS! My mailer is too active to risk it. I'm certain Matt will sadly shake his head ("why did I *ever* let people like John get ahold of my workmanship? What a KLUDGE!") but let us know if it works! John F. Sandhoff, Network Support California State University, Sacramento sandhoff@csus.edu ================================================================================ Archive-Date: Wed, 11 Mar 1992 11:54:27 EST To: mx-list@vms.ecs.rpi.edu Date: 11 Mar 92 16:03:56 GMT From: dmatthews@uap.umd.edu Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <11827@umd5.umd.edu> Reply-To: dmatthews@uap.umd.edu Subject: Undocumented BACK command For those who don't already know, there is an undocumented BACK command in MX (at least since 3.0). It's similar to the one in MAIL, it reads the previous posting, ie the one with number one less than you're reading when you say BACK. Works whether or not the previous one was marked as having been read. Maybe there are other undocumented features? Dr. David L. Matthews, IPST, Univ. of Maryland, College Park MD 20742-2431 Telephone (301)405-4830 Internet dmatthews@uap.umd.edu FAX (301)314-9363 NSI/SPAN UMDUAP::DMATTHEWS ================================================================================ Archive-Date: Wed, 11 Mar 1992 21:16:41 EST To: mx-list@vms.ecs.rpi.edu Date: Wed, 11 Mar 1992 22:41:20 GMT From: root@peponi.wcc.govt.nz (System PRIVILEGED Account) Reply-To: root@peponi.wcc.govt.nz (System PRIVILEGED Account) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar11.224120.29019@peponi.wcc.govt.nz> References: <009573A1314AC3C0.00002646@acad.wit.edu> Subject: Re: problem setting up MX with UUCP I would check the privileges of either the executing process, or the XX_MAILSHR.EXE. I had a similaar problem with the DELIVER (from PMDF) program and got STR-F- errors, I needed CMKRNL, or SYSPRV, I think. Roger ================================================================================ Archive-Date: Thu, 12 Mar 1992 10:56:06 EST Date: Thu, 12 Mar 1992 9:54:46 -0600 (CST) From: KIPPENHAN@fndcd.fnal.gov (H.A. Kippenhan Jr.) Reply-To: KIPPENHAN@fndcd.fnal.gov (H.A. Kippenhan Jr.) Message-ID: <920312095446.21600802@fndcd.fnal.gov> Subject: A problem with lost files (MAIL.TXT) To: mx-list@vms.ecs.rpi.edu Hello MX users: I've encountered a large number of lost files all having the name MAIL.TXT when doing an ANALYZE/DISK/REPAIR on my system disk. I'm certain the problem is not with the MX software, as other sites running the Joiner software here on site experience the problem as well; they don't run MX on those machines. Does anyone out there running the Joiner software experience this? Have you been able to isolate the cause? The system in question runs VMS 5.4-1 and Joiner version 3.5. Thanks in advance for your help. - Kipp - {~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~} { H.A. Kippenhan Jr. | Internet: Kippenhan@FNDCD.FNAL.GOV } { Fermi National Accelerator Lab. | HEPnet/NSI DECnet: FNDCD::KIPPENHAN } { P.O. Box 500 MS: WH-6W/234 | BITnet: Kippenhan@FNDCD.BITNET } { Batavia, Illinois 60510 | Telephone: (708) 840-8068 } {~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~} ================================================================================ Archive-Date: Thu, 12 Mar 1992 20:26:16 EST Date: Thu, 12 Mar 1992 20:10:57 -0500 Message-ID: <199203130110.AA28213@chillon.uicc.com> From: smith@amigo.uicc.com (Dana Smith) Reply-To: smith@amigo.uicc.com (Dana Smith) To: mx-list@vms.ecs.rpi.edu Subject: RE: A problem with lost files (MAIL.TXT) > Hello MX users: > I've encountered a large number of lost files all having the > name MAIL.TXT when doing an ANALYZE/DISK/REPAIR on my system > disk. I'm certain the problem is not with the MX software, > as other sites running the Joiner software here on site > experience the problem as well; they don't run MX on those > machines. I believe these files are generated as part of VMS MAIL and not related to MX or Joiner.... it is essentially a function of how MAIL generates the output file used to print mail messages... the system allocates the file without a file header, in the cases of the files found by ANALYZE /DISK/REPAIR (and placed into [SYSLOST]), these files somehow did not successfully make it to the printer, and were not automatically deleted via the /DEL switch when sent to the print queue. These files will hang around until you do the ANALYZE /DISK /REPAIR command which will pick up headerless files and place them in [SYSLOST] You will also be able to determine the source of each file by the fact that the original file ownership is retained. rgds ************************************************************************** * Mr. Dana S. Smith Telephone: 603/429-8625 * * CIS Manager Internet : SMITH@UICC.COM * * Unitrode Integrated Circuits * * 7 Continental Blvd. "May you live as long as you want, * * Merrimack, NH 03054-0399, USA and never want as long as you live"* ************************************************************************** > Does anyone out there running the Joiner software experience > this? Have you been able to isolate the cause? The system > in question runs VMS 5.4-1 and Joiner version 3.5. > > Thanks in advance for your help. > - Kipp - > {~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~} > { H.A. Kippenhan Jr. | Internet: Kippenhan@FNDCD.FNAL.GOV } > { Fermi National Accelerator Lab. | HEPnet/NSI DECnet: FNDCD::KIPPENHAN } > { P.O. Box 500 MS: WH-6W/234 | BITnet: Kippenhan@FNDCD.BITNET } > { Batavia, Illinois 60510 | Telephone: (708) 840-8068 } > {~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~} ================================================================================ Archive-Date: Thu, 12 Mar 1992 20:40:34 EST Sender: Date: Thu, 12 Mar 1992 17:38:17 PST From: Carl J Lydick Reply-To: Carl J Lydick To: smith@amigo.uicc.com CC: mx-list@vms.ecs.rpi.edu Message-ID: <009577B4.1C1EFFE0.24430@SOL1.GPS.CALTECH.EDU> Subject: RE: A problem with lost files (MAIL.TXT) >> Hello MX users: >> I've encountered a large number of lost files all having the >> name MAIL.TXT when doing an ANALYZE/DISK/REPAIR on my system >> disk. I'm certain the problem is not with the MX software, >> as other sites running the Joiner software here on site >> experience the problem as well; they don't run MX on those >> machines. >I believe these files are generated as part of VMS MAIL and not related to MX >or Joiner.... it is essentially a function of how MAIL generates the output >file used to print mail messages... the system allocates the file without >a file header, in the cases of the files found by ANALYZE /DISK/REPAIR (and >placed into [SYSLOST]), these files somehow did not successfully make it to the >printer, and were not automatically deleted via the /DEL switch when sent to >the print queue. These files will hang around until you do the ANALYZE /DISK >/REPAIR command which will pick up headerless files and place them in [SYSLOST] >You will also be able to determine the source of each file by the fact that the >original file ownership is retained. Afraid not. When you print a file from VMS MAIL, it's called MAIL.LIS, not MAIL.TXT. I don't know of ANYTHING that generates files called MAIL.TXT. ================================================================================ Archive-Date: Thu, 12 Mar 1992 23:11:37 EST To: mx-list@vms.ecs.rpi.edu Date: 12 Mar 92 22:07:14 EST From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar12.220714.5953@dayton.saic.com> References: <009577B4.1C1EFFE0.24430@SOL1.GPS.CALTECH.EDU> Subject: RE: A problem with lost files (MAIL.TXT) In article <009577B4.1C1EFFE0.24430@SOL1.GPS.CALTECH.EDU>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: >>> Hello MX users: > >>> I've encountered a large number of lost files all having the >>> name MAIL.TXT when doing an ANALYZE/DISK/REPAIR on my system >>> disk. I'm certain the problem is not with the MX software, >>> as other sites running the Joiner software here on site >>> experience the problem as well; they don't run MX on those >>> machines. > >>I believe these files are generated as part of VMS MAIL and not related to MX >>or Joiner.... it is essentially a function of how MAIL generates the output >>file used to print mail messages... the system allocates the file without >>a file header, in the cases of the files found by ANALYZE /DISK/REPAIR (and >>placed into [SYSLOST]), these files somehow did not successfully make it to the >>printer, and were not automatically deleted via the /DEL switch when sent to >>the print queue. These files will hang around until you do the ANALYZE /DISK >>/REPAIR command which will pick up headerless files and place them in [SYSLOST] >>You will also be able to determine the source of each file by the fact that the >>original file ownership is retained. > > Afraid not. When you print a file from VMS MAIL, it's called MAIL.LIS, not > MAIL.TXT. I don't know of ANYTHING that generates files called MAIL.TXT. What about temporary files that are created when you send a message via DECnet mail? If the link goes down during the send, I bet that's what the file is called that is left. -Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Fri, 13 Mar 1992 14:08:26 EST To: mx-list@vms.ecs.rpi.edu Date: 13 Mar 92 13:22:14 GMT From: dmatthews@uap.umd.edu Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <11859@umd5.umd.edu> References: <009577B4.1C1EFFE0.24430@SOL1.GPS.CALTECH.EDU>,<1992Mar12.220714.5953@dayton.saic.com> Reply-To: dmatthews@uap.umd.edu Subject: RE: A problem with lost files (MAIL.TXT) In article <1992Mar12.220714.5953@dayton.saic.com>, ake@dayton.saic.com (Earle Ake) writes: >In article <009577B4.1C1EFFE0.24430@SOL1.GPS.CALTECH.EDU>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: >>>> Hello MX users: >> >>>> I've encountered a large number of lost files all having the >>>> name MAIL.TXT when doing an ANALYZE/DISK/REPAIR on my system >>>> disk. I'm certain the problem is not with the MX software, ... rest of message and some responses deleted ... > > What about temporary files that are created when you send a message >via DECnet mail? If the link goes down during the send, I bet that's what >the file is called that is left. > > >-Earle I get about one MAIL.TXT a week on my lightly loaded MV II with UCX and MX, but if I'm not mistaken I've seen them for years, even when I was using CMUTEK and before MX was invented. This agrees with Earle's idea. Isn't there some VMS MAIL expert out there who can confirm or deny that MAIL.TXT is a local DECNET creation? Dr. David L. Matthews, IPST, Univ. of Maryland, College Park MD 20742-2431 Telephone (301)405-4830 Internet dmatthews@uap.umd.edu FAX (301)314-9363 NSI/SPAN UMDUAP::DMATTHEWS ================================================================================ Archive-Date: Fri, 13 Mar 1992 14:12:19 EST To: mx-list@vms.ecs.rpi.edu Date: 13 Mar 92 13:13:10 GMT From: dmatthews@uap.umd.edu Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <11858@umd5.umd.edu> References: <11827@umd5.umd.edu> Reply-To: dmatthews@uap.umd.edu Subject: Re: Undocumented BACK command In article <11827@umd5.umd.edu>, I write: >For those who don't already know, there is an undocumented BACK command in !! NEWSRDR, not >MX !! It's similar to the one in MAIL, it reads the >previous posting, ie the one with number one less than you're reading when >you say BACK. Works whether or not the previous one was marked as having >been read. > >Maybe there are other undocumented features? In NEWSRDR, that is. Thanks to Carl Lydick for pointing out the above mistake. This seems the best newsgroup to post this as NEWSRDR is seldom mentioned in the most likely groups: news.software.* Dr. David L. Matthews, IPST, Univ. of Maryland, College Park MD 20742-2431 Telephone (301)405-4830 Internet dmatthews@uap.umd.edu FAX (301)314-9363 NSI/SPAN UMDUAP::DMATTHEWS ================================================================================ Archive-Date: Fri, 13 Mar 1992 14:12:24 EST Sender: Date: Fri, 13 Mar 1992 10:16:07 EST From: Bob Marshall O/67-92 B/561 x65737 Reply-To: Bob Marshall O/67-92 B/561 x65737 To: mx-list@vms.ecs.rpi.edu Message-ID: <0095783F.81308080.7801@force.ssd.lmsc.lockheed.com> Subject: MAIL.TXT files >>>> Hello MX users: >>>> I've encountered a large number of lost files all having the >>>> name MAIL.TXT when doing an ANALYZE/DISK/REPAIR on my system >>>> disk. >>> >>>I believe these files are generated as part of VMS MAIL and not related to MX >>>or Joiner.... it is essentially a function of how MAIL generates the output >>>file used to print mail messages.... >> >> Afraid not. When you print a file from VMS MAIL, it's called MAIL.LIS, not >> MAIL.TXT. I don't know of ANYTHING that generates files called MAIL.TXT. > > What about temporary files that are created when you send a message >via DECnet mail? If the link goes down during the send, I bet that's what >the file is called that is left. Well, I don't have an answer either, but the temporary mail files have a name like MAIL__SEND.TMP, not MAIL.TXT. But I am 99% sure that the files have something to do with VMSMAIL, since the command SEARCH MAIL_SERVER.EXE "MAIL.TXT" locates that string in the image. Bob Marshall marshall@force.ssd.lmsc.lockheed.com ================================================================================ Archive-Date: Fri, 13 Mar 1992 14:12:27 EST Sender: Date: Fri, 13 Mar 1992 10:23:44 EST From: Bob Marshall O/67-92 B/561 x65737 Reply-To: Bob Marshall O/67-92 B/561 x65737 To: mx-list@vms.ecs.rpi.edu Message-ID: <00957840.9148DFC0.7803@force.ssd.lmsc.lockheed.com> Subject: MAIL.TXT mystery solved Found this article in DSN. It explains the mystery MAIL.TXT files : Bob Marshall marshall@force.ssd.lmsc.lockheed.com ---------------------------------------------------------------------------- No Free Disk Blocks - MAIL.TXT Files in [SYSLOST] After ANALYZE/DISK Last Technical Review: 5-FEB-1992 Size: 78 lines Copyright (c) Digital Equipment Corporation, 1991, All Rights Reserved. Unpublished Rights Reserved Under The Copyright Laws Of The United States. Any party granted access to this information pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement, use, copy, download, store, or transmit such information internally for the exclusive purpose of maintaining and operating the products covered by such agreement. No other use, copying, storage or transmission is permitted except with Digital's prior written consent. COMPONENT: MAIL Utility OP/SYS: VMS LAST TECHNICAL REVIEW: 05-FEB-1992 SOURCE: Customer Support Center/Colorado Springs USA VERSION INFORMATION: Symptoms Identified On: VMS, Versions 5.1, 5.1-1, 5.1-2. 5.2, 5.2-1, 5.3, 5.3-1, 5.3-2, 5.4, 5.4-1, 5.4-2, 5.4-3, 5.5 SYMPTOM: After issuing the ANALYZE/DISK_STRUCTURE/REPAIR command to recover lost disk space, the [SYSLOST] directory may contain over a thousand MAIL.TXT files. NOTE: The user is prompted to issue the ANALYZE command after noticing there is little or no free blocks on the system disk and/or receiving SYSTEM-F-DEVICEFULL or SYSTEM-F-HEADERFULL errors. ANALYSIS: The SYS$SYSTEM:MAIL_SERVER.EXE image creates temporary workfiles named MAIL.TXT to facilitate the transfer of information via MAIL over the network. Under some error conditions, MAIL.TXT files are not deleted when the transfer completes. Since these temporary files are not catalogued in a directory, their occurrence can go unnoticed for some period of time until the user notices that there is little disk space free and issues the ANALYZE/DISK_STRUCTURE/REPAIR command. NOTE: Systems using non-DEC protocols over their network such as NET, WOLLANGONG-TCP or PDMF, may be affected more by this problem. This behavior is not readily reproducible. WORKAROUND: When this conditions occurs, use the ANALYZE/DISK_STRUCTURE Utility to recover lost disk space. The following command should be used: ANALYZE/DISK_STRUCTURE/REPAIR device-name Any MAIL.TXT files on your system will be moved to the [SYSLOST] directory where they can be deleted. NOTE: If this is a common occurrence on your system, it may be advisable to perform the above procedure on a weekly basis. DIGITAL RESPONSE: VMS Engineering has acknowledged this problem and plans on addressing it in a future release. ================================================================================ Archive-Date: Fri, 13 Mar 1992 15:46:29 EST To: mx-list@vms.ecs.rpi.edu Date: 13 Mar 92 16:08:15 GMT From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar13.110816.5955@dayton.saic.com> References: <009577B4.1C1EFFE0.24430@SOL1.GPS.CALTECH.EDU>,<1992Mar12.220714.5953@dayton.saic.com>, <11859@umd5.umd.edu> Subject: RE: A problem with lost files (MAIL.TXT) In article <11859@umd5.umd.edu>, dmatthews@uap.umd.edu writes: > In article <1992Mar12.220714.5953@dayton.saic.com>, ake@dayton.saic.com (Earle Ake) writes: >>In article <009577B4.1C1EFFE0.24430@SOL1.GPS.CALTECH.EDU>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: >>>>> Hello MX users: >>> >>>>> I've encountered a large number of lost files all having the >>>>> name MAIL.TXT when doing an ANALYZE/DISK/REPAIR on my system >>>>> disk. I'm certain the problem is not with the MX software, > ... rest of message and some responses deleted ... >> >> What about temporary files that are created when you send a message >>via DECnet mail? If the link goes down during the send, I bet that's what >>the file is called that is left. >> >> >>-Earle > > I get about one MAIL.TXT a week on my lightly loaded MV II with UCX and MX, > but if I'm not mistaken I've seen them for years, even when I was using > CMUTEK and before MX was invented. This agrees with Earle's idea. Isn't > there some VMS MAIL expert out there who can confirm or deny that MAIL.TXT > is a local DECNET creation? Well I just looked in SYS$SYSTEM:MAIL_SERVER.EXE and there is a string "MAIL.TXT". Makes you say hmmm doesn't it? Earle ================================================================================ Archive-Date: Fri, 13 Mar 1992 16:19:56 EST Sender: Date: Fri, 13 Mar 1992 14:18:25 MST From: "Russ Wilton, Systems Manager" Reply-To: "Russ Wilton, Systems Manager" To: mx-list@vms.ecs.rpi.edu CC: wilton@hg.uleth.ca Message-ID: <00957861.5B407700.10656@hg.uleth.ca> Subject: Case of mailing list addresses Hi: Is it a bug or a feature that addresses in mailing lists are case sensitive? It seems to cause no end of trouble for people managing mailing lists and entering addresses manually. If the case as entered is different from what shows up as the return address on mail from the list member, then they are not considered to be members and can't get off the list by themselves. Since Email addresses are case INsensitive for the purposes of mail routing and delivery, why does the case matter here? There must be a good reason for it since it would be trivial to fix (I think :-). What am I missing? Russ. #===============================================================# # Russell D Wilton E Mail: WILTON@HG.ULeth.CA # # Systems and Comm Manager Voice: (403) 329-2525 # # Computing Services FAX: (403) 329-2022 # # University of Lethbridge # # 4401 University Drive Lethbridge, Alberta, CANADA T1K 3M4 # #===============================================================# ================================================================================ Archive-Date: Fri, 13 Mar 1992 16:30:13 EST Sender: Date: Fri, 13 Mar 1992 16:28:59 EST From: Matt Madison Reply-To: Matt Madison To: wilton@hg.uleth.ca CC: mx-list@vms.ecs.rpi.edu Message-ID: <00957873.97BCE940.16530@mdmvs.ecs.rpi.edu> Subject: RE: Case of mailing list addresses > Is it a bug or a feature that addresses in mailing lists are case sensitive? >It seems to cause no end of trouble for people managing mailing lists and >entering addresses manually. If the case as entered is different from what >shows up as the return address on mail from the list member, then they are >not considered to be members and can't get off the list by themselves. > Since Email addresses are case INsensitive for the purposes of mail >routing and delivery, why does the case matter here? There must be a good >reason for it since it would be trivial to fix (I think :-). What am I >missing? The username part of an address is supposed to be treated in a case-sensitive fashion, according to RFC 822. Some systems are case sensitive, so MLF treats addresses that way. Generally it is best, if you are manually adding addresses to mailing lists, to duplicate _exactly_ the address you are adding from the From: header (or the message that MLF sends you when someone tries to add themselves to a closed list). In MX V3.1 (which should be out early next week), there will be a new /NOCASE qualifier on the ADD command that MLF accepts. If you use it, then the address being added to the list will be treated entirely in a case-insensitive fashion. -Matt -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Fri, 13 Mar 1992 22:39:25 EST Sender: Date: Fri, 13 Mar 1992 22:34:22 EST From: Jonathan Kruger -- UNIX & VMS Systems Staff Reply-To: Jonathan Kruger -- UNIX & VMS Systems Staff To: mx-list@vms.ecs.rpi.edu Message-ID: <009578A6.A32B0EA0.8619@uc780.umd.edu> Subject: 2 questions about how MX fills in the "From:" field I think that both of my problems may have to do with the way MX is configured, at least that's what I'm hoping... Question 1: When I receive mail from user@node.bitnet the From: field appears as MX%"USER%NODE.BITNET@uc780.umd.edu" instead of MX%"USER@NODE.BITNET". We tried to change it before, but we couldn't make it work. Question 2: I receive mail from an Internet mailing list, and the messages appear with list-name@node.domain in the Return-Path: and Reply-To: fields and user@some.where.else in the From: field of the RFC 822. Can I configure MX so it will insert the address from the Reply-To: field in the VMS MAIL From: field instead of using the 822 From: field? Thanks for any help... Jonathan Kruger ================================================================================ Archive-Date: Sat, 14 Mar 1992 12:10:56 EST Sender: Date: Sat, 14 Mar 1992 09:08:28 PST From: Carl J Lydick Reply-To: Carl J Lydick To: dmatthews@uap.umd.edu CC: mx-list@vms.ecs.rpi.edu Message-ID: <009578FF.384928C0.24539@SOL1.GPS.CALTECH.EDU> Subject: RE: A problem with lost files (MAIL.TXT) >In article <1992Mar12.220714.5953@dayton.saic.com>, ake@dayton.saic.com (Earle Ake) writes: >>In article <009577B4.1C1EFFE0.24430@SOL1.GPS.CALTECH.EDU>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: >>>>> Hello MX users: >>> >>>>> I've encountered a large number of lost files all having the >>>>> name MAIL.TXT when doing an ANALYZE/DISK/REPAIR on my system >>>>> disk. I'm certain the problem is not with the MX software, >... rest of message and some responses deleted ... >> >> What about temporary files that are created when you send a message >>via DECnet mail? If the link goes down during the send, I bet that's what >>the file is called that is left. >> >> >>-Earle >I get about one MAIL.TXT a week on my lightly loaded MV II with UCX and MX, >but if I'm not mistaken I've seen them for years, even when I was using >CMUTEK and before MX was invented. This agrees with Earle's idea. Isn't >there some VMS MAIL expert out there who can confirm or deny that MAIL.TXT >is a local DECNET creation? MAIL.TXT is the temporary file created by MAIL_SERVER when it handles an incoming message via the MAIL-11 protocol over DECnet. It is NOT related to MX in any way. ================================================================================ Archive-Date: Mon, 16 Mar 1992 10:27:17 EST Sender: Date: Mon, 16 Mar 1992 16:27:34 gmt+1 From: pasztor@VELLA.SZTAKI.HU Reply-To: pasztor@VELLA.SZTAKI.HU To: MX-LIST@VMS.ECS.RPI.EDU Message-ID: <00957ACE.E4765660.21738@VELLA.SZTAKI.HU> Subject: Questions (MX_SITE, accents in message, mail and logicals) Hi MX-ers, May I ask you some questions: Q.1. I've an MX_SITE gateway to our home-grown national mailing system, named ELLA. I use both MX_SITE and MX_SITE_IN. The latter is necessary in order to put an ELLA "from address" in the message, so the addressee can reply to it. I do not find anything in the manual how to set the "Subject" line when sending a letter via MX_SITE_IN. I guess it is possible, but I can't find it out. Tried .../su="something" but it does not work. Q.2. Our language has some accented vowels. Unfurtunately there are several encodings for them (possibilities are DEC MCS, CWI and several kinds of escaping). When deliveriing mail via MX_SITE I have the message in hand, so I am able to convert accented characters. But what can I do in other cases ? Is there a way ? Q.3. This is not a question on MX, this is on VMS MAIL and logicals. When someone defines a logical like DEF PISTA some_kind_of_vms_mail_address and sends mail to that address, then VMS MAIL does not translate the logical in the To: field, so the addressee will see "PISTA" there. Is it possible to make VMS MAIL to translate this logical ?? Thanks in advance Pa'sztor Miklo's MTA SZTAKI/ASZI Budapest Victor H. u. 18-22 Hungary. Phone: (36)-(1)-149-75-32 (Hungarian Academy of Sciences, Institute for Computation and Automation) E-mail: pasztor@vella.sztaki.hu (Internet) h389pas@ella.hu (ELLA) ib006pas@huearn.bitnet (EARN) ================================================================================ Archive-Date: Mon, 16 Mar 1992 11:16:41 EST Message-ID: Date: 16 Mar 92 08:52:00 EST From: "OTTAWA::TILLMAN" Reply-To: "OTTAWA::TILLMAN" Subject: RE: MAIL.TXT mystery solved To: "mx-list" Bob Marshall (marshall@force.ssd.lmsc.lockheed.com) posted the full text of a copyrighted message. Some of us recognize the illegality of this and respect the rights of the copyright holders. I for one would appreciate a paraphrase of such information in the future. It would have been just as easy for Bob to have said he had found a DSNlink article that said those files are generated by Mail's network activity and that people who use mailers are more susceptible to their appearance without copying the article. ================================================================================ Archive-Date: Mon, 16 Mar 1992 20:56:07 EST To: mx-list@vms.ecs.rpi.edu Date: 17 Mar 92 13:45:49 +1200 From: brockie@med.wcc.govt.nz (Roger Brockie) Reply-To: brockie@med.wcc.govt.nz (Roger Brockie) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar17.134549.4599@med.wcc.govt.nz> Subject: Problem with SMTP mail I've got a small problem I hope someone can help me with. When sending mail via SMTP from an ultrix node to a vms node running MX 3.0a. I get the following. VMS node STM[1]: Send "220 kosmos.wcc.govt.nz MX V3.0A SMTP server ready at Tue, 17 Mar 1992 13:35:22 +1300" STM[1]: Receive "HELO golem.wcc.govt.nz" STM[1]: Send "250 Hello, golem.wcc.govt.nz" STM[1]: Receive "MAIL From:" STM[1]: Send "250 MAIL command accepted." STM[1]: Receive "RCPT To:" STM[1]: Send "501 Syntax error in address" STM[1]: Receive "QUIT" STM[1]: Send "221 kosmos.wcc.govt.nz Service closing transmission channel" STM[1]: Receive "QUIT" Reply on ultrix node. (Message inbox:3) Return-Path: MAILER-DAEMON@wcc.govt.nz Received: by golem.wcc.govt.nz id ; Tue, 17 Mar 92 13:35:30 +1300 Date: Tue, 17 Mar 92 13:35:30 +1300 From: Mail Delivery Subsystem Message-Id: <9203170035.AA09240@golem.wcc.govt.nz> To: root@peponi Subject: Returned mail: Remote protocol error ----- Transcript of session follows ----- While talking to kosmos.wcc.govt.nz: >>> RCPT To: <<< 501 Syntax error in address 554 ... Remote protocol error ----- Unsent message follows ----- Received: from peponi.wcc.govt.nz by golem.wcc.govt.nz id ; Tue, 17 Mar 92 13:35:30 +1300 Received: by peponi.wcc.govt.nz (5.57/Ultrix3.0-C) id AA11610; Tue, 17 Mar 92 13:35:03 +1200 Message-Id: <9203170135.AA11610@peponi.wcc.govt.nz> To: brockie@kosmos Subject: test Date: Tue, 17 Mar 92 13:35:02 +1200 From: root@peponi X-Mts: smtp sdjkhfgkyasdjf ------------------------------------------------------------------------------ This was only a test message. I'm trying to find out why our MX mailing lists are behaving differently after upgrading to V3.0. Does anyone know what the 'Syntax error in address; is. The account exists on the VMS node. A few stats. The VMS node is running VMS v5.4-3 UCX 1.3B (plus patches). Any help would be appreciated. --- Roger Brockie, System Manager Computer Services Section brockie@wcc.govt.nz Wellington City Council Telephone +64 4 801 3350 P.O.Box 2199, PSI 0530147000090::brockie Wellington, New Zealand ================================================================================ Archive-Date: Tue, 17 Mar 1992 11:38:10 EST To: mx-list@vms.ecs.rpi.edu Date: 17 Mar 92 11:31:40 EST From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar17.113140.5959@dayton.saic.com> References: <00957ACE.E4765660.21738@VELLA.SZTAKI.HU> Subject: Re: Questions (MX_SITE, accents in message, mail and logicals) In article <00957ACE.E4765660.21738@VELLA.SZTAKI.HU>, pasztor@VELLA.SZTAKI.HU writes: > Q.3. This is not a question on MX, this is on VMS MAIL and logicals. > When someone defines a logical like > > DEF PISTA some_kind_of_vms_mail_address > > and sends mail to that address, then VMS MAIL does not translate the > logical in the To: field, so the addressee will see "PISTA" there. > Is it possible to make VMS MAIL to translate this logical ?? I have seen this and don't know where it should be fixed. If I use a logical name and send from DCL, it works fine. If however I send a message through ANU-News, the "To:" address looks like logical-name@localhost. Is this an MX problem or ANU-News problem? Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Tue, 17 Mar 1992 13:41:25 EST From: edgecomb@ccrs.emr.ca (John Edgecombe) Reply-To: edgecomb@ccrs.emr.ca (John Edgecombe) Message-ID: <9203171836.AA10632@nova.ccrs.emr.ca> Subject: DECnet mail from remote node not delivered to list[-request] To: mx-list@vms.ecs.rpi.edu Date: Tue, 17 Mar 92 13:36:30 EST I am just trying to use MX for mailing list distribution, in an otherwise DECmail environment. Everything works nicely when requests to the list and request addresses come from the local cluster, BUT when I send mail to either the list or the request addresses from a remote DECnet site, the mail goes into a black hole, and does not make it to the list processor. I enclose a sample of the debug output from the router for a failing and a successful request. Both entry 224 (on node CLOUD) and entry 233 (on node ARTIST) were sent to the address with a body of "review". Normal results came back to the cloud request, but (as seen below) nothing got delivered to the MLF process from the artist request. Can anyone tell me what I'm doing wrong, as I find it hard to believe that this situation has not been faced by others before. --john John Edgecombe edgecombe@ccrs.emr.ca (preferred) Canada Centre for Remote Sensing edgecombe@ccrs.span.nasa.gov (delayed) Ottawa, Ontario, Canada "Whenever I hear of a program that has a known but unfixable bug, the chances are very large that it was written in C." -- Jerry Pournelle **** output from MCP>SHOW QUEUE/ALL/OUT=... **** Entry Status Size Source Agent Entry Status Size ----- ------ ------ ------ ------- ----- ------ ------ 220 FINISH 9 LOCAL 222 FINISH 868 LOCAL 224 FINISH 6 LOCAL 226 FINISH 236 LOCAL 228 FINISH 23 LOCAL 230 FINISH 23 LOCAL 232 FINISH 21 LOCAL <"artist::edgecombe"@cloud.ccrs.emr.ca> 233 FINISH 6 LOCAL <"artist::edgecombe"@cloud.ccrs.emr.ca> **** output from ROUTER debug log file **** 17-MAR-1992 12:46:16.75 %PROCESS, Processing entry number 233 17-MAR-1992 12:46:17.00 %PROCESS, Status from READ_INFO was 00000001 17-MAR-1992 12:46:17.00 %PROCESS, Message originated in VMS Mail. 17-MAR-1992 12:46:17.02 %PROCESS, will run domain expander on envelope addresses. 17-MAR-1992 12:46:17.02 %PROCESS, will run domain expander on message headers. 17-MAR-1992 12:46:18.46 %PROCESS, Finished VMSmail-origin preprocessing. 17-MAR-1992 12:46:18.46 %PROCESS, Marking this entry as finished. **** output from ROUTER debug log file **** 17-MAR-1992 12:42:36.60 %PROCESS, Processing entry number 224 17-MAR-1992 12:42:36.81 %PROCESS, Status from READ_INFO was 00000001 17-MAR-1992 12:42:36.81 %PROCESS, Message originated in VMS Mail. 17-MAR-1992 12:42:36.82 %PROCESS, will run domain expander on envelope addresses. 17-MAR-1992 12:42:36.83 %PROCESS, will run domain expander on message headers. 17-MAR-1992 12:42:37.82 %PROCESS, Finished VMSmail-origin preprocessing. 17-MAR-1992 12:42:37.82 %PROCESS, Recipient #0: 17-MAR-1992 12:42:37.83 %REWRITE, No rewrite rules matched 17-MAR-1992 12:42:37.84 %FINDPATH, Site-spec expand on cloud.ccrs.emr.ca err=00000870 17-MAR-1992 12:42:37.84 %FINDPATH, domain name CLOUD.CCRS.EMR.CA matched path pattern CLOUD.CCRS.EMR.CA 17-MAR-1992 12:42:37.84 %PROCESS, Rewrote as - next hop cloud.ccrs.emr.ca, path 1 17-MAR-1992 12:42:37.84 %FINDALIAS, no alias found for test-request 17-MAR-1992 12:42:37.84 %PROCESS, no alias found for test-request 17-MAR-1992 12:42:37.84 %PROCESS, this is an MList or File req 17-MAR-1992 12:42:37.89 %PROCESS, Adding to MLF path: test-request. 17-MAR-1992 12:42:38.33 %PROCESS, Path MLF gets 1 rcpts, entry number 225 **** in both cases, the message contents was REVIEW **** Similar (identical except final destination, the list itself) occurred on sending a message to the list itself. Got through OK from local node, did not even get to the MLF queue from a different DECnet node. Message 224 (from local) sent to mx%"test-request" Message 233 (from ARTIST::) sent to CLOUD::MX%"test-request" ================================================================================ Archive-Date: Tue, 17 Mar 1992 15:08:06 EST Sender: Date: Tue, 17 Mar 1992 14:59:56 EST From: Matt Madison Reply-To: madison@vms.ecs.rpi.edu To: mx-list@vms.ecs.rpi.edu, info-vax@sri.com, jnet-l@marist.bitnet Message-ID: <00957B8B.D0C304C0.16921@mdmvs.ecs.rpi.edu> Subject: Announcing MX V3.1 Message Exchange V3.1 Message Exchange (MX) is electronic mail distribution and routing software for VMS V5.0 or later. It supports Internet mail over TCP/IP using CMU-Tek, DEC VMS/ULTRIX Connection, TGV MultiNet, and Process Software Corporation's TCPware, as well as SMTP over DECnet and X.25; BITNET mail over Jnet; also interfaces with DECUS UUCP. MX uses VMS Mail for local message entry and delivery, and includes support for mailing lists and mail-based file servers. Support is included for interfacing MX with a custom mail transport and for providing custom address handling routines. V3.1 includes the following new features over previous releases: * SMTP over X.25 is now supported, using VAX P.S.I. * The Jnet interface no long requires a special account to run. * Mailing list processor supports NOCASE, CONCEAL, and NOREPRO flags for subscriber entries. * A NAME_CONVERSION module is included in the examples save set that handles address conversions for both DECnet and MRGATE users. * MX processes now log their startups and exits to log files, and will also log to an operator class, if desired. * New STATUS command added to MCP that lists all running MX processes. * Several other minor improvements and bug fixes. MX V3.1, including installation kit, docs, and sources, is available via anonymous FTP on vms.ecs.rpi.edu [128.113.5.15] and vms2.ecs.rpi.edu [128.113.5.14], in directory [ANONYMOUS.MX.MX031]. If you do not have FTP access, you can obtain MX by requesting it from Fileserv@vms.ecs.rpi.edu (FILESERV@RPIECSVX on BITNET). Send a mail message to that address containing the line SEND MX031.BLURB for further information. -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Tue, 17 Mar 1992 15:23:47 EST Sender: Date: Tue, 17 Mar 1992 15:23:35 EST From: Matt Madison Reply-To: madison@vms.ecs.rpi.edu To: mx-list@vms.ecs.rpi.edu Message-ID: <00957B8F.1F0133C0.16924@mdmvs.ecs.rpi.edu> Subject: DECUS Seminar S122, "Programming in BLISS: Learn to Read and Write BLISS" Hi, If you've ever looked at some of the source code to MX (or to VMS, for that matter), you might have wound up scratching your head wondering what kind of goofy language I (or the VMS development team) was using. Well, here's your chance to find out -- one of the seminars being given on the Saturday before the DECUS Symposium in Atlanta is all about that amazing, magical language caught in that twilight zone between MACRO and C: BLISS! Join me, Hunter Goatley (of vmsnet.internals and VAX Professional fame), and Ed Heinrich for an adventure in discovery! Come find out why you need all those damned dots! Learn the language that's TOPS in VMS systems programming! Ok, so this is a thoroughly shameless plug for my own seminar. Just thought I'd mention it to you all in case you missed it in the registration program (it's on page 68). Even if you won't be taking a seminar, watch the BoF listings at the Symposium for a session on MX. Hope to see you there! -Matt -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Tue, 17 Mar 1992 15:45:13 EST Sender: Date: Tue, 17 Mar 1992 12:43:33 EST From: Bob Marshall O/67-92 B/561 x65737 Reply-To: Bob Marshall O/67-92 B/561 x65737 To: mx-list@vms.ecs.rpi.edu Message-ID: <00957B78.C3335160.7875@force.ssd.lmsc.lockheed.com> Subject: Sorry, my mistake >Bob Marshall (marshall@force.ssd.lmsc.lockheed.com) posted the full text of a >copyrighted message. Some of us recognize the illegality of this and respect >the rights of the copyright holders. I for one would appreciate a paraphrase >of such information in the future. It would have been just as easy for Bob >to have said he had found a DSNlink article that said those files are generated >by Mail's network activity and that people who use mailers are more susceptible >to their appearance without copying the article. The above message was posted to the MX mailing list. I think it adequately chastises me in front of the entire world for my mistake, so all of the rest of you can lay off the personal assaults directed at me via E-mail. It was a stupid oversight on my part and it will not happen again. Bob Marshall ================================================================================ Archive-Date: Tue, 17 Mar 1992 22:32:35 EST To: mx-list@vms.ecs.rpi.edu Date: 17 Mar 92 19:07:07 EST From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar17.190707.4216@dmc.com> Subject: MX or UUCP addressing problem. Well, I'm not quite sure who own's this one, it's either MX or UUCP, so this item has been cross posted to both groups. Anyway, I've finally been successful in getting mail out of the ISVnet cluster at DEC. A major breakthrough, now if the gatewayed their notes files to news groups they would have a real hummer of a set up. I'ld never have to log in to find out what's going on (but that's another story). I wanted to see if I could get mail inbound as well and discovered the following: -------------------------------------------------------------------------------- Return-Path: <> Date: Tue, 17 Mar 1992 18:18:04 EST From: Local delivery agent To: Subject: UUCP delivery error Note: this message was generated automatically. The following error(s) occurred during local delivery of your message. Error delivering to user "<"nm%isvhub::dmunroe"@isvnet.enet.dec.com>": Message number 007E8064 Message follows. Received: by DMC.COM (MX V3.1) id 6517; Tue, 17 Mar 1992 18:17:57 EST Sender: Date: Tue, 17 Mar 1992 18:17:55 EST From: "FABRICATI DIEM, PVNC!" To: "nm%isvhub::dmunroe"@isvnet.enet.dec.com CC: munroe@DMC.COM Message-ID: <00957BA7.797BD040.6517@DMC.COM> Subject: RE: LMF Information Test message back to isvnet -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. USA FAX: (508) 562-1133 -------------------------------------------------------------------------------- Came back from UUCP. MX SEEMS to have done the right thing, but UUCP is choking on the address. Is this an MX problem or a UUCP problem? and what is the fix for it? Thanks for any pointers/help. Dick Munroe -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 ================================================================================ Archive-Date: Wed, 18 Mar 1992 00:07:31 EST To: mx-list@vms.ecs.rpi.edu Date: 17 Mar 92 18:48:39 GMT From: oursler@vax001.kenyon.edu Reply-To: oursler@vax001.kenyon.edu Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar17.134839.11@vax001.kenyon.edu> Subject: MX or BUST! Hullo, I'm looking for advice on switching to MX. Here's the story. I've been using MX 2.3-1 in a test environment for a while on one MicroVAX 3100 in a cluster. It's been ok. Now, I'd like to go ahead and use MX everywhere. I'm talking about 4-6 nodes in a cluster. I'd like mail to be able to be sent to any node in the cluster or just to the domain. But I'd like only one node to process the mail. I'd also like to have a backup node process the mail in case the first one is down. Plus all nodes in the cluster will not use the same TCP/IP package. A limitation I am stuck with. 2 nodes will use TGV Multinet and the rest will use DEC's UCX. Currently we use Wollongong's WIN/TCP on one node. We the the WIN/TCP SMTP mailer. I think it's awful. Anyway, folks are used to typing WINS% and I'd like to be able to switch over gradually. And it would be great if we didn't have to use a prefix or could pick our own. Is that enough of a wish list? ;-) I'd appreciate advice, hints, caveats. Anything that can make this go as smoothly as possible would be VASTLY appreciated. MX looks like a really great product and I've already had anxious folk drool at the thought of being able to have mailing lists. (WIN/TCP is so wimpy) Thanks in advance. - Miles - ------------------------------- Miles Oursler Manager of Networks and Systems Kenyon College oursler@vax001.kenyon.edu (614) 427-5696 ------------------------------- ================================================================================ Archive-Date: Wed, 18 Mar 1992 10:48:18 EST Date: Wed, 18 Mar 1992 10:44:18 EST From: nord@CHEMVAX.PRINCETON.EDU (Daniel R. Nordlund) Reply-To: nord@CHEMVAX.PRINCETON.EDU (Daniel R. Nordlund) To: mx-list@vms.ecs.rpi.edu Message-ID: <00957c31.45901540.24885@CHEMVAX.PRINCETON.EDU> Subject: VMS logical translation In article <00957ACE.E4765660.21738@VELLA.SZTAKI.HU>, pasztor@VELLA.SZTAKI.HU asks: > Q.3. This is not a question on MX, this is on VMS MAIL and logicals. > When someone defines a logical like > DEF PISTA some_kind_of_vms_mail_address > and sends mail to that address, then VMS MAIL does not translate the > logical in the To: field, so the addressee will see "PISTA" there. > Is it possible to make VMS MAIL to translate this logical ?? Here is a section from a VMS MX help file created when we first put up MX to aid users in the transition. Note 3. and 4. Dan Nordlund Princeton University Chemistry Department ------------------------------------------------------------------------------ 2 TRICKS There are a number of ways to make life easy with MX ---- The quotation marks are VERY important! ---- 1. Command files: Create a command file to mail a file automatically. This one asks for the subject and file name. $write sys$output "Sending FILE to nordlund@pucc.princeton.edu" $inquire first " SUBJECT " $inquire second " FILE " $mail/subj="''FIRST'" 'SECOND mx%"""nordlund@pucc.princeton.edu""" $exit 2. Another way to do this is with a symbol (ugly!): note: 6 "'s 6 "'s dan:== "mail filename mx%""""""nordlund@pucc.princeton.edu"""""" 3. The easiest way is to create an alias file and execute it from your LOGIN.COM file. For example, with the following alias defined, you could use dan on the MAIL> To: line or MAIL filename dan at the DCL prompt: $ define dan "mx%""nordlund@pucc.princeton.edu"" 4. With an alias defined as in 3, that alias can be used in a VMS mail distribution list (say, LIST.DIS) and the proper VMS translation will take place. ================================================================================ Archive-Date: Wed, 18 Mar 1992 12:02:50 EST Sender: Date: Wed, 18 Mar 1992 10:00:11 MST From: "Russ Wilton, Systems Manager" Reply-To: "Russ Wilton, Systems Manager" To: mx-list@vms.ecs.rpi.edu CC: wilton@hg.uleth.ca Message-ID: <00957C2B.1C3597C0.18642@hg.uleth.ca> Subject: Mailing list manager Hi: We are running MX 3.0 on a VAXcluster with VMS 5.4-3. We are starting to get into mailing lists in a big way and our User Services people would like to be able to manage them. I would be happy to let them, but I don't want to give them the privileges necessary to run MCP. I would really like to hear comments from other sites who are in a similar situation. How do you split the responsibility without giving the list manager a lot of extra privileges? I know Matt has added the MLF_CONFIG.COM file in recent versions of MX, and this helps, but it doesn't seem to be a full solution. Any comments greatly appreciated. :-) Russ. #===============================================================# # Russell D Wilton E Mail: WILTON@HG.ULeth.CA # # Systems and Comm Manager Voice: (403) 329-2525 # # Computing Services FAX: (403) 329-2022 # # University of Lethbridge # # 4401 University Drive Lethbridge, Alberta, CANADA T1K 3M4 # #===============================================================# ================================================================================ Archive-Date: Wed, 18 Mar 1992 12:21:54 EST Sender: goathunter%WKUVX1.BITNET@vms.ecs.rpi.edu Date: Wed, 18 Mar 1992 11:17:57 CST From: "Hunter Goatley, WKU" Reply-To: "Hunter Goatley, WKU" To: wilton@hg.uleth.ca CC: mx-list@vms.ecs.rpi.edu Message-ID: <00957C35.F891BFA0.21893@WKUVX1.BITNET> Subject: RE: Mailing list manager "Russ Wilton, Systems Manager" writes: > > We are running MX 3.0 on a VAXcluster with VMS 5.4-3. We are starting >to get into mailing lists in a big way and our User Services people would >like to be able to manage them. I would be happy to let them, but I don't >want to give them the privileges necessary to run MCP. I would really >like to hear comments from other sites who are in a similar situation. >How do you split the responsibility without giving the list manager a lot >of extra privileges? Well, I haven't actually been in this position yet because I run all of our lists. However: can't they do *everything* they need to do using the list-request address? They can REVIEW, ADD, and REMOVE using the "-request" form; once the list is set up, I can't think of any reason they'd need to run MCP.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET, 502-745-5251 ================================================================================ Archive-Date: Wed, 18 Mar 1992 18:13:04 EST To: mx-list@vms.ecs.rpi.edu Date: 18 Mar 92 22:51:15 GMT From: rbr4@uhura.cc.rochester.edu (Roland Roberts) Reply-To: rbr4@uhura.cc.rochester.edu (Roland Roberts) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar18.225115.4917@galileo.cc.rochester.edu> References: <00957ACE.E4765660.21738@VELLA.SZTAKI.HU>, <1992Mar17.113140.5959@dayton.saic.com> Subject: Re: Questions (MX_SITE, accents in message, mail and logicals) In article <1992Mar17.113140.5959@dayton.saic.com> ake@dayton.saic.com (Earle Ake) writes: > > In article <00957ACE.E4765660.21738@VELLA.SZTAKI.HU>, > pasztor@VELLA.SZTAKI.HU writes: > > > > .... When someone defines a logical like > > > > DEF PISTA some_kind_of_vms_mail_address > > > > and sends mail to that address, then VMS MAIL does not translate the > > logical in the To: field, so the addressee will see "PISTA" there.... > > > I have seen this and don't know where it should be fixed. If I > use a logical name and send from DCL, it works fine. If however > I send message through ANU-News, the "To:" address looks like > logical-name@localhost. Is this an MX problem or ANU-News problem? I'm rather confused about the first part---I have several logical names defined for use as mail addresses that work fine. It seems to be that MAIL is correctly translating address. For example: $ define joe mx%"""joe@host.domain""" lets me type `joe' at the `To:' prompt within mail. Is this how you are defining the logicals? We don't have ANU-News here, so I can't check that. roland -- Roland Blaine Roberts University of Rochester roberts@uornsrl.bitnet Nuclear Structure Research Laboratory roberts@nsrl31.nsrl.rocester.edu 271 East River Road rbr4@uhura.cc.rochester.edu Rochester, NY 14627 (716) 275-8962 -- Fight `Look and Feel' copyrights and Software Patents. Join the League for Programming Freedom, info from league@prep.ai.mit.edu ================================================================================ Archive-Date: Wed, 18 Mar 1992 18:39:52 EST Sender: Date: Wed, 18 Mar 1992 16:38:04 MST From: "Russ Wilton, Systems Manager" Reply-To: "Russ Wilton, Systems Manager" To: goathunter%WKUVX1.BITNET@vms.ecs.rpi.edu CC: mx-list@vms.ecs.rpi.edu, wilton@hg.uleth.ca Message-ID: <00957C62.B11A0740.19535@hg.uleth.ca> Subject: RE: Mailing list manager Hunter Goatley writes: >Well, I haven't actually been in this position yet because I run all of our >lists. However: can't they do *everything* they need to do using the >list-request address? They can REVIEW, ADD, and REMOVE using the >"-request" form; once the list is set up, I can't think of any reason >they'd need to run MCP.... Well no actually, they can't do everything they need. They want to be able to create and delete lists too. What I am interested in is any information from sites which have made an effort to separate the list management duties from the mail system management. Russ. #===============================================================# # Russell D Wilton E Mail: WILTON@HG.ULeth.CA # # Systems and Comm Manager Voice: (403) 329-2525 # # Computing Services FAX: (403) 329-2022 # # University of Lethbridge # # 4401 University Drive Lethbridge, Alberta, CANADA T1K 3M4 # #===============================================================# ================================================================================ Archive-Date: Wed, 18 Mar 1992 20:24:49 EST To: mx-list@vms.ecs.rpi.edu Date: 18 Mar 92 20:15:04 EST From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar18.201504.5963@dayton.saic.com> References: <00957ACE.E4765660.21738@VELLA.SZTAKI.HU>, <1992Mar17.113140.5959@dayton.saic.com>, <1992Mar18.225115.4917@galileo.cc.rochester.edu> Subject: Re: (incorrect To: line) In article <1992Mar18.225115.4917@galileo.cc.rochester.edu>, rbr4@uhura.cc.rochester.edu (Roland Roberts) writes: > In article <1992Mar17.113140.5959@dayton.saic.com> > ake@dayton.saic.com (Earle Ake) writes: > > > > In article <00957ACE.E4765660.21738@VELLA.SZTAKI.HU>, > > pasztor@VELLA.SZTAKI.HU writes: > > > > > > .... When someone defines a logical like > > > > > > DEF PISTA some_kind_of_vms_mail_address > > > > > > and sends mail to that address, then VMS MAIL does not translate the > > > logical in the To: field, so the addressee will see "PISTA" there.... > > > > > I have seen this and don't know where it should be fixed. If I > > use a logical name and send from DCL, it works fine. If however > > I send message through ANU-News, the "To:" address looks like > > logical-name@localhost. Is this an MX problem or ANU-News problem? > > I'm rather confused about the first part---I have several logical names > defined for use as mail addresses that work fine. It seems to be that > MAIL is correctly translating address. For example: > > $ define joe mx%"""joe@host.domain""" > > lets me type `joe' at the `To:' prompt within mail. Is this how you are > defining the logicals? We don't have ANU-News here, so I can't check that. I just tried a test program and the problem seems to be an interaction between callable mail and MX. I just sent Matt a test program so maybe he can figure out what is up. Earle ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Wed, 18 Mar 1992 22:32:16 EST To: mx-list@vms.ecs.rpi.edu Date: 18 Mar 92 13:28:33 EST From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar18.132834.4218@dmc.com> References: <1992Mar17.190707.4216@dmc.com> Subject: Managed to crash the router in MX 3.1 In article <1992Mar17.190707.4216@dmc.com>, munroe@dmc.com (Dick Munroe) writes: > To: "nm%isvhub::dmunroe"@isvnet.enet.dec.com > Came back from UUCP. MX SEEMS to have done the right thing, but UUCP is > choking on the address. Is this an MX problem or a UUCP problem? and what is > the fix for it? > I figure what is happening is that MX isn't expanding quotes properly when it feeds things into UUCP. I'm not quite sure what the syntax should be (I don't have RFC822 handy) so I can't tell what should really work. Not really related, but during my experimentation I fed mail a mail name constructed as a logical of the form: $ define foo "mx%""''nm%isvhub::dmunroe''""@isvnet.enet.dec.com""" which, interestingly enough crashed the router. Unfortunately the logs have been lost, but the problem IS reproducible. I'm still looking for a solution to the problem. Dick -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 ================================================================================ Archive-Date: Wed, 18 Mar 1992 23:53:30 EST Date: Wed, 18 Mar 1992 20:53:56 PST From: "W. Todd Wipke" Reply-To: "W. Todd Wipke" To: mx-list@vms.ecs.rpi.edu Message-ID: <00957C86.6FE30AA0.4320@SECS.UCSC.EDU> Subject: Re: who creates lists Our campus is running Athena which doesn't have anything as nice as MX but it has mail reflector lists and a list manager. Our campus has decided lists will get created by people making a request to mlists@cats.ucsc.edu. They can discuss what is needed and work out an answer between local usenet and mail reflector, private list or public etc. think that is needed owing to the power to blast msgs to large lists. Its important to have someone in control that understands all aspects, good and bad. W. Todd Wipke wipke@secs.ucsc.edu Molecular Engineering Laboratory wipke@chemistry.ucsc.edu Department of Chemistry wipke@cats.bitnet University of California tel 408 459-2397 Santa Cruz, CA 95064 FAX 408 459-4716 ============= where innovation is a tradition =================== ================================================================================ Archive-Date: Thu, 19 Mar 1992 03:56:41 EST Date: Thu, 19 Mar 1992 00:57:08 PST From: "W. Todd Wipke" Reply-To: "W. Todd Wipke" To: mx-list@vms.ecs.rpi.edu Message-ID: <00957CA8.69363D40.4330@SECS.UCSC.EDU> Subject: Save trees Matt!!!!! Matt: It is hard to say anything about MX, but when I printed out the MLFguide.PS, I found 5 blank pages and 18 non-blank pages. Somebody has inserted unconditional newpage commands--a no-no with smart document prep packages. Further, the information density/page could be improved, as I sit and look at redwoods and other trees, I am saddened by waste of so much paper with so little ink on it, a left margin that starts at 33% pagewidth. Stylish yes, resource efficient no. I know, you are saying, "Wipke, why did you print it, why not just bookread it?" Well I don't have a bookread terminal. Thanks for listening to an environmentalist. Maybe all MX users will say they did not print any manuals before installing 3.1, in which case I will feel much better. W. Todd Wipke wipke@secs.ucsc.edu Molecular Engineering Laboratory wipke@chemistry.ucsc.edu Department of Chemistry wipke@cats.bitnet University of California tel 408 459-2397 Santa Cruz, CA 95064 FAX 408 459-4716 ============= where innovation is a tradition =================== ================================================================================ Archive-Date: Thu, 19 Mar 1992 13:18:20 EST Sender: Date: Thu, 19 Mar 1992 10:16:13 PST From: "System Manager, UCD Geology" Reply-To: "System Manager, UCD Geology" To: wipke@SECS.UCSC.EDU CC: mx-list@vms.ecs.rpi.edu, waterstraat@garnet.ucdavis.edu Message-ID: <00957CF6.831554A0.22707@garnet.ucdavis.edu> Subject: RE: Save trees Matt!!!!! > Matt: > It is hard to say anything about MX, but when I printed out > the MLFguide.PS, I found 5 blank pages and 18 non-blank pages. Somebody > has inserted unconditional newpage commands--a no-no with smart document > prep packages. These are not gratuituous blank pages. If you print the MLFguide.ps documentation to a duplex printer you get out 12 sheets of correctly formated documentation. Or, if you make duplex photocopies of simplex originals for other departments at your institution, then the blank pages keep the chapters and sections correctly alligned so that you can insert index tabsin the right places. > Further, the information density/page could be improved, > [ . . . ] a left margin that starts at 33% pagewidth. Stylish yes, > resource efficient no. I find that I rapidly fill in much of the space with notes, suggestions and examples. I also find printed matter with 12 point type that stretches on for 6-1/2 to 7-1/2 inches across the page almost impossible to read for very long. My tired old eyes lose vertical registration in trying to scan all the way back across the page to find the beginning of the next line. I usually end up not reading documentation that comes formatted like that, in which case printing it out in the first place was a total waste of paper. I congradulate Matt for using a format that makes the MX documentation extremely readable, and therefore, useful. ---Paul. --------------------------------------------------------------------------- | Paul Waterstraat | Internet: waterstraat@jade.ucdavis.edu | Computer Systems Manager | or: epwaterstraat@ucdavis.edu o | Department of Geology | BITNET: epwaters@ucdavis _-\ _ | University of California | uucp: ucdavis!epwaterstraat (_)%(_) | Davis, CA 95616-8605 | Voice: (916) 752-7421 --------------------------------------------------------------------------- ================================================================================ Archive-Date: Thu, 19 Mar 1992 21:51:29 EST Sender: manager%LEMOYNE.bitnet@VM.ITS.RPI.EDU Date: Thu, 19 Mar 1992 21:50:45 EST From: Dan Wheeler Reply-To: manager%LEMOYNE.bitnet@VM.ITS.RPI.EDU To: mx-list@vms.ecs.rpi.edu CC: manager@LEMOYNE.BITNET Message-ID: <00957D57.89AE0E40.5023@socrates.lemoyne.edu> Subject: Configuration questions - TCP/IP LAN not Internet I've been running MX for a JNet/BITNet connection to the outside world, and have just added NETLIB/SMTP support for a TCP/IP LAN -- *not* the Internet. We currently have an HP Unix box on the local net and will eventually add an Ultrix box. Eventually we expect to connect my MX machine to the Internet. How should I be configured, for now and for minimal disruption in the future? My current CONFIG.MCP is attached below. Some specific questions: -- what should my MX node name be? I created a node withing our Internet official domain (socrates.LEMOYNE.EDU) as the MX node, but now that seems to show up in all my messages. Should I still be LEMOYNE? -- what paths/routes/rewrites do I really need? The items below are the result of much trial and error and minimal knowledge. Any advice is welcome for those of us among the networking impaired. --dan ------------------------------------------------------------------------------ Dan Wheeler, Academic Support Specialist & VMS System Manager Office of Information Systems, Le Moyne College, Syracuse, NY 13214-1399 Phone 315.445.4582/4565 (Home 315.655.8193) WHEELER@LEMOYNE.BITNET ------------------------------------------------------------------------------ -------------------------------------------------------------------- ! Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;42 ! MX version id: MX V3.1 DEFINE SYSTEM_USERS ... DEFINE LISTs ... DEFINE REWRITE_RULE - "<{u}@lemoyne>" - "<{u}@lemoyne>" DEFINE REWRITE_RULE - "<{u}@lemoyne.BITNET>" - "<{u}@lemoyne>" DEFINE REWRITE_RULE - "<@{stuff}:{user}@{host}.UUCP>" - "<{user}%{host}%uunet.uu.net@INTERBIT.BITNET>" DEFINE REWRITE_RULE - "<{user}@{host}.UUCP>" - "<{user}%{host}%uunet.uu.net@INTERBIT.BITNET>" DEFINE REWRITE_RULE - "<@{stuff}:{user}@{host}.CSNET>" - "<{user}%{host}.CSNET%relay.cs.net@INTERBIT.BITNET>" DEFINE REWRITE_RULE - "<{user}@{host}.CSNET>" - "<{user}%{host}.CSNET%relay.cs.net@INTERBIT.BITNET>" DEFINE REWRITE_RULE - "<@{route}:{user}@{host}.BITNET>" - "<{user}@{host}.BITNET>" DEFINE REWRITE_RULE - "<{user}@{host}.BITNET>" - "<{user}@{host}.BITNET>" DEFINE REWRITE_RULE - "<@{route}:{user}@{host}>" - "<{user}%{host}@INTERBIT.BITNET>" DEFINE PATH "[192.77.176.100]" Local DEFINE PATH "lemoyne.edu" Local DEFINE PATH "socrates.lemoyne.edu" Local DEFINE PATH "lemoyne" Local DEFINE PATH "lemoyne.BITNET" Local DEFINE PATH "*.BITNET" Jnet DEFINE PATH "admin1" SMTP /ROUTE="ADMIN1" DEFINE PATH "SOCRATES" Local DEFINE PATH "admint" SMTP /ROUTE="[192.77.176.1]" DEFINE ALIAS "POSTMASTER" "POSTMASTER@LEMOYNE" SET SMTP/NOACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 /DNS_RETRIES=12- /NODEFAULT_ROUTER SET LOCAL/NOACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96/HEADERS=(TOP=(- FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID,- RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT,- ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM,- RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER), BOTTOM=(- NOALL)) SET ROUTER/PERCENT_HACK SET JNET/NOPERCENT_HACK/NOBSMTP_REPLY/NOACCOUNTING/NOLENIENT/NOUSERNAME SET DECNET_SMTP/NOACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 SET SITE/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 SET X25_SMTP/NOACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 ================================================================================ Archive-Date: Fri, 20 Mar 1992 10:40:03 EST To: mx-list@vms.ecs.rpi.edu Date: 20 Mar 92 08:53:02 GMT From: rand@merrimack.edu Reply-To: rand@merrimack.edu Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar20.085302.1446@merrimack.edu> References: <00957CA8.69363D40.4330@SECS.UCSC.EDU> Subject: Re: Save trees Matt!!!!! In article <00957CA8.69363D40.4330@SECS.UCSC.EDU>, wipke@SECS.UCSC.EDU (W. Todd Wipke) writes: > Matt: > 33% pagewidth. Stylish yes, resource efficient no. I know, you are > saying, "Wipke, why did you print it, why not just bookread it?" Well > I don't have a bookread terminal. How about reading the .txt files with your handy editor. Works just fine for me. Rand P. Hall, System Janitor, Merrimack College, North Andover, Massachusetts Internet: rand@merrimack.edu, rand@lucy.merrimack.edu ================================================================================ Archive-Date: Fri, 20 Mar 1992 12:53:26 EST Sender: Date: Fri, 20 Mar 1992 12:53:05 EST From: Matt Madison Reply-To: madison@vms.ecs.rpi.edu To: mx-list@vms.ecs.rpi.edu Message-ID: <00957DD5.97A88EC0.17200@mdmvs.ecs.rpi.edu> Subject: MX V3.1 warning: bugs in X25-SMTP, MLF Two defects were found in MX V3.1 just after I put up the distribution kit for release. The first is a problem in the SMTP-over-X.25 support, which causes the X25_SMTP agent to exit after successful delivery of a message. I have fixed this and put up a revised MX031.H save set. If you are using SMTP-over-X.25, you should get this updated save set and re-install the SMTP-over-X.25 support. If you are not using SMTP-over-X.25, you don't have to worry about it. The second defect is in the mailing list processor. Automatically-handled subscriptions are entered in the mailing list with the NOMAIL flag set, which prevents the subscribers from receiving any mail from the list. I have fixed this and put up a revised MX031.J save set. If you are already using MX V3.1 with MLF (the mailing list/file server), you should either obtain this updated save set and re-install the MLF support, or try the following patch: $ PATCH MX_EXE:MX_MLF.EXE SET ECO 1 REPLACE/INSTR 61A8 'PUSHL #01' EXIT 'PUSHL #00' EXIT UPDATE EXIT This patch worked for me, but I'm not 100% sure that it will work everywhere, so use it at your own risk. If you can just re-install the updated MLF component, that's your best bet. -Matt -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Sat, 21 Mar 1992 11:22:22 EST Sender: Date: Sat, 21 Mar 1992 08:19:21 PST From: Carl J Lydick Reply-To: Carl J Lydick To: wipke@SECS.UCSC.EDU CC: mx-list@vms.ecs.rpi.edu Message-ID: <00957E78.84DAE100.24709@SOL1.GPS.CALTECH.EDU> Subject: RE: Save trees Matt!!!!! > It is hard to say anything about MX, but when I printed out >the MLFguide.PS, I found 5 blank pages and 18 non-blank pages. Somebody >has inserted unconditional newpage commands--a no-no with smart document >prep packages. Further, the information density/page could be improved, >as I sit and look at redwoods and other trees, I am saddened by waste of >so much paper with so little ink on it, a left margin that starts at >33% pagewidth. Stylish yes, resource efficient no. I know, you are >saying, "Wipke, why did you print it, why not just bookread it?" Well >I don't have a bookread terminal. > Thanks for listening to an environmentalist. Maybe all MX users will say >they did not print any manuals before installing 3.1, in which case I will >feel much better. Actually, those blank pages make it easier to conserve trees, if you're going to produce two copies of the documentation: Those blank pages make it MUCH easier to produce a two-sided version of the doc set. Please don't remove the blank pages, Matt. ================================================================================ Archive-Date: Sun, 22 Mar 1992 04:13:32 EST Sender: Date: Sun, 22 Mar 1992 01:10:13 PST From: "John F. Sandhoff" Reply-To: sandhoff@csus.edu To: MX-List@vms.ecs.rpi.edu CC: syssand@CCVAX.CCS.CSUS.EDU Message-ID: <00957F05.BC2FC8E0.13082@CCVAX.CCS.CSUS.EDU> Subject: RE: Save Trees... >> ...when I printed out the MLFguide.PS, I found 5 blank pages... > Those blank pages make it MUCH easier to produce a two-sided version > of the doc set... I send the docs straight to an HP IIIsi running in duplex mode and if they did NOT have the blank pages they would NOT print correctly for me! So this is another vote to leave things be! Maybe Matt can create TWO sets of the documents: One for 'normal' single-sided printing and one just like it is now (except maybe even add the DUPLEX command) for us two-sided personalities (No, really I'm just kidding! Matt has enough to do to in his attempts to keep us all happy :-) ). Of course, one things confuses me: >> Maybe all MX users will say they did not print any manuals before >> installing 3.1... We're SYSTEMS folks. Why in the world would any of us bother to look at the documentation ?!?? John F. Sandhoff, Network Support California State University, Sacramento sandhoff@csus.edu ================================================================================ Archive-Date: Sun, 22 Mar 1992 08:40:21 EST Sender: Date: Sun, 22 Mar 1992 14:38:27 MEZ From: "Reinhold Meyer, Forstliche Biometrie UNIGOE" Reply-To: "Reinhold Meyer, Forstliche Biometrie UNIGOE" To: mx-list@vms.ecs.rpi.edu CC: rmeyer@ufobi2.uni-forst.gwdg.de Message-ID: <00957F76.A4E928E0.2121@ufobi2.uni-forst.gwdg.de> Subject: problem with PSC TCP/IP and MX Hello, after installing MX 3.1 on a system running PSCs TCP/IP package, some messages did not leave the local system: Entry: 2103, Origin: [Local] Status: IN-PROGRESS, size: 640 bytes Created: 22-MAR-1992 14:13:13.91, expires 21-APR-1992 14:13:13.91 Last modified 22-MAR-1992 14:13:24.39 SMTP entry #2104, status: READY, size: 320 bytes, - waiting for retry until 22-MAR-1992 14:43:27.74 Created: 22-MAR-1992 14:13:23.36, expires 21-APR-1992 14:13:13.91 Last modified 22-MAR-1992 14:13:27.75 Recipient #1: , Route=gwdgv1.dnet.gwdg.de DNS errors=1 Last error: %MX-F-NOHOST, no such host Normally mail for *.dnet.gwdg.de is redirected to ibm.gwgd.de ( Nameserver entry ). It seems that MX does not take care of this entry when using PSC software. How can this be corrected without doing MCP define path * decnet /route=node_running_cmu ! works fine for the moment Reinhold -------------------------------------------------------------------------------- Reinhold Meyer Abt. Forstliche Biometrie u. Informatik Buesgenweg 4 W-3400 Goettingen Voice : +49 551 393466 Internet: rmeyer@ufobi2.uni-forst.gwdg.de ================================================================================ Archive-Date: Sun, 22 Mar 1992 17:52:46 EST To: mx-list@vms.ecs.rpi.edu Date: 22 Mar 92 05:57:46 EST From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar22.055746.4226@dmc.com> Subject: define list /noadd doesn't suppress addition messages. I just created a mailing list, specifically with /NOADD to suppress the addition message. The list definition follows with some of the security information removed: Name: xxx Owner: ... Reply-to: List, NOSender Errors-to: munroe@dmc.com Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWD,WORLD) I then added a few people to the list with the following message: add swartz@judyl.enet.dec.com,croll@wonder.enet.dec.com,monia@starch.enet.dec.com,munroe@dmc.com /nosig and, incorrectly, received the following addition message from the MLF: Return-Path: Received: by DMC.COM (MX V3.1) id 6851; Sun, 22 Mar 1992 05:50:42 EST Date: Sun, 22 Mar 1992 05:50:42 EST From: MX mailing list processor To: swartz@JUDYL.ENET.DEC.COM, croll@WONDER.ENET.DEC.COM, monia@STARCH.ENET.DEC.COM, munroe@DMC.COM Subject: Subscription to mailing list XXX-L You have been added to mailing list XXX-L@DMC.COM. Further administrative requests regarding this list should be sent to Internet: XXX-L-Request@DMC.COM BITNET: LISTSERV@bitnetnodename The following commands can be handled automatically by the list processor: SIGNOFF XXX-L - to remove yourself from the list REVIEW XXX-L - to get a list of subscribers You may omit the list name if you are using the Internet -Request address. (This message was generated automatically.) isn't this a bug? Dick -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 ================================================================================ Archive-Date: Sun, 22 Mar 1992 17:52:52 EST To: mx-list@vms.ecs.rpi.edu Date: 22 Mar 92 06:51:14 EST From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar22.065115.4227@dmc.com> Subject: Why does the MX Router allocate a CMUTEK IP device? I've just brought up CMUTEK TCP/IP and while poking around I discovered that the MX router has allocated an IP device for some reason: Device IP28: is online, mounted, network device, mailbox device. Error count 0 Operations completed 45 Owner process "MX Router" Owner UIC [SYSTEM] Owner process ID 000000D3 Dev Prot Reference count 1 Default buffer size 1024 Since I installed MX BEFORE I installed CMUTEK and I did NOT install any TCP/IP functionality at the time of installation, I'm a little curious as to what its doing. Dick -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 ================================================================================ Archive-Date: Mon, 23 Mar 1992 09:27:35 EST To: mx-list@vms.ecs.rpi.edu Date: Mon, 23 Mar 1992 14:25:39 GMT From: madison@mdmvs.ecs.rpi.edu (Matt Madison) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: References: <1992Mar22.055746.4226@dmc.com> Reply-To: madison@vms.ecs.rpi.edu Subject: Re: define list /noadd doesn't suppress addition messages. In article <1992Mar22.055746.4226@dmc.com>, munroe@dmc.com (Dick Munroe) writes: >I just created a mailing list, specifically with /NOADD to suppress the addition >message. The list definition follows with some of the security information >removed: Actually, specifying /NOADD does not suppress the add message; it merely causes the use of the default add message. It is documented that way, although now that you mention it, having some way to eliminate all of those kinds of messages might not be such a bad idea. >I then added a few people to the list with the following message: > >add swartz@judyl.enet.dec.com,croll@wonder.enet.dec.com,monia@starch.enet.dec.com,munroe@dmc.com >/nosig Using ADD/NONOTIFY is currently the only way to suppress the add notification. -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Mon, 23 Mar 1992 12:56:33 EST Date: Mon, 23 Mar 1992 12:51 EDT From: Dan Wheeler Reply-To: Dan Wheeler Subject: SMTP Server exiting immediately? To: mx-list@vms.ecs.rpi.edu My SMTP Server process starts and then ends within seconds of starting, with no error messages (I have the debug flag set). This may be due to some recent changes in my UCX software installation, but I'm not sure. Is SMTP Server checking for UCX presence and not finding it? For what exactly does it check? What should I try now? How many questions am I allowed to ask at one time? My configuration: VAX/VMS 5.4-3, MX 3.1, Jnet 3.5, UCX beta ------------------------------------------------------------------------------ Dan Wheeler, Academic Support Specialist & VMS System Manager Office of Information Systems, Le Moyne College, Syracuse, NY 13214-1399 Phone 315.445.4582/4565 (Home 315.655.8193) WHEELER@LEMOYNE.BITNET ------------------------------------------------------------------------------ ================================================================================ Archive-Date: Mon, 23 Mar 1992 13:14:47 EST Date: Mon, 23 Mar 1992 11:13:57 MST From: Tom Van Dreser 303-236-4537 USGS-BGRA Reply-To: Tom Van Dreser 303-236-4537 USGS-BGRA To: mx-list@vms.ecs.rpi.edu Message-ID: <00958023.3E912CC0.662@sgbsn> Pardon my ignorance... I understand from the MX manual that the best way to implement the MX Network file server is to manage the server with VMS_SHARE (or some other package like it) and that it is readily available on the Internet. Well I have searched the Internet and found the string "VMS_SHARE" several times; however, none of the files seem to be the VMS_SHARE described in the manual. Can someone direct me to the proper VMS_SHARE. Perhaps a copy of VMS_SHARE could be included in the MX network file server. Thank you. TVD ================================================================================ Archive-Date: Mon, 23 Mar 1992 13:23:02 EST Sender: Date: Mon, 23 Mar 1992 10:23:50 PST From: "W. Todd Wipke" Reply-To: "W. Todd Wipke" To: mx-list@vms.ecs.rpi.edu Message-ID: <0095801C.3DDE34A0.4940@SECS.UCSC.EDU> Subject: MX031 SITE delivery to BULLETIN problem Matt: I have installed mx031 and in addition to the previous bug I sent to you, my SITE delivery agent is not working. I installed the netlib with MX, am using multinet, have not reinstalled bulletin because date on bulletin share in contrib looks like it is the same one I have. Here is what I did: Two msgs were sent to mx which forwards to mx@bulletin, then I did dir of mx_root:[site] while delivery was being made: [MX3.SITE] dir Directory MX_DEVICE:[MX3.SITE] MX_SITE_LOG.LOG;3 MX_SITE_LOG.LOG;2 MX_SITE_LOG.LOG;1 MX_SITE_SECS.LOG;83 SITESENDER.ADDR;1 SITE_ADR_CC323A00_00958015_22000122.TMP;1 SITE_MSG_CC323A00_00958015_22000122.TMP;1 Total of 7 files. [MX3.SITE] dir Directory MX_DEVICE:[MX3.SITE] MX_SITE_LOG.LOG;3 MX_SITE_LOG.LOG;2 MX_SITE_LOG.LOG;1 MX_SITE_SECS.LOG;83 Total of 4 files. [MX3.SITE] dir Directory MX_DEVICE:[MX3.SITE] MX_SITE_LOG.LOG;4 MX_SITE_LOG.LOG;3 MX_SITE_LOG.LOG;2 MX_SITE_LOG.LOG;1 MX_SITE_SECS.LOG;83 Total of 5 files. [MX3.SITE] ty mx_site_log.log;-1 23-MAR-1992 09:37:42.37 Processing queue entry number 4923. 23-MAR-1992 09:37:46.92 DELIVER: Delivering... 23-MAR-1992 09:37:47.03 DELIVER_FILE: Command: @MX_EXE:SITE_DELIVER "BULLETIN" MX_ROOT:[SITE]SITE_MSG_CC323A00_00958015_22000122.TMP;1 MX_ROOT:[SITE]SITE_ADR_ CC323A00_00958015_22000122.TMP;1 "" 23-MAR-1992 09:37:59.10 DELIVER_FILE: Subprocess says: MX_BULL: Opening messa ge file.... 23-MAR-1992 09:38:00.17 DELIVER_FILE: Subprocess says: MX_BULL: Error status %X00018292 23-MAR-1992 09:38:01.59 DELIVER_FILE: Subprocess says: %RMS-E-FNF, file not f ound 23-MAR-1992 09:38:05.62 DELIVER_FILE: Subprocess says: EXIT:00000001 [MX3.SITE] No messages were added to the bulletin folder. Analyze/rms on the folders shows no errors. ================================================================================ Archive-Date: Mon, 23 Mar 1992 14:45:47 EST Sender: manager%LEMOYNE.bitnet@VM.ITS.RPI.EDU Date: Mon, 23 Mar 1992 14:44:44 EST From: Dan Wheeler Reply-To: manager%LEMOYNE.bitnet@VM.ITS.RPI.EDU To: mx-list@vms.ecs.rpi.edu CC: manager@LEMOYNE.BITNET Message-ID: <00958040.AFC567E0.8028@socrates.lemoyne.edu> Subject: Re: SMTP Server exiting immediately OK - I found it. I had not totally disabled the UCX SMTP. MX SMTP Server was apparently finding UCX SMTP_Receive and exiting (without any informational message, I do not hesitate to add). --dan ------------------------------------------------------------------------------ Dan Wheeler, Academic Support Specialist & VMS System Manager Office of Information Systems, Le Moyne College, Syracuse, NY 13214-1399 Phone 315.445.4582/4565 (Home 315.655.8193) WHEELER@LEMOYNE.BITNET ------------------------------------------------------------------------------ ================================================================================ Archive-Date: Mon, 23 Mar 1992 15:08:31 EST Sender: goathunter%WKUVX1.BITNET@vms.ecs.rpi.edu Date: Mon, 23 Mar 1992 14:02:30 CST From: "Hunter Goatley, WKU" Reply-To: "Hunter Goatley, WKU" To: wipke@SECS.UCSC.EDU CC: mx-list@vms.ecs.rpi.edu Message-ID: <0095803A.C98E6A60.29143@WKUVX1.BITNET> Subject: RE: MX031 SITE delivery to BULLETIN problem "W. Todd Wipke" writes: > >Matt: > I have installed mx031 and in addition to the previous bug I >sent to you, my SITE delivery agent is not working. I installed >the netlib with MX, am using multinet, have not reinstalled >bulletin because date on bulletin share in contrib looks like it >is the same one I have. Here is what I did: > [...] >23-MAR-1992 09:37:46.92 DELIVER: Delivering... >23-MAR-1992 09:37:47.03 DELIVER_FILE: Command: @MX_EXE:SITE_DELIVER "BULLETIN " > MX_ROOT:[SITE]SITE_MSG_CC323A00_00958015_22000122.TMP;1 MX_ROOT:[SITE]SITE_ADR _ >CC323A00_00958015_22000122.TMP;1 "" >23-MAR-1992 09:37:59.10 DELIVER_FILE: Subprocess says: MX_BULL: Opening mess a >ge file.... >23-MAR-1992 09:38:00.17 DELIVER_FILE: Subprocess says: MX_BULL: Error status >%X00018292 >23-MAR-1992 09:38:01.59 DELIVER_FILE: Subprocess says: %RMS-E-FNF, file not f >ound [...] Have you updated your SITE_DELIVER.COM file to adjust for the extra parameter? MX v3.0 added the ROUTE as P1, making the old P1--P3 now P2--P4. It sounds like you need to modify the line that calls MX_BULL from: $ mx_bull 'p1' 'p2' mx_site_dir:sitesender.addr to: $ mx_bull 'p2' 'p3' mx_site_dir:sitesender.addr Let me know if that doesn't solve the problem---I haven't used MX_BULL since last summer, so I forgot that that needs to be updated.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET, 502-745-5251 ================================================================================ Archive-Date: Mon, 23 Mar 1992 15:22:57 EST Sender: Date: Mon, 23 Mar 1992 12:23:24 PST From: "W. Todd Wipke" Reply-To: "W. Todd Wipke" To: goathunter%WKUVX1.BITNET@vms.ecs.rpi.edu CC: mx-list@vms.ecs.rpi.edu Message-ID: <0095802C.F1BE88C0.4990@SECS.UCSC.EDU> Subject: RE: MX031 SITE delivery to BULLETIN problem Hunter, You were correct, I had not changed my site_deliver.com call to mx_bull p2 p3 and incremented p3 to p4 since I was at MX 2.3 and never went to 3.0 where this change occurred. I replaced every occurrence of p3 with p4, p2 with p3, p1 with p2 in site_deliver.com and behold, joy! Thanks for your prompt helpful response. -Todd Wipke W. Todd Wipke wipke@secs.ucsc.edu Molecular Engineering Laboratory wipke@chemistry.ucsc.edu Department of Chemistry wipke@cats.bitnet University of California tel 408 459-2397 Santa Cruz, CA 95064 FAX 408 459-4716 ============= where innovation is a tradition =================== ================================================================================ Archive-Date: Mon, 23 Mar 1992 16:27:08 EST Sender: Date: Mon, 23 Mar 1992 13:27:41 PST From: "W. Todd Wipke" Reply-To: "W. Todd Wipke" To: mx-list@vms.ecs.rpi.edu Message-ID: <00958035.EC2ECD80.5056@SECS.UCSC.EDU> Subject: unknown mailing list "" The problem I described earlier about mailing lists being unknown was not that they were not being found in mx_root:[local.mlists], but rather that I had deleted mx_config.mxcfg, then fired up mcp and @config.mcp and reset the servers BEFORE I saved the mx_config.mxcfg. previously I have always edited config.mcp and then compiled it to mx_config.mxcfg, but now if you already have an mx_config.mxcfg it compares and ignores things that already exist, even if the new configuration is different in some parameters. Of course you can SHOW/COMMAND /OUTPUT=file ALL, but the result lacks all your nice comments and history of changes. The problem is mine, not Matt's. I went from 2.3 to 3.1 in one jump. -Todd Wipke ================================================================================ Archive-Date: Mon, 23 Mar 1992 22:46:10 EST Sender: Date: Mon, 23 Mar 1992 22:41:23 EST From: Ta Fuh Chiam Reply-To: Ta Fuh Chiam To: mx-list@vms.ecs.rpi.edu Message-ID: <00958083.45E38EE0.24134@VULCAN.CBA.OHIOU.EDU> Subject: What exactly is SMTP-over-DECNET support Hi, MX users, I just installed Mx 3.1. Now, what exactly is SMTP-over-DECnet support? What do I gain by using it and how do I use it? Can someone give me some examples? The manuals don't say much about it. Thanks. Ta Fuh ============================================================================ Ta Fuh Chiam Ohio University, College of Business Administration / Phone: (614)593-2088 Management Information Systems FAX: (614)593-1388 Copeland Hall 22 INTERNET : chiam@vulcan.cba.ohiou.edu Athens, Ohio 45701, U.S.A. or : chiam@ouvaxa.ucls.ohiou.edu BITNET : CHIAM@OUACCVMB Use my first Internet address if at all possible. Disclaimer: What I have said are my opinions, not of anyone else. ============================================================================ ================================================================================ Archive-Date: Tue, 24 Mar 1992 08:49:56 EST Sender: Date: Tue, 24 Mar 1992 09:47:40 EST From: sponagle@MERLIN.DREA.DND.CA Reply-To: sponagle@MERLIN.DREA.DND.CA To: mx-list@vms.ecs.rpi.edu CC: sponagle@MERLIN.DREA.DND.CA Message-ID: <009580E0.5A1F0620.1319@MERLIN.DREA.DND.CA> Subject: Problem with mail reply When I reply to internet mail using the DECwindows mail interface I sometimes (roughly half the time) get the following messages. Sending mail... Error activating transport MX. Error activating image $1$DKA200:[MX.][EXE]MX_SHR.EXE. Section table (process/global) is full. Send failed. Mail started from DCL command level seems to be fully functional. Clearly some parameter needs to be increased, but which one? The system appears to have a sufficient number of free global sections, as shown by the following. INSTALL> list/sum/global Summary of Local Memory Global Sections 230 Global Sections Used, 14390/15610 Global Pages Used/Unused SYSGEN> SHOW GBLSECTIONS Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 400 250 20 4095 Sections Any suggestions would be welcome! Neil Sponagle sponagle@merlin.drea.dnd.ca ================================================================================ Archive-Date: Tue, 24 Mar 1992 10:48:30 EST Date: 24 Mar 1992 08:46:14 -0700 (MST) From: Dan Wing Reply-To: Dan Wing Subject: MX across DECnet To: mx-list@vms.ecs.rpi.edu Message-ID: <01GI0LHOQALU00009K@VAXF.COLORADO.EDU> I've checked the MX-LIST archives looking for an answer to this question, but only found the same question had been posted previously, but I didn't find an answer... >Archive-Date: Mon, 02 Dec 1991 12:18:00 EST >Date: Mon, 2 Dec 91 13:19:43 AST >From: 720323w@aucs.acadiau.ca (Bill Wilder) >Reply-To: 720323w@aucs.acadiau.ca (Bill Wilder) >Message-ID: <9112021719.AA07172@aucs.acadiau.ca> >X-MX-Warning: Warning -- Invalid "To" header. >To: -v, mx-list@vms.ecs.rpi.edu >Subject: Need help with quotes > >I'm running MX on a local VAX. A remote VAX runs PMDF and runs as our >Internet gateway. I need a fairly generic rule which will remap: > > user@host.domain > >to > ottgw::in%"user@host.domain" > >The presence of percent signs, at signs and quotes in the replacement >pattern makes it difficult for me to devine the necessary magic. >I have defined SET ROUTER/NOPERCENT_HACK. Can anyone help out? > >The benefit of using MX here is to store and retry in the event >the DECNET link to OTTGW is down temporarily. I have suceeded in sending mail to: MX%"gateway::IN%'internet_address'" and I imagine I could create a rewrite rule to automate this (so I wouldn't need to specify the `gateway::IN%' portion). However, the message is received (when I send the message out of my system back to myself) with a FROM address of: gateway::IN%"'MX%\\'DWING@UH01.Colorado.EDU\\''@UH01.Colorado.EDU" which can be replied to, but isn't exactly the cleanest address... -Dan Wing, DWING@UH01.Colorado.EDU (or WING_D@UCOLMCC.BITNET) Systems Programmer, University Hospital, Denver ================================================================================ Archive-Date: Tue, 24 Mar 1992 13:08:00 EST To: mx-list@vms.ecs.rpi.edu Date: 24 Mar 92 15:36:22 GMT From: burton@bobcat.lmc.edu (Kathryn K. Burton) Reply-To: burton@bobcat.lmc.edu (Kathryn K. Burton) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: Subject: New install - return address doesn't show up Hello, I have just installed MX on a stand-alone system and have been able to send internet mail from VMSmail with mx%user@site. Works, but the from: ends up being burton@lmc.edu rather than burton@bobcat.lmc.edu (bobcat is the node name). 1. What have I done wrong in the configuration to lose the node name? 2. Is a user supposed to get mail to my machine simply with burton@bobcat.lmc.edu, or does he/she have to add some mx stuff for my machine to recognize and accept it for delivery? 3. Since mx delivers to vmsmail, will ALL-in-1 users have to add still more to get a message out? Kathy burton@andy.lmc.edu ================================================================================ Archive-Date: Tue, 24 Mar 1992 15:05:23 EST To: mx-list@vms.ecs.rpi.edu Date: 24 Mar 92 18:17:18 GMT From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar24.131718.5968@dayton.saic.com> References: <01GI0LHOQALU00009K@VAXF.COLORADO.EDU> Subject: Re: MX across DECnet In article <01GI0LHOQALU00009K@VAXF.COLORADO.EDU>, DWING@UH01.Colorado.EDU (Dan Wing) writes: > I've checked the MX-LIST archives looking for an answer to this question, > but only found the same question had been posted previously, but I didn't > find an answer... > >>Archive-Date: Mon, 02 Dec 1991 12:18:00 EST >>Date: Mon, 2 Dec 91 13:19:43 AST >>From: 720323w@aucs.acadiau.ca (Bill Wilder) >>Reply-To: 720323w@aucs.acadiau.ca (Bill Wilder) >>Message-ID: <9112021719.AA07172@aucs.acadiau.ca> >>X-MX-Warning: Warning -- Invalid "To" header. >>To: -v, mx-list@vms.ecs.rpi.edu >>Subject: Need help with quotes >> >>I'm running MX on a local VAX. A remote VAX runs PMDF and runs as our >>Internet gateway. I need a fairly generic rule which will remap: >> >> user@host.domain >> >>to >> ottgw::in%"user@host.domain" >> >>The presence of percent signs, at signs and quotes in the replacement >>pattern makes it difficult for me to devine the necessary magic. >>I have defined SET ROUTER/NOPERCENT_HACK. Can anyone help out? >> >>The benefit of using MX here is to store and retry in the event >>the DECNET link to OTTGW is down temporarily. > > I have suceeded in sending mail to: > > MX%"gateway::IN%'internet_address'" > > and I imagine I could create a rewrite rule to automate this (so I wouldn't > need to specify the `gateway::IN%' portion). However, the message is > received (when I send the message out of my system back to myself) with a > FROM address of: > gateway::IN%"'MX%\\'DWING@UH01.Colorado.EDU\\''@UH01.Colorado.EDU" > > which can be replied to, but isn't exactly the cleanest address... I thought I heard someone say that the SMTP-over-DECnet portion of MX would work with PMDF. Maybe someone else can deny or confirm this. Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Wed, 25 Mar 1992 12:01:50 EST To: mx-list@vms.ecs.rpi.edu Date: 25 Mar 92 16:35:47 GMT From: oursler@vax001.kenyon.edu Reply-To: oursler@vax001.kenyon.edu Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar25.113547.12@vax001.kenyon.edu> Subject: Setup for mail to user@domain? Hullo, Thanks to everyone who responded with hints on making a smooth changeover to MX. I'll be installing version 3.1 sometime this week. There is one thing I'd like to make a little clearer. I asked about setting things up so that you could send mail to any node in the domain or to the domain. That wasn't very clear to some people. Here's what I want: Suppose I have 3 nodes. I'll call them HUEY, DUEY, and LOUIE. If my domain is .kenyon.edu then I'd like people to be able to send mail to: user@huey.kenyon.edu or user@duey.kenyon.edu or user@louie.kenyon.edu OR user@kenyon.edu The last one is what's important. It makes things much simpler. Is this just an MX record in NAMED.HOSTS? Forgive me if this is more generic than MX (mail program) questions. I've never set up SMTP in this fashion before. Thanks for any help. - Miles - ------------------------------- Miles Oursler Manager of Networks and Systems Kenyon College oursler@vax001.kenyon.edu (614) 427-5696 ------------------------------- ================================================================================ Archive-Date: Wed, 25 Mar 1992 15:52:50 EST Sender: Date: Wed, 25 Mar 1992 12:53:27 PST From: "W. Todd Wipke" Reply-To: "W. Todd Wipke" To: mx-list@vms.ecs.rpi.edu Message-ID: <009581C3.78DDDEE0.5403@SECS.UCSC.EDU> Subject: Moderated lists Dear Matt: I now have MX031 installed and lists and fileserver is working perfectly. I am wondering why moderated list option has not been implemented yet since it is a common feature in usenet and allows the list owner to prevent inappropriate postings. I use the moderated property in usenet to cause a posting on usenet to be sent first to an MX list which includes an address that posts to usenet. This enables keeping a mailing list and usnet news group with identical messages without mailing loops. I presume an MX moderated list would redirect postings from subscribers to the moderator, and postings from the moderator would actually be mailed out to the list and archived. The hard part seems what to do about the from and reply-to address if one wanted to make it look like the message was posted directly by the original sender. The extra headers arising from forwarding by the moderator also would be annoying. When will moderated list be implemented? -Todd Wipke PS: Suggestion: where you say personal names can be included as indicated by RFC ..., it would be nice to see a variety of valid examples for those of us who do not know the RFC's. I know, RTFRFC. Just a suggestion. ================================================================================ Archive-Date: Wed, 25 Mar 1992 16:38:54 EST To: mx-list@vms.ecs.rpi.edu Date: 25 Mar 92 15:09:11 EST From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Mar25.150911.5970@dayton.saic.com> References: <1992Mar25.113547.12@vax001.kenyon.edu> Subject: Re: Setup for mail to user@domain? In article <1992Mar25.113547.12@vax001.kenyon.edu>, oursler@vax001.kenyon.edu writes: > Hullo, > > Thanks to everyone who responded with hints on making a smooth > changeover to MX. I'll be installing version 3.1 sometime this > week. > > There is one thing I'd like to make a little clearer. I asked > about setting things up so that you could send mail to any > node in the domain or to the domain. That wasn't very clear to > some people. Here's what I want: > > Suppose I have 3 nodes. I'll call them HUEY, DUEY, and LOUIE. > If my domain is .kenyon.edu then I'd like people to be > able to send mail to: > > user@huey.kenyon.edu > or user@duey.kenyon.edu > or user@louie.kenyon.edu > > OR user@kenyon.edu > > The last one is what's important. It makes things much simpler. > > Is this just an MX record in NAMED.HOSTS? Forgive me if this > is more generic than MX (mail program) questions. I've never > set up SMTP in this fashion before. It is both an MX record that you publish to the world and also what you need to tell MX - Message Exchange as far as local node. MCP> define path "huey.kenyon.edu" Local MCP> define path "duey.kenyon.edu" Local MCP> define path "louie.kenyon.edu" Local MCP> define path "kenyon.edu" Local -Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Wed, 25 Mar 1992 20:03:06 EST Sender: Date: Mon, 23 Mar 1992 15:20:22 CST From: "George D. Greenwade" Reply-To: "George D. Greenwade" To: wilton@hg.uleth.ca CC: mx-list@vms.ecs.rpi.edu Message-ID: <00958045.AA9CF6C0.31159@SHSU.edu> Subject: RE: Mailing list manager On Wed, 18 Mar 1992 16:38:04 MST, "Russ Wilton, Systems Manager" posted: >Hunter Goatley writes: > >>Well, I haven't actually been in this position yet because I run all of our >>lists. However: can't they do *everything* they need to do using the >>list-request address? They can REVIEW, ADD, and REMOVE using the >>"-request" form; once the list is set up, I can't think of any reason >>they'd need to run MCP.... > > Well no actually, they can't do everything they need. They want to be able > to create and delete lists too. What I am interested in is any information > from sites which have made an effort to separate the list management duties > from the mail system management. We have essentially separated list management duties from mail system management here (although it isn't operational, as such, it is our essential design as I have no "official" ties to Computer Services, although I run quite a few lists and am active in MX-related issues). The trick is to have users you want to be able to create lists, etc., to be defined as privileged users in the original configuration (so they can access MCP), then provide those users with SYSLCK privileges (so they can do MCP RESETs). I have no idea how dangerous it is for me to have this priv as all I use it for is MCP-related items, butr this is all we did to provide me with MCP-able access. Given the system-wide nature of the configuration file, I wonder just how advisable it is to allow anyone to create and delete lists, reset certain items, etc. Possibly for MX 3.2 (yes, Matt, already thinking ahead again), Matt ought to provide user-specific aspects of mailing lists in some way (a user-specific personalized MCP overlay maybe). My only hesitation on this is that one lists, alone, can generate quite a bit of traffic. If you have a few users who create heavy-duty lists, I imagine you will have trouble ahead (unless you've got a 9000 on a T1 or something). Enough of the idle ramblings from just an economist. --George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Wed, 25 Mar 1992 23:43:08 EST Sender: Date: Wed, 25 Mar 1992 21:40:02 MST From: "Russ Wilton, Systems Manager" Reply-To: "Russ Wilton, Systems Manager" To: bed_gdg@SHSU.edu CC: mx-list@vms.ecs.rpi.edu, wilton@hg.uleth.ca Message-ID: <0095820D.09DF42A0.1662@hg.uleth.ca> Subject: RE: Mailing list manager George D. Greenwade recently noted: >Possibly for MX 3.2 (yes, Matt, already thinking ahead again), Matt ought >to provide user-specific aspects of mailing lists in some way (a >user-specific personalized MCP overlay maybe). This is sort of what I had in mind, but more like a cut-down version of MCP which only contained commands for manipulating mailing lists. Then I could let my User Services people handle them entirely on their own, and I wouldn't have to worry about them accidently changing a rewrite rule or something. Maybe we could put this on the wish list for some future version. Along with aliases that forward to more than one address. :-) Thanks everone who responded, for your comments and ideas. Russ #===============================================================# # Russell D Wilton E Mail: WILTON@HG.ULeth.CA # # Systems and Comm Manager Voice: (403) 329-2525 # # Computing Services FAX: (403) 329-2022 # # University of Lethbridge # # 4401 University Drive Lethbridge, Alberta, CANADA T1K 3M4 # #===============================================================# ================================================================================ Archive-Date: Thu, 26 Mar 1992 12:00:12 EST Sender: Date: Thu, 26 Mar 1992 17:56:48 MET From: Eckart Meyer Reply-To: Eckart Meyer To: MX-LIST@VMS.ECS.RPI.EDU Message-ID: <009582B7.040748A0.2827@ifn.ing.tu-bs.de> Subject: SMTP Server aborts link after a long time wating VMS V5.5, MX V3.0, CMU-TEK TCP/IP V6.5 Generally we have no problems receiving Mails from SMTP. Only with one Node it fails constantly. Of course, this node also has no problems sending to other nodes than us. SMTP_SERVER_LOG.LOG contains the following: STM[4]: Send "220 ifn01.ifn.ing.tu-bs.de MX V3.0 SMTP server ready at Thu, 26 Mar 1992 16:58:39 MET" STM[4]: Receive "HELO infbssys.ips.cs.tu-bs.de" STM[4]: Send "250 Hello, infbssys.ips.cs.tu-bs.de" 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]: Error: status=002C The SMTP-Port is open for several minutes. What does the last line say? 002C is %SYSTEM-F-ABORT. Who has aborted? Eckart Meyer ================================================================================ Archive-Date: Mon, 30 Mar 1992 10:08:24 EST Sender: Date: Mon, 30 Mar 1992 10:06:47 EST From: "Dick Desroches, ACC Systems Manager" Reply-To: "Dick Desroches, ACC Systems Manager" To: mx-list@vms.ecs.rpi.edu Message-ID: <0095859A.04B953C0.565@woods.ulowell.edu> Subject: Old MX_ROUTER processes that won't go away. This is my first time using this mailing list so I hope this is an appropriate question. I have a persistent problem with old messages in the queue. They all are status "INP", they are all in the process "MX_ROUTER", they all have SIZE=0 and they stay there forever unless I manually cancel them. Does anyone know what these things are and how I can prevent their lingering in the queue forever (without manually cancelling)? ================================================================================ Dick Desroches, Systems Manager | Phone : 508-934-2682 University of Massachusetts at Lowell | Fax : 508-934-3000 Academic Computer Center | Email : DESROCHES@WOODS.ULOWELL.EDU Lowell, MA 01854 | ================================================================================