Archive-Date: Fri, 01 Oct 1993 00:05:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 01 Oct 1993 00:05:10 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <00973577.17F143DD.8684@WKUVX1.BITNET> Subject: MX-LIST Administrivia: Monthly Post Last modified: 31-MAY-1993 23:55 (Added digest info.) Welcome to MX-List@WKUVX1.BITNET, an electronic mailing list established for the discussion of the Message Exchange mail software. This is a routine posting you will see from time to time on MX-List. MX-List postings are also available in a daily digest format. To subscribe to the digest, send the following command in the body of a mail message to MXserver@WKUVX1.BITNET: SUBSCRIBE MX-List-Digest "Your real name here" The MX-List archives are maintained at ARCHIVES@WKUVX1.BITNET. To get a copy of any month's postings, send an e-mail message with the body SEND MX-List.yyyy-mm to ARCHIVES@WKUVX1.BITNET, where "yyyy" is the year and "mm" is the numeric representation of the month. For example, the message SENDME MX-List.1992-04 will send the archives for April 1992. To remove yourself from the mailing list, send the following command to MXserver@WKUVX1.BITNET: SIGNOFF MX-List MXserver supports a few other commands for your convenience. The following commands can be handled automatically by the list processor: SIGNOFF MX-List - to remove yourself from the list REVIEW MX-List - to get a list of subscribers QUERY MX-List - to get the status of your entry on the list SET MX-List NOMAIL - to remain on the list but not receive mail SET MX-List MAIL - to resume receiving mail from the list SET MX-List CONCEAL - to not report your address in a REVIEW SET MX-List NOCONCEAL - to report your address in a REVIEW SET MX-List REPRO - to receive posts you make to MX-List SET MX-List NOREPRO - to not receive posts you make to MX-List LIST - to get a list of mailing lists served by WKUVX1 HELP - to receive a help file By default, subscriptions are set to MAIL, REPRO, NOCONCEAL. If you have any questions, comments, or suggestions about MX-List, please contact the list owner at the address below. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Hunter Goatley, VAX Systems Programmer goathunter@WKUVX1.BITNET Western Kentucky University Academic Computing, STH 226 (502) 745-5251 Bowling Green, KY 42101 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ================================================================================ Archive-Date: Fri, 01 Oct 1993 08:02:19 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU From: "Eric R. Rountree" Date: 1 Oct 1993 9:41:19 ADT Subject: Empty messages in the old corral Reply-To: MX-List@WKUVX1.BITNET Hi, MX folk: I have a question about a situation which is more of a nuisance than a problem, but I would like to know why it's happening, if possible. There is a fair number of zero-byte messages in the MX queue on my system that are just sitting there, doing nothing and going nowhere. They build up over time until I just decide to turf them. Then they start building up again. They have actual recipient names attached to them, but I don't know where they're coming from. If they actually contained anything, I might be more concerned, but they're all of size zero. The output of the QUEUE SHOW/FULL command is appended to the end of this message. Any suggestions or ideas? Any other info I can supply to provide more clues? Thanks for your consideration. Eric R. Rountree System Manager Business School Site Academic Computing Services Dalhousie University Halifax, Nova Scotia, Canada -------------------------------------------------------------------------- Entry: 13319, Origin: [code=0] Status: IN-PROGRESS, size: 0 bytes Created: 23-SEP-1993 11:55:51.99, expires 23-OCT-1993 11:55:51.99 Last modified 23-SEP-1993 11:55:51.99 Entry: 13459, Origin: [code=0] Status: IN-PROGRESS, size: 0 bytes Created: 23-SEP-1993 16:05:41.20, expires 23-OCT-1993 16:05:41.20 Last modified 23-SEP-1993 16:05:41.20 Recipient #1: Entry: 13591, Origin: [code=0] Status: IN-PROGRESS, size: 0 bytes Created: 24-SEP-1993 00:35:40.50, expires 24-OCT-1993 00:35:40.50 Last modified 24-SEP-1993 00:35:40.50 Recipient #1: Entry: 13794, Origin: [code=0] Status: IN-PROGRESS, size: 0 bytes Created: 24-SEP-1993 16:09:37.49, expires 24-OCT-1993 16:09:37.49 Last modified 24-SEP-1993 16:09:37.49 Recipient #1: Entry: 14554, Origin: [code=0] Status: IN-PROGRESS, size: 0 bytes Created: 27-SEP-1993 19:27:16.10, expires 27-OCT-1993 19:27:16.10 Last modified 27-SEP-1993 19:27:16.10 Recipient #1: Entry: 15193, Origin: [code=0] Status: IN-PROGRESS, size: 0 bytes Created: 29-SEP-1993 10:57:47.86, expires 29-OCT-1993 10:57:47.86 Last modified 29-SEP-1993 10:57:47.86 Recipient #1: Entry: 15449, Origin: [code=0] Status: IN-PROGRESS, size: 0 bytes Created: 29-SEP-1993 17:54:47.03, expires 29-OCT-1993 17:54:47.03 Last modified 29-SEP-1993 17:54:47.03 Recipient #1: Entry: 15897, Origin: [code=0] Status: IN-PROGRESS, size: 0 bytes Created: 30-SEP-1993 16:23:28.31, expires 30-OCT-1993 16:23:28.31 Last modified 30-SEP-1993 16:23:28.31 Recipient #1: ================================================================================ Archive-Date: Fri, 01 Oct 1993 09:02:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 01 Oct 1993 09:01:38 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009735C2.09810F2C.3180@WKUVX1.BITNET> Subject: RE: Empty messages in the old corral "Eric R. Rountree" writes: > >Hi, MX folk: > >I have a question about a situation which is more of a nuisance than a >problem, but I would like to know why it's happening, if possible. > >There is a fair number of zero-byte messages in the MX queue on my system >that are just sitting there, doing nothing and going nowhere. They build up >over time until I just decide to turf them. Then they start building up >again. They have actual recipient names attached to them, but I don't know >where they're coming from. If they actually contained anything, I might be >more concerned, but they're all of size zero. > The "why" is that users are disconnecting without exiting MAIL or getting killed by something like WATCHER while they're sending mail. MX tries to get rid of these, but the condition handlers that do that are being bypassed in some cases. I hope to try to do something else about these in a future version. In the meantime, they will *eventually* get cleared out when they expire in a month.... 8-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 01 Oct 1993 10:45:53 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 01 Oct 1993 08:38:45 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: rharwood@Data.Basix.COM Message-ID: <009735BE.D752DF60.9011@Data.Basix.COM> Subject: RE: Empty messages in the old corral > >There is a fair number of zero-byte messages in the MX queue on my system > >that are just sitting there, doing nothing and going nowhere. They build up > >over time until I just decide to turf them. Then they start building up > >again. They have actual recipient names attached to them, but I don't know > >where they're coming from. If they actually contained anything, I might be > >more concerned, but they're all of size zero. > > > The "why" is that users are disconnecting without exiting MAIL > or getting killed by something like WATCHER while they're sending > mail. MX tries to get rid of these, but the condition handlers that > do that are being bypassed in some cases. Look at the following lines from the original post: >From: "Eric R. Rountree" > Recipient #1: I've had this as well, but I had the impression it also comes from "network partners" improperly exiting from an SMTP session, leaving a partially-completed entry on the "incoming" side. Either way, a zero length entry that's more than 24 hours old is subject to cancelation at my sites. (My rule!) Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Fri, 01 Oct 1993 10:53:54 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 01 Oct 1993 10:53:03 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009735D1.99F0A301.3233@WKUVX1.BITNET> Subject: RE: Empty messages in the old corral "Ray Harwood -- Data Basix: (602)721-1988" writes: > >> The "why" is that users are disconnecting without exiting MAIL >> or getting killed by something like WATCHER while they're sending >> mail. MX tries to get rid of these, but the condition handlers that >> do that are being bypassed in some cases. > >Look at the following lines from the original post: > >>From: "Eric R. Rountree" >> Recipient #1: > >I've had this as well, but I had the impression it also comes from "network >partners" improperly exiting from an SMTP session, leaving a >partially-completed entry on the "incoming" side. Either way, a zero length >entry that's more than 24 hours old is subject to cancelation at my sites. >(My rule!) > That's possible too; I assume in the entry above that it was a local user sending to a local user via MX. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sat, 02 Oct 1993 07:11:19 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Securing a mailing list. Message-ID: <28d7jb$aon@lohengrin.umkc.edu> From: Date: 30 Sep 1993 00:00:43 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET First, I'm new to MX and must congratulate MadGoat software on a product I am very impressed with. Now the question, is there any real way to _secure_ a mailing list from people adding themselves to it? I know that it is possible to spoof the mailer and someone whom you don't want access to the list can add/remove themselves from it. What I'm wondering is if it is possible to run the MLF agent _without_ BYPASS & READALL and then setting the protection on the .MAILING_LIST to deny system & owner write and delete access to it? Then we could write a little utility the system manager could run to add/remove people to the mailing lists manually thereby securing the list. Do able? -=Brian ================================================================================ Archive-Date: Sat, 02 Oct 1993 10:50:06 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: help with SMTP delivery problems Message-ID: <28jv53INN47d@gap.caltech.edu> From: Date: 2 Oct 1993 13:19:31 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <289gpj$fj7@samba.oit.unc.edu>, sherman@trln.lib.unc.edu (dennis r. sherman) writes: =I'm having a lot of mail bouncing back for no reason I can determine =by myself -- so Help! = =VMS 5.4-3 Y'know, this *IS* VMS, not Unix. Error status actually means something. =28-SEP-1993 09:58:00.98 SMTP_SEND: Attempting to start session with PS.UIB.ES [130.206.33.5] =28-SEP-1993 09:58:05.76 -- failed, status=00000294 $ WRITE SYS$OUTPUT F$MESSAGE(%X294) %SYSTEM-F-REJECT, connect to network object rejected The remote system isn't accepting SMTP connect requests. =28-SEP-1993 09:58:05.88 SMTP_SEND: Attempting to start session with ITS.NLC-BNC.CA [142.78.40.21] =28-SEP-1993 09:59:21.01 -- failed, status=0000022C $ WRITE SYS$OUTPUT F$MESSAGE(%X22C) %SYSTEM-F-TIMEOUT, device timeout Your system was unable to connect to the remote system. =28-SEP-1993 09:59:21.13 SMTP_SEND: Attempting to start session with BK2000.PKO.DEC.COM [16.124.0.69] =28-SEP-1993 09:59:21.23 -- failed, status=00002094 =28-SEP-1993 09:59:21.24 SMTP_SEND: Failed, sts=00002094 $ WRITE SYS$OUTPUT F$MESSAGE(%X2094) %SYSTEM-F-UNREACHABLE, remote node is not currently reachable There was no path to the remote system. =When I check the status of any of the sites returning a status code of =294, they are alive. (UCX LOOP, equivalent to PING) That makes sense, since the 294 means that the remote system responded to you SMTP connect request by rejectin it. Were the system not alive, it couldn't have so responded. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Sat, 02 Oct 1993 10:59:46 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Securing a mailing list. Message-ID: <1993Oct2.091836.103@buckie.hsc.colorado.edu> From: Date: 2 Oct 93 09:18:36 MDT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <28d7jb$aon@lohengrin.umkc.edu>, mckeever@CSTP.UMKC.EDU (Brian McKeever) writes: >First, I'm new to MX and must congratulate MadGoat software on a product I >am very impressed with. > >Now the question, is there any real way to _secure_ a mailing list from >people adding themselves to it? I know that it is possible to spoof the >mailer and someone whom you don't want access to the list can add/remove >themselves from it. What I'm wondering is if it is possible to run the MLF >agent _without_ BYPASS & READALL and then setting the protection on the >.MAILING_LIST to deny system & owner write and delete access to >it? Should be possible, but it depends on how MLF is opening the files. Edit MX_EXE:MX_START.COM. There's no problem with leaving READALL enabled, though. >Then we could write a little utility the system manager could run to >add/remove people to the mailing lists manually thereby securing the list. >Do able? If/when changes are made to the format of list.MAILING_LIST you'd be sortof out of luck. If a list is so sensitive you're concerned about someone spoofing mail to get onto the list, I'd try setting it up with a bogus owner that won't get past MX's address checking, and also setting up your "system" users with bogus owners, something like "<<>>" might work towards that end. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Sat, 02 Oct 1993 20:03:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 02 Oct 1993 17:57:45 PDT From: "W. Todd Wipke" Reply-To: MX-List@WKUVX1.BITNET To: list-mgr@WKUVX1.BITNET, mx-list@WKUVX1.BITNET Message-ID: <009736D6.1951C6C0.27402@SECS.UCSC.EDU> Subject: RE: how to install bulletin with MX-mail >At the risk of not reading this documentation either, I ask a couple of >question of general interest. > >1) Do I understand correctly that this software can be used to gateway > a mailing list into a Usenet newsgroup? BULLETIN does not funnel a mailing list to a Usenet group. >2) How does the reverse work: How does one retreive messages from > a newsserver and forward them to a mailing list? (Of course, this > process filters out messages that originated from the mailing list > in the first place.) It doesn't do this either. However it is great as a local or network bulletin board to which you can have lists automatically posted and you can post via vms MAIL through MX and the bulletin SITE code, AND you can read Usenet and your local lists with the same program and the same commands, including the ability to copy from Usenet to a local list which gives you control over when it will be purged, and you can individually change its expire date or make the local msg permanent. -Todd Wipke wipke@chemistry.ucsc.edu ================================================================================ Archive-Date: Sun, 03 Oct 1993 01:36:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sun, 03 Oct 1993 09:35:11 +0300 From: syseng@BHUOB00.BITNET Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET Message-ID: <00973759.0E84A4A0.7507@bhuob00> Subject: MX Prefix Reply Dear All, Did any one uses MX Prefix, if so did one try to use it as a mail reply, it must be defined as mail$protocol_"prefix" to mx_mailshr, using it as a mail transport it failed and bounce the mail in a strange header formats, any help ? thanks in advance. Nader Nasry. ================================================================================ Archive-Date: Sun, 03 Oct 1993 07:56:56 CDT Sender: list-mgr@WKUVX1.BITNET Return-Path: Date: Sat, 2 Oct 93 23:26:27 1V Message-ID: <0097370404BE8260.0000BA3D@tanuki.twics.co.jp> From: "Tim Burress" Reply-To: MX-List@WKUVX1.BITNET Subject: Question about MX->uucp COM infinite loop To: mx-list@WKUVX1.BITNET Lately we've been running into the known problem with MX->uucp going into a compute-bound loop when UUCP_MAILSHR fails to deal with the MX temporary file. I'm having to reset the thing at least once a day, in fact, so I wonder if someone could give me some background on what exactly is happening. If I can solve it by an upgrade to UUCP, so much the better, but if I have to, I'll try to get people to stop doing whatever they're doing. Quite often when this happens, the message at the top of queue is from a NeXT machine, so maybe they're attaching something. We have MX 3.1C (soon to upgrade to 3.3 -- any gotchas I should know about?), DECUS UUCP 2.2, and Multinet 3.2 on VMS 5.5. Thanks! -- Tim Burress Internet: burress@twics.co.jp Twics/International Education Center 1-21 Yotsuya, Shinjuku-ku, Tokyo 160 Japan ================================================================================ Archive-Date: Sun, 03 Oct 1993 08:03:47 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <0097374C.323AA4B5.3746@WKUVX1.BITNET> Return-Path: <@ULKYVM.LOUISVILLE.EDU:wipke@SECS.UCSC.EDU> Date: Sat, 02 Oct 1993 17:57:45 PDT From: "W. Todd Wipke" Reply-To: MX-List@WKUVX1.BITNET To: list-mgr@WKUVX1.BITNET, mx-list@WKUVX1.BITNET Subject: RE: how to install bulletin with MX-mail >At the risk of not reading this documentation either, I ask a couple of >question of general interest. > >1) Do I understand correctly that this software can be used to gateway > a mailing list into a Usenet newsgroup? BULLETIN does not funnel a mailing list to a Usenet group. >2) How does the reverse work: How does one retreive messages from > a newsserver and forward them to a mailing list? (Of course, this > process filters out messages that originated from the mailing list > in the first place.) It doesn't do this either. However it is great as a local or network bulletin board to which you can have lists automatically posted and you can post via vms MAIL through MX and the bulletin SITE code, AND you can read Usenet and your local lists with the same program and the same commands, including the ability to copy from Usenet to a local list which gives you control over when it will be purged, and you can individually change its expire date or make the local msg permanent. -Todd Wipke wipke@chemistry.ucsc.edu ================================================================================ Archive-Date: Sun, 03 Oct 1993 11:51:29 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: help with SMTP delivery problems Date: 3 Oct 1993 14:51:40 GMT Message-ID: <28motsINNqsp@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <28c73j$2vu@samba.oit.unc.edu>, sherman@trln.lib.unc.edu (dennis r. sherman) writes: =What does the sts=00000870 mean? Is it really End of File? What file? Whichever file your TCP/IP package uses for name resolution requests. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Mon, 04 Oct 1993 03:39:28 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: help with SMTP delivery problems Message-ID: <199310011023.AA05915@desert.ihep.su> From: Date: Fri, 01 Oct 93 13:23:26 +0300 Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Hunter Goatley, WKU (goathunter%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU) wrote: : >What does the sts=00000870 mean? Is it really End of File? What : >file? : > : I'm pretty sure that that's what UCX returns when it gets no response : from the domain name server when it tries to look up the name. ... or when there is no nameservers defined and static host table does not contain the target host. Use UCX SET NAME/SERVER=a.b.c.d to define nameserver(s). -- Igor Mandrichenko ================================================================================ Archive-Date: Mon, 04 Oct 1993 03:39:38 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: SMTP process dying Message-ID: <199310011026.AA05924@desert.ihep.su> From: Date: Fri, 01 Oct 93 13:26:30 +0300 Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Andy, Systems Manager (udaa055@bay.cc.kcl.ac.uk) wrote: : Dear All, : Twice now, in the space of two days, I have had the MX SMTP process (outgoing : stuff) die with an access violation. The Only entry in the SMTP log is: : 24-SEP-1993 17:16:11.83: MX SMTP (pid 23A01326) starting : 27-SEP-1993 21:11:39.90: MX SMTP (pid 23A01326) exiting, status = 1000000C : The error code translates to: : %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual address=!XL, : PC=!XL, PSL=!XL Try also to switch on debugging of NETLIB by defining system logical NETLIB_DEBUG="TRUE". -- Igor Mandrichenko ================================================================================ Archive-Date: Mon, 04 Oct 1993 03:40:24 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 4 Oct 93 04:07 GMT From: Lindsey Hurtel Crawley <0005668166@mcimail.com> Reply-To: MX-List@WKUVX1.BITNET To: MX mailinglist To: VMSNET list Subject: MX SITE->MX->UUCP causes blank in header Message-ID: <60931004040706/0005668166PK3EM@mcimail.com> I'm having a problem when using the MX (3.3) SITE Transport Interface with UUCP (2.0) as a delivery agent. A line is inserted between the UUCP and MX 'Recieved:' strings in the header, and the UA can't find the From and Subject fields that follow. There is no problem when sending to the same user though MX's LOCAL delivery channel. To add insult to injury, it worked before I re-installed the s/w (to learn it better :) Thanks for any and all much needed help, samples follow Lindsey Crawley ----------------------------------------------------------------------- (bad message) From: UUCP%"(Cannot determine sender)" 3-OCT-1993 19:21:39.93 To: CC: Subj: From SQLFIN.COM!rperot Sun, 03 Oct 1993 19:21:31 EST Received: by lyceum.com (DECUS UUCP /2.0/2.0/2.0/); Sun, 3 Oct 93 19:21:38 EST Received: by lyceum.com (MX V3.3 VAX) with SITE; Sun, 03 Oct 1993 19:21:28 EST Date: 1993-06-03 19:14 From: rperot@SQLFIN.COM Subject: t To: LCRAWLEY@CRL.COM To: LCRAWLEY@LYCEUM.COM test text ---------------------------------------------------------------------- (message that worked before s/w reinstall) From: UUCP%"jbrown@LYCEUM.COM" 24-AUG-1993 20:35:23.70 To: lcrawley@lyceum.com CC: Subj: 2 to:s,3 attach, somewhat long message - From LYCEUM.COM!jbrown Tue, 24 Aug 1993 20:35:19 EST Received: by lycvs1.lyceum.com (DECUS UUCP /2.0/2.0/2.0/); Tue, 24 Aug 93 20:35:21 EST Received: by lycvs1.lyceum.com (MX V3.3 VAX) with SITE; Tue, 24 Aug 1993 20:35:15 EST Date: 1993-07-24 20:24 From: jbrown@LYCEUM.COM Subject: 2 to:s,3 attach, somewhat long message - To: lcrawley@lyceum.com To: lcrawley@crl.com Test message text ================================================================================ Archive-Date: Mon, 04 Oct 1993 04:29:40 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: MX in a mixed VAX AXP environment possible ? Date: 4 Oct 1993 08:51:23 GMT Message-ID: <28oo6b$aa4@hermes.uni-konstanz.de> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET The subject says it all: I plan to use mx033 for vax/vms 5.4-2 and OpenVMS 1.5 in a clustered environment. Is this possible?? regards Eberhard ================================================================================ Archive-Date: Mon, 04 Oct 1993 05:45:41 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 4 Oct 1993 06:43:21 -0400 From: olin@cheme.cornell.edu Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9310041043.AA09545@arkle.cheme.cornell.edu> To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Subject: Re: MX in a mixed VAX AXP environment possible ? Yes, it is possible to use MX 3.3 in a mixed VAX/AXP cluster. I have been doing it for several months with no problems whatsoever. Steve ================================================================================ Archive-Date: Mon, 04 Oct 1993 06:12:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 04 Oct 1993 06:11:33 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00973805.C681CE91.4336@WKUVX1.BITNET> Subject: RE: MX in a mixed VAX AXP environment possible ? writes: > >The subject says it all: > >I plan to use mx033 for vax/vms 5.4-2 and OpenVMS 1.5 in a clustered >environment. > >Is this possible?? > Yes, MX V3.3 was designed to allow this. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Mon, 04 Oct 1993 09:08:52 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 04 Oct 1993 09:08:12 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097381E.73831F92.4422@WKUVX1.BITNET> Subject: RE: Question about MX->uucp COM infinite loop "Tim Burress" writes: > >Lately we've been running into the known problem with MX->uucp going into a >compute-bound loop when UUCP_MAILSHR fails to deal with the MX temporary file. >I'm having to reset the thing at least once a day, in fact, so I wonder if >someone could give me some background on what exactly is happening. If I can >solve it by an upgrade to UUCP, so much the better, but if I have to, I'll >try to get people to stop doing whatever they're doing. > The problem is caused by a certain character in a certain position in the file read by UUCP. I've forgotten the specifics; I didn't bother distributing my patch because the UUCP guys told me there'd be a new version soon that would have the fix. As far as I know, they haven't done so yet, and I didn't bother keeping my fixed version around. Sorry. It sounds like they may be trying to send binary files through? It can happen with regular text, but happens frequently when a user mistakenly tries to mail a binary file. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 05 Oct 1993 07:56:23 CDT Sender: list-mgr@WKUVX1.BITNET Subject: A Modified Name_conversion.c module CODE! Message-ID: <1993Oct5.132418.814@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 5 Oct 93 13:24:17 +1000 To: MX-List@WKUVX1.BITNET Below is the code to do a nickname lookup based on a file and replace the FQDN part of an address. P Mederly (who I believe is on this list but I've lost his address. :-( ) did all the major work. I've just added a bit to handle Mailworks users going via MRGATE. (But NOT All-In-1 users, we use SPECIAL.COM for that.) Carl. ---------- Cut Here ---------------- /* !++ ! ! MODULE: NAME_CONVERSION ! ! FACILITY: MX examples ! ! ABSTRACT: Example of site-installable nickname conversion. ! ! MODULE DESCRIPTION: ! ! This module contains routines for use by MX modules (specifically, ! the MX_MAILSHR interface to VMS Mail and the MX_ROUTER agent process) ! for translating between actual VMS usernames and site-specific aliases. ! ! This module contains a fairly primitive lookup table to implement ! the translation. ! ! To use this module: MODIFY IT AS NEEDED FOR YOUR SITE, then compile it ! and link it with the commands: ! ! $ cc name_conversion ! $ link/share/notrace name_conversion,sys$input:/opt ! sys$share:vaxcrtl/share ! universal=init,convert,cleanup ! ! ! Then copy it to MX_EXE and make it available with the commands: ! ! $ copy name_conversion.exe mx_exe:*.*;0/protection=w:re ! $ install create mx_exe:name_conversion/share/open/header ! $ define/system/exec mx_site_name_conversion mx_exe:name_conversion ! ! Define logicals mentioned below and restart MX - originally here was ! just the instruction to reset router ($ mcp reset router), but I saw ! it not sufficient. That is why I use shutdown/restart (vers. MX 3.2) ! ! $ mcp shutdown ! $ @sys$startup:mx_startup ! ! (You need a suitably privileged account to do this.) ! ! (Also remember to install the image on all nodes of the cluster if ! applicable and do an MCP SHUTDOWN/CLUSTER.) ! ! This module contains name conversion routines that convert ! recipient addresses in the messages going from MX to VMSmail ! to their corresponding VMS usernames. ! ! It also converts sender address in the messages going from VMSmail ! to MX into addresses: ! ! 1) extracts USERNAME and NODEn (if present) from sender address ! which is in one of the forms: ! ! NODE1::NODE2::...::NODEn::USERNAME ! ...MRGATE::"...::USERNAME" ! ! 2) tries to find nickname for the USERNAME and ! creates address: nickname@MX_SITE_AUTHORIZED_DOMAIN or ! nickname@other_domain ! ! for authorized users and ! ! USERNAME@MX_SITE_NOT_AUTHORIZED_DOMAIN or ! USERNAME@NODEn.MX_SITE_NOT_AUTHORIZED_DOMAIN ! ! for not authorized users. ! ! User is authorized iff he/she is included in the table users[]. ! Table users[] is taken from the file MX_SITE_ALIASES, which has lines ! in the form: ! ! username nickname domainname ! ! Where username is user's username without any information about node name. ! nickname is user's nickname, in most cases it is Firstname.Lastname ! domainname is not required - if specified, it is the domain ! part of the adress. It should not contain '@'. ! ! An example - the following line will cause that mail from user PAKO ! on any node will have the "From:" address ! ! pako John.Pako foo.com ! ! Logical names (define them /system): ! ! MX_SITE_AUTHORIZED_DOMAIN - default domain name for users listed in the ! file MX_SITE_ALIASES (e.g. "myorg.com") ! ! MX_SITE_NOT_AUTHORIZED_DOMAIN - suffix of the domain name for users not ! listed in the file MX_SITE_ALIASES ! (e.g. "dnet.myorg.com") ! ! MX_SITE_ALIASES - file with aliases (e.g. MX_DIR:ALIASES.TXT) ! This file should be world-readable. ! ! ! AUTHOR: M. Madison ! COPYRIGHT ) 1990, RENSSELAER POLYTECHNIC INSTITUTE. ! ! THIS SOFTWARE IS PROVIDE "AS IS". NEITHER THE AUTHOR NOR RENSSELAER ! MAKE ANY GUARANTEES REGARDING THE SUITABILITY, RELIABILITY, SECURITY, ! USEFULNESS, OR PERFORMANCE OF THIS SOFTWARE. >>USE AT YOUR OWN RISK. ! ! CREATION DATE: 03-DEC-1990 ! ! MODIFICATION HISTORY: ! ! 03-DEC-1990 V1.0 Madison Initial coding. ! ! 07-MAR-1991 V1.1 Ake Added support for non-MX nodes mailing ! into MX generating a decent return address ! ! 25-Sep-1991 V1.2 Ake Had a problem with addresses coming in that ! looked like node1::node2::mrgate::"A1::user" ! so I decided to ignore those addresses with ! a double-quote in already. ! ! 12-Mar-1992 V1.3 Ake Since Matt now supports translating MRGATE ! addresses, I have now changed the C code ! to also support this. mrgate::"node::user" ! now is translated to user%node.mrgate. ! ! 2-Jun-1993 V1.4 Mederly Changed form user%node.dnet@domain to ! user@node.domain; moved table users[] to ! disk file; distinguishes between authorized ! and not authorized users; avoids return ! SS$_NORMAL when it could cause MX to ! loop when calling CONVERT ! Don't recognize node and UA name when ! sending from MRGATE (as the previous ! version did) - sorry. ! ! ! 15-Aug-1993 V1.4.1 Makin Added a small bit to assume ALL ! mail coming via MRGATE is from Mailworks ! and to create addresses in the form ! @am. ! It's ugly as it's hardcoded in. ! If you have All-In-1 usernames WITHOUT ! spaces then you can possibly modify this to work ! however the spaces really stuff things up. !-- */ #include descrip #include string #include stdio #include ssdef #include str$routines #include lib$routines #define NICK_TO_ADDRESS 1 #define USERNAME_TO_NICK 2 #define MAX_USERS 1000 static struct users { char vms_name[15], full_name[51], domain[51]; } users[MAX_USERS]; static int number_of_users = 0; /* read_in_progress - set by the initialization routine while it reads the file MX_SITE_ALIASES. Perhaps it is not necessary, because I suppose that every process has its own copy of the NAME_CONVERSION module data. */ static int read_in_progress = 0; static $DESCRIPTOR(dcolon, "::"); static $DESCRIPTOR(dquote, "\""); static $DESCRIPTOR(mrgate_dcolon, "MRGATE::\""); static $DESCRIPTOR(lbrack, "<"); static $DESCRIPTOR(rbrack, ">"); static $DESCRIPTOR(atsign, "@"); static $DESCRIPTOR(percent, "%"); static $DESCRIPTOR(period, "."); /* static $DESCRIPTOR(dnet, "dnet"); */ /* static $DESCRIPTOR(mrgate, "mrgate"); */ static $DESCRIPTOR(am, "am"); struct context { struct dsc$descriptor localnode, authorized, not_authorized; }; /* init_dynamic_descriptor - initializes dynamic descriptor */ static void init_dynamic_descriptor(struct dsc$descriptor *d) { d->dsc$b_dtype = DSC$K_DTYPE_T; d->dsc$b_class = DSC$K_CLASS_D; d->dsc$w_length = 0; d->dsc$a_pointer = NULL; } /* init_static_descriptor - initializes static descriptor */ static void init_static_descriptor(struct dsc$descriptor *d, char *string) { d->dsc$b_dtype = DSC$K_DTYPE_T; d->dsc$b_class = DSC$K_CLASS_S; d->dsc$w_length = strlen(string); d->dsc$a_pointer = string; } /* !++ ! ! ROUTINE NAME: INIT ! ! FUNCTIONAL DESCRIPTION: ! ! Allocates and initializes context block for subsequent name conversions. ! ! RETURNS: cond_value, longword (unsigned), write only, by value ! ! PROTOTYPE: ! ! INIT ctxptr ! ! ctxptr: pointer, longword (unsigned), modify, by reference ! ! IMPLICIT INPUTS: None. ! ! IMPLICIT OUTPUTS: None. ! ! COMPLETION CODES: ! ! SS$_NORMAL: normal successful completion. ! ! SIDE EFFECTS: ! ! None. !-- */ unsigned int init (struct context **ctx) { int ctxsize, status; $DESCRIPTOR(mx_node_name, "MX_NODE_NAME"); $DESCRIPTOR(mx_site_authorized, "MX_SITE_AUTHORIZED_DOMAIN"); $DESCRIPTOR(mx_site_not_authorized, "MX_SITE_NOT_AUTHORIZED_DOMAIN"); ctxsize = sizeof(struct context); status = lib$get_vm (&ctxsize, ctx); if (status != SS$_NORMAL) return status; init_dynamic_descriptor(&(*ctx)->localnode); init_dynamic_descriptor(&(*ctx)->authorized); init_dynamic_descriptor(&(*ctx)->not_authorized); status = lib$sys_trnlog (&mx_node_name, 0, &(*ctx)->localnode); if (status != SS$_NORMAL) return status; status = lib$sys_trnlog (&mx_site_authorized, 0, &(*ctx)->authorized); if (status != SS$_NORMAL) return status; status = lib$sys_trnlog (&mx_site_not_authorized, 0, &(*ctx)->not_authorized); if (status != SS$_NORMAL) return status; while (read_in_progress) sleep(1); if (number_of_users == 0) { char buffer[1001], *p, *q; FILE *fp; read_in_progress = 1; fp = fopen("MX_SITE_ALIASES", "r"); if(fp != NULL) { while(number_of_users < MAX_USERS) { if(fgets(buffer, 1000, fp) == NULL) break; for(p=buffer; *p == ' ' || *p == '\t'; p++); if(*p == '!' || *p == '#') continue; for(q=users[number_of_users].vms_name; *p && *p != ' ' && *p != '\t' && *p != '\n'; *(q++) = *(p++)); *q = 0; while(*p == ' ' || *p == '\t') p++; for(q=users[number_of_users].full_name; *p && *p != ' ' && *p != '\t' && *p != '\n'; *(q++) = *(p++)); *q = 0; while(*p == ' ' || *p == '\t') p++; for(q=users[number_of_users].domain; *p && *p != ' ' && *p != '\t' && *p != '\n'; *(q++) = *(p++)); *q = 0; if(*users[number_of_users].vms_name && *users[number_of_users].full_name) number_of_users++; } fclose(fp); } read_in_progress = 0; } return SS$_NORMAL; } /* init */ /* !++ ! ! ROUTINE NAME: FULL_CONVERT ! ! FUNCTIONAL DESCRIPTION: ! ! Converts username -> alias address (full address substitution) ! ! Unlike the CONVERT routine, FULL_CONVERT converts a username ! to a complete RFC822-type address. You must be running MX V3.1C ! or later to use this feature. ! ! NB: You MUST use STR$ routines to copy result to OUTSTR parameter ! to ensure proper operation!!!! ! ! You _may_ safely assume that INSTR is compatible with a DTYPE_T, ! CLASS_S (standard fixed-length) string descriptor. ! ! RETURNS: cond_value, longword (unsigned), write only, by value ! ! PROTOTYPE: ! ! FULL_CONVERT ctxptr, code, instr, outstr ! ! ctxptr: pointer, longword (unsigned), modify, by reference ! code: longword_unsigned, longword (unsigned), read only, by reference ! instr: char_string, character string, read only, by descriptor (fixed) ! outstr: char_string, character string, write only, by descriptor ! ! IMPLICIT INPUTS: None. ! ! IMPLICIT OUTPUTS: None. ! ! COMPLETION CODES: ! ! SS$_NORMAL: normal successful completion. ! ! SIDE EFFECTS: ! ! None. !-- */ static int is_reasonable(char c) { return((c>='A' && c<='Z') || (c>='a' && c<='z') || (c>='0' && c<='9') || c=='.' || c=='_' || c=='$'); } static void to_lower(char *p) { if(*p >= 'A' && *p <= 'Z') (*p) += 32; } unsigned int full_convert (struct context **ctx, int *code, struct dsc$descriptor *instr, struct dsc$descriptor *outstr) { struct dsc$descriptor tmp, tmp2; struct dsc$descriptor username, nodename; int i, j, dcolon_loc, dquote_loc, mrgate_loc, retstat; if (*code != USERNAME_TO_NICK) return 0; mrgate_loc = str$position(instr, &mrgate_dcolon); dquote_loc = str$position(instr, &dquote); dcolon_loc = str$position(instr, &dcolon); init_static_descriptor(&username, ""); init_static_descriptor(&nodename, ""); if(dquote_loc == 0 && mrgate_loc == 0) { /* !++ ! ! Instr has one of the forms: ! ! VMS_USERNAME ! LASTNODE::VMS_USERNAME ! NODE1::NODE2::...::LASTNODE::VMS_USERNAME ! ! We're going to fill in "username" and "nodename". ! !-- */ username.dsc$a_pointer = instr->dsc$a_pointer; username.dsc$w_length = instr->dsc$w_length; nodename.dsc$w_length = 0; while((i=str$position(&username, &dcolon)) != 0) { nodename.dsc$a_pointer = username.dsc$a_pointer; nodename.dsc$w_length = username.dsc$w_length; username.dsc$a_pointer += i+1; username.dsc$w_length -= i+1; } /* At this moment "username" contains VMS_USERNAME and "nodename" contains LASTNODE::VMS_USERNAME or nothing (""). We are to truncate "nodename" to contain only LASTNODE (or nothing). */ if(nodename.dsc$w_length) nodename.dsc$w_length -= (username.dsc$w_length + 2); } else { /* !++ ! ! Instr contains either " or MRGATE::" ! ! We will only try to acquire user name from Instr. Information about the ! node name is lost. ! ! We suppose that the user name is the last element of the address, which ! can be like NODE::MRGATE::"NODE::USER_AGENT::USERNAME". So we are going ! from the end of the Instr and note when we find first "reasonable" character ! (A-Z, 0-9, _, $, .). Then we continue and try to find first character ! which is not "reasonable" and thus we determine the begin and end ! of the the user name. ! ! If the result does not make sense (we find no "reasonable" characters) ! the string returned is "unknown-user". ! !-- */ char *pointer, *beginning, *end; pointer = instr->dsc$a_pointer; end = instr->dsc$a_pointer + instr->dsc$w_length - 1; while(end >= pointer && !is_reasonable(*end)) end--; beginning = end; while(beginning >= pointer && is_reasonable(*beginning)) beginning--; if(end <= beginning) init_static_descriptor(&username, "unknown-user"); else { username.dsc$a_pointer = beginning+1; username.dsc$w_length = end - beginning; } nodename.dsc$w_length = 0; } /* !++ ! ! Well, we have the user name in the string "username" and the node name ! (if any) in the string "nodename". Now we're going to find the user's ! name in the aliases table. ! ! If we find it there, the resulting address will be (depending on ! whether the user's "domain" record is empty) ! ! ! or ! ! and if not, it will be (depending on whether nodename is empty) ! ! ! or ! !-- */ retstat = 0; init_dynamic_descriptor(&tmp); init_static_descriptor(&tmp2, ""); for (i = 0; i < number_of_users; i++) { tmp2.dsc$w_length = strlen(users[i].vms_name); tmp2.dsc$a_pointer = users[i].vms_name; if (str$case_blind_compare(&username, &tmp2) == 0) { j = strlen(users[i].full_name); str$copy_r(&tmp, &j, users[i].full_name); if(*users[i].domain) { struct dsc$descriptor domdsc; init_static_descriptor(&domdsc, users[i].domain); str$concat(outstr, &tmp, &atsign, &domdsc); } else str$concat(outstr, &tmp, &atsign, &(*ctx)->authorized); str$free1_dx(&tmp); retstat = SS$_NORMAL; break; } } if(retstat == 0) { for(i=0; inot_authorized); else str$concat(outstr, &username, &atsign, &am, &period, &(*ctx)->not_authorized); else { for(i=0; inot_authorized); } retstat = SS$_NORMAL; } return retstat; } /* full_convert */ /* !++ ! ! ROUTINE NAME: CONVERT ! ! FUNCTIONAL DESCRIPTION: ! ! Converts username -> nickname or nickname -> RFC821-address. ! ! NB: You MUST use STR$ routines to copy result to OUTSTR parameter ! to ensure proper operation!!!! ! ! You _may_ safely assume that INSTR is compatible with a DTYPE_T, ! CLASS_S (standard fixed-length) string descriptor. ! ! RETURNS: cond_value, longword (unsigned), write only, by value ! ! PROTOTYPE: ! ! CONVERT ctxptr, code, instr, outstr ! ! ctxptr: pointer, longword (unsigned), modify, by reference ! code: longword_unsigned, longword (unsigned), read only, by reference ! instr: char_string, character string, read only, by descriptor (fixed) ! outstr: char_string, character string, write only, by descriptor ! ! IMPLICIT INPUTS: None. ! ! IMPLICIT OUTPUTS: None. ! ! COMPLETION CODES: ! ! SS$_NORMAL: normal successful completion. ! 0: no translation occurred ! ! SIDE EFFECTS: ! ! None. !-- */ unsigned int convert (struct context **ctx, int *code, struct dsc$descriptor *instr, struct dsc$descriptor *outstr) { struct dsc$descriptor tmp, tmp2, tmp3; int i, j, retstat; init_dynamic_descriptor(&tmp); init_static_descriptor(&tmp2, ""); init_static_descriptor(&tmp3, ""); /* !++ ! Local alias -> address ! ! This code should return a status of SS$_NORMAL if an alias is found, ! 0 otherwise. ! ! If an alias is found, the resulting string MUST BE IN RFC821 format: ! ! ! ! >>>>>> EVEN IF THE ADDRESS IS FOR THE LOCAL HOST (so you have to ! look up MX_NODE_NAME and tack it on after the translated name, ! if you're just doing a local-host user directory). !-- */ retstat = 0; switch(*code) { case NICK_TO_ADDRESS: for (i = 0; i < number_of_users; i++) { tmp2.dsc$w_length = strlen(users[i].full_name); tmp2.dsc$a_pointer = users[i].full_name; tmp3.dsc$w_length = strlen(users[i].vms_name); tmp3.dsc$a_pointer = users[i].vms_name; if (str$case_blind_compare(instr, &tmp2) != 0) continue; /* We find a line where full name specified in it equals to Instr. If by accident vms_name == full_name, no conversion need to be done and we MUST return 0, because if we do not, MX would go into infinite loop translating the same name again and again. */ if(str$case_blind_compare(&tmp2, &tmp3) == 0) break; /* The usual case - vms_name != full_name: we return the address */ str$concat(outstr, &lbrack, &tmp3, &atsign, &(*ctx)->localnode, &rbrack); retstat = SS$_NORMAL; break; } break; case USERNAME_TO_NICK: str$copy_dx(outstr, instr); /* Pre-V3.1 compatibility */ break; } return retstat; } /* convert */ /* !++ ! ! ROUTINE NAME: CLEANUP ! ! FUNCTIONAL DESCRIPTION: ! ! Deallocates context block allocated by init routine. ! ! RETURNS: cond_value, longword (unsigned), write only, by value ! ! PROTOTYPE: ! ! CLEANUP ctxptr ! ! ctxptr: pointer, longword (unsigned), modify, by reference ! ! IMPLICIT INPUTS: None. ! ! IMPLICIT OUTPUTS: None. ! ! COMPLETION CODES: ! ! SS$_NORMAL: normal successful completion. ! ! SIDE EFFECTS: ! ! None. !-- */ unsigned int cleanup (struct context **ctx) { int ctxsize, status; status = str$free1_dx(&(*ctx)->localnode); if (status != SS$_NORMAL) return status; status = str$free1_dx(&(*ctx)->authorized); if (status != SS$_NORMAL) return status; status = str$free1_dx(&(*ctx)->not_authorized); if (status != SS$_NORMAL) return status; ctxsize = sizeof(struct context); status = lib$free_vm (&ctxsize, ctx); if (status != SS$_NORMAL) return status; *ctx = NULL; return SS$_NORMAL; } /* cleanup */ -- Carl Makin (VK1KCM) makinc@hhcs.gov.au (Internet) / vk1kcm@vk1kcm.act.aus.oc (Amprnet) 'The best book on programming for the layman is "Alice in Wonderland"; but that's because it's the best book on anything for the layman.' ================================================================================ Archive-Date: Tue, 05 Oct 1993 11:10:32 CDT Sender: list-mgr@WKUVX1.BITNET Subject: MX PATCH TO ELIMINATE MX PREFIX Message-ID: <28s2h9$mju@news.ysu.edu> From: Reply-To: MX-List@WKUVX1.BITNET Date: 5 Oct 1993 15:06:17 GMT To: MX-List@WKUVX1.BITNET Is the patch on ftp.spc.edu in the mx.contrib directory valid for vms 6.0? thanks tony -- *********************************************************** standard disclaimers apply Too much too soon too fast - Zippy the Pinhead ================================================================================ Archive-Date: Tue, 05 Oct 1993 11:14:39 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 05 Oct 1993 11:13:36 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009738F9.22A897D3.4899@WKUVX1.BITNET> Subject: RE: MX PATCH TO ELIMINATE MX PREFIX writes: > >Is the patch on ftp.spc.edu in the mx.contrib directory >valid for vms 6.0? > Yes. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 05 Oct 1993 11:24:42 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX PATCH TO ELIMINATE MX PREFIX Message-ID: <1993Oct5.100933.114@buckie.hsc.colorado.edu> From: Date: 5 Oct 93 10:09:32 MDT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <28s2h9$mju@news.ysu.edu>, ao363@yfn.ysu.edu (Anthony Spinillo) writes: >Is the patch on ftp.spc.edu in the mx.contrib directory >valid for vms 6.0? Yes, for the 'normal' distribution of V6.0 (not for field-test distributions of "V" 6.0). In any event, be sure to keep a pre-patched copy of the .EXE. -d -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Tue, 05 Oct 1993 12:08:56 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Mailing list archive "summarizer" Message-ID: <1993Oct5.160524.1366@news.arc.nasa.gov> From: Date: Tue, 5 Oct 1993 16:05:24 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Has anyone written a program that scans an MX mailing list archive and produces a summary of the messages in it? Just a listing, one per line, of the date, poster, and subject would do. I know it wouldn't be too hard to write one, but I thought I'd check first to see if someone had one they'd be willing to share. Thanks, -Matt -- Matthew Madison | madison@tgv.com | +1 408 457 5200 TGV, Inc. | 101 Cooper Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Tue, 05 Oct 1993 13:08:26 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Mailing list archive "summarizer" Message-ID: <28s9qt$l04@samba.oit.unc.edu> From: Date: 5 Oct 1993 17:10:53 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET madison@tgv.com (Matt Madison) writes: >Has anyone written a program that scans an MX mailing list archive and >produces a summary of the messages in it? Just a listing, one per line, >of the date, poster, and subject would do. I know it wouldn't be too hard >to write one, but I thought I'd check first to see if someone had one >they'd be willing to share. I don't have exactly what you're looking for, but... I'm using keyword indexing and retrieval tools developed by Bruce Tanner that can produce something similar to what you're looking for. The tools are distributed with the VMS Gopher server (FTP from boombox.micro.umn.edu or niord.shsu.edu, Gopher from psulias.psu.edu, niord.shsu,edu, or trln.lib.unc.edu, look for gopher1_2VMS0-server.zip) I am making several MX mailing list archives available for keyword searching via Gopher -- the hit list returned (as I've got things set up) shows date, subject, and poster. -- Dennis R. Sherman Triangle Research Libraries Network dennis_sherman@unc.edu Univ. of North Carolina - Chapel Hill ================================================================================ Archive-Date: Tue, 05 Oct 1993 14:06:15 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 05 Oct 1993 15:04:29 EDT From: smcneilly@fred.bsc.mass.edu Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <00973919.63D55500.8698@fred.bsc.mass.edu> Subject: Help on MX_BULL I'm trying to install MX_BULL. BULLETIN has been up and running for quite some time, and appears to be working properly. When I ran BUILD_MX_BULL, I got the following results: $ define /system bull_source duc1:[users.bulletin] $ @build_mx_bull Compiling MX_BULL.... Linking MX_BULL.... %LINK-W-NUDFSYMS, 3 undefined symbols: %LINK-I-UDFSYM, CTL$GL_IMGHDRBF %LINK-I-UDFSYM, CTL$T_ACCOUNT %LINK-I-UDFSYM, CTL$T_USERNAME %LINK-W-USEUNDEF, undefined symbol CTL$T_ACCOUNT referenced in psect CODE offset %X0000004F in module READ_HEADER file DUC1:[USERS.BULLETIN]BULL.OLB;1 %LINK-W-USEUNDEF, undefined symbol CTL$T_USERNAME referenced in psect SETUSER_CODE offset %X00000081 in module READ_HEADER file DUC1:[USERS.BULLETIN]BULL.OLB;1 %LINK-W-USEUNDEF, undefined symbol CTL$GL_IMGHDRBF referenced in psect READ_HEADER offset %X00000010 in module READ_HEADER file DUC1:[USERS.BULLETIN]BULL.OLB;1 Build of MX_BULL.EXE completed $ I didn't know whether these undefined symbols represented a fatal defect or not so I continued with the installation. (I moved MX_BULL.EXE to MX_EXE, defined a path to BULLETIN, defined a rewrite rule, set up SITE_DELIVER.COM, shutdown and restarted MX, etc.) Then I tried to send a message to a folder in BULLETIN. The message just sits in the queue, as shown below. I've enabled debug/trace, but no reference to these messages appears. Help! What did I do wrong? $ mcp MCP> queue show 21295 Entry Status Size Source Agent Entry Status Size ----- ------ ------ ------ ------- ----- ------ ------ 21295 INPROG 46 LOCAL SITE 21298 READY 46 -------------------------------------------------------------------- Scott Mc Neilly email: smcneilly@fred.bsc.mass.edu Assistant Director Phone: 508-697-1236 Information Services Bridgewater State College Bridgewater, MA 02325 --------------------------------------------------------------------- ================================================================================ Archive-Date: Tue, 05 Oct 1993 14:15:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 05 Oct 1993 14:11:35 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00973912.001F6F57.4984@WKUVX1.BITNET> Subject: RE: Help on MX_BULL smcneilly@fred.bsc.mass.edu writes: > >I'm trying to install MX_BULL. BULLETIN has been up and running >for quite some time, and appears to be working properly. >When I ran BUILD_MX_BULL, I got the following results: > >$ define /system bull_source duc1:[users.bulletin] >$ @build_mx_bull >Compiling MX_BULL.... >Linking MX_BULL.... >%LINK-W-NUDFSYMS, 3 undefined symbols: >%LINK-I-UDFSYM, CTL$GL_IMGHDRBF >%LINK-I-UDFSYM, CTL$T_ACCOUNT >%LINK-I-UDFSYM, CTL$T_USERNAME [...] >I didn't know whether these undefined symbols represented a fatal defect >or not so I continued with the installation. (I moved MX_BULL.EXE to >MX_EXE, defined a path to BULLETIN, defined a rewrite rule, set up >SITE_DELIVER.COM, shutdown and restarted MX, etc.) Sounds like BULLETIN has changed since I wrote MX_BULL. It must now be linked with SYS$SYSTEM:SYS.STB/SELECTIVE_SEARCH, apparently. > Then I tried to send a >message to a folder in BULLETIN. The message just sits in the queue, >as shown below. I've enabled debug/trace, but no reference to these >messages appears. > Are you sure MX SITE is running? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 06 Oct 1993 03:35:46 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 06 Oct 1993 08:14:00 +0300 From: syseng@BHUOB00.BITNET Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET Message-ID: <009739A9.36472EC0.8040@bhuob00> Subject: CSNET-RELAY Mails ? Dear All, Some user over here tried to send a mail to CSNET-RELAY but MX Mailer didnot find a route to this address, I searched mailer names and domain names but I didn't find any entry related to CSNET, any help ? Thanks in advance. Nader Nasry. ================================================================================ Archive-Date: Wed, 06 Oct 1993 03:36:53 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX PATCH TO ELIMINATE MX PREFIX Message-ID: <1993Oct5.174229.18376@alpha.montagar.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 5 Oct 93 17:42:29 CDT To: MX-List@WKUVX1.BITNET In article <28s2h9$mju@news.ysu.edu>, ao363@yfn.ysu.edu (Anthony Spinillo) writes: > > Is the patch on ftp.spc.edu in the mx.contrib directory > valid for vms 6.0? I'm not sure, but I have updated the patch for V6.0, and it is available from my file server. Send mail to FILESERV@montagar.com and put the words: SEND VMSMAIL_PATCH in the body of the message. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - David L. Cathey |INET: davidc@montagar.com Montagar Software Concepts |UUCP: ...!montagar!davidc P. O. Box 260772, Plano TX 75026-0772 |Fone: (214)-618-2117 ================================================================================ Archive-Date: Wed, 06 Oct 1993 05:05:28 CDT Sender: list-mgr@WKUVX1.BITNET Return-Path: Message-ID: <9310060919.AA14792@psk2.am.lod.edu.pl> From: Reply-To: MX-List@WKUVX1.BITNET To: MX-list@WKUVX1.BITNET Subject: ignature.mail Date: Wed, 6 Oct 93 10:19:14 CET I'm a novice user of MX so please don't laugh if the question would seem to you very stupid. I can not use list control commands neither as a system_user nor as a list_owner. In both cases I have got the postmaster aswering : "not privileged". While entering MCP show> show system I obtaine the valid address, also MCP> show list gives the proper user addresses. Debugging shows that address is translated properly but checking proper mask (0000010 for add command) fails. Where should I look for the hints to solve the problem? Wojtek ================================================================================ Archive-Date: Wed, 06 Oct 1993 06:50:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 06 Oct 1993 06:46:20 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097399C.F7099CE5.5254@WKUVX1.BITNET> Subject: RE: ignature.mail writes: > >I'm a novice user of MX so please don't laugh if the question would >seem to you very stupid. >I can not use list control commands neither as a system_user nor as a >list_owner. In both cases I have got the postmaster aswering : >"not privileged". >While entering MCP show system >I obtaine the valid address, also MCP> show list >gives the proper user addresses. >Debugging shows that address is translated properly but checking proper mask >(0000010 for add command) fails. >Where should I look for the hints to solve the problem? > Are you sure you matched the case properly? The addresses should look like "wjjankow@PSK2.AM.LOD.EDU.PL". Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 06 Oct 1993 09:21:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 6 Oct 93 13:56 GMT From: Lindsey Hurtel Crawley <0005668166@mcimail.com> Reply-To: MX-List@WKUVX1.BITNET To: MX mailinglist Subject: Re: Re: MX_SITE_IN->MX->UUCP causes blank in header Message-ID: <35931006135653/0005668166PK3EM@mcimail.com> , 0005668166@mcimail.com writes: > I'm having a problem when using the MX (3.3) SITE Transport > Interface (MX_SITE_IN) with UUCP (2.0) as a delivery agent. > > A line is inserted between the UUCP and MX 'Recieved:' strings in the > header, and the UA can't find the From and Subject fields that follow. > > There is no problem when sending to the same user though MX's LOCAL > delivery channel. > >>Off the top of my head... >> >>What is your SITE agent doing? Can you post your SITE_DELIVER.COM? Are >>you sure that it is doing the same thing that it did before you >>reinstalled >>the software? >> >>I could see this behavior if now your SITE agent is doing >> >> $ MAIL some.file "UUCP%""user@dom.ain""" >> >>when before it did >> >> $ MAIL /PROTOCOL=UUCP_MAILSHR some.file "user@dom.ain" >>There is a big difference in those two methods which is reflected in the >>header processing. >>--- Tom >>Tom Allebrandi | At home I have three cats.... >>Inland Steel Research Labs | >>Allebrandi@Research.Inland.Com | ...their names are "/", "." and >>".." ------------------------------------------------------------------------ Thanks for the help, I'm using $MX_EXE:MX_SITE_IN, and have the same problem with or without the 'origin_address', optional third parameter. If a PATH entry is defined to deliver the mail through the LOCAL instead of UUCP channel, it works fine. Other ideas or directions?? Lindsey Crawley lcrawley@mcimail.com ================================================================================ Archive-Date: Wed, 06 Oct 1993 10:11:34 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 06 Oct 1993 11:01:53 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: info-vax@sri.com Message-ID: <009739C0.AA37D980.10590@nscvax.princeton.edu> Subject: RE: CSNET-RELAY Mails ? Nader Nasry writes: > Some user over here tried to send a mail to CSNET-RELAY > but MX Mailer didnot find a route to this address, > I searched mailer names and domain names but I didn't find > any entry related to CSNET, any help ? > CSNET is no longer in operation. According to my information, it shut down in 1991. You can't find CSNET-RELAY because it doesn't exist! ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Wed, 06 Oct 1993 10:43:20 CDT Sender: list-mgr@WKUVX1.BITNET Return-Path: Date: Thu, 7 Oct 93 00:04:45 1V Message-ID: <00973A2E07E40640.00000127@tanuki.twics.co.jp> From: "Tim Burress" Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX PATCH TO ELIMINATE MX PREFIX To: mx-list@WKUVX1.BITNET In article <1993Oct5.100933.114@buckie.hsc.colorado.edu>, dwing@uh01.Colorado.EDU writes: > In article <28s2h9$mju@news.ysu.edu>, ao363@yfn.ysu.edu (Anthony Spinillo) > > In any event, be sure to keep a pre-patched copy of the .EXE. All of which makes me (new to MX) wonder what possible pitfalls I may run into if I install this. It'd be great to be able to do without MX%"", but what price will we pay? I take it that many people are using the patch -- do I give up anything except the prefix? Thanks! -- Tim Burress Internet: burress@twics.co.jp Twics/International Education Center 1-21 Yotsuya, Shinjuku-ku, Tokyo 160 Japan ================================================================================ Archive-Date: Wed, 06 Oct 1993 10:43:56 CDT Sender: list-mgr@WKUVX1.BITNET Return-Path: Date: Thu, 7 Oct 93 00:01:34 1V Message-ID: <00973A2D965B1540.00000127@tanuki.twics.co.jp> From: "Tim Burress" Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Question about MX->uucp COM infinite loop To: mx-list@WKUVX1.BITNET In article <0097381E.73831F92.4422@WKUVX1.BITNET>, "Hunter Goatley, WKU" writes: > It sounds like they may be trying to send binary files through? It can > happen with regular text, but happens frequently when a user mistakenly > tries to mail a binary file. Thanks -- I'll try to contact the DECUS UUCP developers and see if they can at least point me at the code that needs changing. No vacations for me until I can leave mail alone and rely on it to work! We're doubly hexed because in our multi-lingual environment users often have files with 8-bit character codes (especially Japanese). BTW I mistakenly said that we had UUCP 2.2 in my original post. It's 2.0. And I just upgraded to MX 3.3 (expect my registration shortly). Thanks! -- Tim Burress Internet: burress@twics.co.jp Twics/International Education Center 1-21 Yotsuya, Shinjuku-ku, Tokyo 160 Japan ================================================================================ Archive-Date: Wed, 06 Oct 1993 11:02:13 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 6 Oct 1993 10:50:21 -0600 To: mx-list%wkuvx1.bitnet@ulkyvm.louisville.edu From: reef@xenon.che.ilstu.edu Reply-To: MX-List@WKUVX1.BITNET Subject: Patch to remove "mx%" Hunter, any comments about the patch to remove the mx% and quotation marks from the mx mailer? Is this pretty good? Have you checked it out? Thanks, Reef *************************************************************************** Philip D. (Reef) Morse II Internet address: reef@xenon.che.ilstu.edu Department of Chemistry Telephone (voice and voice mail): (309) 438-5595 Illinois State University Telephone (FAX): (309) 438-5538 Normal, IL 61761 Telephone (answering machine): (309) 829-9257 USA *************************************************************************** ================================================================================ Archive-Date: Wed, 06 Oct 1993 11:17:40 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 06 Oct 1993 11:15:37 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009739C2.950BA7B5.5373@WKUVX1.BITNET> Subject: RE: Patch to remove "mx%" reef@xenon.che.ilstu.edu writes: > >Hunter, any comments about the patch to remove the mx% and quotation marks >from the mx mailer? Is this pretty good? Have you checked it out? I assume this was meant to be private e-mail, but.... I ran with the patch for a while. I had no problems with it that I could remember. The patch has been around for a long time and has been used by lots of people, so I'm confident that there are no hidden "features." Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 06 Oct 1993 12:05:34 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 06 Oct 1993 09:09:05 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: rharwood@Data.Basix.COM Message-ID: <009739B0.E86B9120.9469@Data.Basix.COM> Subject: Re: MX PATCH TO ELIMINATE MX PREFIX > All of which makes me (new to MX) wonder what possible pitfalls I may run into > if I install [MX Prefix Patch]. It'd be great to be able to do without > MX%"", but what price will we pay? I take it that many people are using > the patch -- do I give up anything except the prefix? I've only run into one problem: user's on the two systems I manage want to know why other [VMS] systems can't be so user-friendly! Face it, most users HATE the XYZ%"address" scheme. Just yesterday someone called me to ask why he could no longer send Internet EMail on his [other] system, and why had they changed the format requirements? He had only forgotten the percent sign. Users will appreciate being able to "just put the Internet address" and let the SOFTWARE decide it's an Internet-destined address. Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Wed, 06 Oct 1993 12:41:44 CDT Sender: list-mgr@WKUVX1.BITNET From: john@vax.sbu.ac.uk Reply-To: MX-List@WKUVX1.BITNET Subject: Put message directly into SMTP queue Message-ID: <1993Oct6.165851.3390@vax.sbu.ac.uk> Date: 6 Oct 93 16:58:51 GMT To: MX-List@WKUVX1.BITNET Hope someone can help!!! We would like to enter a message directly into the SMTP queue in MX, can this be done? Does anyone know how? Should we do this? Really grateful for any suggestions or pointers! Thanks -------------------------------------------------------------------------------- John Murphy john@vax.sbu.ac.uk ================================================================================ Archive-Date: Wed, 06 Oct 1993 12:42:03 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 06 Oct 1993 13:30:12 EST From: "Steve Thompson, Cheme System Mangler" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: olin@cheme.cornell.edu Message-ID: <009739D5.622DCA04.32650@cheme.cornell.edu> Subject: Re: MX PATCH TO ELIMINATE MX PREFIX > All of which makes me (new to MX) wonder what possible pitfalls I may run into > if I install [MX Prefix Patch]. It'd be great to be able to do without > MX%"", but what price will we pay? I take it that many people are using > the patch -- do I give up anything except the prefix? Anyone done a patch like this for AXP/VMS? -steve /ig ================================================================================ Archive-Date: Wed, 06 Oct 1993 13:18:26 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 06 Oct 1993 13:06:53 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009739D2.207F7A10.5433@WKUVX1.BITNET> Subject: Re: MX PATCH TO ELIMINATE MX PREFIX "Steve Thompson, Cheme System Mangler" writes: > >> All of which makes me (new to MX) wonder what possible pitfalls I may run into >> if I install [MX Prefix Patch]. It'd be great to be able to do without >> MX%"", but what price will we pay? I take it that many people are using >> the patch -- do I give up anything except the prefix? > >Anyone done a patch like this for AXP/VMS? > I posted about this a while back. You're not likely to see such a patch for OpenVMS AXP. Starting with the fact that there's no PATCH on AXP 8-), the patch would be *extremely* difficult to implement because there's quite a bit to the VAX patch. Doing the AXP patch for my DCL_RECALL was a major pain, and that was a pretty simple patch. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 06 Oct 1993 14:48:03 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 06 Oct 1993 12:34:36 PDT From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: syssand@CCVAX.CCS.CSUS.EDU Message-ID: <009739CD.9E3D3780.7429@CCVAX.CCS.CSUS.EDU> Subject: Re: MX PATCH TO ELIMINATE MX PREFIX >> All of which makes me (new to MX) wonder what possible pitfalls I may run >> into if I install [MX Prefix Patch]. > I've only run into one problem: user's on the two systems I manage want to > know why other [VMS] systems can't be so user-friendly! There are a couple of problems, one that hasn't been mentioned, the other illustrated here. Problem 1: This patch causes all mail addresses to be uppercased no matter how they are typed. Now, while case sensitivity of usernames should not pose an issue, unfortunately on some systems it *will* be an impact. When this patch was first discussed long ago, a couple of sites had problems sending mail because "joeuser@site.domain" was valid while "JOEUSER@SITE.DOMAIN" was not - or more precisely, a few sites had problems *receiving* mail... Yes, it's a mailer error on the receiving end, but try explaining to an irate user why he can no longer send mail to a well- known site. Problem 2: Consistency. I'd love to run this patch, but I don't. Why? Because of the what-if factor. What if we move to a version of VMS that we can't patch? What if I personally no longer run the mailer, and the next guy doesn't want to patch the O/S (a *big* reason we avoid any patches like this). What if someone uses both *our* VAXen, and other (unpatched) ones on campus? There's no consistency! Yes, the patch is a major advantage; one that I'd do in a moment if I didn't fear the repercussions if something breaks down the road. And yes, the same problems exist if we ever move away from MX and have to use some *other* prefix - the thought of trying to convince all our users to now type FOO% instead of MX% is frightening (luckily, we'll never, ever find something that will usurp MX as the mailer of choice here). Oh, uh. Plot complication here... let's change direction and suddenly realize that this patch may also have a future BENEFIT *if* a site changes mailers... Since the patch eliminates the prefix from the user's perspective, we *could* change mailers and have the patch worry about the change. The user *still* just types joeuser@site.domain; the PATCH worries about MX%, PMDF%, FOO%, etc. AS LONG AS the person running the system in the future knows that this patch was installed, and is able/willing to support it. The true answer, of course, is for Digital to get off their, umm... posteriors and give the user community a supported hook with this patch's functionality... John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu ================================================================================ Archive-Date: Thu, 07 Oct 1993 13:30:48 CDT Sender: list-mgr@WKUVX1.BITNET Subject: MX and DECNET-OSI ? Message-ID: <1993Oct7.172404.1@condor> From: blacka@logica.co.uk Reply-To: MX-List@WKUVX1.BITNET Date: Thu, 7 Oct 1993 17:24:04 GMT To: MX-List@WKUVX1.BITNET Does MX support DECNET OSI , and if so are there any problems with it. Currently we run MX3.1 with STMP over DECNET. We have no TCP/IP . We are running DECNET VAX extensions at the present; we understand that support for this will cease, forcing us migrate to OSI. Thanks in advance ---------------------------------------------------------------- Andrew Black blacka@logica.co.uk Logica Finance, London ---------------------------------------------------------------- ================================================================================ Archive-Date: Thu, 07 Oct 1993 14:09:15 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 07 Oct 1993 13:34:09 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00973A9F.1A5A320B.5878@WKUVX1.BITNET> Subject: RE: MX and DECNET-OSI ? blacka@logica.co.uk writes: > >Does MX support DECNET OSI , and if so are there any problems with it. > Who knows? Try it and let me know. 8-) >Currently we run MX3.1 with STMP over DECNET. We have no TCP/IP . >We are running DECNET VAX extensions at the present; we understand >that support for this will cease, forcing us migrate to OSI. > I haven't even thought about moving to DECnet/OSI, so I have no idea if anything MX uses will change or not. (I would recommend that you upgrade to MX V3.3; you can find it on ftp.spc.edu in [.MX.MX033].) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 07 Oct 1993 19:23:04 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX and All-in-1 Mail Date: 7 Oct 1993 22:32:01 GMT Message-ID: <2925d1$3ik@news.ysu.edu> To: MX-List@WKUVX1.BITNET Can MX work with DEC's All-in-1 Mail product? If so how do I set it up? thanks tony -- ********************************************************* Tony Spinillo spinillo@marywood1.marywood.edu ********************************************************* ================================================================================ Archive-Date: Thu, 07 Oct 1993 20:07:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 07 Oct 1993 18:05:01 PST From: "David Scott Cunningham, TRIUMF, 604 222-1047" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00973AC4.F10BEA40.5751@erich.triumf.ca> Subject: very scary problem with MX Apologies if this has been noticed before and fixed, but: I had a user who'd set up his mail to place the MAIL.MAI in a subdirectory called MAIL.DIR (the old MAIL>SET MAIL_DIRECTORY [.MAIL] business), and had created a text file called MAIL.TXT also in his root. Suddenly people started calling him saying that his account would not accept MX mail, that it was being returned by postmaster with the error 'privilege or file protection violation'. I sent him some test messages and that was the result I got as well. All of the protection masks on his root, the mail subdirectory, and the mail.mai file were okay, but a dir/prot of mail.* in his root revealed MAIL.DIR (RWE,RWE,,) MAIL.TXT (RE,RWED,RE,RE) On a rediculous hunch I changed the protection of MAIL.TXT to s:rwe such that now the dir/prot read MAIL.DIR (RWE,RWE,,) MAIL.TXT (RWE,RWED,RE,RE) And mail sent to his account didn't bounce back with the privilege violation, but IT WASN'T DELIVERED EITHER. MCP showed the state of the router and delivery agent for that message as FIN, and as far as MX was concerned the file had been delivered okay. I then deleted the MAIL.TXT file, and sent test messages, which *were* delivered to his MAIL.MAI. I recreated the MAIL.TXT file, and once again mail was either bounced back or dissapeared according to the system protection mask. I'm running MX 3.3, on VMS 5.5-2. Has anyone else noticed this? Dave Cunningham ================================================================================ Archive-Date: Thu, 07 Oct 1993 20:24:34 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 07 Oct 1993 20:23:19 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00973AD8.4335455B.6008@WKUVX1.BITNET> Subject: RE: very scary problem with MX "David Scott Cunningham, TRIUMF, 604 222-1047" writes: > >Apologies if this has been noticed before and fixed, but: > >I had a user who'd set up his mail to place the MAIL.MAI in a subdirectory >called MAIL.DIR (the old MAIL>SET MAIL_DIRECTORY [.MAIL] business), and >had created a text file called MAIL.TXT also in his root. Suddenly people >started calling him saying that his account would not accept MX mail, >that it was being returned by postmaster with the error 'privilege or >file protection violation'. I sent him some test messages and that >was the result I got as well. > This has been discussed a couple of times. MX is finding the MAIL.TXT file and writing the mail to that file. This only happens if you're running MultiNet and the user has a MAIL.TXT file, which is the name of file MM uses. I have .EXEs that will disable delivery to the MAIL.TXT files. If you want them, ftp to ftp.spc.edu, user anonymous, CD to [.MX.BETA] and get either MX_NO_MM_AXP.ZIP or MX_NO_MM_VAX.ZIP. These .ZIP files contains new MX_LOCAL.EXE and MCP.EXE files that, by default, will not allow delivery via MM. A new command, SET LOCAL/MM_DELIVER, has been added to MCP to let you enable delivery. This will be included in MX V3.4. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 08 Oct 1993 00:18:32 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 07 Oct 1993 22:07:18 PDT From: "W. Todd Wipke" Reply-To: MX-List@WKUVX1.BITNET To: list-mgr@WKUVX1.BITNET, mx-list@WKUVX1.BITNET Message-ID: <00973AE6.C9D4DAAA.28963@SECS.UCSC.EDU> Subject: RE: MX PATCH TO ELIMINATE MX PREFIX > >The true answer, of course, is for Digital to get off their, umm... >posteriors and give the user community a supported hook with this patch's >functionality... > > John F. Sandhoff, University Network Support > California State University, Sacramento - USA > sandhoff@csus.edu > Here, here. OPEN VMS should have a mail system that handles the OPEN standard tcpip in a natural way. 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 =================== Banana Slug Chosen "Best College Mascot" in 1992 by National Directory of College Athletics ================================================================================ Archive-Date: Fri, 08 Oct 1993 01:39:02 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX PATCH TO ELIMINATE MX PREFIX Message-ID: <1993Oct7.080247.18386@alpha.montagar.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 7 Oct 93 08:02:47 CDT To: MX-List@WKUVX1.BITNET In article <009739CD.9E3D3780.7429@CCVAX.CCS.CSUS.EDU>, "John F. Sandhoff" writes: > The true answer, of course, is for Digital to get off their, umm... > posteriors and give the user community a supported hook with this patch's > functionality... They do, it's call "SET TRANSPORT". However, they still try to process the "@"'s and "!"'s as distribution lists and comments, so it virtually useless to the majority of potential users. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - David L. Cathey |INET: davidc@montagar.com Montagar Software Concepts |UUCP: ...!montagar!davidc P. O. Box 260772, Plano TX 75026-0772 |Fone: (214)-618-2117 ================================================================================ Archive-Date: Fri, 08 Oct 1993 01:39:09 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX Prefix Reply Message-ID: <292t67INNgh8@gap.caltech.edu> From: Date: 8 Oct 1993 05:17:59 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <00973759.0E84A4A0.7507@bhuob00>, syseng%BHUOB00.bitnet@ULKYVM.LOUISVILLE.EDU writes: =Dear All, = Did any one uses MX Prefix, if so did one try to use it = as a mail reply, it must be defined as mail$protocol_"prefix" = to mx_mailshr, using it as a mail transport it failed and bounce = the mail in a strange header formats, any help ? = thanks in advance. Could you try again, next time either phrasing your question in English or providing an example, including any error messages you got and the bounced mail? -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Fri, 08 Oct 1993 05:44:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 08 Oct 1993 05:42:55 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00973B26.6F97523A.6116@WKUVX1.BITNET> Subject: Re: MX PATCH TO ELIMINATE MX PREFIX writes: > >In article <009739CD.9E3D3780.7429@CCVAX.CCS.CSUS.EDU>, "John F. Sandhoff" > writes: >> The true answer, of course, is for Digital to get off their, umm... >> posteriors and give the user community a supported hook with this patch's >> functionality... > > They do, it's call "SET TRANSPORT". However, they still try to >process the "@"'s and "!"'s as distribution lists and comments, so it >virtually useless to the majority of potential users. > It sure is nice on a workstation though---I use MXALIAS for most of my regular contacts and WKUVX1.BITNET as my system name, even though that's not really it's name. With SET TRANSPORT, all local mail gets deliver via MX to WKUVX1.BITNET and aliases are handled automatically. I rarely have to type MX% anymore. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 08 Oct 1993 10:16:16 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 08 Oct 1993 10:59:56 EDT From: kam@ycvax.york.cuny.edu Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <00973B52.B971A960.1366@ycvax.york.cuny.edu> Subject: RE: MX and All-in-1 Mail Allin1 mail works with mx provided MRGate is running. And the syntax for sendingmail from allin1 is at To: mx%"username@node.domain"@mrgate to send mail from UNIX node to allin1 the address can be as follows. "mrgate::a1::kam"@ycvax.york.cuny.edu probably it will work. /Kamrul ================================================================================ Archive-Date: Sun, 10 Oct 1993 22:20:45 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Put message directly into SMTP queue Date: 11 Oct 1993 02:47:48 GMT Message-ID: <29ahgkINN6rp@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993Oct6.165851.3390@vax.sbu.ac.uk>, john@vax.sbu.ac.uk writes: = =Hope someone can help!!! = =We would like to enter a message directly into the SMTP queue in MX, can this =be done? Does anyone know how? Should we do this? = =Really grateful for any suggestions or pointers! This is presumably as intended as a "solution" to some more basic problem. You'd probably have better luck if you told us what you were REALLY trying to accomplish rather than asking for help in one step of your proposed solution. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Mon, 11 Oct 1993 15:56:13 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX and All-in-1 Mail Message-ID: <1993Oct11.123414.816@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 11 Oct 93 12:34:14 +1000 To: MX-List@WKUVX1.BITNET > Can MX work with DEC's All-in-1 Mail product? If so how do > I set it up? The answer is "yes" but it's a kludge. Shipped with MX in the [.contrib] directory is a file called SPECIAL.COM. This is a "back door" interface to VMS Mail from All-In-1 which automatically adds the MX% prefix and the quotes and mails the message via VMS Mail. To use it your users just enter an address in the form _ NOTE. This sends messages out with the user's VMS Userid and not the All-In-1 id so replies will go to the users VMS Mailbox. Use the "V" option in the EM panel of All-In-1 to import those messages into All-in-1. Dec's Message Router causes MX problems. Carl. -- Carl Makin (VK1KCM) makinc@hhcs.gov.au (Internet) / vk1kcm@vk1kcm.act.aus.oc (Amprnet) 'The best book on programming for the layman is "Alice in Wonderland"; but that's because it's the best book on anything for the layman.' ================================================================================ Archive-Date: Tue, 12 Oct 1993 08:20:41 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 12 Oct 1993 11:34:44 +0200 From: mgiurgiu@ROEARN.BITNET Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00973E7C.3FABCE80.28344@roearn.ici.ro> SUBSCRIBE MX-LIST "M GIURGIU" ================================================================================ Archive-Date: Wed, 13 Oct 1993 21:27:38 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: MX and All-in-1 Mail Message-ID: <1993Oct13.141153.818@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 13 Oct 93 14:11:53 +1000 To: MX-List@WKUVX1.BITNET In article <00973B52.B971A960.1366@ycvax.york.cuny.edu> , kam@ycvax.york.cuny.edu writes: > Allin1 mail works with mx provided MRGate is running. And the syntax for > sendingmail from allin1 is > at To: mx%"username@node.domain"@mrgate This only works if you do NOT have spaces in your all-in-1 usernames. :-( Carl. -- Carl Makin (VK1KCM) "Speaking for myself only!" makinc@hhcs.gov.au (Internet) / vk1kcm@vk1kcm.act.aus.oc (Amprnet) 'The best book on programming for the layman is "Alice in Wonderland"; but that's because it's the best book on anything for the layman.' ================================================================================ Archive-Date: Thu, 14 Oct 1993 12:05:51 CDT Sender: list-mgr@WKUVX1.BITNET Subject: For the wish list... Message-ID: <1993Oct14.094857.2323@dmc.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 14 Oct 93 09:48:56 EDT To: MX-List@WKUVX1.BITNET It would be nice if the list processor was smart enough not to duplicate messages. For example, if I send a message to: fred, barney, foo-l and fred appears on foo-l, fred shouldn't get a SECOND copy of the message. I did this in a mail interface I wrote back a Prime and found it incredibly handy. Dick -- Dick Munroe Internet: munroe@dmc.com Acorn Software, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. 01749 USA FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Thu, 14 Oct 1993 12:11:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 14 Oct 1993 12:09:46 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00974013.7908D5C7.7880@WKUVX1.BITNET> Subject: RE: For the wish list... writes: > >It would be nice if the list processor was smart enough not to >duplicate messages. For example, if I send a message to: > Yes, it would be nice. 8-) On the wish list.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 14 Oct 1993 17:16:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 14 Oct 1993 14:56:18 PDT From: "Bob Johns, (604)363-6520" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <0097402A.BD10ADA0.18097@ccs.ios.bc.ca> Subject: Re: MX and All-in-1 Mail Some background info: This issue is raised from time to time on this list. In many cases, the responses confuse "All-in-1 Mail" with the mail bundled within the All-in-1 office automation product. In the past, Digital has differentiated these by calling the former "mail", but the latter "messaging". Now, they have formally renamed the All-in-1 product as "DEC Mailworks", if on VMS or DOS, or "Teamlinks Mail", if on MS Windows. The messaging component of the ALL-in-1 office automation product remains unchanged in name. Confused? Oh well... ;-) Bob Johns (bob@ios.bc.ca) Institute of Ocean Sciences Sidney, B.C. Canada ================================================================================ Archive-Date: Thu, 14 Oct 1993 19:46:46 CDT Sender: list-mgr@WKUVX1.BITNET Subject: MX and MAIL.TXT Message-ID: <1993Oct14.021002.3948@kcvax1> From: Reply-To: MX-List@WKUVX1.BITNET Date: 14 Oct 93 02:10:02 -0500 To: MX-List@WKUVX1.BITNET Hullo At my site, we use MX and Multinet. We do not use Multinet Mail. The users don't really like the interface and get confused when they accidentally get into it. I've even gone ahead and removed MM from the command tables. However... I have discovered that MX apparently decides to deliver mail as "Multinet Mail" if it finds a MAIL.TXT file in the user's SYS$LOGIN directory. As a real quick test, I just create a dummy file MAIL.TXT in my directory, sent myself some mail and *poof* it showed up in MAIL.TXT instead of being delivered via regular VMS Local. This is a problem. It turns out that MANY users extract mail messages to the name "MAIL.TXT". I guess it's the first thing they think of. I'm sure I've done it myself. But just because someone has a MAIL.TXT file floating around doesn't mean I want mail delivered there. Do I understand this correctly? Is there some way to override this behavior? And if there isn't can we put it on list (yes, I know it's long) of things to add. I just spent a couple of hours piecing back together over 10,000 blocks worth of mail. Thanks in advance.... - Miles - ------------------------------- Miles Oursler Manager of Networks and Systems Kenyon College oursler@kenyon.edu ------------------------------- ================================================================================ Archive-Date: Fri, 15 Oct 1993 06:22:53 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 15 Oct 1993 06:21:34 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009740AB.FEC09243.8160@WKUVX1.BITNET> Subject: RE: MX and MAIL.TXT writes: > > At my site, we use MX and Multinet. We do not use Multinet Mail. [...] > I have discovered that MX apparently decides to deliver > mail as "Multinet Mail" if it finds a MAIL.TXT file in > the user's SYS$LOGIN directory. > This has been covered at least twice in the last three weeks.... > Do I understand this correctly? Is there some way to > override this behavior? And if there isn't can we put > it on list (yes, I know it's long) of things to add. > It's already fixed for the next version, which is still a ways off. However, ftp to ftp.spc.edu, CD to MX.BETA, and get either of these files: MX_NO_MM_AXP.ZIP;1 177 7-OCT-1993 21:18 ARCHIVES (RWED,RWED,RE,RE) MX_NO_MM_VAX.ZIP;1 86 7-OCT-1993 21:17 ARCHIVES (RWED,RWED,RE,RE) Those contain new MX_LOCAL.EXE and MCP.EXE images for the AXP and VAX. A new qualifier, SET LOCAL/MM_DELIVER, has been added to MCP. By default, with these .EXEs in place, MX will *not* deliver to MM, unless you execute the command above. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 15 Oct 1993 07:13:01 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 15 Oct 93 09:47:58 WET Message-ID: <009740C8D43CCBA0.25E0232D@ittpub.nl> From: "Hans van Veen - DIS/SSS - Ext 797" Reply-To: MX-List@WKUVX1.BITNET Subject: To: mx-list@WKUVX1.BITNET SUBSCRIDE "Hans van Veen" ================================================================================ Archive-Date: Fri, 15 Oct 1993 07:13:14 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 15 Oct 93 09:49:45 WET Message-ID: <009740C9142B5F60.26202150@ittpub.nl> From: "Hans van Veen - DIS/SSS - Ext 797" Reply-To: MX-List@WKUVX1.BITNET Subject: Using MX with PC's and MAC's To: mx-list@WKUVX1.BITNET We plan to use MX V3.3 as our mail router and delivery system. We also use PCmail and MSmail for a bunch of PC's and MAC's on the network, all using PathWorks. Has anyone experience on how to setup MX, in order to service those type of 'systems' ??? Any comment/hint/tip/.... appreciated Thanks, Hans --->>> Happiness is just an illusion filled with sadness and confusion. <<<--- Hans van Veen Email: hansv@ittpub.nl ITT Publitec PSI%022846811423::VANVEEN Datacenter/SSS Phone: +31 20 56 76 797 Hoekenrode 1 Fax : +31 20 69 10 374 1102 BR AMSTERDAM Netherlands Disclaimer: No responsibility is accepted by anyone on anything I say, write, or do. This also includes myself. --->>> It's not reality that's important, but how you perceive things <<<--- ================================================================================ Archive-Date: Fri, 15 Oct 1993 08:17:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 15 Oct 1993 08:09:53 CDT From: klausner@cathv1.int-med.uiowa.edu Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: klausner@cathv1.int-med.uiowa.edu Message-ID: <009740BB.2094E540.5668@cathv1.int-med.uiowa.edu> Subject: RE: Using MX with PC's and MAC's >We plan to use MX V3.3 as our mail router and delivery system. We also use >PCmail and MSmail for a bunch of PC's and MAC's on the network, all using >PathWorks. >Has anyone experience on how to setup MX, in order to service those type of >'systems' ??? Set up MX as you would if you didn't have PathWorks. On each Mac you can use PathWorks' mail notification to send notification to each Mac that there is new mail. Copy the Listener from the Examples folder to the system folder on the Mac, restart the Mac, start Pathworks mail, in the server menu under remote preferences select custom notification. Select the node of the MX server. On the MX server you need to run NCP to set/define the node name of the Mac. Older versions of the Listener will put an alert message box on the Mac's screen. Newer versions will open a window on the Mac and put a message in the open window. None of my users like the newer version and all went back to the older version (1.1). Note that only messages arriving while the Mac os turned on will get a notice of new mail. You could put an alias of the mailer in the startup folder so mail delivered while the Mac was off will be seen as soon as the Mac is powered up. Ed Klausner Cardiac Cath Lab Univ of Iowa Hospitals ================================================================================ Archive-Date: Fri, 15 Oct 1993 11:16:25 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 15 Oct 1993 17:04:00 +0100 From: Herve GILIBERT CRI universite Jean Monnet ST ETIENNE Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <00974105.BE5E44C0.13510@stroph.univ-st-etienne.fr> Subject: Debuging router. Hi MXers ! I would like to get explanations about "Site-spec expand ..." given by debbuging router : When recipient address is criter.univ-st-etienne.fr (which is an MX record pointing to STROPH - the real machine) I get an error code O134 : 5-OCT-1993 16:35:51.89 %PROCESS, Processing entry number 13505 15-OCT-1993 16:35:52.20 %PROCESS, Status from READ_INFO was 00000001 15-OCT-1993 16:35:52.20 %PROCESS, Message originated in VMS Mail. 15-OCT-1993 16:35:52.24 %PROCESS, will run domain expander on envelope addresse s. 15-OCT-1993 16:35:52.25 %PROCESS, Processing address: 15-OCT-1993 16:35:52.68 %PROCESS, ... address now reads: 15-OCT-1993 16:35:52.68 %PROCESS, will run domain expander on message headers. 15-OCT-1993 16:35:55.55 %PROCESS, Finished VMSmail-origin preprocessing. 15-OCT-1993 16:35:55.55 %PROCESS, Recipient #0: 15-OCT-1993 16:35:55.58 %REWRITE, No rewrite rules matched 15-OCT-1993 16:35:57.53 %FINDPATH, Site-spec expand on criter.univ-st-etienne.fr err=00000134 ^^^^^^^^^^^^ 15-OCT-1993 16:35:57.53 %FINDPATH, domain name CRITER.UNIV-ST-ETIENNE.FR matched path pattern CRITER.UNIV-ST-ETIENNE.FR 15-OCT-1993 16:35:57.54 %PROCESS, Rewrote as - next hop criter.univ-st-etienne.fr, path 1 15-OCT-1993 16:35:57.54 %FINDALIAS, no alias found for system 15-OCT-1993 16:35:57.54 %PROCESS, no alias found for system 15-OCT-1993 16:35:57.55 %PROCESS, this is just a local delivery 15-OCT-1993 16:35:57.65 %PROCESS, Adding to LOCAL path: system. 15-OCT-1993 16:35:58.49 %PROCESS, Path LOCAL gets 1 rcpts, entry number 13506 When the address is reduced to univ-st-etienne.fr I get 0870 : 15-OCT-1993 16:33:21.75 %PROCESS, Processing entry number 13502 15-OCT-1993 16:33:22.40 %PROCESS, Status from READ_INFO was 00000001 15-OCT-1993 16:33:22.41 %PROCESS, Message originated in VMS Mail. 15-OCT-1993 16:33:22.55 %PROCESS, will run domain expander on envelope addresse s. 15-OCT-1993 16:33:22.55 %PROCESS, Processing address: 15-OCT-1993 16:33:24.09 %PROCESS, ... address now reads: 15-OCT-1993 16:33:24.09 %PROCESS, will run domain expander on message headers. 15-OCT-1993 16:33:26.67 %PROCESS, Finished VMSmail-origin preprocessing. 15-OCT-1993 16:33:26.68 %PROCESS, Recipient #0: 15-OCT-1993 16:33:26.70 %REWRITE, No rewrite rules matched 15-OCT-1993 16:33:26.86 %FINDPATH, Site-spec expand on univ-st-etienne.fr err=00 000870 ^^^^^^ 15-OCT-1993 16:33:26.87 %FINDPATH, domain name UNIV-ST-ETIENNE.FR matched path pattern UNIV-ST-ETIENNE.FR 15-OCT-1993 16:33:26.88 %PROCESS, Rewrote as - next hop univ-st-etienne.fr, path 1 15-OCT-1993 16:33:26.88 %FINDALIAS, no alias found for system 15-OCT-1993 16:33:26.88 %PROCESS, no alias found for system 15-OCT-1993 16:33:26.89 %PROCESS, this is just a local delivery 15-OCT-1993 16:33:27.08 %PROCESS, Adding to LOCAL path: system. 15-OCT-1993 16:33:27.94 %PROCESS, Path LOCAL gets 1 rcpts, entry number 13503 Finally when I the recipient address is STROPH.UNIV_ST_ETIENNE.FR I get an error code of 0000 What does it mean exactly ? Thanks in advance. MX logicals are : "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "STROPH$DUA0:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "SYS$SYSDEVICE:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "STROPH" "MX_FLQ_RECLAIM_WAIT" = "0 02:00:00" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_JNET_DIR" = "MX_ROOT:[JNET]" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" = "MX_ROOT:[LOCAL.MLIST]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "stroph.univ-st-etienne.fr" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DEBUG" = "MX_ROUTER_DIR:MX_ROUTER_LOG.LOG" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DIR" = "MX_ROOT:[SITE]" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_UUCP_DIR" = "MX_ROOT:[UUCP]" "MX_VMSMAIL_FROM_FORMAT" = "" "MX_VMSMAIL_LOCALHOST" = "@criter.univ-st-etienne.fr" -- Herve GILIBERT UUUU UUUU CRITeR UUUU UUUU Universite Jean Monnet St-Etienne UUUU UUUU 23, Rue du Dr. P. Michelon UUUU UUUU 42023 ST ETIENNE Cedex 2 UUUU UUUU Tel : 33 77 42 15 79 UUUU UUUU Fax : 33 77 42 15 75 UUUUUUUUUUU RFC822: gilibert@criter.univ-st-etienne.fr UUUUUUUUU ================================================================================ Archive-Date: Fri, 15 Oct 1993 14:23:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 15 Oct 1993 12:27 EDT From: MCW@UFPINE.BITNET Reply-To: MX-List@WKUVX1.BITNET Subject: queue file grows and grows To: mx-list@WKUVX1.BITNET We've always had this problem and I thought it was because we used an old version of MX, but we recently upgraded to V 3.3 and it still does it. Our queue file in MX_FLQ_DIR grows and grows and grows. Every week or so I use CONVERT to reorganize it, but it just gets big again. When I last shrunk it, it was over 30,000 blocks, but I could shrink it to less than 1000. I haven't set any of the logicals that redefine the periods for reclaims, so I assume it's being done every 2 hours. Should it be done more often? Mike Wright University of Florida mcw@pine.circa.ufl.edu ================================================================================ Archive-Date: Fri, 15 Oct 1993 14:35:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 15 Oct 1993 14:34:01 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009740F0.CA2DB2F0.8452@WKUVX1.BITNET> Subject: RE: queue file grows and grows MCW@UFPINE.BITNET writes: > >We've always had this problem and I thought it was because we >used an old version of MX, but we recently upgraded to V 3.3 >and it still does it. > Yep. The queue file hasn't changed. >Our queue file in MX_FLQ_DIR grows and grows and grows. Every >week or so I use CONVERT to reorganize it, but it just gets big >again. When I last shrunk it, it was over 30,000 blocks, but >I could shrink it to less than 1000. > >I haven't set any of the logicals that redefine the periods for >reclaims, so I assume it's being done every 2 hours. Should >it be done more often? > I have my MX_FLQ_RECLAIM_WAIT set to "0 00:30:00". Setting it that low made a big difference on my system---that file can grow a lot in two hours, depending on your traffic. I also highly recommend that all MX users shut down MX nightly and do a CONVERT/FDL on the SYSTEM_QUEUE file. I've found that it really helps MX performance to do this every night. My .COM file, which I run from DECscheduler, is included below. Note that it skimps on error-checking, etc. 8-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ------------------------------------------------------------------------------- $ set noon $ say := write sys$output $ mcp := $mx_exe:mcp.exe/file=mx_dir:mx_config.mxcfg $ say "Shutting down MX" $ mcp shutdown $! $! Loop until we can OPEN the SYSTEM_QUEUE file; when we can, nobody $! else is using it, which means all the agents have shutdown. $! $ wait_loop: $ wait 00:00:15 $ open/read/error=wait_loop tmp mx_flq_dir:system_queue.flq_ctl $ close tmp $ convert/fdl=mx_flq_dir:system_queue mx_flq_dir:system_queue.flq_ctl - mx_flq_dir:system_queue.flq_ctl; $ purge mx_flq_dir:system_queue.flq_ctl $ rename mx_flq_dir:system_queue.flq_ctl; ;1 $ say "" $ say "Restarting MX" $ submit/user=mxmailer sys$startup:mx_startup.com $ wait 00:00:30 $ exit ================================================================================ Archive-Date: Sat, 16 Oct 1993 15:51:34 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 15 Oct 1993 18:56:06 EDT From: kam@ycvax.york.cuny.edu Reply-To: MX-List@WKUVX1.BITNET To: mx-list%wkuvx1.bitnet@ycvax.york.cuny.edu Message-ID: <00974115.66F59C00.1763@ycvax.york.cuny.edu> Subject: TCP/IP port for mx smtp Which port is used by SMTP of MX?. UCX's SMTP uses port 25. I guess it would not cause any problem if I start both SMTPs provided MX's SMTP uses different port for incoming request. thank you. /Kamrul Ahsan York College, CUNY ================================================================================ Archive-Date: Sat, 16 Oct 1993 15:59:02 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 16 Oct 1993 00:39:22 MET From: Daniel DAGNEAUX (LURE-CNRS) Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00974145.5BB13CC0.6559@lurvax.lure.ups.circe.fr> Subject: RE: Using MX with PC's and MAC's Another solution (free!): At LURE, we are using IUPOP3 version 1.7 on VAX, and Eudora on Macs and PCs, it works great with 2 alternate server POP for more than 200 micro- computers. ================================================================================ Archive-Date: Sat, 16 Oct 1993 16:09:38 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 16 Oct 1993 08:43:29 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: rharwood@Data.Basix.COM Message-ID: <00974188.FD10BF80.10302@Data.Basix.COM> Subject: Next release info? > It's already fixed for the next version, which is still a ways off. Are there any semi-firm plans for the date of next release? It fixes a number of things I (and others) are looking forward to, and I was just hoping for some advance warning. Also, another possible "wish list" item which I don't recall seeing: A way to totally eliminate header/trailer info (the RFC-822 stuff) for *selected* users. Many of my users on East.Pima.EDU *do* want to see the things like organization, etc., but I've got a couple of blind students for whom that stuff is a real pain. I don't know how easy it would be to implement; would there be a command the user would enter, or one the administrator would enter? Possibly grant an identifier to some users of NO_MX_MAIL_HEADERS or something? Naturally this would also interest some non-blind folks as well, especially the novices (I mean the really *green* ones) that just can't handle any extra "garbage" in the EMail. Thanks Hunter for all your hard work! (Wish I knew some BLISS to be of help!) Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Sat, 16 Oct 1993 17:59:05 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 16 Oct 1993 17:57:42 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009741D6.694B9B2D.8841@WKUVX1.BITNET> Subject: RE: TCP/IP port for mx smtp kam@ycvax.york.cuny.edu writes: > >Which port is used by SMTP of MX?. UCX's SMTP uses port 25. I guess it would not >cause any problem if I start both SMTPs provided MX's SMTP uses different port >for incoming request. thank you. > Port 25 is the standard SMTP port. If you intend to use MX, then you must disable UCX's SMTP mailer. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sat, 16 Oct 1993 18:03:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 16 Oct 1993 18:02:09 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009741D7.07F21761.8843@WKUVX1.BITNET> Subject: RE: Next release info? "Ray Harwood -- Data Basix: (602)721-1988" writes: > >> It's already fixed for the next version, which is still a ways off. > >Are there any semi-firm plans for the date of next release? It fixes a number >of things I (and others) are looking forward to, and I was just hoping for some >advance warning. > No, I have absolutely no idea when the next one will be out. I've been swamped with all kinds of other stuff, including a number of things related to my real job. 8-) We've been setting up a campus backbone, and my Internet connection should, at long last, happen next week or the week after. And the fixes you're waiting for (whichever ones they are) haven't been done yet. I haven't had time to do much at all on V3.4 yet. >Also, another possible "wish list" item which I don't recall seeing: A way to >totally eliminate header/trailer info (the RFC-822 stuff) for *selected* users. That's been on my personal wish list for a long time. It *might* be in MX V3.4. >Thanks Hunter for all your hard work! (Wish I knew some BLISS to be of help!) Thanks. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sat, 16 Oct 1993 20:23:11 CDT Sender: list-mgr@WKUVX1.BITNET Subject: MX Mail <--> News Gateway. Message-ID: <29kr36$462@lohengrin.umkc.edu> From: Date: 15 Oct 1993 00:32:38 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET I've whipped up a few programs/procedures that implements a MX Mail to News bidirectional gateway using Multinet as TCP/IP provider. I've been using it for a week now, and after 40+ messages, only two have given me problems. One was because we had a UN*X machine with a bum sendmail.cf (big surprise) and the other was because the News server we used choked because a message had more included text than answer :-( I feel I'm ready for some constructive criticism. I think one of its best features is that it only requires software on the host running MX and Multinet. The MX host doesn't even have to be running an NNTP client let alone a server. No software is needed on the NNTP server. All you need is a NNTP server that is willing to let you talk to it. It is available via anonymous FTP from FTP.CSTP.UMKC.EDU in the [.MX_POST] directory. I've attached the top of the readme. -=Brian ======================================================================= MX_POST V0.1 1993-10-06 This set of files implement a simple MX <--> News bidirectional gateway. The source was synthesized by reading a lot of other people's code. The credits are as follows: Who Where What --------------- ----------------------------- ------------- Ted Nieland nieland_t@asd-yf.wpafb.af.mil MX_TO_NEWS Matthew Madison madison@TGV.COM NEWSRDR TGV TCPECHOCLIENT Mike Coleman coleman@cstp.umkc.edu The Moderated list idea I must confess a certain amount of ignorance about the ins and outs of e-mail and news. The package can be best described as a hack just to get the job done and not an attempt to create a finely crafted finished product suitable for framing. Please let me know if you find this software useful. Also let me know if you have any suggestions for improvements. I've added a brief list of things I intend to do when I have time at the bottom of this file. Check there first, I might have already thought of it. Additionally, I'd really appreciate an analysis of the technical aspects of the mail and news headers that are generated and omitted. Should I have left out the "Path:" header? Should I add some other header? Incompatibility implications? Stuff like that. The code was written and is successfully running under OpenVMS/AXP V1.5 via Multinet V3.2C and MX V3.3 AXP. It should compile under OpenVMS/VAX and VAXC with no problem although I haven't tried it. Option files are included for your convenience. As for using other versions of TCP/IP, you should be able to port it to any flavor that supports BSD sockets. ================================================================================ Archive-Date: Sat, 16 Oct 1993 20:39:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 16 Oct 1993 13:24:12 EST From: "Steve Thompson, Cheme System Mangler" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: olin@cheme.cornell.edu Message-ID: <009741B0.340484F0.11960@cheme.cornell.edu> Subject: arguments to the MX_SITE_IN program? In regard to the arguments of the MX_SITE_IN program, the MX programmer's guide states: $ MX_ENTER = "$MX_EXE:MX_SITE_IN" $ MX_ENTER msg-file-spec dest-file-spec [origin-address] MX_SITE_IN takes up to three parameters, which correspond exactly to the last three parameters passed out by the MX_SITE delivery agent. The first parameter should be the name of a file containing a properly- formatted RFC822 message. The second parameter should be the name of a file containing a list of RFC822 route addresses (they must have the surrounding angle brackets, just as in an SMTP transaction). The third parameter, which is optional, should be the RFC822 route address of the sender (also including the surrounding angle brackets). If the third parameter is omitted, the address of the user running the program will be used as the origin of the message. It appears to me, however, that MX_SITE_IN is expecting a filespec for the third parameter. If I include the sender's address directly as this parameter, MX_SITE_IN exits with: %RMS-F-FNM, error in file name Have I screwed up somewhere, or is the doc wrong? -Steve --------------------------------------------------------------------------- Steve Thompson, System Mangler Internet: thompson@cheme.cornell.edu School of Chemical Engineering Bitnet: thompson@crnlchme Olin Hall, Cornell University Phone: (607) 255 5573 Ithaca NY 14853 FAX: (607) 255 9166 --------------------------------------------------------------------------- ================================================================================ Archive-Date: Sat, 16 Oct 1993 20:55:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 16 Oct 1993 20:53:49 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009741EF.0355A5F2.8948@WKUVX1.BITNET> Subject: RE: arguments to the MX_SITE_IN program? "Steve Thompson, Cheme System Mangler" writes: > >In regard to the arguments of the MX_SITE_IN program, the MX programmer's >guide states: > > $ MX_ENTER = "$MX_EXE:MX_SITE_IN" > $ MX_ENTER msg-file-spec dest-file-spec [origin-address] > [...] >It appears to me, however, that MX_SITE_IN is expecting a filespec for >the third parameter. If I include the sender's address directly as >this parameter, MX_SITE_IN exits with: > > %RMS-F-FNM, error in file name > >Have I screwed up somewhere, or is the doc wrong? > The docs are right. Did you put quotes around the origin-address? For example, something like: $ MX_ENTER 'p2' 'p3' "''p4'" Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sun, 17 Oct 1993 01:07:20 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 16 Oct 1993 22:21:50 PDT From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: kam@ycvax.york.cuny.edu, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <009741FB.4F47A080.32055@CCVAX.CCS.CSUS.EDU> Subject: RE: TCP/IP port for mx smtp > Which port is used by SMTP of MX?. UCX's SMTP uses port 25... Ummm... SMTP *is* port 25. Any other mailer in the world (except perhaps one you locally configure) is going to use port 25 to send SMTP mail. Period. You *cannot* run multiple mailers concurrently. However, you can use MX as a REPLACEMENT to the UCX mailer (and I *strongly* recommend it). The MX installation guide details how to disable the UCX server and allow MX to run in its place. But simultaneously? Sorry, it doesn't work. John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu ================================================================================ Archive-Date: Sun, 17 Oct 1993 06:24:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sun, 17 Oct 1993 07:18:36 EST From: "Steve Thompson, Cheme System Mangler" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: olin@cheme.cornell.edu Message-ID: <00974246.4BBF6F10.13168@cheme.cornell.edu> Subject: RE: arguments to the MX_SITE_IN program? I said: >In regard to the arguments of the MX_SITE_IN program, the MX programmer's >guide states: > > $ MX_ENTER = "$MX_EXE:MX_SITE_IN" > $ MX_ENTER msg-file-spec dest-file-spec [origin-address] [...] >It appears to me, however, that MX_SITE_IN is expecting a filespec for >the third parameter. If I include the sender's address directly as >this parameter, MX_SITE_IN exits with: > > %RMS-F-FNM, error in file name > >Have I screwed up somewhere, or is the doc wrong? Hunter said: >The docs are right. Did you put quotes around the origin-address? >For example, something like: > > $ MX_ENTER 'p2' 'p3' "''p4'" Of course it was I who screwed up. I did have the quotes as Hunter suggests, but I had written the line as: $ MX_ENTER "''p2'" 'p3' "''p4'" which MX_SITE_IN didn't like at all. Sorry, folks! -Steve --------------------------------------------------------------------------- Steve Thompson, System Mangler Internet: thompson@cheme.cornell.edu School of Chemical Engineering Bitnet: thompson@crnlchme Olin Hall, Cornell University Phone: (607) 255 5573 Ithaca NY 14853 FAX: (607) 255 9166 --------------------------------------------------------------------------- ================================================================================ Archive-Date: Sun, 17 Oct 1993 13:12:42 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sun, 17 Oct 1993 11:09:38 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: rharwood@Data.Basix.COM Message-ID: <00974266.9272BF00.10354@Data.Basix.COM> Subject: RE: TCP/IP port for mx smtp On Sat, 16 Oct 1993 22:21:50 PDT, "John F. Sandhoff" wrote: > > Which port is used by SMTP of MX?. UCX's SMTP uses port 25... > > Ummm... SMTP *is* port 25. Any other mailer in the world (except perhaps > one you locally configure) is going to use port 25 to send SMTP mail. Period. > > You *cannot* run multiple mailers concurrently. However, you can use MX as a > REPLACEMENT to the UCX mailer (and I *strongly* recommend it). The MX > installation guide details how to disable the UCX server and allow MX to > run in its place. But simultaneously? Sorry, it doesn't work. Not to muddy the water (much!), but I thought I'd add a little techincal detail to John's answer. You cannot run multiple mail RECEIVERS simultaneously, since it's the TCP/IP software which receives the "connection request" over port 25, which in turn must know (i.e., must have been told by some sort of configuration command) EXACTLY which software to run to handle the incoming SMTP request. (Trivial detail: since mail/SMTP is a very frequently used item, most TCP/IP packages run the SMTP handler as a detached process and pass the requests directly, rather than "starting up" a new image for each EMail.) One COULD, however, run multiple mail SENDERS simultaneously. Each SMTP "sender" process simply requests a connection to the SMTP port of the destination, and the TCP/IP software on the sender's end simply "puts the call through". This is why EMail is not very secure! Anyone could write a mailer, crank 'er up, and pretend to send EMail from anywhere! Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Sun, 17 Oct 1993 23:42:16 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 18 Oct 1993 01:37:12 +0100 From: Per Hogstedt Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Using MX with PC's and MAC's To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.edu Message-ID: <009742DF.C475BE20.17158@plab.se> >Another solution (free!): > > At LURE, we are using IUPOP3 version 1.7 on VAX, and Eudora on Macs >and PCs, it works great with 2 alternate server POP for more than 200 micro- >computers. Just to display my ignorance in public :-) Doesn't this solution require you to run TCP/IP or can it be used with good (?) old DECNET? /Per ------- Per Hogstedt, Lindholmen Utveckling, Box 8714, S-402 75 Gothenburg, Sweden Internet: hogstedt@plab.se (or: hogstedt@ae.chalmers.se) Phone: +46 31 50 70 50, Fax +46 31 51 53 13 ================================================================================ Archive-Date: Mon, 18 Oct 1993 06:23:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 18 Oct 1993 11:12:50 -0305 From: mtaghavi@IREARN.BITNET Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00974330.2ECBABE0.1679@IREARN.BITNET> Subject: RE: MX-LIST Digest V93 #124 sign off ================================================================================ Archive-Date: Mon, 18 Oct 1993 10:46:42 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 18 Oct 1993 16:11:32 MET From: Daniel DAGNEAUX (LURE-CNRS) Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00974359.E94D0BC0.6996@lurvax.lure.ups.circe.fr> Subject: Infos on IUPOP3 and Eudora Oooops, In my very short message, I make reference to IUPOP3 and Eudora, you can ftped this stuff: 1/ IUPOP3 : ftp.indiana.edu in /pub/VMS/iupop3 running in: OpenCMU-IP, UCX 2.0 and Multinet. 2/ Eudora : (this product is in commercial phase by QualCom) - Mac : In any info-mac archive (sumex for example) but need MacTCP. - PC : dorm.rutgers.edu or ftp.sunet.se... need a Winsock API. Notes: A alternative solution for micros is POPMAIL. For european users all this materials is ftpable at ftp.switch.ch in /software/[vms,mac,msdos]/[iupop3,mail] Hope for this help. D. Dagneaux ================================================================================ Archive-Date: Mon, 18 Oct 1993 11:38:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 18 Oct 1993 12:32:45 EDT From: Irv Eisen Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097433B.59277A80.13885@ccstat.mc.duke.edu> Subject: Controlling size of queue file Last week Hunter sent out the following example of a com file to keep the queue file down to size. I was wondering why he used the dcl convert command as opposed to 'mcp queue reclaim.' <$ set noon <$ say := write sys$output <$ mcp := $mx_exe:mcp.exe/file=mx_dir:mx_config.mxcfg <$ say "Shutting down MX" <$ mcp shutdown <$! <$! Loop until we can OPEN the SYSTEM_QUEUE file; when we can, nobody <$! else is using it, which means all the agents have shutdown. <$! <$ wait_loop: <$ wait 00:00:15 <$ open/read/error=wait_loop tmp mx_flq_dir:system_queue.flq_ctl <$ close tmp <$ convert/fdl=mx_flq_dir:system_queue mx_flq_dir:system_queue.flq_ctl - < mx_flq_dir:system_queue.flq_ctl; <$ purge mx_flq_dir:system_queue.flq_ctl <$ rename mx_flq_dir:system_queue.flq_ctl; ;1 <$ say "" <$ say "Restarting MX" <$ submit/user=mxmailer sys$startup:mx_startup.com <$ wait 00:00:30 <$ exit Thanks, ================================================================ Irv Eisen, Systems Manager Bitnet : EISEN001@DUKEMC Cancer Center BioStatistics Internet: IRV@CCSTAT.MC.DUKE.EDU Duke University Medical Center DUMC Box 3958 Voice : (919) 416-5138 Durham, NC 27710 Fax : (919) 286-3956 ================================================================ ================================================================================ Archive-Date: Mon, 18 Oct 1993 12:38:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 18 Oct 1993 12:36:03 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097433B.CF150096.9407@WKUVX1.BITNET> Subject: RE: Controlling size of queue file Irv Eisen writes: > >Last week Hunter sent out the following example of a com file to keep the >queue file down to size. I was wondering why he used the dcl convert >command as opposed to 'mcp queue reclaim.' > Because CONVERT/FDL creates a new, smaller file. MCP QUEUE RECLAIM just reclaims space (make it reusable) in the existing file. MX Router normally does what amounts to an MCP QUEUE RECLAIM---that's what's controlled by the logical MX_FLQ_RECLAIM_WAIT. The point of the .COM file was to create a brand-new, smaller SYSTEM_QUEUE file. ><$ submit/user=mxmailer sys$startup:mx_startup.com ><$ wait 00:00:30 And the WAIT was in the .COM file because I also take down Jnet each night and wanted to be sure MX_STARTUP was mostly-finished before MX Jnet was started. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Mon, 18 Oct 1993 16:31:51 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: For the wish list... Message-ID: <1993Oct18.151619.2333@dmc.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 18 Oct 93 15:16:19 EDT To: MX-List@WKUVX1.BITNET In article <1993Oct14.094857.2323@dmc.com>, munroe@dmc.com (Dick Munroe) writes: > It would be nice if the list processor was smart enough not to > duplicate messages. For example, if I send a message to: > > fred, barney, foo-l > > and fred appears on foo-l, fred shouldn't get a SECOND copy of > the message. I did this in a mail interface I wrote back a Prime > and found it incredibly handy. In a similar vein, it would be handy if is was possible to say something like: ADD /alias=foo@dmc.com bar@some.other.domain Which would basically say, messages from bar@some.other.domain should be treated as coming from foo@dmc.com. I have a situation in which several people have several identities on the list. Being able to say that each of these "other" people are really a single person would be a big help. -- Dick Munroe Internet: munroe@dmc.com Acorn Software, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. 01749 USA FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Mon, 18 Oct 1993 18:42:22 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 18 Oct 1993 15:55:30 PDT From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: syssand@CCVAX.CCS.CSUS.EDU Message-ID: <00974357.ABDFDDA0.2185@CCVAX.CCS.CSUS.EDU> Subject: RE: Controlling size of queue file Hunter Goatley (the current overseer of MX Mail) writes: > I also highly recommend that all MX users shut down MX nightly and do > a CONVERT/FDL on the SYSTEM_QUEUE file. I've found that it really > helps MX performance to do this every night. Quite agreed, but I have a question: If you shut down all the mailer agents, can't local users still send INTO the MX system if there timing is just right (or just wrong, as the case may be). Also, what about the SMTP_SERVER process - can't an incoming message get dumped into the queue in the midst of the process? My very-unsatisfactory workaround to date has been to run a reclaim manually in the middle of the night, after ascertaining that the system is pretty idle (and crossing my fingers). And for added safety I rename the system_queue file (then if someone tries to send a message they get a nasty, ugly error message. Better that than they lose a message, though). Am I being paranoid? Is there a better way to be 110% safe? John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu ================================================================================ Archive-Date: Mon, 18 Oct 1993 18:55:45 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Sig missing from previous posting. Message-ID: <29mhg5$lqq@unicorn.ccc.nottingham.ac.uk> From: Date: 15 Oct 1993 16:01:09 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Sorry, I left off the sig. I've just moved from using NEWSRDR on the VAX to my new Alpha. ================================================================================ Archive-Date: Mon, 18 Oct 1993 18:57:10 CDT Sender: list-mgr@WKUVX1.BITNET Subject: UK peculiarities Message-ID: <29ma2a$dgu@unicorn.ccc.nottingham.ac.uk> From: Date: 15 Oct 1993 13:54:18 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In the UK academic community we've had a mail system (Coloured Books) for some years for which there's a mail transport CBS. I'm trying to run MX on the same system and find that MX manages the SMTP mail very well but there are problems when the two systems intersect. 1. If a user does a SET FORWARD CBS%place::person in MAIL and then receives a message on the VAX from the SMTP world, the "From" line gets messed up and looks like From: "person@original-smtp-address" and the stuff in the angle brackets is an invalid address. Coloured Books should be able to understand MX%"person@original-smtp-address"@UK.AC.NOTTINGHAM.CCC.VAX Is this something that's fixable by the "percent-hack" switch? I think I've tried all the possible settings without success. 2. As you will observe, (and may already know) the Coloured Books address UK.AC.NOTTINGHAM.CCC.VAX is big-endian rather than SMTP little-endian vax.ccc.nottingham.ac.uk. Leaving aside how we got into this mess, is there any way I can make MX send mail to big-endian addresses? If I get mail from MX%"person@UK.AC.NOTTINGHAM.CCC.VME" the current configuration tries and fails to look that up in the DNS although I have a record DEFINE PATH "uk.ac.nottingham.ccc.vme" SMTP /ROUTE="mail.nottingham.ac.uk" in my MCP configuration file before the default "*" record. I'm full aware that these problems are (a) UK-specific and (b) possibly due to my lack of comprehension of the options in MX but I'd be grateful for any advice. We're running MX 3.3 over UCX 2.0D, VMS 5.5-2. ================================================================================ Archive-Date: Tue, 19 Oct 1993 06:34:43 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 19 Oct 1993 06:33:20 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009743D2.4D56CA48.9728@WKUVX1.BITNET> Subject: RE: Controlling size of queue file "John F. Sandhoff" writes: > > >Hunter Goatley (the current overseer of MX Mail) writes: >> I also highly recommend that all MX users shut down MX nightly and do >> a CONVERT/FDL on the SYSTEM_QUEUE file. I've found that it really >> helps MX performance to do this every night. > >Quite agreed, but I have a question: >If you shut down all the mailer agents, can't local users still send INTO >the MX system if there timing is just right (or just wrong, as the case >may be). It's only possible before the CONVERT/FDL starts---after that, the file is locked, just as when the MX Router is reclaiming space. Users sending mail during the CONVERT will get the error message that the system queue is locked and to try again. >Also, what about the SMTP_SERVER process - can't an incoming >message get dumped into the queue in the midst of the process? > The same thing would happen here. >My very-unsatisfactory workaround to date has been to run a reclaim >manually in the middle of the night, after ascertaining that the system >is pretty idle (and crossing my fingers). And for added safety I rename >the system_queue file (then if someone tries to send a message they get >a nasty, ugly error message. Better that than they lose a message, though). > I intend, I think for V3.4, to include a logical that you can define to prevent users from specifying MX% (something like MX_SHUTDOWN); they'll get a real error message when that logical is defined. >Am I being paranoid? Is there a better way to be 110% safe? > You're being paranoid some, and there *are* some sites where this won't work, either because they have users who are logged in at all hours, or leave while logged in and in MAIL sending a message through MX. That's why I check to make sure all the processes are there every morning. I've only had a couple of instances where MX didn't get restarted, and that was because the file was so internally-fragmented that MX Router never got around to shutting down. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 19 Oct 1993 09:18:23 CDT Sender: list-mgr@WKUVX1.BITNET From: "Pasztor Miklos" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Date: Tue, 19 Oct 1993 15:01:24 GMT+1 Subject: RE: Controlling size of queue file Message-ID: Hunter writes: > I also highly recommend that all MX users shut down MX nightly and do > a CONVERT/FDL on the SYSTEM_QUEUE file. I've found that it really > helps MX performance to do this every night. > This spring Eric Thomas (eric@sujnet.se) posted his FDL file for the system queue file to this list. I followed his advice, created a new system queue file and I'm using it since then. I notice a significant improvement in performance, and the system queue file does NOT grow, although the traffic is rather heavy (several thousands of messages per day). I do merely a "manual" reclaim every night from batch. I find that if you have an appropriate system queue file it is not necessary to do any convert/fdl on it. Miklo's ==================================================================== Pa'sztor Miklo's | E-mail: pasztor@hugbox.bitnet MTA SZTAKI/ASZI Budapest Victor H. u. 18-22 | Phone: (36)-(1)-149-75-32 Institute for Computation and Automation, Hungarian Academy of Sciences ==================================================================== ================================================================================ Archive-Date: Tue, 19 Oct 1993 09:18:31 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Controlling size of queue file Message-ID: <1993Oct19.124636.17305@vax.oxford.ac.uk> Date: 19 Oct 93 12:46:35 GMT To: MX-List@WKUVX1.BITNET In article <00974357.ABDFDDA0.2185@CCVAX.CCS.CSUS.EDU>, "John F. Sandhoff" writes: > > Hunter Goatley (the current overseer of MX Mail) writes: >> I also highly recommend that all MX users shut down MX nightly and do >> a CONVERT/FDL on the SYSTEM_QUEUE file. I've found that it really >> helps MX performance to do this every night. > > Quite agreed, but I have a question: > If you shut down all the mailer agents, can't local users still send INTO > the MX system if there timing is just right (or just wrong, as the case > may be). Also, what about the SMTP_SERVER process - can't an incoming > message get dumped into the queue in the midst of the process? > > My very-unsatisfactory workaround to date has been to run a reclaim > manually in the middle of the night, after ascertaining that the system > is pretty idle (and crossing my fingers). And for added safety I rename > the system_queue file (then if someone tries to send a message they get > a nasty, ugly error message. Better that than they lose a message, though). > > Am I being paranoid? Is there a better way to be 110% safe? > > John F. Sandhoff, University Network Support > California State University, Sacramento - USA > sandhoff@csus.edu > What you need to do is to shut down MX completely and deinstall the MX_MAILSHR image. That stops users submitting messages to the queue. Unfortunately they get a nasty error message if they try but it ensures that you can run a CONVERT on the queue file. Dave -- David Hastings | "There's nothing wrong with my sense VAX Systems Programmer | of reality - I have it thoroughly Oxford University Computing Services| serviced once a fortnight" - DNA daveh@vax.oxford.ac.uk | ================================================================================ Archive-Date: Tue, 19 Oct 1993 09:18:38 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: UK peculiarities Message-ID: <1993Oct19.125438.17307@vax.oxford.ac.uk> Date: 19 Oct 93 12:54:38 GMT To: MX-List@WKUVX1.BITNET In article <29ma2a$dgu@unicorn.ccc.nottingham.ac.uk>, cczanj@axp0 (Andy Jack) writes: > In the UK academic community we've had a mail system (Coloured Books) for some > years for which there's a mail transport CBS. I'm trying to run MX on the same > system and find that MX manages the SMTP mail very well but there are problems > when the two systems intersect. > > 1. If a user does a SET FORWARD CBS%place::person in MAIL and then receives a > message on the VAX from the SMTP world, the "From" line gets messed up and > looks like > > From: "person@original-smtp-address" > > and the stuff in the angle brackets is an invalid address. Coloured Books > should be able to understand > > MX%"person@original-smtp-address"@UK.AC.NOTTINGHAM.CCC.VAX > > Is this something that's fixable by the "percent-hack" switch? I think I've > tried all the possible settings without success. > We hit this problem as well. There doesn't seem to be a way of avoiding it except to get rid of CBS (you'll have to soon anyway because it won't work with VMS6) > > 2. As you will observe, (and may already know) the Coloured Books address > UK.AC.NOTTINGHAM.CCC.VAX is big-endian rather than SMTP little-endian > vax.ccc.nottingham.ac.uk. Leaving aside how we got into this mess, is there any > way I can make MX send mail to big-endian addresses? If I get mail from > > MX%"person@UK.AC.NOTTINGHAM.CCC.VME" > > the current configuration tries and fails to look that up in the DNS although I > have a record > > DEFINE PATH "uk.ac.nottingham.ccc.vme" SMTP /ROUTE="mail.nottingham.ac.uk" > > in my MCP configuration file before the default "*" record. > > > I'm full aware that these problems are (a) UK-specific and (b) possibly due to > my lack of comprehension of the options in MX but I'd be grateful for any > advice. We're running MX 3.3 over UCX 2.0D, VMS 5.5-2. > > Are you using a dedicated mailer? We've got a Sun running the pp program which will sort out grey book mail even if it is transfered from the VAX to the mailer by SMTP, ie we do: DEFINE PATH "*" SMTP/ROUTE="oxmail.ox.ac.uk" The other point is that all incoming mail is routed though the mailer, so if anybody sends grey book mail to the VAX the address is rewritten to an MX-style one. Dave -- David Hastings | "There's nothing wrong with my sense VAX Systems Programmer | of reality - I have it thoroughly Oxford University Computing Services| serviced once a fortnight" - DNA daveh@vax.oxford.ac.uk | ================================================================================ Archive-Date: Tue, 19 Oct 1993 17:15:54 CDT Sender: list-mgr@WKUVX1.BITNET Subject: MX Mail headers Message-ID: <1993Oct19.141004.1@stimpy.hsc.ucalgary.ca> From: Reply-To: MX-List@WKUVX1.BITNET Date: Tue, 19 Oct 1993 20:10:04 GMT To: MX-List@WKUVX1.BITNET I've got a strange problem with the "To:" header on outgoing mail. The header looks like this: To: your.domain@my.domain and it should be: To: you@your.domain I'm using a modified NAME_CONVERSION routine. It's my understanding that the NAME_CONVERSION module only mucks with the "From:" and "Return-Path:" headers. The "From:" and "Return-Path:" headers are being correctly generated, as per the NAME_CONVERSION routine. The following are the headers that were generated when sending from ren::byron, which gets 'aliased' to Byron.Draudson@FhHosp.AB.CA. The "To:" header should read "To: draudson@geo.ucalgary.ca". >Return-Path: >From: Byron Draudson >To: geo.ucalgary.ca@FhHosp.AB.CA Any ideas as to what might be causing the "To:" header to be generated as above? Shouldn't the "To:" header always be identical to what the user entered at the "To:" prompt? BTW, VMS 5.5-3, VMS Mail, Multinet 3.2B and MX 3.3. Thanks. :byron ________________________________________________________________________ Byron Draudson, Systems Manager | Internet: Diagnostic Imaging - Foothills Hospital, | Byron.Draudson@FhHosp.AB.CA Calgary, Alberta, Canada (403) 670-2442 | ================================================================================ Archive-Date: Wed, 20 Oct 1993 05:14:59 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: TCP/IP port for mx smtp Date: 20 Oct 1993 07:38:00 GMT Message-ID: <2a2pso$1j6@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <00974115.66F59C00.1763@ycvax.york.cuny.edu>, kam@ycvax.york.cuny.edu writes: =Which port is used by SMTP of MX?. UCX's SMTP uses port 25. I guess it would not =cause any problem if I start both SMTPs provided MX's SMTP uses different port =for incoming request. thank you. You might consider THINKING about what you're asking. Now, how would a remote machine know to use a port other than 25 to try to get SMTP service? No, UCX, MULTInet, and every other package with SMTP service uses port 25. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 20 Oct 1993 05:15:27 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Debuging router. Date: 20 Oct 1993 07:34:20 GMT Message-ID: <2a2pls$1j6@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <00974105.BE5E44C0.13510@stroph.univ-st-etienne.fr>, Herve GILIBERT CRI universite Jean Monnet ST ETIENNE writes =When recipient address is criter.univ-st-etienne.fr (which is an MX record =pointing to STROPH - the real machine) I get an error code O134 : No, you get error code %X134: $ WRITE SYS$OUTPUT F$MESSAGE(%X134) %SYSTEM-F-IVADDR, invalid media address If I recall correctly, that's CMUIP's way of telling you there was a problem with the name service lookup. Which TCP/IP package are you using? =15-OCT-1993 16:35:57.53 %FINDPATH, Site-spec expand on criter.univ-st-etienne.fr = err=00000134 = ^^^^^^^^^^^^ I just did an NSLOOKUP on CRITER.UNIV-ST-ETIENNE.FR. There's a record for it, but no A records. =When the address is reduced to univ-st-etienne.fr I get 0870 : Again, you get %X870: $ WRITE SYS$OUTPUT F$MESSAGE(%X870) %SYSTEM-W-ENDOFFILE, end of file another indication that your software is having problems. This node also has an MX record but no A record. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 20 Oct 1993 06:10:45 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Controlling size of queue file Message-ID: <1993Oct20.111501.17335@vax.oxford.ac.uk> Date: 20 Oct 93 11:15:01 GMT To: MX-List@WKUVX1.BITNET The Problem with the MX Queue Control File ****************************************** Here at Oxford we have a problem with an ever increasing MX queue file. As the file grows, so the performance declines and MX virtually grinds to a halt. Our MX system receives about 1500 outgoing and 4200 incoming messages per day: we are running on a VAX 6620. When this happens we have no choice but to shut down all the MX processes and tidy up the queue file with a CONVERT/RECLAIM job. Users are given a warning, then if they don't quit they are thrown off. The CONVERT/RECLAIM job recovers space in the queue file. MX is shut down twice daily automatically for this purpose. And also to perform a CONVERT/FDL at night, if necessary. As it is the start of a new academic year, we are presently signing up new users by the dozen so this problem is likely to become significantly worse in the near future. The cause of the problem seems to be as follows. The MX router attempts to perform a CONVERT/RECLAIM at regular time intervals defined by the logical FLQ_RECLAIM_WAIT. In order to do this it requires exclusive access to the queue file. If this is not the case it tries again every minute until it is successful. Unfortunately the MX_MAILSHR program, which is the interface between VMS MAIL and MX, is written in such a way that the queue file is held open by a user throughout the period of time that he is typing his message. This means that any user has the power to prevent CONVERT/RECLAIM from happening. On our system there is normally somebody typing MAIL in round the clock, so the automatic CONVERT/RECLAIM is generally only performed about once a day. One possible strategy we are contemplating is to modify the source code of MX_MAILSHR, to avoid the user holding the queue file open. This requires careful consideration of cases where the user aborts his message, or the CONVERT/FDL process steps in while he is typing. Hunter Goatley is to rewrite the queue handling routines to use a 'relative file' structure instead of an indexed file, which will solve the problem. But this is not imminent. If anybody has successfully tackled this problem in a simpler way I would be most interested to know. Jeremy Martin ================================================================================ Archive-Date: Wed, 20 Oct 1993 07:46:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 13:41:22 +0100 From: Herve GILIBERT CRI universite Jean Monnet ST ETIENNE Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <009744D7.43797600.14263@stroph.univ-st-etienne.fr> Subject: Re: Debuging router. > No, you get error code %X134: > $ WRITE SYS$OUTPUT F$MESSAGE(%X134) > %SYSTEM-F-IVADDR, invalid media address > If I recall correctly, that's CMUIP's way of telling you there was a problem > with the name service lookup. Which TCP/IP package are you using? > I'm effectively using CMUIP. > > I just did an NSLOOKUP on CRITER.UNIV-ST-ETIENNE.FR. There's a record for it, > but no A records. > You are right Carl, my purpose was to have mail addresses independant of the real node name (STROPH), it seems not to be the good way ! Perhaps I should have to use CNAME record : criter in cname stroph in mx 0 stroph.univ-st-etienne.fr Or is there a more efficient way to do that ? > =When the address is reduced to univ-st-etienne.fr I get 0870 : > > Again, you get %X870: > $ WRITE SYS$OUTPUT F$MESSAGE(%X870) > %SYSTEM-W-ENDOFFILE, end of file > another indication that your software is having problems. This node also has > an MX record but no A record. It is CMUIP 6.5-A Thanks Carl. -- Herve GILIBERT UUUU UUUU CRITeR UUUU UUUU Universite Jean Monnet St-Etienne UUUU UUUU 23, Rue du Dr. P. Michelon UUUU UUUU 42023 ST ETIENNE Cedex 2 UUUU UUUU Tel : 33 77 42 15 79 UUUU UUUU Fax : 33 77 42 15 75 UUUUUUUUUUU RFC822: gilibert@criter.univ-st-etienne.fr UUUUUUUUU ================================================================================ Archive-Date: Wed, 20 Oct 1993 08:15:36 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU From: "Eric R. Rountree" Date: 20 Oct 1993 9:22:34 ADT Subject: RE: queue file grows and grows Reply-To: MX-List@WKUVX1.BITNET Okay, I've changed the value of the logical name MX_FLQ_RECLAIM_WAIT to thirty minutes. Now, how do I get that value to stay after MX is stopped and restarted? Thanks Eric Rountree System Manager Business School Site Academic Computing Services Dalhousie University Halifax, Nova Scotia ================================================================================ Archive-Date: Wed, 20 Oct 1993 08:15:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 09:04:24 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <009744B0.92690CC0.31932@swdev.si.com> Subject: Bad numbers in QUEUE SHOW This morning I executed MCP QUEUE SHOW/ALL and saw the following: 31815 INPROG ****** LOCAL SMTP 31816 READY ****** (waiting until 20-OCT-1993 08:51:37.65) I assume this is due to the person sending a very large file whose byte count is over five digits. At the same time, I saw entries like this: Entry: 31908, Origin: [Local] Status: IN-PROGRESS, size: 85 bytes Created: 20-OCT-1993 08:39:13.38, expires 19-NOV-1993 08:39:13.38 Last modified 20-OCT-1993 08:39:58.25 SMTP entry #31911, status: READY, size: 85 bytes, waiting for retry until 20-O CT-1993 09:10:21.69 Created: 20-OCT-1993 08:39:44.40, expires 19-NOV-1993 08:39:13.38 Last modified 20-OCT-1993 08:40:21.78 Recipient #1: , Route=MAILTALK.SI.COM Error count=1 Last error: %MX_SMTP-W-INSUFF_STORAGE, action not taken: insufficient syst em storage Are they related? Is there a maximum size to messages people may send? -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Wed, 20 Oct 1993 09:33:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 09:31:32 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009744B4.5C931E39.10296@WKUVX1.BITNET> Subject: RE: Bad numbers in QUEUE SHOW "Brian Tillman" writes: > >This morning I executed MCP QUEUE SHOW/ALL and saw the following: > >31815 INPROG ****** LOCAL > SMTP 31816 READY ****** > (waiting until 20-OCT-1993 08:51:37.65) > >I assume this is due to the person sending a very large file whose byte count is >over five digits. Correct >At the same time, I saw entries like this: > [...] > Recipient #1: , Route=MAILTALK.SI.COM > Error count=1 > Last error: %MX_SMTP-W-INSUFF_STORAGE, action not taken: insufficient syst >em storage > >Are they related? Is there a maximum size to messages people may send? Not by MX, but there may be a limit on what the remote system will receive. That's what you're seeing here---the remote system didn't have enough storage for the message being sent. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 20 Oct 1993 10:07:14 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 09:30:39 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009744B4.3D6434E9.10294@WKUVX1.BITNET> Subject: RE: queue file grows and grows "Eric R. Rountree" writes: > >Okay, I've changed the value of the logical name MX_FLQ_RECLAIM_WAIT to >thirty minutes. Now, how do I get that value to stay after MX is stopped and >restarted? > Add the following line to MX_DIR:MX_LOGICALS.DAT: MX_FLQ_RECLAIM_WAIT\/SYSTEM/EXEC\0 00:30:00 Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 20 Oct 1993 11:47:31 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 17:41:22 EDT From: "Andy, Systems Manager" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: udaa055@bay.cc.kcl.ac.uk Message-ID: <009744F8.CACB2C40.337@bay.cc.kcl.ac.uk> Subject: MX repeated delivery Here's an odd problem that frightened one of our users near to death!!! This user was logged in and suddenly started receiving a flood of messages from MX - approx 1 per second. On looking at the mail file, all of these messages where EXACTLY the same - down to the dates and times of the sender - so it appears that MX local or MX Router has run amok and is delivering the same message over and over again. In desperation we shut down MX and restarted it and that seemed to solve the problem. However, the user was left with 60000 messages to delete! Now I'm concerned about this. Firstly, it happened once before and I put it down to a glitch of some kind but now it's happened again, I worry that there might be a subtle synchronization bug in MX. Secondly, because MX uses EXQUOTA, there's a serious danger of filling up the disk uncontrollably. I've removed EXQUOTA from the MX local process to gauge the pros and cons of having it/not having it. Can anyone (Matt or Hunter perhaps) shed light on this `bug'? What would be the best combination of debug logicals to set in order to get more information should it happen again? Oh yes, versions are: VMS 5.5-2 MX 3.3 NETLIB 1.5 CMU 6.6-5a Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Wed, 20 Oct 1993 11:52:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 12:39:38 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.BITNET To: WKUVX1.BITNET!mx-list@esseye.si.com Message-ID: <009744CE.A3A106A0.32246@swdev.si.com> Subject: RE: Bad numbers in QUEUE SHOW Hunter Goatley (goathunter@WKUVX1.BITNET) writes: >Not by MX, but there may be a limit on what the remote system will >receive. That's what you're seeing here---the remote system didn't >have enough storage for the message being sent. OK, maybe you can explain this: I stopped MX, CONVERTed the queue file, restarted MX and the messages were all delivered within five minutes. I didn't change the remote system at all. Could you add displaying six digit (or seven) byte counts to the wish list? -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Wed, 20 Oct 1993 11:52:55 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 12:44:12 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.BITNET To: WKUVX1.BITNET!mx-list@esseye.si.com Message-ID: <009744CF.473CE040.32252@swdev.si.com> Subject: MX error mesage listing When MX encounters an error in sending mail, messages are displayed in the QUEUE listings MCP displays, like this: Last error: %MX_SMTP-W-INSUFF_STORAGE, action not taken: insufficient system storage I've gone through the MX documentation a couple of times looking for an appendix that lists the errors MX can display and an explanation of what they mean, much like one can find in documentation for other VMS product vendors and I don't see it. Am I blind? If not, would it be possible to include such an appendix in a future release of the documentation? -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Wed, 20 Oct 1993 14:57:42 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 14:55:21 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009744E1.99312FDE.10405@WKUVX1.BITNET> Subject: RE: MX repeated delivery "Andy, Systems Manager" writes: > >Here's an odd problem that frightened one of our users near to death!!! > >This user was logged in and suddenly started receiving a flood of messages from >MX - approx 1 per second. On looking at the mail file, all of these messages >where EXACTLY the same - down to the dates and times of the sender - so it >appears that MX local or MX Router has run amok and is delivering the same >message over and over again. [...] >Can anyone (Matt or Hunter perhaps) shed light on this `bug'? What would be >the best combination of debug logicals to set in order to get more information >should it happen again? > >Oh yes, versions are: > > VMS 5.5-2 > MX 3.3 Are you sure you're running the final MX V3.3 release, or could it be one of the beta versions? This was one of the last bugs I fixed before releasing MX V3.3 back in May. It *could* be something new, but I don't think it is. Setting debug logicals wouldn't net you much---the problem occurred when MX Local couldn't open the user's MAIL.MAI for some reason. Instead of retrying, it got into a loop trying the delivery over and over and over and over and.... As I said, that was one of the last bugs I fixed.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 20 Oct 1993 15:04:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 14:57:57 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009744E1.F6518E0C.10410@WKUVX1.BITNET> Subject: RE: Bad numbers in QUEUE SHOW "Brian Tillman" writes: > >>Not by MX, but there may be a limit on what the remote system will >>receive. That's what you're seeing here---the remote system didn't >>have enough storage for the message being sent. > >OK, maybe you can explain this: > >I stopped MX, CONVERTed the queue file, restarted MX and the messages were all >delivered within five minutes. I didn't change the remote system at all. > Whatever happened on the remote system must have cleared by that time (meaning that there was some other problem and *not* a file size limit). >Could you add displaying six digit (or seven) byte counts to the wish list? Already on there. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 20 Oct 1993 15:06:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 15:01:22 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009744E2.704470A3.10412@WKUVX1.BITNET> Subject: RE: MX error mesage listing "Brian Tillman" writes: > >When MX encounters an error in sending mail, messages are displayed in the QUEUE >listings MCP displays, like this: > >Last error: %MX_SMTP-W-INSUFF_STORAGE, action not taken: insufficient system >storage > >I've gone through the MX documentation a couple of times looking for an appendix >that lists the errors MX can display and an explanation of what they mean, much >like one can find in documentation for other VMS product vendors and I don't see >it. Am I blind? If not, would it be possible to include such an appendix in a >future release of the documentation? I'll try. As I hinted at earlier, this particular message is coming from the remote system---the SMTP server on the remote system is returning this error status to MX. There are a number of those that are documented in RFC 821. This one is: 452 Requested action not taken: insufficient system storage The full list is included below my sig. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ------------------------------------------------------------------------------- 4.2.1. REPLY CODES BY FUNCTION GROUPS 500 Syntax error, command unrecognized [This may include errors such as command line too long] 501 Syntax error in parameters or arguments 502 Command not implemented 503 Bad sequence of commands 504 Command parameter not implemented 211 System status, or system help reply 214 Help message [Information on how to use the receiver or the meaning of a particular non-standard command; this reply is useful only to the human user] 220 Service ready 221 Service closing transmission channel 421 Service not available, closing transmission channel [This may be a reply to any command if the service knows it must shut down] 250 Requested mail action okay, completed 251 User not local; will forward to 450 Requested mail action not taken: mailbox unavailable [E.g., mailbox busy] 550 Requested action not taken: mailbox unavailable [E.g., mailbox not found, no access] 451 Requested action aborted: error in processing 551 User not local; please try 452 Requested action not taken: insufficient system storage 552 Requested mail action aborted: exceeded storage allocation 553 Requested action not taken: mailbox name not allowed [E.g., mailbox syntax incorrect] 354 Start mail input; end with . 554 Transaction failed ================================================================================ Archive-Date: Wed, 20 Oct 1993 18:59:54 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 20 Oct 1993 17:59:03 MDT From: Bill Dailey (303) 490-8324 Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <009744FB.432FDF80.22053@gpsrv1.gpsr.colostate.edu> Subject: Word Perfect Office I'm looking into a mail package called Word Perfect Office, the powers tobe said this is the package that we will be using in the future. (AND I AIM TO PLEASE) All of our mail is routed from our VMS/VAX running MX to (pathworks, suns, & hp computers) The Question IS: Is there a way to forward mail from "MX to the WordPerfect Office package" and back? VMS mail can forward to WP OFFICE with a username like "WPGATE::username" I need to give WP Office internet access thru VMS MAIL & MX unless there is better way of doing this. VMS 5.4 ucx 1.3 using mx3.1 (will upgrade soon) thank you, William J. Dailey, GPSR Systems Analyst ------------------------------------------------------------------------------ USDA-ARS-NPA Great Plains Systems Res. TEL: 303-490-8324 P.O. Box E FAX: 303-490-8310 303 South Howes Rm. 227 FTS2000: A03RLGPSR Fort Collins, CO 80522 INTERNET: dailey@gpsrv1.gpsr.colostate.edu ------------------------------------------------------------------------------ ================================================================================ Archive-Date: Thu, 21 Oct 1993 12:29:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 21 Oct 1993 17:42:11 EDT From: "Andy, Systems Manager" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: udaa055@bay.cc.kcl.ac.uk Message-ID: <009745C2.1255E4A0.3209@bay.cc.kcl.ac.uk> Subject: RE: MX repeated delivery >Are you sure you're running the final MX V3.3 release, or could it be >one of the beta versions? This was one of the last bugs I fixed >before releasing MX V3.3 back in May. It *could* be something new, >but I don't think it is. Well I'm fairly sure I've got the latest version but I'm happy to pick it up again if you think that might be the problem. I'll do that and get back to you. >Setting debug logicals wouldn't net you much---the problem occurred >when MX Local couldn't open the user's MAIL.MAI for some reason. >Instead of retrying, it got into a loop trying the delivery over and >over and over and over and.... As I said, that was one of the last >bugs I fixed.... I've already discovered this! I've sent you some mail with a log file that shows some repeated attempts - this may or may not be the same problem. Thanks for your help Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Thu, 21 Oct 1993 14:07:56 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Controlling size of queue file Message-ID: <2a4iv4$o79@gap.cco.caltech.edu> From: Date: 20 Oct 1993 23:52:04 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0097433B.59277A80.13885@ccstat.mc.duke.edu>, Irv Eisen writes: =Last week Hunter sent out the following example of a com file to keep the =queue file down to size. I was wondering why he used the dcl convert =command as opposed to 'mcp queue reclaim.' ><$ convert/fdl=mx_flq_dir:system_queue mx_flq_dir:system_queue.flq_ctl - >< mx_flq_dir:system_queue.flq_ctl; QUEUE RECLAIM uses, I think, callable CONVERT to do the equivalent of a CONVERT/RECLAIM. This frees empty buckets for reuse. It doesn't, however, give as much of an improvement as CONVERT does. See the CONVERT and CONVERT/RECLAIM Utility manual for details. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Thu, 21 Oct 1993 15:29:02 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 21 Oct 1993 13:24:05 PDT From: Jim Wheeler # 916-978-5089 Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: jimww@sacto.mp.usbr.gov Message-ID: <0097459E.03CD893E.17546@sacto.mp.usbr.gov> Subject: RE: Word Perfect Office >From: MX%"MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU" 20-OCT-1993 17:06:58.00 > >I'm looking into a mail package called Word Perfect Office, >the powers tobe said this is the package that we will be using in the >future. (AND I AIM TO PLEASE) as you should - BUT - you'll be soreeeeeeeeeeeeee >All of our mail is routed from our VMS/VAX running MX to >(pathworks, suns, & hp computers) ^^^^ We put the WPO/SMTP gateway on our SUN. We can mail through the gateway to our NOVELL net running WPO both ways. We are in the process of setting this up now. Your WPO net may be smaller than ours and your routes might be small, however, you do need the mail routes and they can get interesting. We are using MX to simplify the mail address. You will need width 132 to evaluate the rewrite rules. These are ones we use: Address-rewriting rules: Rewrite "<{user}@2kpo100.mp.usbr.gov>" => "" ^ ^ ^ ^ ^ ^ ^ ------------------ | | | | | | | ip domain name | | | | | | wpo/smtp gate on sun | | | | | WPO host | | | | WPO mail hub | | | WPO mail hub | | wpo/smtp gate on wpo pc | wpo/platform bridge on pc & sun wpo host (the sun) The wpo "route" must be included on each to line (mpnetmgr......2kpo100) with the mx: jbryant@2kpo100.mp.usbr.gov and mx takes care of it. Rewrite "<{user}@2mp1100.mp.usbr.gov>" => "" Henry Miller (henrym@sacto.mp.usbr.gov) set it up and it does work. > >The Question IS: Is there a way to forward mail from "MX to the WordPerfect > Office package" and back? > >VMS mail can forward to WP OFFICE with a username like "WPGATE::username" >I need to give WP Office internet access thru VMS MAIL & MX unless there >is better way of doing this. > >VMS 5.4 >ucx 1.3 >using mx3.1 (will upgrade soon) > >thank you, > > >William J. Dailey, GPSR Systems Analyst >------------------------------------------------------------------------------ >USDA-ARS-NPA >Great Plains Systems Res. TEL: 303-490-8324 >P.O. Box E FAX: 303-490-8310 >303 South Howes Rm. 227 FTS2000: A03RLGPSR >Fort Collins, CO 80522 INTERNET: dailey@gpsrv1.gpsr.colostate.edu >------------------------------------------------------------------------------ jimww ================================================================================ # James W. Wheeler # # # Regional Systems & WAN Manager # voice: 916 978-5089 fax: 916-978-5284 # # Mid Pacific Region # # # U.S. Bureau of Reclamation # inet: jimww@sacto.mp.usbr.gov # # 2800 Cottage Way MP1130 # # # Sacramento, CA 95825 # # ================================================================================ ================================================================================ Archive-Date: Thu, 21 Oct 1993 19:25:24 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Mass mailing list adds Message-ID: <1993Oct21.133752.3709@merrimack.edu> From: Reply-To: MX-List@WKUVX1.BITNET Date: 21 Oct 93 13:37:51 To: MX-List@WKUVX1.BITNET I was just given a list of a couple hundred people to add to a mailing list. Is there an easy way to do it? cheers, rand ================================================================================ Archive-Date: Thu, 21 Oct 1993 19:25:45 CDT Sender: list-mgr@WKUVX1.BITNET Subject: converting and fragmentation Message-ID: <1993Oct21.091546.3708@merrimack.edu> From: Reply-To: MX-List@WKUVX1.BITNET Date: 21 Oct 93 09:15:45 To: MX-List@WKUVX1.BITNET Re: Converting the system_queue regularly Please don't all go and blindly convert your queue files. Get out EDIT/FDL and make the FDL fit your site. Is there a way to get the smtp accounting file to preallocate a big chunk of space and use large extensions? cheers, rand ================================================================================ Archive-Date: Thu, 21 Oct 1993 19:25:51 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Mass mailing list adds Message-ID: <1993Oct21.170702.178@buckie.hsc.colorado.edu> From: Date: 21 Oct 93 17:07:02 MDT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993Oct21.133752.3709@merrimack.edu>, Rand@lucy.merrimack.edu. (Rand) writes: >I was just given a list of a couple hundred people to add to a mailing >list. >Is there an easy way to do it? Create a file with approprate ADD commands and then send the file to MX%listname-REQUEST. I'll type them in for $50/hour if you need. :-) -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Thu, 21 Oct 1993 19:25:59 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Why do reverse lookups? Message-ID: <1993Oct21.110407.17375@vax.oxford.ac.uk> From: Reply-To: MX-List@WKUVX1.BITNET Date: 21 Oct 93 11:04:07 GMT To: MX-List@WKUVX1.BITNET Hi, Is there a reason why the Router does reverse address lookups? We hit a problem trying to send a message to site salk-sc2.sdsc.edu. The router did a reverse lookup and rewrote this as salk-sc2.153.31.192.in-addr.arpa. This generated a 'non-existant host/domain' error. Sending to this site from a mailer that doesn't do reverse lookups works OK. How about a SET ROUTER/NOREVERSE command so that reverse lookups could be disabled? Dave -- David Hastings | "There's nothing wrong with my sense VAX Systems Programmer | of reality - I have it thoroughly Oxford University Computing Services| serviced once a fortnight" - DNA daveh@vax.oxford.ac.uk | ================================================================================ Archive-Date: Thu, 21 Oct 1993 19:26:20 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: queue file grows and grows Message-ID: <1993Oct21.105417.17374@vax.oxford.ac.uk> From: Reply-To: MX-List@WKUVX1.BITNET Date: 21 Oct 93 10:54:17 GMT To: MX-List@WKUVX1.BITNET In article , "Eric R. Rountree" writes: > Okay, I've changed the value of the logical name MX_FLQ_RECLAIM_WAIT to > thirty minutes. Now, how do I get that value to stay after MX is stopped and > restarted? > > Thanks > > Eric Rountree > System Manager > Business School Site > Academic Computing Services > Dalhousie University > Halifax, Nova Scotia You define the logical in the file MX_DIR:MX_LOGICALS.DAT. See the MX Management Guide chapter 9. Dave -- David Hastings | "There's nothing wrong with my sense VAX Systems Programmer | of reality - I have it thoroughly Oxford University Computing Services| serviced once a fortnight" - DNA daveh@vax.oxford.ac.uk | ================================================================================ Archive-Date: Thu, 21 Oct 1993 19:26:36 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: queue file grows and grows Message-ID: <2a6e28$lq5@gap.cco.caltech.edu> From: Date: 21 Oct 1993 16:40:39 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article , "Eric R. Rountree" writes: =Okay, I've changed the value of the logical name MX_FLQ_RECLAIM_WAIT to =thirty minutes. Now, how do I get that value to stay after MX is stopped and =restarted? You edit MX_DIR:MX_LOGICALS.DAT. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Thu, 21 Oct 1993 19:47:31 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Why do reverse lookups? Message-ID: <1993Oct21.173636.14727@news.arc.nasa.gov> From: Date: Thu, 21 Oct 1993 17:36:36 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993Oct21.110407.17375@vax.oxford.ac.uk>, daveh@vax.oxford.ac.uk (Dave Hastings, OUCS) writes: >Is there a reason why the Router does reverse address lookups? Primarily to do host name completion. For example, if you sent a message to "daveh@vax", it wants to try and expand that to "daveh@vax.oxford.ac.uk". This makes the address valid for SMTP purposes. Admittedly, this probably isn't the best way to do this, and it probably shouldn't be done on addresses whose host names contain dots. However, you can write your own domain expander if you like. >We hit a problem trying to send a message to site salk-sc2.sdsc.edu. The router >did a reverse lookup and rewrote this as salk-sc2.153.31.192.in-addr.arpa. This >generated a 'non-existant host/domain' error. Because SDSC has messed up the IN-ADDR entry for that system. >Sending to this site from a mailer that doesn't do reverse lookups works OK. > >How about a SET ROUTER/NOREVERSE command so that reverse lookups could be >disabled? You an remove the existing domain expander with: $ DEASSIGN/SYSTEM/EXEC MX_SITE_DOM_EXPANSION $ DELETE MX_EXE:DOMAIN_EXPANSION.EXE;* Or, as I mentioned above, you can write your own that works more to your liking. -Matt -- Matthew Madison | madison@tgv.com | +1 408 457 5200 TGV, Inc. | 101 Cooper Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Fri, 22 Oct 1993 07:56:37 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 22 Oct 1993 08:53:06 EST From: Alan Simon Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <00974641.52F1B5A0.5519@shrsys.hslc.org> Subject: RE: Mass mailing list adds > From: MX%"MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU" 21-OCT-1993 20:33:03.49 > Subj: Mass mailing list adds > I was just given a list of a couple hundred people to add to a mailing > list. > Is there an easy way to do it? > > cheers, > > rand Here's a crude but effective command file I recently wrote to convert a VMS Mail distribution list to a MX mailing list. Modify the file before invoking to reflect your environment. $! CONVERT_DISTLIST_TO_LISTSERV.COM $! 21-SEP-1993 $! Alan C. Simon (simon@hslc.org) $! $! This command file will convert a VMS Mail distribution list to a MX mailing $! list. $! $ DISTLISTNAME: $ READ/END=EXIT/ERROR=EXIT/PROMPT="Distribution List Name?: " - SYS$COMMAND DLN $ DLN = F$EDIT(DLN,"TRIM,UPCASE") $ IF F$LOCATE(".DIS",DLN) .EQS. F$LENGTH(DLN) THEN DLN = "''DLN'.DIS" $! $! Set the directory specification in the next line as needed. $! $ IF F$SEARCH("SYS$APPS0:[MAILDIST]''DLN'") .EQS. "" $ THEN WRITE SYS$OUTPUT "" $ WRITE SYS$OUTPUT "Distribution list not found." $ WRITE SYS$OUTPUT "" $ GOTO DISTLISTNAME $ ENDIF $! $ LISTSERVNAME: $ READ/END=EXIT/ERROR=EXIT/PROMPT="Mailing List Name?: " SYS$COMMAND MLN $ MLN = F$EDIT(MLN,"TRIM,UPCASE") $! $! $! Set the directory specification in the next line as needed. $! $ OPEN/SHARE=WRITE DISTLIST SYS$APPS0:[MAILDIST]'DLN' $ READ_NAMES: $ READ/END_OF_FILE=EXIT DISTLIST NAME $! $ SEND: $ IF F$LOCATE("MX%",NAME) .NES. F$LENGTH(NAME) THEN NAME = "''F$EXTRACT(4,F$LENGTH(NAME),NAME)' $ IF F$LOCATE("mx%",NAME) .NES. F$LENGTH(NAME) THEN NAME = "''F$EXTRACT(4,F$LENGTH(NAME),NAME)' $! $! Set the location in the next line as needed. $! $ IF F$LOCATE("@",NAME) .EQS. F$LENGTH(NAME) THEN NAME = "''NAME'@SHRSYS.HSLC.ORG" $ WRITE SYS$OUTPUT NAME $ OPEN/WRITE OUTPUT_FILE ADD_'F$GETJPI("","PID")'.TXT $ WRITE OUTPUT_FILE "ADD/NONOTIFY ''MLN' ''NAME'" $ CLOSE OUTPUT_FILE $! $! Set the location in the next line as needed. $! $ MAIL ADD_'F$GETJPI("","PID")'.TXT "LISTSERV@HSLC.ORG" $ DELETE ADD_'F$GETJPI("","PID")'.TXT;0 $ GOTO READ_NAMES $ EXIT: $ CLOSE DISTLIST $ EXIT ------------------------------------------------------------------------------- Alan Simon simon@hslc.org Associate Director simon@shrsys.hslc.org Health Sciences Libraries Consortium VOICE: (215) 222-1532 3600 Market Street, Suite 550 FAX: (215) 222-0416 Philadelphia, PA 19104 ------------------------------------------------------------------------------- ================================================================================ Archive-Date: Fri, 22 Oct 1993 22:12:26 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX repeated delivery Message-ID: <1993Oct22.184947.1@etu.univ-compiegne.fr> From: system@etu.univ-compiegne.fr Reply-To: MX-List@WKUVX1.BITNET Date: 22 Oct 93 18:49:47 MET To: MX-List@WKUVX1.BITNET We have had the same problem VMS 5.5-2, MX3.3, MSA 1.2 A user activating the Mail notifier/forwarder to a Mac cause the same behavior turn around: NO forwarding to a MAC Someone said to me that DEC is not supporting Mail notification on a MAC with MSA V1.2 (will be supported with next version). But I'm not sure of that Gilbert Delafosse System Manager Universite de Technologie de Compiegne e-mail: Gilbert.Delafosse@mx.univ-compiegne.fr ================================================================================ Archive-Date: Mon, 25 Oct 1993 08:22:28 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sun, 24 Oct 1993 11:31 EDT From: MCW@UFPINE.BITNET Reply-To: MX-List@WKUVX1.BITNET Subject: Yet another queue question To: mx-list@WKUVX1.BITNET Thanks for all the advice about reducing the size of the queue file. Here's another problem. I have numerous entries in my file that look like this: Entry: 740, Origin: [SMTP] Status: IN-PROGRESS, size: 981 bytes Created: 28-SEP-1993 11:52:20.69, expires 28-OCT-1993 11:52:20.69 Last modified 28-SEP-1993 12:47:57.96 They don't change, they don't go anywhere, and they hang around for a month. I have a lot with the same date, which happened to be a day we were having disk problems, but there are others as well. I assume I could cancel them, but other than that, how could I make the router do something with them? Would I want to? Is there anyway to change the 30 day expiration? (I'd settle for a week or so.) Mike Wright University of Florida Internet: mcw@pine.circa.ufl.edu BITNET: mcw@ufpine ================================================================================ Archive-Date: Mon, 25 Oct 1993 09:09:11 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sun, 24 Oct 1993 23:49:32 +0100 From: Per Hogstedt Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Mass mailing list adds To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.edu Message-ID: <00974850.E2AED040.17548@plab.se> >>I was just given a list of a couple hundred people to add to a mailing >>list. >>Is there an easy way to do it? > >Create a file with approprate ADD commands and then send the file to >MX%listname-REQUEST. I seem to recall that last time I did this, the "how-do-I-get-the-personal- name-of-the-subscriber-FAQ" was not yet in the docs. Since I am at home right now, I cannot check the doc:s, so to spare you some trouble or repeat what you already know: Provided you have appropriate access to the list (owner and/or manager), you type: ADD "Personal Name" The "'s and <>'s are needed. You may want to add a /NOCASE to the ADD command. >I'll type them in for $50/hour if you need. :-) Hmm, with the current recession in Sweden, I'm tempted to offer it at $49.95 :-) >-Dan Wing, Systems Administrator, University Hospital, Denver > dwing@uh01.colorado.edu or wing@eisner.decus.org ------- Per Hogstedt, Lindholmen Utveckling, Box 8714, S-402 75 Gothenburg, Sweden Internet: hogstedt@plab.se (or: hogstedt@ae.chalmers.se) Phone: +46 31 50 70 50, Fax +46 31 51 53 13 ================================================================================ Archive-Date: Mon, 25 Oct 1993 14:24:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 25 Oct 1993 12:03:08 PDT From: "Bob Johns, (604)363-6520" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <009748B7.5F6E7AC0.24728@ccs.ios.bc.ca> Subject: Question re return address I have noticed that sometimes mail is delivered with a "From:" address of the form MX%"user@domain" and sometimes of the form IOSCCS::MX%"user@domain" where "IOSCCS" is our cluster alias. (MX runs on all cluster members). If a reply is sent to the first form, all remote mailers seem to be happy. But if a reply is sent to the second form, some mailers complain (when the remote addressee tries to reply to our reply). Further investigation shows the following: Mail sent to IOSCCS::MX%"bob@ios.bc.ca" (i.e. to myself) shows up with a "From:" address of IOSCCS::MX%"'IOSCCS::BOB'@ccs.ios.bc.ca". The "ccs" is my nodename. No problem there. I'm assuming MX is generating the correct return address, but that some remote mailers can't handle this more complicated form. The more fundamental question, then, is why does the mail sometimes appear in my mailbox with our cluster alias as a prefix (which results in the more complex return address), and sometimes without the alias? A workaround seems to be to carefully watch for the cluster alias prefix case, and delete it from the return address before sending one's reply. But mistakes are made, with the result that some systems cannot reply. I am running MX v3.1b, with VMS v5.5-1 and UCX v2.0d. Any ideas? Suggestions? Thanks for your help! Bob Johns (bob@ios.bc.ca) Institute of Ocean Sciences Sidney, B.C. Canada ================================================================================ Archive-Date: Mon, 25 Oct 1993 14:24:21 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Yet another queue question Message-ID: <2agvac$7ks@gap.cco.caltech.edu> From: Date: 25 Oct 1993 16:36:28 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <16843363@MVB.SAIC.COM>, MCW%UFPINE.bitnet@ULKYVM.LOUISVILLE.EDU writes: = =Thanks for all the advice about reducing the size of the queue file. =Here's another problem. I have numerous entries in my file that =look like this: = =Entry: 740, Origin: [SMTP] = Status: IN-PROGRESS, size: 981 bytes = Created: 28-SEP-1993 11:52:20.69, expires 28-OCT-1993 11:52:20.69 = Last modified 28-SEP-1993 12:47:57.96 = =They don't change, they don't go anywhere, and they hang around for =a month. I have a lot with the same date, which happened to be a =day we were having disk problems, but there are others as well. = =I assume I could cancel them, but other than that, how could I make the =router do something with them? Would I want to? Is there anyway to change =the 30 day expiration? (I'd settle for a week or so.) $ MCR MX_EXE:MCP QUEUE READY 740 -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Mon, 25 Oct 1993 14:54:46 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 25 Oct 1993 15:45:28 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: hardis@garnet.nist.gov Message-ID: <009748D6.6E2DB700.26364@garnet.nist.gov> Subject: Re: Debuging router. >> No, you get error code %X134: >> $ WRITE SYS$OUTPUT F$MESSAGE(%X134) >> %SYSTEM-F-IVADDR, invalid media address >> If I recall correctly, that's CMUIP's way of telling you there was a problem >> with the name service lookup. Which TCP/IP package are you using? > I'm effectively using CMUIP. Pardon me for getting into this discussion late, but this may be related to the CMUIP bug where NAMRES forgets about the IP: device. When I get "invalid media address" errors, it's a reminder that after CMUIP starts up, I should have entered (from the SYSTEM account): $ IPNCP NAMRES EXIT $ IPNCP STARTUP/NAMRES ================================================================================ Archive-Date: Mon, 25 Oct 1993 16:04:40 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 25 Oct 1993 16:12:05 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.BITNET To: WKUVX1.BITNET!MX-list@esseye.si.com Message-ID: <009748DA.25CEF6A0.2576@swdev.si.com> Subject: RE: Question re return address >I have noticed that sometimes mail is delivered with a "From:" address of the >form > > MX%"user@domain" > >and sometimes of the form > > IOSCCS::MX%"user@domain" > >where "IOSCCS" is our cluster alias. (MX runs on all cluster members). What you describe can occur when you do not have MAIL$SYSTEM_FLAGS set correctly on all nodes of the cluster. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Mon, 25 Oct 1993 17:04:26 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Question re return address Message-ID: <1993Oct25.140229.199@buckie.hsc.colorado.edu> From: Date: 25 Oct 93 14:02:29 MDT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <16853235@MVB.SAIC.COM>, "Bob Johns, (604)363-6520" writes: >The "ccs" is my nodename. No problem there. I'm assuming MX is generating >the correct return address, but that some remote mailers can't handle this >more complicated form. Right. >The more fundamental question, then, is why does the >mail sometimes appear in my mailbox with our cluster alias as a prefix (which >results in the more complex return address), and sometimes without the alias? You probably have an incorrect value for MAIL$SYSTEM_FLAGS. This is described on page 6-35 of the VMS V6.0 "OpenVMS System Manager's Manual: Essentials", and in VMS V5.x in the Mail manual (with no cross reference from the System Management index, alas): value 1: This node is part of a homogeneous VMScluster (all disks are accessible to all VMScluster nodes, and there is a common SYSUAF). value 2: Mail should attempt to $BRKTHRU all VMScluster nodes for new mail value 4: Mail should include a timestamp on the user's screen when informing about new mail. On most VMSclusters you want a value of 3 (2+1) or 7 (4+2+1) for this logical. The poor placement of this documentation in the MAIL manual in VMS V5.0 explains why a lot of sites don't have this logical set correctly. This logical is also briefly mentioned in the MX V3.3 installation guide, section 1.2, "VMScluster Support and MX Clusters". -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Mon, 25 Oct 1993 23:23:47 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 26 Oct 1993 03:46:11 GMT From: Jamie Jones Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <0097493B.1C8E6060.2275@hicom.lut.ac.uk> Subject: RE: MX-LIST Digest V93 #130 => > MX%"person@original-smtp-address"@UK.AC.NOTTINGHAM.CCC.VAX => > => > Is this something that's fixable by the "percent-hack" switch? I think I've => > tried all the possible settings without success. => > => => We hit this problem as well. There doesn't seem to be a way of avoiding it => except to get rid of CBS (you'll have to soon anyway because it won't work with => VMS6) Same here. This is what we've done : dropped CBS completely, and only use MX. => > => => Are you using a dedicated mailer? We've got a Sun running the pp program => which will sort out grey book mail even if it is transfered from the VAX to the => mailer by SMTP, ie we do: => => DEFINE PATH "*" SMTP/ROUTE="oxmail.ox.ac.uk" => => The other point is that all incoming mail is routed though the mailer, so if => anybody sends grey book mail to the VAX the address is rewritten to an MX-style => one. We have done a similar thing here. Our incomming X25 mail is routed to the pp mailhost which forwards it to us via SMTP. However, using the paths : DEFINE PATH "*.ac.uk" SMTP/ROUTE="mailhost.lut.ac.uk" DEFINE PATH "*" SMTP allows us to handle the majority of our traffic directly. Only the UK academic mail is forwarded on. This brings me onto my question. Our use of the mailhost is as a favour. The less we use it, the better. Now, JANET rules say something along the lines of that if we, as a site on the X25 JANET network, want to send outgoing mail to a JANET site without SMTP, we must send it via grey book X25 mail. If the message is sourced with SMTP (as in our case) there must be a local host that can do the conversion for us. I.E. we musn't look up the MX record for the site, and route it via that (nsfnet-relay.ac.uk) The "mailhost.lut.ac.uk" host does this job for us, but with an increasing number of uk.ac sites on internet, it would be better if we could send to them directly. So, is there an easy way to say: "if its MX record is nsfnet-relay.ac.uk" then smtp/route="mailhost.lut.ac.uk" else smtp. ? Thanks, Jamie ================================================================================ Archive-Date: Tue, 26 Oct 1993 21:24:56 CDT Sender: list-mgr@WKUVX1.BITNET Subject: MX Mailer and Japanese Kanji codes Message-ID: <1993Oct26.201753.6192@msus1.msus.edu> From: Reply-To: MX-List@WKUVX1.BITNET Date: 26 Oct 93 20:17:52 -0600 To: MX-List@WKUVX1.BITNET At our site we use MX V3.3 VAX/SMTP for mailing. This works really well for inputting and receiving texts in Japanese characters. Basically, MX takes 8 bit code called "EUC" and turns it into a 7 bit code called "JIS" for network transmission. And when MX receives the network standard JIS (7 bit) coded msgs, it displays them in EUC codes. The only thing is one need to make sure that the terminal characteristics is set to eight_bit. My question is: is there any way to change the EUC code required by MX for inputting/displaying msgs to JIS? I am using Eudora-J for Macs which can download any Chinese character codes and display them in Shift-JIS for Macs. The problem occurs when Eudora-J is used to send out a msg. MX requires EUC codes but Eudora-J seems to be set to send out only JIS codes. Thus Japanese msgs are mangled into unreadble strings. The solution has to be one of the two: 1. Eudora-J should be modified to send out EUC codes as well as the current JIS codes. or 2. MX Mailer should be able to take JIS codes. Any advice wouldbe highly appreciated. Thank you. -Katsuhiko Momoi -- $B%_%M%=%?=#%;%s%H!&%/%i%&%I;T(J | Katsuhiko Momoi, Foreign Langs & Lit $B%;%s%H!&%/%i%&%I=#N)Bg3X(J | St. Cloud State University $B309q8l3X2J(J $B!!(J| St. Cloud, MN 56301-4498 U.S.A. $BEm0f>!I'(J | momoi@condor.stcloud.msus.edu ================================================================================ Archive-Date: Wed, 27 Oct 1993 00:02:40 CDT Sender: list-mgr@WKUVX1.BITNET Subject: alias/name_conversion question Message-ID: <1993Oct26.214443.2753@alien.vax.syncrude.com> From: davis@alien.vax.syncrude.com Reply-To: MX-List@WKUVX1.BITNET Date: 26 Oct 93 21:44:43 MDT To: MX-List@WKUVX1.BITNET Hello, I am using MX 3.3 as the mail router for our company. I would like to say how pleased I am to see such high quality software available through DECUS. Internally to the company there are several domains, and many hosts. I would like to provide a standard interface to the outside world for email addresses. In addition, the alias translation should be confined to one system for easier maintainance. I think that MX is a good candidate for this. For example: user: "Xavier" email address: "xx12345@foo.bar.syncrude.com" alias: "Xavier@Syncrude.Com" After reading the docs, it appears that this can be accomplished with a combination of aliases (for incoming mail) and using a "name_conversion" hook to translate the "From:" address for outbound mail. I was not clear, if "name_conversion" could be used for mail arriving from different sources (UUCP/SMTP/DECnet). Can someone tell me if this is the correct approach? There will be approx 2000 names/aliases that will have to be configured. I am concerned that this will result in poor performance in alias lookups. In fact I recall reading a comment about this issue in the documentation. Is there another way to handle this, or should I look at modifying the code? Thanks, Glenn --- Glenn Davis +1 403 790 4626 / davis@syncrude.com (Work) Syncrude Canada Ltd +1 403 743 9675 / davis@realtime.ab.ca (Home) ================================================================================ Archive-Date: Wed, 27 Oct 1993 00:47:10 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 26 Oct 1993 23:29:51 CDT From: Larry Horn Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: hornlo@okra.millsaps.edu Message-ID: <009749E0.77E66980.18185@okra.millsaps.edu> Subject: domain expander Situation: My help desk sent me: A student here has been trying to communicate with the address XXX@CHS.CORINTH.K12.MS.US but the address is not coming out the same. Instead it is coming out XXX@CHARON4.MSTATE.EDU. He wrote to the postmaster at Ms State and he says our machine is rewriting addresses. So I tried: send mail to get a bounce from charon4.msstate.edu (attached after sig) in part saying Sent: RCPT TO: Rcvd: 553 Non-Local recipients not accepted, address: is not local. look at router debug log (attached after sig) in part saying Processing address: ... expanded chs.corinth.k12.ms.us to Charon4.MsState.Edu ... address now reads: nslookup on chs.corinth.k12.ms.us says address is 130.18.80.40 nslookup on charon4.msstate.edu say addres is ALSO 130.18.80.40 I've not installed any modified domain expander -- just running MX out of the box. pardon my ignorance, but is this 1) a bug, 2) my problem, or 3) MS State's problem? Thanks, - ---------------------------------- 26-OCT-1993 23:27 C*T (USA) --- - Larry Horn / Millsaps College / Jackson, MS / hornlo@okra.millsaps.edu - ------------------------------------------------------------------ - The Bounce ---------- >Error occurred sending to the following user(s): > (via Charon4.MsState.Edu): > %MX_SMTP-F-MBX_SYNTAX_ERRO, action not taken: mailbox name not allowed > > Transcript: > Rcvd: 220 Charon4.MSstate.edu Charon 4.0-VROOM Ready > Sent: HELO okra03.millsaps.edu > Rcvd: 250 greetings okra03.millsaps.edu pleased to meet you > Sent: MAIL FROM: > Rcvd: 250 Sender Ok > Sent: RCPT TO: > Rcvd: 553 Non-Local recipients not accepted, address: is not local. > Sent: QUIT > Rcvd: 221 Charon4.MSstate.edu Saying Goodbye The Router Debug Log -------------------- >26-OCT-1993 22:47:48.15 %PROCESS, Processing entry number 18128 >26-OCT-1993 22:47:48.42 %PROCESS, Status from READ_INFO was 00000001 >26-OCT-1993 22:47:48.42 %PROCESS, Message originated in VMS Mail. >26-OCT-1993 22:47:48.43 %PROCESS, will run domain expander on envelope addresses. >26-OCT-1993 22:47:48.47 %PROCESS, Processing address: >26-OCT-1993 22:47:48.62 %PROCESS, ... expanded chs.corinth.k12.ms.us to Charon4.MsState.Edu >26-OCT-1993 22:47:48.65 %PROCESS, ... address now reads: >26-OCT-1993 22:47:48.65 %PROCESS, will run domain expander on message headers. >26-OCT-1993 22:47:48.96 %PROCESS, ... for xxx@chs.corinth.k12.ms.us expanded chs.corinth.k12.ms.us to Charon4.MsState.Edu >26-OCT-1993 22:47:50.19 %PROCESS, Finished VMSmail-origin preprocessing. >26-OCT-1993 22:47:50.19 %PROCESS, Recipient #0: >26-OCT-1993 22:47:50.19 %REWRITE, No rewrite rules matched >26-OCT-1993 22:47:50.40 %FINDPATH, Site-spec expand on Charon4.MsState.Edu err=00000000 >26-OCT-1993 22:47:50.40 %FINDPATH, domain name CHARON4.MSSTATE.EDU matched path pattern * >26-OCT-1993 22:47:50.40 %PROCESS, Rewrote as - next hop Charon4.MsState.Edu, path 2 >26-OCT-1993 22:47:50.65 %PROCESS, Adding to SMTP path: . >26-OCT-1993 22:47:51.14 %PROCESS, Path SMTP gets 1 rcpts, entry number 18129 ================================================================================ Archive-Date: Wed, 27 Oct 1993 05:27:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 27 Oct 1993 05:25:45 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00974A12.2F9F0006.12858@WKUVX1.BITNET> Subject: RE: alias/name_conversion question davis@alien.vax.syncrude.com writes: > >Hello, > >I am using MX 3.3 as the mail router for our company. I would like to say >how pleased I am to see such high quality software available through DECUS. > On behalf of MadGost Software, thanks! >Internally to the company there are several domains, and many hosts. I would >like to provide a standard interface to the outside world for email addresses. >In addition, the alias translation should be confined to one system for easier >maintainance. I think that MX is a good candidate for this. > Yes, it would. >For example: user: "Xavier" > email address: "xx12345@foo.bar.syncrude.com" > alias: "Xavier@Syncrude.Com" > >After reading the docs, it appears that this can be accomplished with a >combination of aliases (for incoming mail) and using a "name_conversion" >hook to translate the "From:" address for outbound mail. I was not clear, >if "name_conversion" could be used for mail arriving from different >sources (UUCP/SMTP/DECnet). Can someone tell me if this is the correct >approach? > Sort of. Your NAME_CONVERSION module will actually handle the address conversions in both directions (incoming and outgoing). There's an example that I believe does everything you want that's available via anonymous ftp from ftp.spc.edu in [.MX.CONTRIB]NICKNAMES.ZIP. A slightly older version can be found in MX_ROOT:[CONTRIB], if you installed the contrib stuff when you installed MX. >There will be approx 2000 names/aliases that will have to be configured. >I am concerned that this will result in poor performance in alias lookups. >In fact I recall reading a comment about this issue in the documentation. > Yes, that's true. Having 2000 aliases would consume a lot of memory all the time. Besides, you'd have to maintain two sets of translations. >Is there another way to handle this, or should I look at modifying the code? > Go with NICKNAMES or something like it. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 27 Oct 1993 05:41:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 27 Oct 1993 05:39:48 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00974A14.266BF073.12862@WKUVX1.BITNET> Subject: RE: domain expander Larry Horn writes: > [...] >So I tried: > > send mail to > > get a bounce from charon4.msstate.edu (attached after sig) in part saying > Sent: RCPT TO: > Rcvd: 553 Non-Local recipients not accepted, address: > is not local. > > look at router debug log (attached after sig) in part saying > Processing address: > ... expanded chs.corinth.k12.ms.us to Charon4.MsState.Edu > ... address now reads: > > nslookup on chs.corinth.k12.ms.us says address is 130.18.80.40 > > nslookup on charon4.msstate.edu say addres is ALSO 130.18.80.40 > >I've not installed any modified domain expander -- just running MX out of >the box. pardon my ignorance, but is this 1) a bug, 2) my problem, or >3) MS State's problem? > Ultimately, I'd say it's MS State's problem for having what appears to be two different systems with the same IP addresses. What's happening with MX, I think, is that it's converting the name to an address, then looking up the name again. I think this has to do with the reverse name lookups that Matt mentioned here last week. (I'll confess ignorance in this area---since we're still working on getting our Internet connection, my direct experience with domain names, expansions, etc., has mostly been with our simple local internet.) When it looks up the name given the address, it gets the Charon4 address from the DNS. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 28 Oct 1993 00:38:15 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX and SYSPRV Message-ID: <1993Oct27.224346.220@buckie.hsc.colorado.edu> From: Date: 27 Oct 93 22:43:46 MDT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993Oct27.181503.1@condor>, blacka@logica.co.uk writes: >I am curious why the two accounts need SYSPRV. >- MAILER (that runs ROUTER, LOCAL etc) > Presumably the LOCAL service has to write to any users MAIL.DAT, > but presumably it uses CALLABLE MAIL to do this ? A process needs SYSPRV to specify a VMSmail "From:" address other than its own username. This is a VMS restriction. If you're running your local delivery agent under a process without SYSPRV, then all locally-deliverd VMSmail will have a From: address address of the username running the local delivery agent. You can easily restrict the privileges the detached MX process aquire by changing the /PRIV qualifer on the RUN command in the MX startup files (MX_EXE:MX_START.COM or MX___STARTUP.COM, I don't recall which one), if you want. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Thu, 28 Oct 1993 06:55:56 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU From: "Eric R. Rountree" Date: 28 Oct 1993 8:48:21 ADT Subject: Absence of Domain Nameserver stops mail delivery Reply-To: MX-List@WKUVX1.BITNET Hi folks. When our Domain Nameserver (called Ac.Dal.CA) was down for most of yesterday afternoon, my local MX host (Moon.SBA.Dal.CA) stopped delivering mail. This morning, things are back to normal and all the mail got delivered. I'm using Multinet for the other TCP/IP services. Do I need to define a backup domain nameserver in the Multinet configuration. Or is there something I need to do with MX that I am somehow missing? Thanks for any help. Eric Rountree System Manager Business School Site Academic Computing Services Dalhousie University Halifax, Nova Scotia ================================================================================ Archive-Date: Thu, 28 Oct 1993 09:58:10 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Absence of Domain Nameserver stops mail delivery Message-ID: <1993Oct28.140907.19687@news.arc.nasa.gov> From: Date: Thu, 28 Oct 1993 14:09:07 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <16955888@MVB.SAIC.COM>, "Eric R. Rountree" writes: >When our Domain Nameserver (called Ac.Dal.CA) was down for most of yesterday >afternoon, my local MX host (Moon.SBA.Dal.CA) stopped delivering mail. This >morning, things are back to normal and all the mail got delivered. > >I'm using Multinet for the other TCP/IP services. Do I need to define a >backup domain nameserver in the Multinet configuration. Or is there >something I need to do with MX that I am somehow missing? If your system has a direct connection to the Internet, then you should probably be running a caching-only domain name server on your own system, and the MULTINET_NAMESERVERS logical name should point to 127.0.0.1 (the local host). That way, your system can do its own name lookups. If you want to have the name server forward queries to another, "smarter", system you can do that by adding a "forwarders" line to your DNS configuration. It sounds from your description like you just have MULTINET_NAMESERVERS pointing to the other system. If that's the case, then yes, you probably should reconfigure. -Matt -- Matthew Madison | madison@tgv.com | +1 408 457 5200 TGV, Inc. | 101 Cooper Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Thu, 28 Oct 1993 17:16:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 28 Oct 1993 23:01:28 +0100 From: Per Hogstedt Reply-To: MX-List@WKUVX1.BITNET Subject: Network documentation? To: MX-List@WKUVX1.BITNET Message-ID: <00974B6E.D5796EA0.17664@plab.se> OK, go ahead, roll me in tar and feathers since this is not strictly MX-related, but I know most of you are managing large LAN/WAN:s and I'd like to know how you go about keeping the network documentation in shape? Are there any software (free/share/payware) that enables you to keep track of the physical side of things; how/where different segments are routed, location of routers/bridges/repeaters et.c. and also on the "logical" side i.e. what parts of the network are connected et.c. If the software you'd reccomend (or advice me not to use) is built on top of some commercial product (e.g., AutoCad or something similar) that is ok, just as long as we are not talking multi-thousand-$ type of products. Preferred platforms are PC/Windows/NT or X11/MOTIF. Since this list is MX, I suppose that you should mail me privately, but if there are requests for a summary, I'll be happy to supply that. Best regards, Per ------- Per Hogstedt, Lindholmen Utveckling, Box 8714, S-402 75 Gothenburg, Sweden Internet: hogstedt@plab.se (or: hogstedt@ae.chalmers.se) Phone: +46 31 50 70 50, Fax +46 31 51 53 13 ================================================================================ Archive-Date: Fri, 29 Oct 1993 05:01:47 CDT Sender: list-mgr@WKUVX1.BITNET Subject: MX SMTP death thereof Message-ID: <2aqr1kINN7c8@zephyr.grace.cri.nz> From: srlncct@lhn.gns.cri.nz Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 29 Oct 93 10:31:00 GMT To: MX-List@WKUVX1.BITNET Hi, I have run into a bit of a problem with MX. The "MX SMTP" process is dying almost immediately after startup and I cannot see the cause of it. The only error that I can trace down is the following from the accounting file: %SYSTEM-F-NOLOGNAM, no logical name match (And I get the same if I try and run it interactively). I am not sure what logical name is missing - have done my best to read the manuals, sort though the startup files etc. but to no avail. In the mean-time the user's mail messages are piling up. This is on a system that is normally looked after by another person who is on annual leave and I can't trace down what changes were made before he left. The problem has appeared since a reboot. (Have tried rebooting again). The system is running CMUTEK. The list of MX logicals that are currently defined are as follows: (LNM$SYSTEM_TABLE) "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "M2G$DUB1:" "MX_DIR" = "MX_DEVICE:[SRSVCLU.MX]" "MX_EVENT_OPER_CLASS" = "NETWORK" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "MX_ROOT:[QUEUE]" "MX_FLQ_NODE_NAME" = "M1G" "MX_FLQ_RECLAIM_WAIT" = "0 02:00:00" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "m1g.gns.cri.nz" "MX_ROOT" = "MX_DEVICE:[SRSVCLU.MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DEBUG" = "1" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_SMTP_SERVER_THREADS" = "8" "MX_TIMEZONE" = "NZDT" "MX_VMSMAIL_LOCALHOST" = "@m1g.gns.cri.nz" The contents of the MX_LOGICALS.DAT file are: MX_FLQ_NODE_NAME\/SYSTEM/EXEC\M1G MX_NODE_NAME\/SYSTEM/EXEC\m1g.gns.cri.nz MX_VMSMAIL_LOCALHOST\/SYSTEM/EXEC\@m1g.gns.cri.nz MX_FLQ_DIR\/SYSTEM/EXEC\MX_ROOT:[QUEUE] MX_FLQ_RECLAIM_WAIT\/SYSTEM/EXEC\0 02:00:00 MX_ROUTER_DIR\/SYSTEM/EXEC\MX_ROOT:[ROUTER] MX_LOCAL_DIR\/SYSTEM/EXEC\MX_ROOT:[LOCAL] MX_MCP_HELPLIB\/SYSTEM\MX_DIR:MX_MCP_HELPLIB MX_ALIAS_HELPLIB\/SYSTEM\MX_DIR:MX_ALIAS_HELPLIB The contents of the MX_STARTUP_INFO.DAT file are: 001NETLIB:M1G 002ROUTER:M1G 003LOCAL:M1G 004SMTP:M1G 004SMTP_SERVER:M1G And the $ MCP STAT returns: PID Node Process name Agent type -------- ------ --------------- ------------ 21600125 M1G MX Router Router agent 216000A7 M1G MX Local Local delivery agent 21600129 M1G SMTP Server SMTP server (over TCP/IP) Any help would be much appreciated. ************************************************************ Colin Tinker Institute of Geological & Nuclear Sciences, Lower Hutt New Zealand srlncct@lhn.gns.cri.nz Ph: (04)570-4819 Fax: (04)569-5016 ************************************************************ ================================================================================ Archive-Date: Fri, 29 Oct 1993 06:45:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 09:44:03 EDT From: system@LAB01.SARAH.BR Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <00974BC8.9A163C80.368@LAB01.SARAH.BR> Subject: RE: MX SMTP death thereof Hi ! I had the same problem a few days ago! Do you have, by the way, the CMUTEK_IP package installed in your machine? Which options did you choose for both MX and CMUTEK packages? I discovered that the problem (I don't know why) is generated CMUTEK packages? I discovered that the problem (I don't know why) is generated when you choose the options. The WAY you select the options affects the final result. My "MX SMTP" delivery agent was going out just after installation, without any reason. Please send a mail with a list of the options you want and I will post what I would do to generate and configure the packages. Dener Martins \ ================================================================================ Archive-Date: Fri, 29 Oct 1993 08:54:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 09:49:06 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: srlncct@lhn.gns.cri.nz, hardis@garnet.nist.gov Message-ID: <00974BC9.4EAD50C0.26697@garnet.nist.gov> Subject: RE: MX SMTP death thereof > I have run into a bit of a problem with MX. The "MX SMTP" process > is dying almost immediately after startup and I cannot see the > cause of it. The only error that I can trace down is the following > from the accounting file: > > %SYSTEM-F-NOLOGNAM, no logical name match > This is on a system that is normally looked after by another person who > is on annual leave and I can't trace down what changes were made before > he left. > The system is running CMUTEK. If you know the other person "made changes," then the changes were most likely the installation of a newer version of CMU/TEK TCP/IP. There is a "gotcha" in doing that upgrade which would give the symptom you report, and so it's worth checking out. In IP_STARTUP.COM, which is normally in SYS$MANAGER:, and which was replaced during an upgrade, you have to uncomment and edit the line with the INTERNET_HOST_NAME definition. More to the point, if MX_SMTP is dying, verify that INTERNET_HOST_NAME is defined (correctly) on your host. While you are editing that file, also comment out the line(s) having to do with the TCP$SMPTSV variable. If this is indeed your problem, take some comfort in knowing that it's a common one after doing the upgrade. - Jonathan ================================================================================ Archive-Date: Fri, 29 Oct 1993 09:33:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 28 Oct 1993 19:15:38 PDT From: Virtual Bill Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <00974B4F.492B8EC0.599@powers.mtv.gtegsc.com> Subject: Return Address Problem I've got a problem regarding internet users replying to mail sent from my cluster. It seems that the fully qualified name is being chopped down to only the User@Host part when mail is sent out, i.e., POWERS@SNEED.CUL.GTEGSC.COM is being shortened to POWERS@SNEED. I've included my CONFIG.MCP file and the MX_SMTP_LOG.LOG file for reference. I'm running MX V3.2 and VMS V5.5-2. Can someone tell me what I've overlooked. ! MX_DEVICE:[MX]CONFIG.MCP ! Created: 12-OCT-1993 18:32:49.29 by MXCONFIG ! Modified: 12-OCT-1993 19:50:50 by Bill Powers ! DEFINE PATH "sneed.cul.gtegsc.com" LOCAL DEFINE PATH "sneed" LOCAL DEFINE PATH "elmer3.cul.gtegsc.com" LOCAL DEFINE PATH "elmer3" LOCAL DEFINE PATH "elmer5.cul.gtegsc.com" LOCAL DEFINE PATH "elmer5" LOCAL DEFINE PATH "elmer4.cul.gtegsc.com" LOCAL DEFINE PATH "elmer4" LOCAL DEFINE PATH "elmer1.cul.gtegsc.com" LOCAL DEFINE PATH "elmer1" LOCAL DEFINE PATH "elmer2.cul.gtegsc.com" LOCAL DEFINE PATH "elmer2" LOCAL DEFINE PATH "sneed.dnet" LOCAL DEFINE PATH "elmer3.dnet" LOCAL DEFINE PATH "elmer5.dnet" LOCAL DEFINE PATH "elmer4.dnet" LOCAL DEFINE PATH "elmer1.dnet" LOCAL DEFINE PATH "elmer2.dnet" LOCAL DEFINE PATH "sneed.dnet.cul.gtegsc.com" DECNET_SMTP/ROUTE=sneed DEFINE PATH "elmer3.dnet.cul.gtegsc.com" DECNET_SMTP/ROUTE=elme3r DEFINE PATH "elmer5.dnet.cul.gtegsc.com" DECNET_SMTP/ROUTE=elmer5 DEFINE PATH "elmer2.dnet.cul.gtegsc.com" DECNET_SMTP/ROUTE=elmer2 DEFINE PATH "elmer1.dnet.cul.gtegsc.com" DECNET_SMTP/ROUTE=elmer1 DEFINE PATH "elmer4.dnet.cul.gtegsc.com" DECNET_SMTP/ROUTE=elmer4 DEFINE PATH *.BITNET SMTP/ROUTE="cunyvm.cuny.edu" DEFINE PATH *.UUCP SMTP/ROUTE=uunet.uu.net DEFINE REWRITE "<{user}@{node}.dnet>" "<""{node}::{user}""@sneed.cul.gtegsc.com>" 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>" ! NOTE: The next path definition should always be LAST. DEFINE PATH * SMTP ! ! Done with routing information. ! DEFINE ALIAS "Postmaster" "system@sneed.cul.gtegsc.com" DEFINE ALIAS "POSTMAST" "system@sneed.cul.gtegsc.com" ! for BITNET compatibility set local/header=(top:noall,bottom:all)/MAXIMUM_RETRIES=100/retry=00:15:00 set smtp/MAXIMUM_RETRIES=100/retry=00:15:00 set DECNET_SMTP/MAXIMUM_RETRIES=100/retry=00:15:00 save MX_DIR:MX_CONFIG.MXCFG reset/all MX_SMTP_LOG.LOG 28-OCT-1993 18:09:06.38 Processing queue entry number 14993 on node elmer1 28-OCT-1993 18:09:06.66 Recipient: , route=EISNER.DECUS.ORG 28-OCT-1993 18:09:06.66 SMTP_SEND: looking up host name EISNER.DECUS.ORG 28-OCT-1993 18:09:06.76 SMTP_SEND: Attempting to start session with EISNER.DECUS.ORG [192.67.173.2] 28-OCT-1993 18:09:06.87 SMTP_SEND: Connected 28-OCT-1993 18:09:08.32 SMTP_SEND: Rcvd: 220 Eisner.DECUS.Org -- Server SMTP (PMDF V4.2-12 #4291) 28-OCT-1993 18:09:08.35 SMTP_SEND: Sent: HELO elmer1 28-OCT-1993 18:09:08.47 SMTP_SEND: Rcvd: 250 Eisner.DECUS.Org OK, elmer1.cul.gtegsc.com. 28-OCT-1993 18:09:08.47 SMTP_SEND: Sent: MAIL FROM: 28-OCT-1993 18:09:08.60 SMTP_SEND: Rcvd: 250 Address Ok. 28-OCT-1993 18:09:08.60 SMTP_SEND: Sent: RCPT TO: 28-OCT-1993 18:09:09.36 SMTP_SEND: Rcvd: 250 POWERS@EISNER.DECUS.ORG OK. 28-OCT-1993 18:09:09.40 SMTP_SEND: Sent: DATA 28-OCT-1993 18:09:09.51 SMTP_SEND: Rcvd: 354 Enter mail, end with a single ".". 28-OCT-1993 18:09:09.51 SMTP_SEND: Sent: Received: by sneed (MX V3.2) id 14990; Thu, 28 Oct 1993 18:09:04 EDT 28-OCT-1993 18:09:09.51 SMTP_SEND: Sent: Sender: powers@sneed.cul.gtegsc.com 28-OCT-1993 18:09:09.52 SMTP_SEND: Sent: Date: Thu, 28 Oct 1993 18:09:03 EDT 28-OCT-1993 18:09:09.52 SMTP_SEND: Sent: From: Virtual Bill 28-OCT-1993 18:09:09.52 SMTP_SEND: Sent: To: POWERS@EISNER.DECUS.ORG 28-OCT-1993 18:09:09.52 SMTP_SEND: Sent: Message-ID: <00974B45.FBCDBC60.14990@sneed> 28-OCT-1993 18:09:09.52 SMTP_SEND: Sent: Subject: MORE 28-OCT-1993 18:09:09.52 SMTP_SEND: Sent: 28-OCT-1993 18:09:09.52 SMTP_SEND: Sent: GETTING BORING 28-OCT-1993 18:09:09.53 SMTP_SEND: Sent: . 28-OCT-1993 18:09:09.53 SMTP_SEND: will wait 00:10:30.00 for reply. 28-OCT-1993 18:09:10.42 SMTP_SEND: Rcvd: 250 Ok. 28-OCT-1993 18:09:10.42 SMTP_SEND: Sent: QUIT 28-OCT-1993 18:09:10.53 SMTP_SEND: Rcvd: 221 Bye received. Goodbye. 28-OCT-1993 18:09:10.60 Recipient status=00000001 for 28-OCT-1993 18:09:10.67 Entry now completely processed, no retries needed. 28-OCT-1993 18:09:10.69 *** End of processing pass *** ================================================================================ Archive-Date: Fri, 29 Oct 1993 10:05:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 10:59:02 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: powers@powers.mtv.gtegsc.com, hardis@garnet.nist.gov Message-ID: <00974BD3.13F958C0.26711@garnet.nist.gov> Subject: RE: Return Address Problem > I've got a problem regarding internet users replying to mail sent > from my cluster. It seems that the fully qualified name is being > chopped down to only the User@Host part when mail is sent out, i.e., > POWERS@SNEED.CUL.GTEGSC.COM is being shortened to POWERS@SNEED. You didn't say what IP transport you were using, but this sounds like a configuration problem there. Read the MX Release Notes. They explain how, when using UCX or Multinet, you have to make the Fully Qualified Domain Name (FQDN) the primary host name. ================================================================================ Archive-Date: Fri, 29 Oct 1993 10:50:33 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 11:45:55 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: powers@powers.mtv.gtegsc.com Message-ID: <00974BD9.A0D7E940.15002@nscvax.princeton.edu> Subject: RE: Return Address Problem Virtual Bill writes: > I've got a problem regarding internet users replying to mail sent > from my cluster. It seems that the fully qualified name is being > chopped down to only the User@Host part when mail is sent out, i.e., > POWERS@SNEED.CUL.GTEGSC.COM is being shortened to POWERS@SNEED. > I've included my CONFIG.MCP file and the MX_SMTP_LOG.LOG file for > reference. I'm running MX V3.2 and VMS V5.5-2. Can someone tell > me what I've overlooked. > How is MX_VMSMAIL_LOCALHOST defined? If it's not "@sneed.cul.gtegsc.com" that could be your problem. ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Fri, 29 Oct 1993 11:42:09 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 12:35:37 E From: tony spinillo Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET Message-ID: <00974BE0.91C0D3C0.8209@marywood1.marywood.edu> Subject: CNAME Help I have set up a cname alias for one of our hosts, marywood1.marywood.edu. When I send mail from a host that is outside of our domain the mail arrives with no problem. But when I send mail from a host inside of our domain the following happens: (I sent this mail from the cnamed host to itself) ac.marywood.edu is the alias for marywood1.marywood.edu ************************************************************ Note: this message was generated automatically. A problem occurred during SMTP delivery of your message. Error occurred sending to the following user(s): (via AC.MARYWOOD.EDU): %MX_SMTP-F-TRANSACTION_FAI, transaction failed Transcript: Rcvd: 220 MARYWOOD1.MARYWOOD.EDU MX V3.3 VAX SMTP server ready at Fri, 29 Oct 1993 12:22:55 E Sent: HELO MARYWOOD1.MARYWOOD.EDU Rcvd: 250 Hello, MARYWOOD1.MARYWOOD.EDU Sent: MAIL FROM: Rcvd: 250 MAIL command accepted. Sent: RCPT TO: Rcvd: 250 Recipient okay (at least in form) Sent: DATA Rcvd: 354 Start mail input; end with . Rcvd: 554 Received too many times by this host. Sent: QUIT Rcvd: 221 MARYWOOD1.MARYWOOD.EDU Service closing transmission channel ======================================================================== Message follows. Received: from MARYWOOD1.MARYWOOD.EDU by MARYWOOD1.MARYWOOD.EDU (MX V3.3 VAX) with SMTP; Fri, 29 Oct 1993 12:22:54 E Received: from MARYWOOD1.MARYWOOD.EDU by MARYWOOD1.MARYWOOD.EDU (MX V3.3 VAX) with SMTP; Fri, 29 Oct 1993 12:22:52 E Received: from MARYWOOD1.MARYWOOD.EDU by MARYWOOD1.MARYWOOD.EDU (MX V3.3 VAX) with SMTP; Fri, 29 Oct 1993 12:22:49 E Received: from MARYWOOD1.MARYWOOD.EDU by MARYWOOD1.MARYWOOD.EDU (MX V3.3 VAX) with SMTP; Fri, 29 Oct 1993 12:22:47 E Received: from MARYWOOD1.MARYWOOD.EDU by MARYWOOD1.MARYWOOD.EDU (MX V3.3 VAX) with SMTP; Fri, 29 Oct 1993 12:22:45 E Received: from MARYWOOD1.MARYWOOD.EDU by MARYWOOD1.MARYWOOD.EDU (MX V3.3 VAX) with SMTP; Fri, 29 Oct 1993 12:22:44 E Received: from MARYWOOD1.MARYWOOD.EDU by MARYWOOD1.MARYWOOD.EDU (MX V3.3 VAX) with SMTP; Fri, 29 Oct 1993 12:22:42 E Received: from MARYWOOD1.MARYWOOD.EDU by MARYWOOD1.MARYWOOD.EDU (MX V3.3 VAX) with SMTP; Fri, 29 Oct 1993 12:22:40 E Received: by marywood1.marywood.edu (MX V3.3 VAX) id 8160; Fri, 29 Oct 1993 12:22:39 E Date: Fri, 29 Oct 1993 12:22:38 E From: Tony Spinillo To: SYSTEM@AC.MARYWOOD.EDU Message-ID: <00974BDE.C1A8D800.8160@marywood1.marywood.edu> Subject: test local ac hello ******************************************************* thanks in advance tony ************************************************************ Anthony Spinillo - Tech Services Marywood College PHONE: 717-348-6215 ext 557 2300 Adams Ave Scranton, PA 19509 spinillo@marywood1.marywood.edu ************************************************************ ================================================================================ Archive-Date: Fri, 29 Oct 1993 12:43:31 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 13:40:27 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU CC: spinillo@marywood1.marywood.edu Message-ID: <00974BE9.A07E3D40.15023@nscvax.princeton.edu> Subject: RE: CNAME Help tony spinillo writes: >I have set up a cname alias for one of our hosts, marywood1.marywood.edu. >When I send mail from a host that is outside of our domain the mail >arrives with no problem. But when I send mail from a host inside >of our domain the following happens: > >(I sent this mail from the cnamed host to itself) > >ac.marywood.edu is the alias for marywood1.marywood.edu > > >************************************************************ > You need to tell MX where to deliver mail to the alias! You need some lines that look like this in your config file. DEFINE PATH "marywood1.marywood.edu" LOCAL DEFINE PATH "ac.marywood.edu" LOCAL DEFINE PATH "marywood1" LOCAL DEFINE PATH "ac" LOCAL DEFINE PATH "[192.159.104.1]" LOCAL Lacking this, your machine sees the alias, sends the message via smtp, looks at the address on the message just received, sends the message via smtp... until it gets killed for too many visits. ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Fri, 29 Oct 1993 14:13:41 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Return Address Problem Message-ID: <2arlbf$nv@gap.cco.caltech.edu> From: Date: 29 Oct 1993 17:53:51 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <16996164@MVB.SAIC.COM>, Virtual Bill writes: = I've got a problem regarding internet users replying to mail sent = from my cluster. It seems that the fully qualified name is being = chopped down to only the User@Host part when mail is sent out, i.e., = POWERS@SNEED.CUL.GTEGSC.COM is being shortened to POWERS@SNEED. = I've included my CONFIG.MCP file and the MX_SMTP_LOG.LOG file for = reference. I'm running MX V3.2 and VMS V5.5-2. Can someone tell = me what I've overlooked. You've overlooked the matter of which TCP/IP implementation you're using. It's probably UCX, and you probably followed the UCX installation instructions that told you to use the nickname for your system as the primary name in UCX's host database. Check the MX release notes for instructions on how to fix this. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Fri, 29 Oct 1993 15:16:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 13:07:47 PDT From: Virtual Bill Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Message-ID: <00974BE5.10228200.620@powers.mtv.gtegsc.com> Subject: Re: Return Address Problem My problem has been solved. I want to thank both Carl Lydick and Jonathan Hardis for their help. I am using the UCX implementation of TCP/IP and although the release notes for MX3.2 don't cover my problem, the release notes for MX V3.3 does. Thanks again for leading me in the right direction. ================================================================================ Archive-Date: Fri, 29 Oct 1993 16:31:43 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 16:26:40 CDT From: "John Clement-Rice U. (713)527-8101x2037" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: clement@physics.rice.edu Message-ID: <00974C00.D8EC8800.17600@physics.rice.edu> Subject: VMSMAIL_PATCH.TXT It fails to work under VAX/VMS V5.5-2. Does anyone know of the wherabouts of a new patch that works under 5.5-2. My users are addicted to it and I would like to repatch the mailer!!!! /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ John M. Clement Hepnet: UTSPAN::RIPHYS::CLEMENT PO Box 1892 Internet: CLEMENT@PHYSICS.RICE.EDU Rice University Bitnet: CLEMENT@RICEVM1 Houston, Tx. 77251 BellTel: (713)527-8181 x2037 /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ ================================================================================ Archive-Date: Fri, 29 Oct 1993 16:49:42 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 16:42:46 CDT From: "John Clement-Rice U. (713)527-8101x2037" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: clement@physics.rice.edu Message-ID: <00974C03.18C3B140.17602@physics.rice.edu> 1 MXmail MX - Message Exchange V3.3 Message Exchange (MX) is software that provides store-and-forward routing and delivery of electronic mail messages. MX can be used to enhance local electronic mail (E-mail) support, and it can be used with several kinds of network protocols to provide a unified E-mail interface to different networks. VMS MAIL on this system may be used to send and receive mail to the worldwide uucp (uucp to uucp copy), bitnet, Internet, and to other networks gatewayed to them. 2 Sending_Mail Users on uucp and Internet sites generally have addresses of the form username@systemname where "systemname" is usually (but not always) a series of names separated by dots, e.g. jeh@crash.cts.com madison@rpiecsvx.bitnet To send mail to such an address, use VMS MAIL in the usual way, but answer the "To:" prompt with an entry of the form MX%"username@systemname". For example, MAIL> send To: MX%"jeh@crash.cts.com" Subj: This is a test This format is specific, and the quotes must be used exactly as shown in the examples. A missing trailing quote will cause VMSmail to exit with an error message (earlier versions would simply hang; type ctrl-Y to escape). Some uucp users have "bang form" addresses which consist of a series of uucp hostnames, separated by !'s (which are pronounced "bang" when reading such addresses aloud), with their username at the end, as in decwrl!simpact!jeh These addresses may also be used, as follows: MAIL> send To: MX%"decwrl!simpact!jeh" Subj: This is a test See the "Addressing" topic for information on more complex addresses. NOTE: At some sites it is possible to omit MX% from the address specification. If the address does not contain an exclamation point "!" then the quotes may be omitted also. This is only possible if the system manager has installed a patch to the VMS MAIL file. 2 Receiving_Mail To tell people how to send mail to you, you will have to give them your network address. In the Internet address form user@system the "user" part is simply your VMS username. The "system" part is, however, *not* the local DECnet nodename (at least not usually). To find out your system's name in Internet terms, issue the following command from the DCL prompt: $ SHOW LOGICAL MX_NODE_NAME The translation of this logical name is your system's name from the Internet's point of view. Thus, if this name translates to the string crash.cts.com (it won't, because that name is already in use, but never mind; this is just an example), and your user name is JSMITH, your network address is jsmith@crash.cts.com When you send network mail, you usually want your recipient to be able to reply to you. The MX mailer will automatically precede your message with an Internet-compatible "From:" line that shows your address; this will usually allow replies to work correctly. However, some network "gateways" modify the "From" information in such a way as to make the mail unreplyable. It is therefore advisable to include your network address in the text of your message (usually as part of your "signature"; see the entry for "Signatures"). 2 Checking_Mail Normally if your mail is undeliverable you will be notified of this, and after the timeout delay, it will be returned. If you are uncertain about whether your mail has actually been delivered, or is still waiting for delivery use the command: $ MAILQUEUE or $ RUN MX_EXE:MAILQUEUE You will be shown the current status of your mail. It it does not appear it "probably" has already been sent. The output of MAILQUEUE resembles: Entry: 4933, Origin: [Local] Status: IN-PROGRESS SMTP entry 4934, status: READY Waiting for retry until: 29-JUL-1992 14:30:05.88 Recipient 1: , Route=NORTH-POLE.ARCTIC-OCEAN.WORLD DNS errors=1 Last error: %MX-F-NOHOST, no such host 2 Forwarding_Mail You can use the SET FORWARD command in VMS MAIL to set a forwarding address for your mail through MX. To do this, however, requires that you add extra quotes to the address. The forwarding address should be quoted, and, since MX addresses must be quoted, the inner quotes must be doubled to comply with the command parsing. For example: MAIL> SET FORWARD MX%"""user@host""" To check if it is correct use the command: MAIL> SHOW FORWARD and you will see: Your mail is being forwarded to MX%"user@host" You should also send yourself mail to make sure that it is properly forwarded. 2 Addressing For most Internet sites, anywhere that VMSmail asks for an address, you can respond with MX%"user@host" where host is usually something like machine.organization.domain, but may be as simple as a internet host name, and user is a username on that system. A series of MX addresses may be used, separated by commas, and possibly mixed with local and remote (reached via DECNet) user names, as follows: MAIL> send To: MX%"jeh@crash.cts.com",MX%"ta2@esther.uucp",LABVAX::SYSTEM Subj: This is a test Under VMS Version 5, MX addresses may also be used in response to the CC: prompt. If someone gives you an address like remhost!user you can generally use a VMSmail "To:" address of MX%"user@remhost.uucp" 3 Routing If you must route your mail through several hosts to get to the intended user, you will need to use a complicated address. For example you need to route it through HOST1 to get to HOST2 and then from HOST2 to USER@HOST3. The address would be specified as follows: @HOST1,@HOST2:USER@HOST3 you may also perform routing using the percent sign hack. The same address would be: USER%HOST3%HOST2@HOST1 3 Percent_Signs Many addresses include imbedded percent signs; for example: TNIELAND%FALCON@AAMRL.AF.MIL There are differences of opinion as to how this should be interpreted. In general it usually is interpreted with everything to the left of the "@" as being a "funny username", so the mail is sent to TNIELAND%FALCON at AAMRL.AF.MIL on the assumption that aamrl.af.mil will know what to do with it. (In this particular case, they do.) The "proper" way to specify such routing is: @AAMRL.AF.MIL:TNIELAND@FALCON 2 Redirecting_replies If your mail replies are to be sent to another address other than the one you are sending your mail from, you can include this information in your message by defining the logical: $ DEFINE MX_REPLY_TO "user@host" The host name must be "fully qualified" or it must be the complete host name. For example if you wish replies to go to JEH@CRASH.CTS.COM. you can not abbreviate it to JEH@CRASH. 2 Signature_files The majority of mail users usually include a "signature" file at the end of their message. This helps better identify the person sending the message. Information included usually states the person's name, their com- pany, their e-mail address, and possibly a phone number. This is usually done as a courtesy, so if someone wants to reply to your mail and can't, they can still reach you some way. The MX/VMS MAIL interface provides support for "signature" files. Once you have created a signature file, you inform MX of its existence by defining the logical name MX_SIGNATURE: $ DEFINE MX_SIGNATURE device:[directory]name.type You can then have the signature included in your message by entering the line /SIGNATURE in your message. To be recognized, there can be no other text on the line and no leading blanks. Case is not important, and you can abbreviate SIGNATURE to SIG. Your signature file will be inserted in the message at the point where you place the /SIGNATURE line. To enable your signature file every time you login, include the DEFINE command in your login command procedure. If you always want to include the signature at the end of the message then define: $ DEFINE MX_AUTO_SIGNATURE TRUE The signature will automatically be included either at the end of your mail, or at the /SIGNATURE line. 3 Examples Here are a few "signature" files. There is no "format", you are free to do whatever you wish. I include these only to help new users. This first example is my own. I like to keep it simple, and I've chosen to include an amusing quote at the end.... ------------------------------------------------------------------- Kent C. Brodie - Systems Manager brodie@mcw.edu Medical College of Wisconsin +1 414 778 4500 "Gee, I hope these are the right coordinates..." -Chief O' Brien; STTNG This second example belongs to Jamie Hanrahan (one of the co-authors of DECUS uucp). Jamie provides more information than I do. --- Jamie Hanrahan, Simpact Associates, San Diego CA Chair, VMSnet and Internals Working Groups, DECUS VAX Sytems SIG Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com Uucp: ...{crash,scubed,decwrl}!simpact!jeh 2 Set_MX_Default The undocumented VMS Mail command SET TRANSPORT can be used to establish MX as the default transport to be used for all mail messages. The format of the command is: MAIL> SET TRANSPORT MX% The MX% prefix can be omitted from MX aliases when the default transport has been set. Note that non-alias "user@domain" addresses must still be prefixed. The MAIL command SET NOTRANSPORT can be used to disable the default transport. Note: The SET TRANSPORT command is undocumented; its behavior could change with a future release of VMS. Also, once it has been set, all local mail will be delivered through MX. 2 MXAlias MXALIAS is a simple database manager for user-defined MX aliases. An alias is a name that is equated with a mail address that can be used to address electronic mail. For example, the address "BOB" can be equated with "smithjb@node1.school.edu"; it can then be used in VMS Mail by specifying MX%BOB at the "To:" prompt: MAIL> SEND To: MX%BOB Subj: .... MX aliases are stored, by default, in a file called MXALIASDATABASE.DAT in your login directory (SYS$LOGIN:). You can define the MXALIASDATABASE logical in your LOGIN.COM to relocate the database file: $ DEFINE MXALIASDATABASE dev:[user.MAIL]ALIASES.DAT MXALIAS will automatically create the MX alias database the first time you add an alias definition. MXALIAS can be executed by setting up a foreign symbol in your LOGIN.COM: $ mxalias :== $mxexe:mxalias.exe Your system manager may have already defined it for you in the system login procedure. You can also just use RUN MXEXE:MXALIAS to run MXALIAS. When MXALIAS is invoked without any parameters on the DCL command, your are put into an interactive mode. The prompt is "MXalias>": $ mxalias MXalias> At the MXALIAS prompt, you can ADD aliases, MODIFY them, REMOVE them, and list them using the DIRECTORY command. There is on-line help available by typing HELP at the MXalias> prompt. 2 Binary_files The VMS Mail command SEND accepts an undocumented qualifier, /FOREIGN. SEND/FOREIGN allows you to mail any VMS file to another user on the same system or over DECnet. The file retains all of the VMS file attributes. When the recipient tries to read the mail message containing the file, the following information is displayed: 2 14-APR-1993 15:28:02.11 NEWMAIL From: GOATHUNTER To: GOATHUNTER Cc: Subj: RESET.EXE You cannot read this foreign format message Use the EXTRACT command to copy the message to an external file MAIL> The EXTRACT command copies the message to the named external file with all VMS file attributes intact. The SEND/FOREIGN command can also be used to send VMS binary files through MX, if the target user is a system running MX V3.3 or higher, MultiNet V3.2 or higher, or PMDF V4.1 or higher. When SEND/FOREIGN is used, MX encodes the message using an algorithm called BASE64, which is defined in RFC 1341, a document describing MIME (Multipurpose Internet Mail Extensions). The BASE64-encoded file is wrapped in a MIME-compliant message and mailed to the recipients. When the message is received on a system running the appropriate versions of either MX, MultiNet, or PMDF, the encoded binary file is automatically decoded and mailed to the local user as a foreign file. The recipient will receive two messages-one containing the headers for the message, and the other containing the foreign file as shown above. The MIME "Content-Type:" for the file is "APPLICATION/VMS-RMS". MX will automatically recognize and decode incoming "VMS-RMS" files that are encoded using BASE64. 2 DECUS_uucp "DECUS uucp", as it is known, was developed by the VMSNET working group, which is a part of the DECUS organization. Although many people have done work on this package (and various utilities/parts of previous versions), the following three people organized efforts to make this a complete package available to the general DECUS user community. All three programmers involved would love to hear comments about their work! Jamie Hanrahan Tom Allebrandi II Mark Pizzolato Simpact Associates Inland Steel, Inc. Infocomm jeh@crash.cts.com allebrandi@inland.com mark@infocomm.com 2 Logicals 1. $ DEFINE MX_VMSMAIL_SHOW_ADDR TRUE Will show you all the address translations when you send mail. 2. $ DEFINE MX_SIGNATURE device:[directory]name.type Defines a signature at the line /SIGNATURE 3. $ DEFINE MX_AUTO_SIGNATURE text Defines an automatic signature at end of text. 4. $ DEFINE MX_REPLY_TO "user@host,user2@host2" Defines the reply destination 5. $ DEFINE MX_VMSMAIL_SHOW_INFO TRUE Gives you an informational message when MX receives the mail. It does NOT give you mail verification. 6. $ DEFINE MX_ALIAS_DATABASE dev:[user.MAIL]ALIASES.DAT Defines the location of the MX alias database. 2 Problem_Reports An electronic mailing list exists to discuss the MX software and report problems. The address of the mailing list is MX-List@WKUVX1.BITNET. Internet users can subscribe to this list by sending an E-mail message to MX-List-Request%WKUVX1.BITNET@UKCC.UKY.EDU, with the command "SUBSCRIBE" appearing in the body of the message. Do NOT send the command to MX-List@WKUVX1.BITNET. To get off the mailing list send a message with the command "SIGNOFF" appearing in the body of the message. BITNET users can subscribe to this list by the method described for Internet users, or by sending an E- mail message to LISTSERV@WKUVX1, with the command "SUBSCRIBE MX-List" appearing in the body of the message. The MX-List mailing list is also gatewayed to the VMSnet newsgroup vmsnet.mail.mx. Archives of the mailing list are available by anonymous FTP from ftp.spc.edu in directory [ANONYMOUS.MX]. The current version of MX is also available at the same location. 2 Documentation If your local system manager has installed the MX documentation, it may be found in: MXROOT:[DOC] There are plain text files .TXT and postscript files .PS. In addition you may have bookreader files, that may be accessed by DECwindows. 2 Acknowledgments I wish to thank Matt Madison for giving us such a useful product as MX. It has made my life much easier since it allows me to link SMTP mail with DECUS uucp mail. I would also like to thank him for listening to all the comments and suggestions the beta testers and users of MX have sent him. MX was originally written by Matthew D. Madison, formerly of Rensselaer Polytechnic Institute and currently employed by TGV, Inc. The software is currently maintained by Hunter Goatley, Western Kentucky University. Copyright Ü1993 MadGoat Software. All rights reserved. 3 This_help_file This HELP file was originally written for DECUS uucp by: Kent C. Brodie Medical College of Wisconsin brodie@mcw.edu This HELP file was modified for MX by: Earle F. Ake Science Applications Intl. Corp. ake@dayton.saic.com Updated Oct 1993 for V3.3 by: John Clement Rice University, Houston, Tx. clement@physics.rice.edu /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ John M. Clement Hepnet: UTSPAN::RIPHYS::CLEMENT PO Box 1892 Internet: CLEMENT@PHYSICS.RICE.EDU Rice University Bitnet: CLEMENT@RICEVM1 Houston, Tx. 77251 BellTel: (713)527-8181 x2037 /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ ================================================================================ Archive-Date: Fri, 29 Oct 1993 17:34:59 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 29 Oct 1993 17:33:02 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00974C0A.1E520330.13761@WKUVX1.BITNET> Subject: RE: VMSMAIL_PATCH.TXT "John Clement-Rice U. (713)527-8101x2037" writes: > >It fails to work under VAX/VMS V5.5-2. Does anyone know of the wherabouts of a >new patch that works under 5.5-2. My users are addicted to it and I would like >to repatch the mailer!!!! > The current file on ftp.spc.edu in [.MX.CONTRIB] has v5.5-2 commented out. Just uncomment it and comment out V6.0. Or whichever it is that's not commented. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 29 Oct 1993 20:57:47 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: MX SMTP death thereof Message-ID: <2ask13INNdtt@zephyr.grace.cri.nz> From: srlncct@lhn.gns.cri.nz Reply-To: MX-List@WKUVX1.BITNET Date: Sat, 30 Oct 93 02:43:30 GMT To: MX-List@WKUVX1.BITNET Hi, Thanks for the help. The wonders of Internet and NEWS. The problem was that the logical INTERNET_HOST_NAME wasn't being set during the IP_STARTUP phase. Added this and away it went - the missing logical obviously. Thanks again. Regards Colin ************************************************************ Colin Tinker Institute of Geological & Nuclear Sciences, Lower Hutt New Zealand srlncct@lhn.gns.cri.nz Ph: (04)570-4819 Fax: (04)569-5016 ************************************************************ ================================================================================ Archive-Date: Fri, 29 Oct 1993 21:52:03 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: VMSMAIL_PATCH.TXT Message-ID: <1993Oct29.200911.423@tachyon.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 29 Oct 93 20:09:11 CDT To: MX-List@WKUVX1.BITNET In article <17010743@MVB.SAIC.COM>, "John Clement-Rice U. (713)527-8101x2037" writes: > It fails to work under VAX/VMS V5.5-2. Does anyone know of the wherabouts of a > new patch that works under 5.5-2. My users are addicted to it and I would like > to repatch the mailer!!!! > > > John M. Clement Hepnet: UTSPAN::RIPHYS::CLEMENT The patch actually contains code for several different versions of VMS (the latest one includes V6). Only one version is active at a time; the others are commented out. You need to edit the file to comment out the patch for whatever version of VMS you were using before and uncomment the patch for 5.5-2, thereby activating it. Wayne -- ============================================================================== Wayne Sewell |INET: wayne@tachyon.com Tachyon Software Consulting |UUCP: uupsi!uupsi6!tachyon!wayne P. O. Box 550937, Dallas TX 75355-0937 |Voice: (214)-553-9760, Fax: -553-0077 ============================================================================= Elwood Blues:"Our Lady of Blessed Acceleration, don't fail me now!" ================================================================================ Archive-Date: Sat, 30 Oct 1993 10:45:32 CDT Sender: list-mgr@WKUVX1.BITNET Subject: MX and SYSPRV Message-ID: <1993Oct27.181503.1@condor> From: blacka@logica.co.uk Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 27 Oct 1993 18:15:03 GMT To: MX-List@WKUVX1.BITNET I run MX with SMTP DECNET. Currently out of lazines I run MX under the system account. and the Decnet server runs under an account called MAILER. I want to tidy up the security of the system. The installation manual says : > If you intend to use the MX SMTP-over-DECnet or > SMTP-over-X.25 support, you may want to establish a > special server account to be used exclusively for > the DECSMTP and X25_SMTP DECnet objects What are the pros and cons of having seperate accounts? I am curious why the two accounts need SYSPRV. - MAILER (that runs ROUTER, LOCAL etc) Presumably the LOCAL service has to write to any users MAIL.DAT, but presumably it uses CALLABLE MAIL to do this ? - Does this need to write to anything other than the queue files. Can the need for SYSPRV be removed by ensuring the protection on the various MX directories used are such that the two accounts can write to it. Would it be best to get the MX_ROOT:[...] files owned by the MAILER user. Thanks for the help. ---------------------------------------------------------------- Andrew Black blacka@logica.co.uk Logica Finance, London ----------------------------------------------------------------- ================================================================================ Archive-Date: Sat, 30 Oct 1993 16:41:22 CDT Sender: list-mgr@WKUVX1.BITNET From: John Caruso Reply-To: MX-List@WKUVX1.BITNET Message-ID: <199310302136.RAA07288@nova.umd.edu> Subject: Re: VMSMAIL_PATCH.TXT To: MX-List%WKUVX1.bitnet@ULKYVM.LOUISVILLE.EDU Date: Sat, 30 Oct 1993 17:36:57 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I've just installed the MAILSHR patch and I have one question. The documentation in the patch indicates (in two separate places) that addresses of the form user@system will be rewritten as MX%"user@system" rather than as system::user, which was apparently the patch's original behavior. But after I installed the patch I found that this wasn't the case. I ended up having to unpatch MAILSHR and reverse engineer the code changes based on the comments, and then repatch the executable. Now user@system is being rewritten as MX%"user@system" as advertised. But my question is--why the misleading comments? Would whoever is taking care of the patch code please consider updating it to save some unnecessary confusion for future sysadmins? Regardless of the tricky installation, I'm very happy with the patch, and I'm sure my users will be too...should save us about 2-3 questions a week. Now if only it worked with SET FORWARD. :-) --------------------------------------------------------------------- John Caruso caruso@nova.umd.edu Unix/VMS System Administrator caruso@UMUC (Bitnet) University of Maryland University College Work: (301) 985-7447 --------------------------------------------------------------------- ================================================================================ Archive-Date: Sun, 31 Oct 1993 11:39:33 CST Sender: list-mgr@WKUVX1.BITNET Subject: DECnet addresses in "To" line. Message-ID: <2amras$f3q@lohengrin.umkc.edu> From: Date: 27 Oct 1993 22:05:16 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET I've got addresses that look like this: To: "cstp::mckeever"@PRIMUS.CSTP.UMKC.EDU I would really like to do away with the DECnet portion of the address and replace it with just the username. "cstp::" is the cluster alias name not the nodes name (PRIMUS::). I'm _sure_ this has probably been covered before, but I took a couple of hours and searched through the MX archives but couldn't find anything that looked appropriate. Thanks, -=Brian ================================================================================ Archive-Date: Sun, 31 Oct 1993 12:00:35 CST Sender: list-mgr@WKUVX1.BITNET Subject: Re: DECnet addresses in "To" line. Message-ID: <1993Oct31.085617.240@buckie.hsc.colorado.edu> From: Date: 31 Oct 93 08:56:17 MDT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <2amras$f3q@lohengrin.umkc.edu>, mckeever@CSTP.UMKC.EDU (Brian McKeever) writes: >I've got addresses that look like this: > > To: "cstp::mckeever"@PRIMUS.CSTP.UMKC.EDU > >I would really like to do away with the DECnet portion of the address >and replace it with just the username. "cstp::" is the cluster alias >name not the nodes name (PRIMUS::). > >I'm _sure_ this has probably been covered before, but I took a couple >of hours and searched through the MX archives but couldn't find >anything that looked appropriate. This was discussed, on MX-LIST, just a few weeks ago. Check the value of MAIL$SYSTEM_FLAGS on all nodes in your cluster. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org