Archive-Date: Tue, 01 Jun 1993 00:05:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 01 Jun 1993 00:04:54 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D598.D7F807A0.2327@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: Tue, 01 Jun 1993 01:37:24 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX rewrite rules? Message-ID: <1993Jun1.133345.774@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 1 Jun 93 13:33:44 +1000 To: MX-List@WKUVX1.BITNET In article <1993May31.100747.158@anorad.com> Mikel Beck, mikel@anorad.com writes: >>> I'm looking at doing the same thing here. You have to use the address >>> modification interface (NAME_CONVERSION is using it) to rewrite the >>> addresses for you. > So does this mean that NAME_CONVERSION has to be modified to generate > the sort of address I'm looking for? I'll have to take a look at that routine > next week... Yes it does. You also have to use the FULL_CONVERT routing as well as the CONVERT routine. The CONVERT routine only modifies the username part of the address. The FULL_CONVERT routine must give the complete RFC-822 formatted address back. Carl. -- Carl Makin (VK1KCM) Internet: makinc@hhcs.gov.au Amprnet: vk1kcm@vk1kcm.act.aus.oc "Life is something to do when you can't get to sleep." - Fran Lebowitz ================================================================================ Archive-Date: Tue, 01 Jun 1993 06:13:44 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9306011005.AA02133@bogart.mpib-tuebingen.mpg.de> To: mx-list@WKUVX1.BITNET Subject: mx033 on cluster. Date: Tue, 01 Jun 93 11:05:32 +0100 From: root@bogart.mpib-tuebingen.mpg.de Reply-To: MX-List@WKUVX1.BITNET Hi, i have installed mx033 on cluster. If i send mail from every node to a UNIX node, the sender (host+domainname) always the same. >From UNIX-machine to member of cluster is only to the router (zappa)posibility. to genvax e.q. not . ... can,t translate .... gruss rudi ================================================================================ Archive-Date: Tue, 01 Jun 1993 11:52:17 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX rewrite rules? Message-ID: <1993Jun1.101341.159@anorad.com> Date: 1 Jun 93 10:13:41 EST To: MX-List@WKUVX1.BITNET >>>>> I'm looking at doing the same thing here. You have to use the address >>>>> modification interface (NAME_CONVERSION is using it) to rewrite the >>>>> addresses for you. >> >>> So does this mean that NAME_CONVERSION has to be modified to generate >>> the sort of address I'm looking for? I'll have to take a look at that routine >>> next week... >> >> Yes it does. You also have to use the FULL_CONVERT routing as well >> as the CONVERT routine. The CONVERT routine only modifies the username >> part of the address. The FULL_CONVERT routine must give the complete >> RFC-822 formatted address back. I see. Has anybody already done this? There's no sense in me spending time trying to figuire out how to do it if it's already been done, right? +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mikel Beck - Senior Business Programmer, Anorad Corporation | | E-Mail: mikel@rygel.anorad.com | | "Excellence In Motion" | +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ ================================================================================ Archive-Date: Wed, 02 Jun 1993 00:01:01 CDT Sender: list-mgr@WKUVX1.BITNET From: jeh@cmkrnl.com Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Any update on MX --> DECUS UUCP bug? Message-ID: <1993Jun1.195257.2101@cmkrnl.com> Date: 1 Jun 93 19:52:57 PDT To: MX-List@WKUVX1.BITNET In article <1993May28.160219.1821@mala.bc.ca>, dunnett@mala.bc.ca (Malcolm Dunnett) writes: > From the MX V3.3 release notes: >> 5.3 DECUS UUCP UUCP_MAILSHR Bug >> [...] > Is there a "beta" version of the fixed UUCP_MAILSHR available? Not that I know of. > If so would it work with V2.0 of DECUS UUCP ( ie could I install just this > file ) If there was a beta version of a "post-2.0" uucp_mailshr, it would probably work with the rest of the 2.0 code. None of us has had much of a chance to do anything wrt releases after 2.0 -- we have all been busy with paying jobs. However I will forward this directly to Tom Allebrandi (who "owns" uucp_mailshr). It's possible that there's a very simple fix. (Then again...!) --- Jamie Hanrahan, Kernel Mode Systems, San Diego CA drivers, internals, networks, applications, and training for VMS and Windows NT uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and Chair, Programming and Internals Working Group, U.S. DECUS VMS Systems SIG Internet: jeh@cmkrnl.com Uucp: uunet!cmkrnl!jeh CIS: 74140,2055 ================================================================================ Archive-Date: Wed, 02 Jun 1993 01:46:42 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 08:39:56 CET From: Hans-Joachim Koch Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: sys_hjk@lifra.lif.de Message-ID: <0096D6A9.F574FBA0.24964@lifra.lif.de> Subject: Signature problems NEWSRDR with MX Hello, I have set things this way: if I send mail with MX, the signature will be appended by default. If I post something with NEWSRDR, the signature will be appended too. But if I combine these two, I get problems. If I "reply/post" to an article with NEWSRDR, the new article gets a single signature. If I "reply/mail" to an article with NEWSRDR, the mail gets two signatures, one from NEWSRDR and one from MX. No problem, I simply use "reply/mail/nosig" and the mail gets only one signature from MX. But what can I do, when I use "reply/post/mail"? Either the posting gets NO signature (using "reply/post/mail/nosig") and the mail gets ONE, or the postings gets ONE signature (using "reply/post/mail"), but the mail gets TWO signatures... The behaviour of both programs is correct. Is there a simple solution? Thanks, Hans. -- Hans-Joachim Koch, Computer department of Lahmeyer International Lyoner Strasse 22, POB 71 06 51, D-6000 Frankfurt (Main) 71, Germany Phone: +49 69 6677-642, Fax: +49 69 6677-571, Tx: 413478 li d EUnet: koch@lifra.lif.de, AMPRnet: dk9om@db0lj.ampr.org ================================================================================ Archive-Date: Wed, 02 Jun 1993 04:31:08 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9306021026.AA03864@bogart.mpib-tuebingen.mpg.de> To: mx-list@WKUVX1.BITNET CC: boerner@bogart.mpib-tuebingen.mpg.de Subject: install mx033; mx takes all recouces ??? Date: Wed, 02 Jun 93 11:26:00 +0100 From: boerner@bogart.mpib-tuebingen.mpg.de Reply-To: MX-List@WKUVX1.BITNET Hi, i have installed MX033. Something is wrong or i can understand MX. First MX is installed on CLUSTER. I will, that all user get the mail-sender from the machine on witch they work. E.g smith@genvax.mpib-tueb....... . But there isn't. All user get sender from network-hostname : e.g. zappa. If i send a mail to smith@genvax... they could't deliver. To smith@zappa...... ok. install-config: router: zappa,genvax local delivery agent:zappa,genvax smtp server : zappa,genvax and so on. I have change mcp config on genvax, but no effect: MCP> sh path Domain-to-path mappings: Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*.BITNET", Path=SMTP, Route="ibm.gwdg.de" Domain="*", Path=SMTP Domain="genvax.mpib-tuebingen.mpg.de", Path=Local Domain="genvax", Path=Local I have observed al MX-process: I/O MX-SMTP ????? no mail was send and arrvied. I is normal ???? $sh system 20600D7B MX Router RWSCS 5 9092576 0 01:39:02.92 10888 3000 20600D7C MX Local HIB 5 912014 0 00:08:55.02 714 886 20600D7D MX Site Agent HIB 6 927034 0 00:09:16.25 426 434 20600D7E MX SMTP RWSCS 5 95378557 0 04:54:44.13 2262 2529 20600D7F SMTP Server HIB 5 7143740 0 04:53:37.16 4312 2854 20600D80 MX MLF HIB 5 915054 0 00:08:53.06 208 371 Direct I/O Rate Buffered I/O Rate Cur Top: MX SMTP (36) Cur Top: SYSTEM (0) Direct I/O Rate Buffered I/O Rate Cur Top: MX Router (62) Cur Top: MX Router (1) Direct I/O Rate Buffered I/O Rate Cur Top: SMTP Server (8) Cur Top: MX SMTP (636) <==== ???? regards rudi email boerner@bogart.mpib-tuebingen.mpg.de ================================================================================ Archive-Date: Wed, 02 Jun 1993 06:01:36 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Any update on MX --> DECUS UUCP bug? Message-ID: <1993Jun2.054838.1717@dmc.com> Date: 2 Jun 93 05:48:38 EDT To: MX-List@WKUVX1.BITNET In article <1993Jun1.195257.2101@cmkrnl.com>, jeh@cmkrnl.com writes: > None of us has had much of a chance to do anything wrt releases after 2.0 -- we > have all been busy with paying jobs. However I will forward this directly to > Tom Allebrandi (who "owns" uucp_mailshr). It's possible that there's a very > simple fix. (Then again...!) It's a simple fix (one line change). Hunter tracked it down and, as a side effect of some other conversations we were having, sent it to me. I popped it into my copy of uucico and it's been running for at least 2 months with no problems. I don't have the original patch around anymore, but Hunter might or if necessary I can drag up the original sources and diff them to find it. Dick Munroe -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Wed, 02 Jun 1993 08:06:23 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 11:04:45 MET From: Pavol Mederly Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D6BE.30843760.14730@dnet.mff.uniba.cs> Subject: Re: MX rewrite rules? > >> Yes it does. You also have to use the FULL_CONVERT routing as well > >> as the CONVERT routine. The CONVERT routine only modifies the username > >> part of the address. The FULL_CONVERT routine must give the complete > >> RFC-822 formatted address back. > > I see. Has anybody already done this? There's no sense in me > spending time trying to figuire out how to do it if it's already > been done, right? Yes, we had the same problem. I took NAME_CONVERSION.C from [.CONTRIB]DECNET_NAME_CONVERSION (made by Earle F. Ake; version 1.2) which did the conversion NODENAME::USERNAME --> username%nodename.dnet@domain-name and rewrote it to do the conversion NODENAME::USERNAME --> either Firstname.Lastname@domain-name or username@nodename.another-domain-name (The reason for doing such differences was that the faculty stuff was authorized to send mail worldwide, while students only campus-wide. Our gateway to the outside world was set up in such way that it did not allow the messages with ".another-domain-name" pass through). The modified NAME_CONVERSION.C takes data from the text file (ALIASES.TXT) containing lines with VMS username, user's full name and optionally part "domain-name" for users which want to have domain different from our default. When the message passes from VMSmail to MX, the FULL_CONVERT is called. If it finds the username in the ALIASES.TXT, it translates username to full name (Firstname.Lastname) and appends the domain, which is either default or defined in the file. If it don't find the username, it will use the second form of conversion (user@node.another-domain-name). This is not exactly what you need but you can easily make FULL_CONVERT choose always the second form (containing also the information about node name). When the message passes from MX back to VMSmail, the CONVERT is called. It simply tries to find the text it gets (which can be either true username or Firstname.Lastname) in the "Full name" column of ALIASES.TXT and if it finds it, it returns corresponding username. If you want the module, send me a note and I will mail it to you. But before it I will add some comments and MRGATE support which I had left out - I'm sorry but I never thought that someone else could be interested in the beast I did. One disadvantage of reading data from file - I suppose the file is read by VMSmail Entry Agent with each message posted to MX. If you have many users and therefore big file... Pavol Mederly (Pavol.Mederly@fmph.uniba.cs) ================================================================================ Archive-Date: Wed, 02 Jun 1993 08:19:49 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 08:19:18 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D6A7.1380F7A0.16688@WKUVX1.BITNET> Subject: RE: install mx033; mx takes all recouces ??? boerner@bogart.mpib-tuebingen.mpg.de writes: > >i have installed MX033. Something is wrong or i can understand MX. > [...] >But there isn't. All user get sender from network-hostname : e.g. zappa. >If i send a mail to smith@genvax... they could't deliver. >To smith@zappa...... ok. > That's because your PATH definitions are in the wrong order. > MCP> sh path > >Domain-to-path mappings: > Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" > Domain="*.BITNET", Path=SMTP, Route="ibm.gwdg.de" > Domain="*", Path=SMTP > Domain="genvax.mpib-tuebingen.mpg.de", Path=Local > Domain="genvax", Path=Local > MX searches PATHs in the order in which they're stored. The last two *must* come before the others (specifically before the "*"). What's happening is that a message to sent user@genvax... matches with "*" and is sent via SMTP, resulting in a probable mail loop. The solution is to remove the PATHs, then DEFINE PATH them in the correct order, with the two LOCAL PATHs first. The easiest way to ensure the order is right it to maintain a CONFIG.MCP file and use it to make your MX changes. >I have observed al MX-process: > >I/O MX-SMTP ????? no mail was send and arrvied. I is normal ???? > The process resource problems are most likely a result of the mail forwarding loop you've unintentionally created. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 02 Jun 1993 08:22:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 08:22:18 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D6A7.7F158E40.16690@WKUVX1.BITNET> Subject: Re: Any update on MX --> DECUS UUCP bug? writes: > >It's a simple fix (one line change). Hunter tracked it down and, as a side >effect of some other conversations we were having, sent it to me. I popped it >into my copy of uucico and it's been running for at least 2 months with no >problems. I don't have the original patch around anymore, but Hunter might or >if necessary I can drag up the original sources and diff them to find it. > I didn't bother to keep the fix because I talked to Tom about it and found that he already knew about it and had fixed it too. Obviously, they've been busy, but I threw my changes out because I thought there was going to be a new version soon. Sorry. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 02 Jun 1993 08:52:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 09:31:13 EDT From: "Brian Tillman, Smiths Industries, VAX Support, x8425" Reply-To: MX-List@WKUVX1.BITNET To: boerner@bogart.mpib-tuebingen.mpg.de CC: mx-list@WKUVX1.BITNET Message-ID: <0096D6B1.1FE73540.3590@swdev.si.com> Subject: RE: install mx033; mx takes all recouces ??? rudi (boerner@bogart.mpib-tuebingen.mpg.de) writes: >i have installed MX033. Something is wrong or i can understand MX. ...stuff deleted... > > MCP> sh path > >Domain-to-path mappings: > Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" > Domain="*.BITNET", Path=SMTP, Route="ibm.gwdg.de" > Domain="*", Path=SMTP > Domain="genvax.mpib-tuebingen.mpg.de", Path=Local > Domain="genvax", Path=Local The first thing you must do is to put all of your LOCAL paths first. That is, your paths should look like this: Domain-to-path mappings: Domain="genvax.mpib-tuebingen.mpg.de", Path=Local Domain="genvax", Path=Local Domain="zappa.mpib-teubingen.mpg.de", Path=Local Domain="zappa", Path=Local Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*.BITNET", Path=SMTP, Route="ibm.gwdg.de" Domain="*", Path=SMTP You can accomplish this by editing MX_DIR:CONFIG.MCP to place them in the proper order. Then, stop MX and load the new configuration like this: $ mcr mx_exe:mcp/nofile MCP> @mx_dir:config.mcp MCP> save mx_dir:mx_config MCP> exit Now, restart MX: $ sysman SYSMAN> set env/clu SYSMAN> do @sys$startup:mx_startup SYSMAN> exit If you have problems after this, write back. -- Brian Tillman tillman_brian@si.com ================================================================================ Archive-Date: Wed, 02 Jun 1993 10:51:25 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Signature problems NEWSRDR with MX Message-ID: <1993Jun2.153203.19337@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 2 Jun 1993 15:32:03 GMT To: MX-List@WKUVX1.BITNET In article <0096D6A9.F574FBA0.24964@lifra.lif.de>, Hans-Joachim Koch writes: >I have set things this way: if I send mail with MX, the signature will >be appended by default. If I post something with NEWSRDR, the signature >will be appended too. [...] >The behaviour of both programs is correct. Is there a simple solution? Yes. In NEWSRDR, SET SIGNATURE_FILE/AUTOMATIC=(POST,NOMAIL) -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Wed, 02 Jun 1993 11:20:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 11:19:32 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D6C0.414E16E0.16812@WKUVX1.BITNET> Subject: The fix for UUCP_MAILSHR (assuming you have the sources and compiler) I found my original post from February about the UUCP_MAILSHR problem, including the instructions for fixing it. Note that you'll need the sources and a Pascal compiler to fix it. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) --------------------------------------------------------------------------- Date: Sun, 28 Feb 1993 00:48:45 CST From: Hunter Goatley Subject: RE: mx -> uucp hung in compute bound loop munroe@DMC.COM writes: > >I have a queue entry that causes the MX -> UUCP process to go into an infinite >loop. The only way out is to kill the process, cancel the entry, and restart >the process manually (mcp shut is ineffective). This bug has shown up >occasionally with 3.1 and is data dependent, particular messages cause the >problem. I'm sending a VMSSHARE of the queue entry causing the problem under >seperate header. Hope you can find this one. > I did. As I mentioned the other day, I thought the problem was not an MX problem but was instead a DECUS UUCP problem. Well, I was right---it *is* a DECUS UUCP problem, and it's an incredibly subtle bug! When a file is sent through UUCP_MAILSHR (using, say, SEND/NOEDI file or, in the case of MX->uucp, MAIL/PROTOCOL=UUCP_MAILSHR filename....), UUCP_MAILSHR makes sure that every line is wrapped to produce lines that are no longer than 255 characters. When a line is read that is longer than 255 characters, it starts at the 255th character and starts looking backwards for either a space or a linefeed. When either is found, that point becomes the place where the line is broken for wrapping. The MX->uucp looping problem only occurs when a binary file is sent through that contains lines with substrings longer than 255 characters with no space or linefeed in them *except* the very first character! For example: 0 40 320 512 Word ... Word ....nospaceorlinefeed. .......... UUCP_MAILSHR would try to break this line into multiple lines. The first line would be "Word ..." (up to the 40th byte), and then, the way the code is written, it will loop forever writing out 0 bytes because it found a blank at offset 1, which set a "done" flag to true, then decremented the number of bytes from 1 to 0. The check after that loop says, "if ((bytes = 0) and (not done) then bytes := 255;". Well, in this case, bytes is 0 by done is true, so bytes stays 0 and the later, when recalculating bytes left, we subtract 0 and reprocess the characters 40-294. Voila! Infinite loop! It's easy to fix---in UUPC_MAIL.PAS in procedure put_text, change the check above ("if ((bytes = 0)....") to just "if (bytes = 0) then bytes := 255;". That'll write out the line with a leading blank. You could try to handle this case specifically, but I see no point in doing so. On Monday, I'll let the UUCP guys (and MX-List) know about this bug. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Wed, 02 Jun 1993 12:33:48 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 13:29:14 EDT From: Alan Simon Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET Message-ID: <0096D6D2.5F818B80.28424@shrsys.hslc.org> Subject: MX Logicals Hunter - I have set a canonical name for my VAX that is completely different from the existing host and domain name, for use by a selected group of users. However, the MX mail header contains numerous references to the original host and domain names. Would you consider modifying the source code to allow the definition of MX_NODE_NAME, MX_VMSMAIL_FROM_FORMAT, and MX_VMSMAIL_LOCALHOST at the process level, so that I can customize the header for different groups of users? ------------------------------------------------------------------------------- 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: Wed, 02 Jun 1993 12:36:05 CDT Sender: list-mgr@WKUVX1.BITNET Date: 02 Jun 93 17:27:45+0000 From: Fabien Marathee Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9306021727.AA03929(a)eliot.cnes.fr> To: MX-List@WKUVX1.BITNET Subject: MX Router Problem CC: marathee@eliot.cnes.fr I have installed MX033 on : CNESTD (Microvax II - VMS 5.4) : running fine and CNESTA (Microvax 3600 - VMS 5.5-2) : I have a problem here... Both systems are running Multinet 3.2. My problem is: MX Router on CNESTA stops before delivering SMTP input messages to local agent, messages are queued with status INPRG or READY but nothing else seems to be done (in fact mx router process aborts ...): BAD LOG: ======== 2-JUN-1993 16:41:02.29 %PROCESS, Processing entry number 28 2-JUN-1993 16:41:02.53 %PROCESS, Status from READ_INFO was 00000001 2-JUN-1993 16:41:02.53 %PROCESS, Recipient #0: 2-JUN-1993 16:41:02.55 %REWRITE, Applying rewrite rule: <{user}@cnesta.span.cnes.fr> => <"cnesta::{user}"@cnesta.cnes.fr> to: 2-JUN-1993 16:41:03.06 %FINDPATH, Site-spec expand on cnesta.cnes.fr err=000000 00 2-JUN-1993 16:41:03.06 %FINDPATH, domain name CNESTA.CNES.FR matched path patte rn CNESTA.CNES.FR 2-JUN-1993 16:41:03.06 %PROCESS, Rewrote as <"cnes ta::system"@cnesta.cnes.fr> - next hop cnesta.cnes.fr, path 1 Here is the equivalent log from CNESTD: GOOD LOG: ========= 2-JUN-1993 14:57:05.29 %PROCESS, Processing entry number 205 2-JUN-1993 14:57:05.73 %PROCESS, Status from READ_INFO was 00000001 2-JUN-1993 14:57:05.74 %PROCESS, Recipient #0: 2-JUN-1993 14:57:05.78 %REWRITE, Applying rewrite rule: <{user}@cnestd.span.cnes.fr> => <"cnestd::{user}"@cnestd.cnes.fr> to: 2-JUN-1993 14:57:05.93 %FINDPATH, Site-spec expand on cnestd.cnes.fr err=000000 00 2-JUN-1993 14:57:05.93 %FINDPATH, domain name CNESTD.CNES.FR matched path patte rn CNESTD.CNES.FR 2-JUN-1993 14:57:05.94 %PROCESS, Rewrote as <"cnes td::system"@cnestd.cnes.fr> - next hop cnestd.cnes.fr, path 1 2-JUN-1993 14:57:05.94 %FINDALIAS, no alias found for "cnestd::system" 2-JUN-1993 14:57:05.95 %PROCESS, no alias found for "cnestd::system" 2-JUN-1993 14:57:05.95 %PROCESS, this is just a local delivery 2-JUN-1993 14:57:06.10 %PROCESS, Adding to LOCAL path: "cnestd::system". 2-JUN-1993 14:57:06.97 %PROCESS, Path LOCAL gets 1 rcpts, entry number 206 Any idea ? or I'm gonna be killed soon ! Thank you, Fabien Marathee (eliot.cnes.fr) --- HERE IS CNESTD CONFIGURATION WHICH IS RUNNING OK --------------------------- CNESTD$ set def mx_router_dir CNESTD$ dir Directory MX_ROOT:[ROUTER] MX_ROUTER.LOG;15 MX_ROUTER.LOG;14 MX_ROUTER.LOG;13 MX_ROUTER_LOG.LOG;25 MX_ROUTER_LOG.LOG;24 MX_ROUTER_LOG.LOG;23 MX_ROUTER_LOG.LOG;22 MX_ROUTER_LOG.LOG;21 MX_ROUTER_LOG.LOG;20 MX_ROUTER_LOG.LOG;19 Total of 10 files. CNESTD$ type *.* %TYPE-W-OPENIN, error opening MX_ROOT:[ROUTER]MX_ROUTER.LOG;15 as input -RMS-E-FLK, file currently locked by another user MX_ROOT:[ROUTER]MX_ROUTER_LOG.LOG;25 2-JUN-1993 14:57:05.29 %PROCESS, Processing entry number 205 2-JUN-1993 14:57:05.73 %PROCESS, Status from READ_INFO was 00000001 2-JUN-1993 14:57:05.74 %PROCESS, Recipient #0: 2-JUN-1993 14:57:05.78 %REWRITE, Applying rewrite rule: <{user}@cnestd.span.cnes.fr> => <"cnestd::{user}"@cnestd.cnes.fr> to: 2-JUN-1993 14:57:05.93 %FINDPATH, Site-spec expand on cnestd.cnes.fr err=000000 00 2-JUN-1993 14:57:05.93 %FINDPATH, domain name CNESTD.CNES.FR matched path patte rn CNESTD.CNES.FR 2-JUN-1993 14:57:05.94 %PROCESS, Rewrote as <"cnes td::system"@cnestd.cnes.fr> - next hop cnestd.cnes.fr, path 1 2-JUN-1993 14:57:05.94 %FINDALIAS, no alias found for "cnestd::system" 2-JUN-1993 14:57:05.95 %PROCESS, no alias found for "cnestd::system" 2-JUN-1993 14:57:05.95 %PROCESS, this is just a local delivery 2-JUN-1993 14:57:06.10 %PROCESS, Adding to LOCAL path: "cnestd::system". 2-JUN-1993 14:57:06.97 %PROCESS, Path LOCAL gets 1 rcpts, entry number 206 CNESTD$ sho log mu* (LNM$PROCESS_TABLE) (LNM$JOB_80A53E60) (LNM$GROUP_000001) (LNM$SYSTEM_TABLE) "MULTINET" = "MULTINET_ROOT:[MULTINET]" "MULTINET_CLUSTER_ALIAS_MAILBOX" = "MBA16:" "MULTINET_COMMON_ROOT" = "DUA2:[SYS0.SYSCOMMON.]" "MULTINET_HOST_NAME" = "CNESTD.CNES.FR" "MULTINET_KERNEL_BASE_ADDRESS" = "80749200" "MULTINET_KERNEL_SIZE" = "180224" "MULTINET_NAMESERVERS" = "192.134.216.18" "MULTINET_NETWORK_IMAGE" = "MULTINET_COMMON_ROOT:[MULTINET]MULTINET.EXE;2" "MULTINET_ROOT" = "DUA2:[SYS0.]" = "MULTINET_COMMON_ROOT:" "MULTINET_SMTP_POSTMASTER" = "SYSTEM" "MULTINET_SOCKET_LIBRARY" = "MULTINET:MULTINET_SOCKET_LIBRARY" "MULTINET_SPOOL" = "MULTINET_COMMON_ROOT:[MULTINET.SPOOL]" "MULTINET_TIMEZONE" = "WET" "MULTINET_TOPS_LIBRARY" = "MULTINET:MULTINET_TOPS_LIBRARY" "MULTINET_VMS_SHAREABLE" = "MULTINET:MULTINET_VMS_SHAREABLE" (DECW$LOGICAL_NAMES) CNESTD::SYSTEM$ sho log mx* (LNM$PROCESS_TABLE) "MX_VMSMAIL_SHOW_ADDR" = "TRUE" (LNM$JOB_80A53E60) (LNM$GROUP_000001) (LNM$SYSTEM_TABLE) "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "DUA2:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EVENT_OPER_CLASS" = "NETWORK" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "SYS$SYSDEVICE:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "CNESTD" "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" = "cnestd.cnes.fr" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DEBUG" = "TRUE" "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_SITE_NAME_CONVERSION" = "MX_EXE:NAME_CONVERSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_VMSMAIL_LOCALHOST" = "@cnestd.cnes.fr" (DECW$LOGICAL_NAMES) CNESTD$ mcp MCP> sho all Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;20 MX version id is: MX V3.3 VAX Address-rewriting rules: Rewrite "<{user}@cnestd.span.cnes.fr>" => "<""cnestd::{user}""@cnestd.cnes.fr> " Rewrite "<{user}@cnestd>" => "<""cnestd::{user}""@cnestd.cnes.fr>" Rewrite "<{user}@{node}.span>" => "<""{node}::{user}""@cnestd.cnes.fr>" Rewrite "<{user}@{node}.span.cnes.fr>" => "<""{node}::{user}""@cnestd.cnes.fr> " Rewrite "<{user}%{node}.decnet@cnestd.cnes.fr>" => "<""{node}::{user}""@cnestd .cnes.fr>" Domain-to-path mappings: Domain="cnestd.cnes.fr", Path=Local Domain="cnestd", Path=Local Domain="[192.134.216.35]", Path=Local Domain="cnestd.span.cnes.fr", Path=Local Domain="*.span.cnes.fr", Path=Local Domain="*.span", Path=Local Domain="*.bitnet", Path=SMTP, Route="mailimailo.cicb.fr" Domain="*.uucp", Path=SMTP, Route="pamir.inria.fr" Domain="*", Path=SMTP, Route="pamir.inria.fr" Aliases: LocalName="Postmaster", Address="system@cnestd.cnes.fr" LocalName="POSTMAST", Address="system@cnestd.cnes.fr" SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Number of DNS failure retries: 12 Accounting: disabled Default router: pamir.inria.fr LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. Multiple VMS Mail From: addresses allowed. Top headers: FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID, RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT, ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM, RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER Bottom headers: (none) ROUTER agent settings: Automatic percent-hack handling: disabled MCP> sho queue/all MCP> quit --- HERE IS CNESTA CONFIGURATION - ROUTER/LOCAL delivery PROBLEM --------------- CNESTA$ set def mx_router_dir CNESTA$ dir Directory MX_ROOT:[ROUTER] MX_ROUTER_CNESTA.LOG;2 MX_ROUTER_LOG.LOG;1 Total of 2 files. CNESTA$ type *.* MX_ROOT:[ROUTER]MX_ROUTER_CNESTA.LOG;2 2-JUN-1993 15:58:48.64: MX Router (pid 00000187) starting 2-JUN-1993 16:02:52.44: MX Router (pid 00000187) resetting 2-JUN-1993 16:41:03.17: MX Router (pid 00000187) exiting, status = 1000000C MX_ROOT:[ROUTER]MX_ROUTER_LOG.LOG;1 2-JUN-1993 16:41:02.29 %PROCESS, Processing entry number 28 2-JUN-1993 16:41:02.53 %PROCESS, Status from READ_INFO was 00000001 2-JUN-1993 16:41:02.53 %PROCESS, Recipient #0: 2-JUN-1993 16:41:02.55 %REWRITE, Applying rewrite rule: <{user}@cnesta.span.cnes.fr> => <"cnesta::{user}"@cnesta.cnes.fr> to: 2-JUN-1993 16:41:03.06 %FINDPATH, Site-spec expand on cnesta.cnes.fr err=000000 00 2-JUN-1993 16:41:03.06 %FINDPATH, domain name CNESTA.CNES.FR matched path patte rn CNESTA.CNES.FR 2-JUN-1993 16:41:03.06 %PROCESS, Rewrote as <"cnes ta::system"@cnesta.cnes.fr> - next hop cnesta.cnes.fr, path 1 CNESTA$ sho log mx* (LNM$PROCESS_TABLE) (LNM$JOB_80916E10) (LNM$GROUP_000001) (LNM$SYSTEM_TABLE) "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "CNESTA$DUA0:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EVENT_OPER_CLASS" = "NETWORK" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "SYS$SYSDEVICE:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "CNESTA" "MX_FLQ_RECLAIM_WAIT" = "0 02:00:00" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DEBUG" = "TRUE" "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" = "cnesta.cnes.fr" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DEBUG" = "TRUE" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SITE_NAME_CONVERSION" = "MX_EXE:NAME_CONVERSION" "MX_SMTP_DEBUG" = "TRUE" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_SMTP_SERVER_DEBUG" = "TRUE" "MX_VMSMAIL_LOCALHOST" = "@cnesta.cnes.fr" (DECW$LOGICAL_NAMES) CNESTA$ sho log mu* (LNM$PROCESS_TABLE) (LNM$JOB_80916E10) (LNM$GROUP_000001) (LNM$SYSTEM_TABLE) "MULTINET" = "MULTINET_ROOT:[MULTINET]" "MULTINET_CLUSTER_ALIAS_MAILBOX" = "MBA50:" "MULTINET_COMMON_ROOT" = "CNESTA$DUA0:[SYS0.SYSCOMMON.]" "MULTINET_HOST_NAME" = "cnesta.cnes.fr" "MULTINET_KERNEL_BASE_ADDRESS" = "8022A000" "MULTINET_KERNEL_SIZE" = "180224" "MULTINET_NAMESERVERS" = "132.149.0.19" "MULTINET_NETWORK_IMAGE" = "MULTINET_COMMON_ROOT:[MULTINET]MULTINET.EXE;1" "MULTINET_ROOT" = "CNESTA$DUA0:[SYS0.]" = "MULTINET_COMMON_ROOT:" "MULTINET_SMTP_POSTMASTER" = "SYSTEM" "MULTINET_SOCKET_LIBRARY" = "MULTINET:MULTINET_SOCKET_LIBRARY" "MULTINET_SPOOL" = "MULTINET_COMMON_ROOT:[MULTINET.SPOOL]" "MULTINET_TIMEZONE" = "GMT" "MULTINET_TOPS_LIBRARY" = "MULTINET:MULTINET_TOPS_LIBRARY" "MULTINET_VMS_SHAREABLE" = "MULTINET:MULTINET_VMS_SHAREABLE" (DECW$LOGICAL_NAMES) CNESTA$ mcp MCP> sho all Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;6 MX version id is: MX V3.3 VAX Address-rewriting rules: Rewrite "<{user}@cnesta.span.cnes.fr>" => "<""cnesta::{user}""@cnesta.cnes.fr> " Rewrite "<{user}@{node}.span.cnes.fr>" => "<""{node}::{user}""@cnesta.cnes.fr> " Rewrite "<{user}%{node}.decnet@cnesta.cnes.fr>" => "<""{node}::{user}""@cnesta .cnes.fr>" Rewrite "<{user}@cnesta>" => "<""cnesta::{user}""@cnesta.cnes.fr>" Rewrite "<{user}@{node}.span>" => "<""{node}::{user}""@cnesta.cnes.fr>" Domain-to-path mappings: Domain="cnesta.cnes.fr", Path=Local Domain="cnesta", Path=Local Domain="[132.149.0.13]", Path=Local Domain="cnesta.span.cnes.fr", Path=Local Domain="*.span.cnes.fr", Path=Local Domain="*.span", Path=Local Domain="*", Path=SMTP, Route="eliot.cnes.fr" Aliases: LocalName="POSTMASTER", Address="system@cnesta.cnes.fr" LocalName="POSTMAST", Address="system@cnesta.cnes.fr" SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Number of DNS failure retries: 12 Accounting: enabled Default router: eliot.cnes.fr LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting enabled. Multiple VMS Mail From: addresses allowed. Top headers: FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID, RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT, ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM, RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER Bottom headers: (none) ROUTER agent settings: Automatic percent-hack handling: disabled MCP> sho queue/all Entry Status Size Source Agent Entry Status Size ----- ------ ------ ------ ------- ----- ------ ------ 28 INPROG 0 SMTP MCP> quit -------------------------------------------------------------------------------- ================================================================================ Archive-Date: Wed, 02 Jun 1993 13:10:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 13:08:39 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D6CF.7F6506A0.16846@WKUVX1.BITNET> Subject: RE: MX Router Problem Fabien Marathee writes: > >I have installed MX033 on : > > CNESTD (Microvax II - VMS 5.4) : running fine >and > CNESTA (Microvax 3600 - VMS 5.5-2) : I have a problem here... > >Both systems are running Multinet 3.2. > >My problem is: > >MX Router on CNESTA stops before delivering SMTP input messages to local agent, >messages are queued with status INPRG or READY but nothing else seems to be >done (in fact mx router process aborts ...): > I don't know why the MX Router is accvio'ing. However, I suspect that it has something to do with the way you're rewriting addresses. Address-rewriting rules: Rewrite "<{user}@cnesta.span.cnes.fr>" => "<""cnesta::{user}""@cnesta.cnes.fr>" Rewrite "<{user}@{node}.span.cnes.fr>" => "<""{node}::{user}""@cnesta.cnes.fr>" Why do you have the first rewrite rule defined?? It seems like what you really want is: "<{user}@cnesta.span.cnes.fr>" -> "<{user}@cnesta.cnes.fr>" That way you avoid "cnesta::system"@cnesta.... Shouldn't make any difference, as far as I can see, but it does simplify the addresses a whole lot. Are cnesta and cnestd in a cluster? Do they share the same VMSMAIL_PROFILE and SYSUAF? If so, then you'd be better off defining them all as local and not using the DECnet addresses. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 02 Jun 1993 13:56:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 13:56:16 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D6D6.26775AA0.16864@WKUVX1.BITNET> Subject: Correcting * PATH in wrong order Carl J Lydick send me the following quick fix for the * PATH being specified in the middle of the paths: >=>Domain-to-path mappings: >=> Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" >=> Domain="*.BITNET", Path=SMTP, Route="ibm.gwdg.de" >=> Domain="*", Path=SMTP >=> Domain="genvax.mpib-tuebingen.mpg.de", Path=Local >=> Domain="genvax", Path=Local >=> I wrote: >=The solution is to remove the PATHs, then DEFINE PATH them in the >=correct order, with the two LOCAL PATHs first. The easiest way to >=ensure the order is right it to maintain a CONFIG.MCP file and use it >=to make your MX changes. > And Carl supplied the following commands, which will fix the problem *and* create a CONFIG.MCP file for future maintenance. >The easiest way to fix his problem is: > $ RUN MX_EXE:MCP > MCP> REMOVE PATH * > MCP> DEFINE PATH * SMTP > MCP> SAVE > MCP> RESET > MCP> SHOW ALL/COMMAND/OUTPUT=MX_DIR:CONFIG.MCP Thanks, Carl! (I forwarded this to the list because I wasn't sure if Carl had.) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 02 Jun 1993 14:04:33 CDT Sender: list-mgr@WKUVX1.BITNET Date: 02 Jun 1993 14:52:25 -0400 (EDT) From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET Subject: MLF hoses NAMSRV To: MX-List@WKUVX1.BITNET CC: hardis@garnet.nist.gov Message-ID: <0096D6DD.FEFB58C0.14962@garnet.nist.gov> Content-Transfer-Encoding: 7BIT I don't know if this is an MX problem or a was-CMU/was-TEK TCP/IP problem, but I try here first. My system had been working well for many months until I set up my first mailing list with a non-trivial number of subscribers. Now, when mail comes in for the list, NAMSRV gets hosed. In order to recover I have to reboot or (as I figured out how to do today) restart NAMSRV. The symptoms are: 1) After what happens happens, all outgoing SMTP mail appears (MCP QUEUE SHOW /A /F) as: Last error: %SYSTEM-F-IVADDR, invalid media address 2) Name service doesn't work for anything else, either. 3) A review of all MX log files shows that the message comes in through SMTP_SERVER, apparently normally, and that something apparently goes wrong during the routing phase: $ type MX_ROUTER_LOG.LOG;142 1-JUN-1993 08:34:36.89 %PROCESS, Processing entry number 14847 1-JUN-1993 08:34:38.11 %PROCESS, Status from READ_INFO was 00000001 1-JUN-1993 08:34:38.12 %PROCESS, Recipient #0: 1-JUN-1993 08:34:38.12 %PROCESS, Recipient #1: 1-JUN-1993 08:34:38.87 %FINDPATH, Site-spec expand on MICF.NIST.GOV err=00000870 1-JUN-1993 08:34:38.88 %FINDPATH, domain name MICF.NIST.GOV matched path pattern * 1-JUN-1993 08:34:38.88 %PROCESS, Rewrote as - next hop MICF.NIST.GOV, path 2 This continues, with a mixture of error 840 and error 0, until error 134's begin. Then, they are all error 134. In the SMTP phase, the error 134's continue: 1-JUN-1993 08:34:56.65 Processing queue entry number 14850 1-JUN-1993 08:34:58.74 Recipient: , route=MICF.NIST.GOV (and so on) 1-JUN-1993 08:34:59.57 SMTP_SEND: looking up host name MICF.NIST.GOV 1-JUN-1993 08:34:59.99 SMTP_SEND: Failed, sts=00000134 1-JUN-1993 08:34:59.99 SMTP send failed, sts=0C27804A, sts2=00000134 1-JUN-1993 08:35:00.00 Recipient status=0C27804A for I note again that, after a reboot, the mail is sent normally. So, whatever is happening isn't caused by the SMTP agent. Only the router, which does its thing once, seems to cause this. I suspect that the problem is "too many" of something happening "too quickly" in rapid succession, which hadn't been a problem until there were a lot of addresses to look up. Is there a quota or limit for NAMRES which might be too low? Thanks for your help, Jonathan Hardis ================================================================================ Archive-Date: Wed, 02 Jun 1993 14:55:15 CDT Sender: list-mgr@WKUVX1.BITNET From: bg@dymaxion.ns.ca Reply-To: MX-List@WKUVX1.BITNET Subject: MAIL/FOREIGN preserve original filename Message-ID: <1993Jun2.142335.1774@dymaxion.ns.ca> Date: 2 Jun 93 14:23:34 AST To: MX-List@WKUVX1.BITNET Is there any way more elegant than just including the filename in the subject of storing/retrieving the original filename of a file sent via MAIL/FOREIGN? I want write something to do the following: $ smail disk:[dir]filename.exe To: mx%"someuser@somenode.net" Subj: filename.exe $ smail disk:[dir]filename2.exe To: mx%"someuser@somenode.net" Subj: filename2.exe And at somenode.net login as someuser and: $ xmail %XMAIL-I-EXTRACT Extracting: filename.exe %XMAIL-I-EXTRACT Extracting: filename2.exe Ben. -- Ben Armstrong (INTP), Software Development, bus: (902)422-1973 Dymaxion Research Ltd., fax: (902)421-1267 Halifax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca ================================================================================ Archive-Date: Wed, 02 Jun 1993 15:38:50 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 15:38:02 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D6E4.5E1ACA60.16898@WKUVX1.BITNET> Subject: RE: MAIL/FOREIGN preserve original filename bg@dymaxion.ns.ca writes: > >Is there any way more elegant than just including the filename in the >subject of storing/retrieving the original filename of a file sent via >MAIL/FOREIGN? I want write something to do the following: > Giving it on the Subject: line is the only way to get the file name through to the remote node when using MAIL/FOREIGN. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 02 Jun 1993 16:29:26 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 15:23:17 -0700 (MST) From: "Louis B. Moore" Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX rewrite rules? To: MX-List@WKUVX1.BITNET Message-ID: <0096D6E2.4E651A00.8764@tchden.org> Content-Transfer-Encoding: 7BIT > I see. Has anybody already done this? There's no sense in me > spending time trying to figuire out how to do it if it's already > been done, right? There is an example application of the convert in NICKNAME.ZIP in the [.CONTRIB] directory of the MX 3.3 distribution. See if this works for you. Louis B. Moore Internet: MOORE.LOUIS@tchden.org Systems Programmer Phone: +1.303.837.2513 The Children's Hospital of Denver Denver, Colorado USA 80218 ================================================================================ Archive-Date: Wed, 02 Jun 1993 17:00:10 CDT Sender: list-mgr@WKUVX1.BITNET From: bg@dymaxion.ns.ca Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Subscribing one mailing list to another Message-ID: <1993Jun2.155557.1784@dymaxion.ns.ca> Date: 2 Jun 93 15:55:56 AST To: MX-List@WKUVX1.BITNET In article <1u5m4aINNru@gap.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: > So what Ben *REALLY* wants to > know is: Is there a way to make Medianet-L insert its own name in the From: > field in all messages it forwards. > > Offhand, the answer appears to be, No. OK. So how about introducing a third list which has "reply to list" set and whose sole purpose is to relay messages from Medianet-L to MUG-L? i.e. - create Medianet-to-MUG as list with: - "reply to list" set - "world write" granted (anyone can post, but noone can subscribe or read) - subscribe MUG-L to Medianet-to-MUG - subscribe Medianet-to-MUG to Medianet-L Now when someone posts to Medianet-L: - it gets relayed to Medianet-to-MUG - Medianet-to-MUG relays the message to MUG-L with the From: header set to Medianet-to-MUG - MUG-L receives the message - MUG-L recognizes that Medianet-to-MUG is a valid user and therefore accepts it - MUG-L relays the message to all MUG-L members The only thing that is lost is that the From: header is now Medianet-to-MUG, so if someone tries to respond to the message, it will go back to Medianet-to-MUG which will in turn echo the message back to all MUG-L members, but not to the Medianet-L members who saw the original post. Will this approach work? Ben. P.S. Short of this approach, I may have to go to using the SITE agent. Any hints? -- Ben Armstrong (INTP), Software Development, bus: (902)422-1973 Dymaxion Research Ltd., fax: (902)421-1267 Halifax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca ================================================================================ Archive-Date: Wed, 02 Jun 1993 17:01:36 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: foo!user@dmc.com doesn't pass through SMTP... Message-ID: <1993Jun2.165944.1721@dmc.com> Date: 2 Jun 93 16:59:44 EDT To: MX-List@WKUVX1.BITNET The SMTP server for MX when faced with addresses of the form: foo!user@dmc.com where foo is a down stream site for DMC.COM, gives forth with a no local user identification. Other SMTP implementation don't have this problem. Is this a "bug" with the MX SMTP server or a missing feature? Dick Munroe -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Wed, 02 Jun 1993 17:38:26 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 15:28:22 PDT From: "Bob Johns, (604)363-6520" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%wkuvx1.BITNET@cunyvm.cuny.edu Message-ID: <0096D6E3.04720560.9256@ccs.ios.bc.ca> Subject: How to prevent poor man's routing with MX We are part of an inter-provincial, corporate DECnet. As such, it is technically possible for users within other provinces on the same network to use our Internet access for Email by sending to: node::mx%"user@domain" where "node" is our DECnet nodename. However, our agreement with our Internet provider limits use to clients having accounts on our local machine. How can I prevent this kind of "poor man's routing" via MX, without disallowing normal DECnet traffic to/from other nodes? Bob Johns (bob@ios.bc.ca) Manager, Central Systems & Networks Scientific Computing Institute of Ocean Sciences Sidney, B.C. ================================================================================ Archive-Date: Wed, 02 Jun 1993 17:46:04 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Any update on MX --> DECUS UUCP bug? Message-ID: <1993Jun2.161528.3040@inland.com> Date: 2 Jun 93 16:15:28 CST To: MX-List@WKUVX1.BITNET In article <1993May28.160219.1821@mala.bc.ca>, dunnett@mala.bc.ca (Malcolm Dunnett) writes: >> Binary files sent through MX to DECUS UUCP can cause >> the MX->uucp process to go into a compute-bound >> infinite loop. This is a bug in the DECUS UUCP UUCP_ >> MAILSHR's handling of the temporary file created by >> MX. > Is there a "beta" version of the fixed UUCP_MAILSHR available? If so > would it work with V2.0 of DECUS UUCP ( ie could I install just this > file ) This is fixed in the next release. This bug was discovered right before the version 2.0 kit was put together, a fix was prepared, but it got lost somewhere. I would be concerned about the symptoms and not the bug. This bug only occurs when a) the inbound message contains a line longer than 255 characters; b) such a line contains a contiguous chunk of text consisting of over 255 non-whitespace characters. The inbound delivery mechanism used by the DECUS UUCP Mail Handler only allows lines of maximum 255 characters. The infinite loop occurs because of a mis-coding in the section that tries to break up lines that are too long. My concern is over the fact that a mail message generated by MX and delivered via DECUS UUCP will not arrive at its destination "unmolested". The file will be changed in transit by the UUCP mail transport agent. --- Tom Tom Allebrandi | Mail guru - DECUS UUCP Development Team Inland Steel Research Labs | NFS grunt - CMU/Tek-IP East Chicago, IN | Chairperson - VMSnet Working Group, DECUS VAX SIG 219 399 6306 | Internet: allebrandi@inland.com DECUServe: allebrandi | UUCP: ...!uunet!inland!allebrandi ================================================================================ Archive-Date: Wed, 02 Jun 1993 19:17:12 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: foo!user@dmc.com doesn't pass through SMTP... Date: 2 Jun 1993 23:16:20 GMT Message-ID: <1ujcc4INNhlt@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993Jun2.165944.1721@dmc.com>, munroe@dmc.com (Dick Munroe) writes: =The SMTP server for MX when faced with addresses of the form: = =foo!user@dmc.com = =where foo is a down stream site for DMC.COM, gives forth with a =no local user identification. = =Other SMTP implementation don't have this problem. Is this a ="bug" with the MX SMTP server or a missing feature? It's the lack of a rewrite rule. You need to add a rewrite rule of the form: DEFINE REWRITE_RULE - "<{host}!{user}@dmc.com>" "<{user}@{host}>" -------------------------------------------------------------------------------- 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, 02 Jun 1993 19:32:27 CDT Sender: list-mgr@WKUVX1.BITNET Subject: What is wrong with this from header? Message-ID: <5936@mitech.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 2 Jun 93 19:10:30 GMT To: MX-List@WKUVX1.BITNET Can somebody tell me what is wrong with this from header. X-Mx-Warning: Warning -- Invalid "From" header. From: George Carrette, Mitech Corporation To: gjc@world.std.com Subject: test X-Vms-Mail-To: UUCP%"gjc@world.std.com" Status: R ================================================================================ Archive-Date: Wed, 02 Jun 1993 19:41:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 02 Jun 1993 19:40:22 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D706.38B107E0.16954@WKUVX1.BITNET> Subject: RE: What is wrong with this from header? writes: > >Can somebody tell me what is wrong with this from header. > >X-Mx-Warning: Warning -- Invalid "From" header. >From: George Carrette, Mitech Corporation The "," is a special character that can only appear in a quoted string in this context, according to RFC822. Which makes sense, since the comma separates multiple addresses outside of a quoted string. >X-Vms-Mail-To: UUCP%"gjc@world.std.com" Looks like UUCP isn't doing the quoting like it's supposed to. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 03 Jun 1993 01:37:52 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: foo!user@dmc.com doesn't pass through SMTP... Date: Thu, 3 Jun 1993 05:40:39 GMT Message-ID: <1993Jun3.054039.11743@cerberus.bhpese.oz.au> To: MX-List@WKUVX1.BITNET munroe@dmc.com (Dick Munroe) writes: >The SMTP server for MX when faced with addresses of the form: >foo!user@dmc.com >where foo is a down stream site for DMC.COM, gives forth with a >no local user identification. >Other SMTP implementation don't have this problem. Is this a >"bug" with the MX SMTP server or a missing feature? Sounds like perfectly sensible behaviour to me. Instead of trying to propogate mangled addresses, get a domain name for foo, ie foo.x.y, have the mx record for foo.x.y point at dmc.com, and tell MX on dmc.com how to route to foo.x.y. This way, the address for foo!user is user@foo.x.y, which is lots less likely to cause confusion, and much more likely to work. Sm -- Scott Merrilees, BHP Information Technology, Newcastle, Australia Internet: Sm@bhpese.oz.au Phone: +61 49 40 2132 Fax: ... 2165 Disclaimer: In no way speaking for BHP Information Technology. ================================================================================ Archive-Date: Thu, 03 Jun 1993 03:50:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: 03 Jun 93 06:15:28+0000 From: Fabien Marathee Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9306030615.AA06747(a)eliot.cnes.fr> To: MX-List@WKUVX1.BITNET Subject: RE: MX Router Problem I have simplified my rewriting rules on CNESTA: the only one is now : "<{user}@cnesta.span.cnes.fr>" -> "<{user}@cnesta.cnes.fr>" still mx router exits with status = 1000000C. The problem is somewhere else ... CNESTD and CNESTA are NOT in a cluster and so they do not share VMSMAIL_PROFILE or SYSUAF. another idea ? Thank you Fabien. ================================================================================ Archive-Date: Thu, 03 Jun 1993 06:29:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 03 Jun 1993 06:28:55 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D760.D240E920.17028@WKUVX1.BITNET> Subject: RE: MX Router Problem Fabien Marathee writes: > >I have simplified my rewriting rules on CNESTA: > >the only one is now : > >"<{user}@cnesta.span.cnes.fr>" -> "<{user}@cnesta.cnes.fr>" > >still mx router exits with status = 1000000C. The problem is somewhere else ... > What TCP/IP are you using? If you mentioned it, I don't remember. Another site is reporting similar problems using Wollongong's Pathway. >CNESTD and CNESTA are NOT in a cluster and so they do not share VMSMAIL_PROFILE >or SYSUAF. > >another idea ? You might try using SMTP-over-DECnet instead of SMTP until the problem is actually found. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 03 Jun 1993 06:46:43 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 3 Jun 1993 06:40:35 +0000 From: Fabien Marathee Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9306031140.AA08892@eliot.cnes.fr> To: MX-List Subject: RE: MX Router Problem I am using Multinet 3.2 - VMS 5.5-2 - MX 3.3 on CNESTA where there is the MX router problem and Multinet 3.2 - VMS 5.4 - MX 3.3 on CNESTD where everything is working ok. Fabien. ================================================================================ Archive-Date: Thu, 03 Jun 1993 08:28:51 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: pathworks mail to mailing list problem Message-ID: Date: Thu, 3 Jun 1993 12:46:37 GMT To: MX-List@WKUVX1.BITNET I am having problems with mailing lists and pathworks mail users. I set up the test mailing list. Any VMS user has no problem communicating with MX%test-request and MX%test. When a pathworks mail user does the same thing, nothing happens. In fact, MX does not work at all for those users. Same thing if I try from another DECnet node to send something to mx_running_node::MX%"test", it works if I go through tcp/ip. What am I missing ? Can some kind knowledgeable person help me ? I was running UCX 2.0, and changed it to CMU/TEK 6.5, with no result (well it is better but for other reasons). I was running MX 3.1 and changed it to 3.3. I have another node running same config ( at least I can't see the difference ), and this works. Here is my config file ( the one that does not work ). Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;36 MX version id is: MX V3.3 VAX Mailing lists: Name: test Owner: "system@NCCR.CCR.HYDRO.QC.CA" Reply-to: List, NOSender Description: test test test test Errors-to: system@nccr.ccr.hydro.qc.ca Strip header: NOReceived Private list: No Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:R) Domain-to-path mappings: Domain="nccr.ccr.hydro.qc.ca", Path=Local Domain="nccr", Path=Local Domain="ncuvcr", Path=Local Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*", Path=SMTP Domain="", Path=Local Aliases: LocalName="Postmaster", Address="system@nccr.ccr.hydro.qc.ca" LocalName="POSTMAST", Address="system@nccr.ccr.hydro.qc.ca" SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Number of DNS failure retries: 12 Accounting: disabled Default router: (none) LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. Multiple VMS Mail From: addresses allowed. Top headers: FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID, RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT, ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM, RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER Bottom headers: (none) ROUTER agent settings: Automatic percent-hack handling: enabled JNET agent settings: Automatic percent-hack handling: enabled BSMTP replies: disabled Accounting: disabled Lenient about gatewaying mail: no No mailer username set. DECnet_SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. SITE agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 X25_SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. $ show log mx* (LNM$PROCESS_TABLE) (LNM$JOB_808EF0D0) (LNM$GROUP_000001) (LNM$SYSTEM_TABLE) "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "NCUVCR$DKB0:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DNSMTP_DIR" = "MX_ROOT:[DNSMTP]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "DKB0:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "NCUVCR" "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" = "nccr.ccr.hydro.qc.ca" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_UUCP_DIR" = "MX_ROOT:[UUCP]" "MX_VMSMAIL_LOCALHOST" = "@nccr.ccr.hydro.qc.ca" (DECW$LOGICAL_NAMES) Thank you for your help. Alain Martineau Hydro Quebec martineau@macmartineau.ccr.hydro.qc.ca ================================================================================ Archive-Date: Thu, 03 Jun 1993 08:36:51 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: foo!user@dmc.com doesn't pass through SMTP... Message-ID: <1993Jun3.085711.1726@dmc.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 3 Jun 93 08:57:11 EDT To: MX-List@WKUVX1.BITNET In article <1993Jun3.054039.11743@cerberus.bhpese.oz.au>, Sm@cerberus.bhpese.oz.au (Scott Merrilees) writes: > munroe@dmc.com (Dick Munroe) writes: > > Sounds like perfectly sensible behaviour to me. I couldn't agree more, but... > Instead of trying to propogate mangled addresses, get a domain name > for foo, ie foo.x.y, have the mx record for foo.x.y point at dmc.com, > and tell MX on dmc.com how to route to foo.x.y. The particular site has a domain name (foo.com) for which DMC.COM is the forwarder. Someone along the way rewrites the addresses in bang path notation and UUNET then gets them to me via SMTP by slamming @dmc.com onto the address, generating foo!user@dmc.com. > This way, the address for foo!user is user@foo.x.y, which is lots less > likely to cause confusion, and much more likely to work. Agreed, but it's out of my hands at this stage all I can do is provide the necessary rewriting. Which brings up why the forwarding wasn't happening. I botched the rewrite rules. All is well now. Dick Munroe -- Dick Munroe Internet: munroe@dmc.com Doyle, Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. 01749 USA FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Thu, 03 Jun 1993 08:53:03 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 03 Jun 1993 09:26:42 EDT From: "Brian Tillman, Smiths Industries, VAX Support, x8425" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D779.A8A504C0.4548@swdev.si.com> Subject: MIME request. I'd like to request that MX handle messages with the following MIME headers: Content-Type: TEXT/PLAIN Content-Transfer-Encoding: BASE64 I can envision another mailer sending a plain text file encoded BASE64. Right now, since MX recognizes only the Context-Type APPLICATION/VMS-RMS, a plain file received in BASE64 encoding will not be decoded. Likewise, if possible, I'd like MX to support TEXT/PLAIN on outbound non-binary files that are sent /FOREIGN. For example, page 1-6 of the User's Guide shows the example: $ mail/foreign/sub="My LOGIN.COM" login.com "mx%""user@node.edu""" To me, this is exactly the case that should be sent with Context-Type TEXT/PLAIN. Finally, is there any way to get a stand-alone BASE64 encode-decode program, in case someone does send a TEXT/PLAIN file that is BASE64-encoded? ================================================================================ Archive-Date: Thu, 03 Jun 1993 08:55:02 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 03 Jun 1993 09:03:17 EDT From: "Brian Tillman, Smiths Industries, VAX Support, x8425" Reply-To: MX-List@WKUVX1.BITNET To: WKUVX1.BITNET!MX-list@esseye.si.com Message-ID: <0096D776.6323C600.4518@swdev.si.com> Subject: Re: foo!user@dmc.com doesn't pass through SMTP... Carl Lydick writes: >It's the lack of a rewrite rule. You need to add a rewrite rule of the form: > >DEFINE REWRITE_RULE - > "<{host}!{user}@dmc.com>" "<{user}@{host}>" Hmm... I don't have any rewrite rule such as Carl recommends and all my mail from the Internet has exactly that form. For example, I'm sending this message to: MX%"uunet!WKUVX1.BITNET!MX-list@esseye.si.com" Perhaps the difference is that "esseye" is our UUCP-connected system, distinct from "swdev" which is the cluster from which I write this, whereas Dick's system _is_ "dmc.com", so SMTP has no smart host (default router to pass off unknown addresses to. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Thu, 03 Jun 1993 13:11:09 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: What is wrong with this from header? Message-ID: <1993Jun3.114642.3043@inland.com> Date: 3 Jun 93 11:46:42 CST To: MX-List@WKUVX1.BITNET In article <0096D706.38B107E0.16954@WKUVX1.BITNET>, Hunter Goatley writes: > writes: >> >>Can somebody tell me what is wrong with this from header. >> >>X-Mx-Warning: Warning -- Invalid "From" header. >>From: George Carrette, Mitech Corporation > > The "," is a special character that can only appear in a quoted > string in this context, according to RFC822. Which makes sense, since > the comma separates multiple addresses outside of a quoted string. > >>X-Vms-Mail-To: UUCP%"gjc@world.std.com" > > Looks like UUCP isn't doing the quoting like it's supposed to. > Not guilty. If the length of the personal name is non-zero, then the UUCP Mail Handler encloses the entire name in "". (It also scans the personal name and converts " to \".) It didn't always do this, I guess we need to ask the question: What version of UUCP. By the way, if the length of the personal name is zero, it emits From: mailbox@dom.ain (no <>'s) in accordance with Internet conventions. --- Tom Tom Allebrandi | Mail guru - DECUS UUCP Development Team Inland Steel Research Labs | NFS grunt - CMU/Tek-IP East Chicago, IN | Chairperson - VMSnet Working Group, DECUS VAX SIG 219 399 6306 | Internet: allebrandi@inland.com DECUServe: allebrandi | UUCP: ...!uunet!inland!allebrandi ================================================================================ Archive-Date: Thu, 03 Jun 1993 14:23:31 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: MX Router Problem Date: 3 Jun 1993 17:28:58 GMT Message-ID: <1ulccqINNh6u@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096D760.D240E920.17028@WKUVX1.BITNET>, Hunter Goatley writes: =>I have simplified my rewriting rules on CNESTA: => =>the only one is now : => =>"<{user}@cnesta.span.cnes.fr>" -> "<{user}@cnesta.cnes.fr>" => =>still mx router exits with status = 1000000C. The problem is somewhere else ... => =What TCP/IP are you using? If you mentioned it, I don't remember. =Another site is reporting similar problems using Wollongong's Pathway. = =>CNESTD and CNESTA are NOT in a cluster and so they do not share VMSMAIL_PROFILE =>or SYSUAF. => =>another idea ? = =You might try using SMTP-over-DECnet instead of SMTP until the problem =is actually found. Or it could be a problem with his queue file. He might want to consider deleting and recreating the queue file. -------------------------------------------------------------------------------- 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, 03 Jun 1993 14:23:47 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: foo!user@dmc.com doesn't pass through SMTP... Date: 3 Jun 1993 17:34:05 GMT Message-ID: <1ulcmdINNh6u@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096D776.6323C600.4518@swdev.si.com>, "Brian Tillman, Smiths Industries, VAX Support, x8425" writes: =>It's the lack of a rewrite rule. You need to add a rewrite rule of the form: => =>DEFINE REWRITE_RULE - => "<{host}!{user}@dmc.com>" "<{user}@{host}>" = =Hmm... I don't have any rewrite rule such as Carl recommends and all my mail =from the Internet has exactly that form. For example, I'm sending this message =to: = =MX%"uunet!WKUVX1.BITNET!MX-list@esseye.si.com" = =Perhaps the difference is that "esseye" is our UUCP-connected system, distinct =from "swdev" which is the cluster from which I write this, whereas Dick's system =_is_ "dmc.com", so SMTP has no smart host (default router to pass off unknown =addresses to. What mail software is esseye running? If it's MX then I'd be interested in hearing how it's configured to deal with the bang path addresses. If not, then it's irrelevent, as MX will treat "uunet!WKUVX1.BITNET!MX-list" as a username and simply pass that to essey.si.com, and it's up to esseye.si.com to figure out what it means. On Dick's system, MX is trying to treat it as a local username, and there is no such local user. -------------------------------------------------------------------------------- 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, 03 Jun 1993 15:17:55 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 03 Jun 1993 11:52:18 EDT From: fraser_h@qis.dofasco.ca Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Message-ID: <0096D78D.FFB7E200.28718@qis.dofasco.ca> Subject: Re: MX rewrite rules? I'd like a copy of it as well, if it's not too much trouble. ================================================================================ Archive-Date: Thu, 03 Jun 1993 16:39:46 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 03 Jun 1993 16:30:31 CDT From: dingbaum@hepnet.fnal.gov Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D7B4.DD68ADAE.415@HEPNET.HEP.NET> Subject: from address Hi, I am a new mx administrator and I am having some difficulty with some from addresses. I recently installed mx version 3.3, upgrading from version 2.2 (the dark ages). When I test a mailing list some of my return headers look pretty bad. I'm really not sure what is going on, I have read the manuals, but am still stumped. Here is what the from lines look like. From dingbaum@nic.hep.net Thu Jun 3 15:51:24 From "MX%"dingbaum%hep.net"%HEPNET.BITNET"@FNAL.FNAL.GOV Thu Jun 3 15:51:35 199 From "net%"dingbaum%hep.net""@fndcd.fnal.gov Thu Jun 3 15:52:29 (BTW these are three different messages, just the top lines) Here are some of the mlf and router parameters. MCP> review hepnet-test dingbaum@hep.net dingbaum%FNDCD.BITNET@HEPNET.FNAL.GOV "fnal::dingbaum"@HEPNET.FNAL.GOV MCP> show rewrite %MCP-W-NOMATCH, no record matched specified rule MCP> show path Domain-to-path mappings: Domain="hepnet.hep.net", Path=Local Domain="131.225.100.1", Path=Local Domain="hepnet.fnal.gov", Path=Local Domain="nic.hep.net", Path=Local Domain="hepnet", Path=Local Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="hepnet.BITNET", Path=Local Domain="*", Path=SMTP Domain="*.BITNET", Path=Jnet Actually Domain="*.BITNET", Path=Jnet is the last entry, but my editor won't let me go back up to put the jnet entry in before it ( I missed it with cutting and pasting line at a time.) I hope this is enough information. Thanks in advance Jeff Dingbaum dingbaum@hep.net dingbaum@hepnet.bitnet fnal::dingbaum ================================================================================ Archive-Date: Thu, 03 Jun 1993 18:40:29 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: foo!user@dmc.com doesn't pass through SMTP... Message-ID: <1993Jun3.185538.1727@dmc.com> Date: 3 Jun 93 18:55:38 EDT To: MX-List@WKUVX1.BITNET In article <0096D776.6323C600.4518@swdev.si.com>, "Brian Tillman, Smiths Industries, VAX Support, x8425" writes: > Perhaps the difference is that "esseye" is our UUCP-connected system, distinct > from "swdev" which is the cluster from which I write this, whereas Dick's system > _is_ "dmc.com", so SMTP has no smart host (default router to pass off unknown > addresses to. What was actually happening (I FINALLY managed to catch one of these suckers in my debugging logs) was pretty cool: 1. Address foo!user@dmc.com presented to SMTP and passed to the router. 2. Router didn't see any rewrite rules. 3. Router, correctly, selected the path DMC.COM which delivers the message to local user foo!user 4. Local delivery agent, correctly, barfs because foo!user really ISN'T a local user. 5. Rejection message gets flung back at the sender. You should have TWO sets of rewrite rules to handle the general case here: 1. rewrites foo!user@f.q.d.n user@foo 2. rewrites foo!bar!...!user@f.q.d.n to bar!...!user@foo This allows your downstream sites to do anything they want to in the way of nets without affecting your site any more. Don't assume that you can rewrite foo to foo.uucp since I have seen domain names in the bang paths. In any event, this seems to work just fine for me. Thanks again to Carl for the suggestion. -- Dick Munroe Internet: munroe@dmc.com Doyle, Munroe Consultants, 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: Fri, 04 Jun 1993 01:10:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 4 Jun 1993 01:06:20 +0000 From: Fabien Marathee Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9306040606.AA13243@eliot.cnes.fr> To: MX-List Subject: RE: MX Router Problem Context: MX_Router exiting (code 1000000c) when receiving a message from MX_Smtp_Server (after rewriting addr and just before passing the message to local agent). VAX VMS 5.5-2 / Multinet 3.2 / MX 3.3 > You might try using SMTP-over-DECnet instead of SMTP until the problem > is actually found. Well it's not possible for me to do that ... > Or it could be a problem with his queue file. He might want to consider > deleting and recreating the queue file. Do I have to try something with the queue file ? Is there any more information i can give to help solve the problem ? Thank you, Fabien Marathee (marathee@eliot.cnes.fr) ================================================================================ Archive-Date: Fri, 04 Jun 1993 11:05:34 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: including real name with listserv ADD command Message-ID: <1993Jun4.113825.83@ube.ub.umd.edu> Date: 4 Jun 93 11:38:25 -0500 To: MX-List@WKUVX1.BITNET I have setup a private mailing list in MX. I use the ADD command in a mail messge to listserv to add subscribers and that works fine, but I would like to also add the name of the subscriber for when users use the review command. Doing an "ADD listname user@host firstname lastname" does not work, in fact the subscriber is not even added, though no error message is returned. Is there a way to accomplish this? I'm using MX 3.1C, UCX 2.0b, vms 5.5-2. Perhaps MX 3.3 has this functionality, though I didn't see it in the release notes. Thanks, George =================================================================== George H. Weitzel BITNET: george@UBE Network Services Manager Internet: george@ube.ub.umd.edu Academic Computing Center Voice: (410) 234-3942 University of Baltimore FAX: (410) 539-3714 1420 North Charles Street Baltimore, Maryland, USA 21201 =================================================================== ================================================================================ Archive-Date: Fri, 04 Jun 1993 12:36:16 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 04 Jun 1993 12:35:21 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D85D.2DC45C80.17468@WKUVX1.BITNET> Subject: RE: including real name with listserv ADD command writes: > >I have setup a private mailing list in MX. I use the ADD command in a mail >messge to listserv to add subscribers and that works fine, but I would like >to also add the name of the subscriber for when users use the review >command. Doing an "ADD listname user@host firstname lastname" does not >work, in fact the subscriber is not even added, though no error message is >returned. > You can do it with: ADD listname "Personal name" Or send it to the -Request address as: ADD "Personal name" The quotes aren't strictly necessary, depending on the characters in the personal name. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 04 Jun 1993 15:54:38 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 04 Jun 1993 15:48:38 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: george@ube.ub.umd.edu Message-ID: <0096D878.2DE73280.6352@SHSU.edu> Subject: RE: including real name with listserv ADD command On 4 Jun 93 11:38:25 -0500, George H. Weitzel posted: > I have setup a private mailing list in MX. I use the ADD command in a mail > messge to listserv to add subscribers and that works fine, but I would like > to also add the name of the subscriber for when users use the review > command. Doing an "ADD listname user@host firstname lastname" does not > work, in fact the subscriber is not even added, though no error message is > returned. > > Is there a way to accomplish this? I'm using MX 3.1C, UCX 2.0b, vms 5.5-2. > Perhaps MX 3.3 has this functionality, though I didn't see it in the > release notes. This has been supported for some time (MX 3.0, Matt?). The easiest way to achieve this is to use the listname-Request address and include: ADD "Joe B. User" in your mail message to the -Request address. Two words of caution: First, you're always safe if you enclose the name string in quotes as it is cleaner in a true RFC 822 way. In the original code to support this, if a period, comma, or other RFC 822 reserved character which could be viewed as a token appeared in the personal name string, things got broke (which I think Matt quickly fixed in a pre-official release version, I think, but....). Second, when using a personal name string, enclose the address in angle brackets (as shown above) to clearly delineate the address from the personal name string. The addition of ADD to LISTSERV/MXServer is a relatively new development (3.2, Hunter?) and initially did not support personal names. While it very well may by now, the -Request address does and has and will serve this function quite nicely if you follow the two points above. Regards, George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Fri, 04 Jun 1993 17:56:26 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 04 Jun 1993 19:33:33 EDT From: "Andy, Systems Manager" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: udaa055@elm.cc.kcl.ac.uk Message-ID: <0096D897.99CB57A0.22944@elm.cc.kcl.ac.uk> Subject: How to specify uucp style addresses...? ok, here's a problem involving uucp style `bang' addressing... I'm running MX 3.3 on VMS 5.5-2 talking SMTP over Internet. I do NOT have UUCP on the host system but I do have access to a remote system that can relay stuff between our network and the uucp network. So, I have configured the following.... 1. DEFINE PATH "*!*" SMTP /ROUTE= If I now mail to MX%"site!user", it bombs out telling me that there is no such `local' username as "site!user" (it also changes all the dots to dollars!) So, thinking it needs a "@" to make it recognize the name as `non-local', I now add: 2. DEFINE REWRITE_RULE "<{site}!{user}>" "<{site}!{user}@relay-site>" and the same thing happens (it doesn't seem to go through the rewrite rule). The error message mailed back refers to the original string I specify: "site!user" I'ld be grateful for a clue as to where I'm getting it wrong... Thanks Andy Harper Kings College London ================================================================================ Archive-Date: Sat, 05 Jun 1993 20:40:17 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 05 Jun 1993 22:33:12 ADT From: Greg Bishop Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Message-ID: <0096D979.DCC274C0.21211@ac.nsac.ns.ca> Subject: RE: How to specify uucp style addresses...? > So, I have configured the following.... > 1. DEFINE PATH "*!*" SMTP /ROUTE= I use a DEFINE PATH "*.UUCP" SMTP /ROUTE="UUNET.UU.NET" as the last entry before the "*". MCP SHOW PATHS produces: Domain-to-path mappings: . . Domain="*.UUCP", Path=SMTP, Route="UUNET.UU.NET" Domain="*", Path=SMTP > If I now mail to MX%"site!user", it bombs out telling me that there is no such > `local' username as "site!user" (it also changes all the dots to dollars!) Users then send to addresses such as "esri!boris!noname!michael@uunet.UU.NET". > So, thinking it needs a "@" to make it recognize the name as `non-local', > I now add: > 2. DEFINE REWRITE_RULE "<{site}!{user}>" "<{site}!{user}@relay-site>" I don't have any rewrite rules. > and the same thing happens (it doesn't seem to go through the rewrite rule). > The error message mailed back refers to the original string I specify: > "site!user" > I'd be grateful for a clue as to where I'm getting it wrong... I'm just relaying what works for me. Hope this helps. Greg Greg Bishop Internet: GBISHOP@AC.NSAC.NS.CA System Manager Voice: (902) 893-6693 Nova Scotia Agricultural College Fax: (902) 895-4547 Truro, Nova Scotia CANADA B2N 5E3 ================================================================================ Archive-Date: Mon, 07 Jun 1993 07:32:55 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 07 Jun 1993 07:32:11 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096DA8E.52CBD660.17801@WKUVX1.BITNET> Subject: MX BOF is Wednesday at 11AM In case any MX-ers are reading this from DECUS, the MX BOF will be Wednesday at 11 AM in Room 156 at the World Congress Center. Hunter ================================================================================ Archive-Date: Mon, 07 Jun 1993 10:32:14 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 07 Jun 1993 13:52:45 MEZ ( +0200) From: Peter Kobe Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096DAC3.7CCA29A0.17841@pib1.physik.uni-bonn.de> Subject: SMTP Agent setup MCP allows to set_up the maximum DNS_RETRIES. in order to tell the user relativly quickly about domain server failures. There are some domain server failures which should trigger an ad hoc message Example: %MX-F-NOHOST, no such host It would be helpfull, if this could be implemented. Regards Peter ===================================================================== Peter Kobe Internet: Peter.Kobe@uni-bonn.de Physikalisches Institut HEPNET: 13562::SYSTEM Universitaet Bonn Tel: (49) 228 73 3222 D 53 Bonn FAX: (49) 228 73 7869 Nussallee 12 ================================================================================ Archive-Date: Mon, 07 Jun 1993 14:42:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 07 Jun 1993 12:35:37 EDT From: Virtual Bill Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Message-ID: <0096DAB8.B6742120.17629@gtewd> Subject: Re: MX rewrite rules? Is a third "me too" permissible? ================================================================================ Archive-Date: Mon, 07 Jun 1993 16:49:21 CDT Sender: list-mgr@WKUVX1.BITNET From: desroches@woods.ulowell.edu Reply-To: MX-List@WKUVX1.BITNET Subject: SIGNATURE missing when using MailWorks Message-ID: <1993Jun7.152840.1@woods.ulowell.edu> Date: Mon, 7 Jun 1993 20:28:40 GMT To: MX-List@WKUVX1.BITNET I have a problem getting the signature file sent along with the message when using DEC's MailWorks product (formerly All-In-1 Mail). We converted to MailWorks in March and since that time when we send something from MailWorks via MX the signature file does not get appended to the end of the message even though the mx_signature.txt file exists and the mx_signature and mx_auto_signature logicals have been defined. It doesn't even work if you add the /SIGNATURE statement to the end of the message. There is no problem when using regular VMSMail. Please note that we are using MAILWORKS (formerly All-In-1 Mail) - this is a SEPARATE product from All-In-1 - there is little, if any, relationship between the two. ================================================================================ Dick Desroches, Systems Manager | Phone : 508-934-2682 University of Massachusetts Lowell | Fax : 508-934-3001 Academic Computer Center | Email : DESROCHES@WOODS.ULOWELL.EDU Lowell, MA 01854 | ================================================================================ ================================================================================ Archive-Date: Mon, 07 Jun 1993 18:01:04 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: SIGNATURE missing when using MailWorks Message-ID: <1993Jun7.221757.5371@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Mon, 7 Jun 1993 22:17:57 GMT To: MX-List@WKUVX1.BITNET In article <1993Jun7.152840.1@woods.ulowell.edu>, desroches@woods.ulowell.edu writes: >I have a problem getting the signature file sent along with the message >when using DEC's MailWorks product (formerly All-In-1 Mail). > >We converted to MailWorks in March and since that time when we send >something from MailWorks via MX the signature file does not get appended to >the end of the message even though the mx_signature.txt file exists and >the mx_signature and mx_auto_signature logicals have been defined. It >doesn't even work if you add the /SIGNATURE statement to the end of the >message. > >There is no problem when using regular VMSMail. The signature file feature in MX applies only to the VMS MAIL interface; the code is located in MX_MAILSHR.EXE, which is only activated if you send via VMS MAIL. You'd have to look for a similar feature built into A1MAIL; I don't know if there is one, though. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Mon, 07 Jun 1993 20:00:33 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 08 Jun 1993 02:56:40 +0200 From: "Gerhard Raimann, Inst.f.Exp.phys.3, Uni Bochum, FRG" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: raimann@EP3.RUHR-UNI-BOCHUM.DE Message-ID: <0096DB30.FFBBA880.15109@EP3.RUHR-UNI-BOCHUM.DE> Subject: Re: MX rewrite rules? Seeeehr gut! Ich wollte morgen eine News genau zu diesem Thema schreiben !!! ================================================================================ Archive-Date: Mon, 07 Jun 1993 21:31:16 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 08 Jun 1993 04:25:07 +0200 From: "Gerhard Raimann, Inst.f.Exp.phys.3, Uni Bochum, FRG" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: raimann@EP3.RUHR-UNI-BOCHUM.DE Message-ID: <0096DB3D.5B691620.15113@EP3.RUHR-UNI-BOCHUM.DE> Subject: Re: MX rewrite rules? Sorry for my garbage reply; I replied to the wrong mail. It won't happen again. Gerry ================================================================================ Archive-Date: Tue, 08 Jun 1993 10:12:24 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 08 Jun 1993 16:26:39 MEZ ( +0200) From: Peter Kobe Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096DBA2.270014A0.18618@pib1.physik.uni-bonn.de> ===================================================================== Peter Kobe Internet: Peter.Kobe@uni-bonn.de Physikalisches Institut HEPNET: 13562::SYSTEM Universitaet Bonn Tel: (49) 228 73 3222 D 53 Bonn FAX: (49) 228 73 7869 Nussallee 12 ================================================================================ Archive-Date: Tue, 08 Jun 1993 13:55:10 CDT Sender: list-mgr@WKUVX1.BITNET Date: 08 Jun 1993 14:32:20 -0400 (EDT) From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET Subject: MLP and the FQDN To: MX-List@WKUVX1.BITNET CC: hardis@garnet.nist.gov Message-ID: <0096DB92.2F14D140.15621@garnet.nist.gov> Content-Transfer-Encoding: 7BIT I recently received mail from a Postmaster at another site, politely suggesting that I use my fully qualified domain name (FQDN) in mail messages. (I won't mention the site, other than that they make lots of computers that sport brightly colored, striped fruit.) A review of the logs finds that the FQDN is used in all messages, EXCEPT those automatically generated by the MLF processor (i.e., in reply to Subscribe, Review, and Unsubscribe commands). For these messages, during the SMTP transaction, the mailer initiates a transaction with MAIL FROM:. Unless I've done something really stupid, this strikes me as a bug in MX. - Jonathan Hardis ================================================================================ Archive-Date: Tue, 08 Jun 1993 19:08:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 8 Jun 93 18:10:11 EST From: Reply-To: MX-List@WKUVX1.BITNET Subject: Why is MX mute? To: MX-List@WKUVX1.BITNET Message-ID: <9306082110.AA09058@rnpdf2.cnpq.br> Our MX has stopped sending messages, although it is receiving OK, and "show que" shows messages as sent. Even messages sent to myself with MX are lost. There were no changes in the Vax configuration. Any suggestion as to where to look for a solution? Thanks in advance, LLazarte@cnpq.br ================================================================================ Archive-Date: Tue, 08 Jun 1993 21:16:29 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX SMTP dieing... Message-ID: <1993Jun8.062851.1739@dmc.com> Date: 8 Jun 93 06:28:51 EDT To: MX-List@WKUVX1.BITNET This is the second time this has happened to me, but I have more information this time. The MX SMTP server died with an error of: 20ec in the MX debugging long (I don't have the original error message as produced by SMTP, but this translates to: %SYSTEM-F-LINKDISCON, network partner disconnected logical link ) After this happens, when I attempt to connect to port 25 via telnet, I get connection refused. When I stop and restart MX (including the SMTP server and client), I get connection refused. When I stop mx, restart Multinet (3.2B) and restart MX, everything works fine. This looks like a Multinet problem of some kind, but has anybody seen this before? -- Dick Munroe Internet: munroe@dmc.com Doyle, Munroe Consultants, 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: Wed, 09 Jun 1993 01:01:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 9 Jun 93 02:52:08 EST From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Why is MX mute? To: MX-List@WKUVX1.BITNET Message-ID: <9306090552.AA09824@rnpdf2.cnpq.br> =>Our MX has stopped sending messages, although it is receiving OK, =>and "show que" shows messages as sent. Even messages sent to myself =>with MX are lost. The problem was *partially* due to NAMRES, CMU/Tek's Name resolver. After restarting it, *SOME* messages begun to be sent. Now, at least I see messages not being sent, using "show que", but, why do some get sent while others remain in the que? The error shown is: MX_SMTP-W-SERVICE_NOT_AVA, !AS service not avaliable. I have tried commenting out CMU/Tek's SMTP, thus using MX's SMTP, and the other way around, seing the same error in the queue. Any help welcome in advance, LLazarte@cnpq.br ================================================================================ Archive-Date: Wed, 09 Jun 1993 13:16:26 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 09 Jun 1993 19:01:33 EDT From: "Andy, Systems Manager" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: udaa055@elm.cc.kcl.ac.uk Message-ID: <0096DC80.F5BFA2E0.28013@elm.cc.kcl.ac.uk> Subject: UUCP style bang addresses problem solved... My thanks to Carl Lydick for pointing out how to get MX (3.3) to recognize an address of the form "site!user" and have it routed to an smtp/uucp mail relay. Here's the gen for anyone else who might need it. If you specify an address that does NOT contain an "@" sign, MX kindly appends a string of the form "@localsite" to transform an apparently local username into a network one. So my UUCP address of "site!user" was getting transformed to: site!user@localsite I had a rewrite rule of: define rewrite "<{site}!{user}>" "<{site}!{user}@relaysite>" which then transformed this address into: site!user@localsite@relaysite Clearly not what I want. The trick is to filter out the "@localsite" bit by using a rewrite rule like this: define rewrite "<{site}!{user}@localsite>" "<{site}!{user}@relaysite>" This may need some tweaking, depending on what the relay site expects to see in the header - but MX now does the right thing with it! Thanks carl.. Andy Harper Kings College London ================================================================================ Archive-Date: Thu, 10 Jun 1993 05:55:31 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Why is MX mute? Message-ID: <1993Jun10.053436.1745@dmc.com> Date: 10 Jun 93 05:34:36 EDT To: MX-List@WKUVX1.BITNET In article <9306090552.AA09824@rnpdf2.cnpq.br>, writes: > I have tried commenting out CMU/Tek's SMTP, thus using MX's SMTP, > and the other way around, seing the same error in the queue. You must comment out the supplied CMUIPs SMTP. If you don't, things will get VERY confused when the MX SMTP server and the CMUIP SMTP server start competing for connections. I've also seen things hung in the queue, but you might be able to get them going by using the QUEUE READY entry command. Dick Munroe -- Dick Munroe Internet: munroe@dmc.com Doyle, Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. 01749 USA FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Thu, 10 Jun 1993 13:43:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 10 Jun 1993 13:43:03 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096DD1D.A1445B00.18792@WKUVX1.BITNET> Subject: RE: MLP and the FQDN "Jonathan E. Hardis" writes: > >I recently received mail from a Postmaster at another site, politely >suggesting that I use my fully qualified domain name (FQDN) in mail >messages. (I won't mention the site, other than that they make lots of >computers that sport brightly colored, striped fruit.) > >A review of the logs finds that the FQDN is used in all messages, EXCEPT those >automatically generated by the MLF processor (i.e., in reply to Subscribe, >Review, and Unsubscribe commands). For these messages, during the SMTP >transaction, the mailer initiates a transaction with MAIL FROM:. > >Unless I've done something really stupid, this strikes me as a bug in MX. > How do you have MX_VMSMAIL_LOCALHOST defined? It sounds like it's not defined correctly. It should be equated to "@fqdn". Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 10 Jun 1993 13:52:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 10 Jun 1993 14:45:15 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: <0096DD26.51D04DA0.15853@garnet.nist.gov> Subject: RE: MLP and the FQDN > How do you have MX_VMSMAIL_LOCALHOST defined? It sounds like it's not > defined correctly. It should be equated to "@fqdn". It is. "MX_VMSMAIL_LOCALHOST" = "@garnet.nist.gov" And, for that matter, "MX_NODE_NAME" = "garnet.nist.gov" As I said, this only happens in messages generated by the MLF automated list processor. Could this be it: "MX_FLQ_NODE_NAME" = "GARNET" - Jonathan ================================================================================ Archive-Date: Thu, 10 Jun 1993 14:05:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 10 Jun 1993 14:04:48 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096DD20.AAF87520.18830@WKUVX1.BITNET> Subject: RE: MLP and the FQDN "Jonathan E. Hardis" writes: > >As I said, this only happens in messages generated by the MLF automated >list processor. Could this be it: > > "MX_FLQ_NODE_NAME" = "GARNET" > No, that's only used for lock communication among the MX processes. Looking at your original message again (it helps to read them right, doesn't it?), I'd guess that you have "HARDIS@GARNET" defined as a SYSTEM_USERS in MCP. When sending out replies to SUBSCRIBE, etc., MX will use the first SYSTEM_USERS address as the SMTP MAIL FROM: envelope address. If no SYSTEM_USERS are defined, it uses Postmaster@node. Unless I'm missing something else, it sounds like changing the SYSTEM_USERS to "hardis@garnet.nist.gov" will do the trick. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 10 Jun 1993 14:34:00 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 10 Jun 1993 15:23:20 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: <0096DD2B.A38F2D00.15865@garnet.nist.gov> Subject: RE: MLP and the FQDN > Unless I'm missing something else, it sounds like changing the > SYSTEM_USERS to "hardis@garnet.nist.gov" will do the trick. Yup. That's it. Thanks! (Note to others: if you have a DEFINE SYSTEM_USERS command in your configurations, please make sure the address is the FQDN.) ================================================================================ Archive-Date: Fri, 11 Jun 1993 09:46:36 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Every once in a while... Message-ID: <1993Jun10.145544.635@kenyon.edu> From: oursler@kenyon.edu Reply-To: MX-List@WKUVX1.BITNET Date: 10 Jun 93 14:55:44 -0500 To: MX-List@WKUVX1.BITNET Folks: I have an problem. I have been using MX for about a year and a half now. I think it's great. I've only had a couple of problems and I've bugged you all with them and they've always been resovled. Thanks. However, throughout all this time I have had one annoying mystery. Periodically, an agent process will disappear. Typically, it is the Router agent although I have seen other agents disappear. This only happens every once in a while. Two months might go by without a hitch and then it happens. It has happend a couple of times in a week and then not for a long time. Here's the bad part. I have no clues to offer you at all. I've enabled debugging to no avail. All I end up with is a log of the last successfully delivered message. There never seems to be any pattern. It just seems to go away. (By "go away", I mean that the agent process is no longer running. I restart it and things are ok.) I really, really like MX and I have even convinced some other sites to switch to it. They *don't* have problems. ;-) I know there's precious little hope of solving my personal little glitch, but I'd appreciate any ideas or suggestions anyone might have. Thanks, and I'm sorry for bringing up a problem with no additional information. It's just that some rather cranky users are pressuring me to switch to another product to solve the problem and I really don't want to do that. - Miles - ------------------------------- Miles Oursler Manager of Networks and Systems Kenyon College oursler@kenyon.edu ------------------------------- ================================================================================ Archive-Date: Fri, 11 Jun 1993 10:38:55 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 11 Jun 1993 10:13:52 +0000 From: Fabien Marathee Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9306111513.AA07886@eliot.cnes.fr> To: MX-List Subject: Re: Every once in a while... Well, my MX Router also exits quite often when delivering messages to SMTP agent (it processes an average of 200 per day coming from everywhere). It exists (1000000c) systematicaly when receiving incoming messages from SMTP Server (on a MicroVax 3600/VMS 5.5-2/MX 3.3). It's running fine on a MicroVax II/VMS 5.4/MX 3.3, the one I use for incoming messages until the problems is solved. Could this be caused by some abnormal messages, VMS 5.5-2, some system specific parameter ? ... read my "MX Router problem" message to the list ... Thanks for any help ! Fabien. ================================================================================ Archive-Date: Fri, 11 Jun 1993 11:18:58 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 11 Jun 1993 12:09:52 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: oursler@kenyon.edu Message-ID: <0096DDD9.C750C740.23935@nscvax.princeton.edu> Subject: RE: Every once in a while... oursler%kenyon.edu@ULKYVM.LOUISVILLE.EDU writes: > I have an problem. > > I have been using MX for about a year and a half now. I think > it's great. I've only had a couple of problems and I've bugged > you all with them and they've always been resovled. Thanks. > > However, throughout all this time I have had one annoying > mystery. Periodically, an agent process will disappear. > Typically, it is the Router agent although I have seen > other agents disappear. This only happens every once in > a while. Two months might go by without a hitch and then > it happens. It has happend a couple of times in a week > and then not for a long time. > > Here's the bad part. I have no clues to offer you at all. > I've enabled debugging to no avail. All I end up with > is a log of the last successfully delivered message. There > never seems to be any pattern. It just seems to go away. > (By "go away", I mean that the agent process is no longer > running. I restart it and things are ok.) > > I really, really like MX and I have even convinced some > other sites to switch to it. They *don't* have problems. ;-) > > I know there's precious little hope of solving my personal > little glitch, but I'd appreciate any ideas or suggestions > anyone might have. > > Thanks, and I'm sorry for bringing up a problem with no > additional information. It's just that some rather cranky > users are pressuring me to switch to another product to > solve the problem and I really don't want to do that. > Miles, Check your accounting file. That should show a termination status for the process. ************************************************************************* * * * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Fri, 11 Jun 1993 11:42:29 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 11 Jun 1993 11:42:09 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096DDD5.E81BB1A0.19040@WKUVX1.BITNET> Subject: RE: Every once in a while... oursler@kenyon.edu writes: > > I know there's precious little hope of solving my personal > little glitch, but I'd appreciate any ideas or suggestions > anyone might have. > Do you have the final exit status from accounting? I'd guess that it's probably generating an access violation (just because that's usually what kills it), though I don't have any idea why. Also, the MX_ROUTER_node.LOG should have the final exit status in it. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 11 Jun 1993 11:56:40 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 11 Jun 1993 11:33:35 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Message-ID: <0096DDD4.B5BA7760.30886@SHSU.edu> Subject: RE: Every once in a while... On 10 Jun 93 14:55:44 -0500, Miles Oursler reported his problems (which I haven't an answer for -- sorry). His note ended with something which concerns me, though. > I really, really like MX and I have even convinced some other sites to > switch to it. They *don't* have problems. ;-) >...... > Thanks, and I'm sorry for bringing up a problem with no additional > information. It's just that some rather cranky users are pressuring me to > switch to another product to solve the problem and I really don't want to > do that. We also have occasional software problems, although rarely with MX -- just as often as not, it's some proprietary software (in other words, software -- especially software which is layered upon other software -- sometime fails for seemingly mysterious reasons -- whatta surprise!). The other sites aren't having problems -- most sites represented on MX-List aren't having problems (but when they do, the problems are usually quickly and satisfactorily resolved). So....... Here's a question I propose that you ask your "cranky users" (I'd more likely call them anal orifices, but that's another issue altogether): Given the known performance of MX (which, by most standards, is excellent) and the mystery seemingly shrouding your problems, what leads them to believe that switching to another product will "solve" anything besides probably eating up some of your time and budget? Regards, George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Fri, 11 Jun 1993 12:30:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 11 Jun 1993 13:23:14 EDT From: "Edward J. Groth" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: GROTH@PUPGG.PRINCETON.EDU Message-ID: <0096DDE4.07308260.12737@PUPGG.PRINCETON.EDU> Subject: RE: Every once in a while... Miles - > Folks: > > I have an problem. > > I have been using MX for about a year and a half now. I think > it's great. I've only had a couple of problems and I've bugged > you all with them and they've always been resovled. Thanks. > > However, throughout all this time I have had one annoying > mystery. Periodically, an agent process will disappear. > Typically, it is the Router agent although I have seen > other agents disappear. This only happens every once in > a while. Two months might go by without a hitch and then > it happens. It has happend a couple of times in a week > and then not for a long time. > > Here's the bad part. I have no clues to offer you at all. > I've enabled debugging to no avail. All I end up with > is a log of the last successfully delivered message. There > never seems to be any pattern. It just seems to go away. > (By "go away", I mean that the agent process is no longer > running. I restart it and things are ok.) > > I really, really like MX and I have even convinced some > other sites to switch to it. They *don't* have problems. ;-) > > I know there's precious little hope of solving my personal > little glitch, but I'd appreciate any ideas or suggestions > anyone might have. > > Thanks, and I'm sorry for bringing up a problem with no > additional information. It's just that some rather cranky > users are pressuring me to switch to another product to > solve the problem and I really don't want to do that. > > - Miles - > > > > ------------------------------- > Miles Oursler > Manager of Networks and Systems > Kenyon College > oursler@kenyon.edu > ------------------------------- Happens to me too - once in a while an MX process dies. Since no harm seems to be done (except for messages not being delivered), I wrote a little procedure that periodically checks to be sure that all mx process are running. If one is missing it just restarts it. I've appended the procedure below. You may have to edit it for your site (also I think I'm 1 or 2 versions behind the latest MX, so that's another reason you may need to edit it!) - Ed /----------------------------------------------------------------------\ | Edward J. Groth | Phone: 609-258-4361 | | Physics Dept., Jadwin Hall | Fax: 609-258-6853 <- Changed 1-Feb-93 | | Princeton University | SPAN/HEPNET: PUPGG::GROTH=44117::GROTH | | Princeton, NJ 08544 | Internet: groth@pupgg.princeton.edu | \----------------------------------------------------------------------/ $ set noverify $! This procedure is to be run as a detached process under the $! system account (an input for loginout.exe). It periodically $! checks for the existence of the MX processes. If one is $! found to be missing, it is restarted and messages are written $! to the log file. $! $! If run with the p1 = start, then a detached process is started $! to run this procedure. $! $! If the system logical name MX_MONITOR_STOP is defined, then $! this procedure stops after its next iteration. $! $! $! Number of MX processes $ nmxproc=5 $! $! names of processes (each name preceded by an index which is $! it's position in the next list (will work for 9 processes!)) $ pnames="1MX Router2MX Local3MX MLF4MX SMTP5SMTP Server" $! $! corresponding names of processes for MX_EXE:MX_START $ snames="/ROUTER/LOCAL/MLF/SMTP/SMTP_SERVER" $! $! $! $! Check for start $ if p1 .nes. "START" then goto MAIN $! $! Here we fire it up $ run sys$system:loginout/noauthorize/uic=[1,4]/process="MX Monitor"- /input=sys$manager:mx_monitor.com/output=sys$common:[sysmgr]mx_monitor.log $! $! and quit $ exit $! $MAIN: $! $! Purge old versions of monitor log file $ if f$search("sys$common:[sysmgr]mx_monitor.log") .nes. "" then - purge/keep=3 sys$common:[sysmgr]mx_monitor.log $! $! $! Start a loop where we check on all processes $LOOP: $! $! Say we don't have any processes $ pcnt=1 $PILOOP: $ have'pcnt'=0 $ pcnt=pcnt+1 $ if pcnt .le. nmxproc then goto PILOOP $! $! establish context symbol $ context="" $! $! Look at all processes on the system $FINDPROC: $! $ pid=f$pid(context) $ if pid .eqs. "" then goto DONEFINDPROC $ testname=f$getjpi(pid,"PRCNAM") $ testname=f$edit(testname,"TRIM") $ pos=f$locate(testname,pnames) $ if pos .eq. f$length(pnames) then goto FINDPROC $ pos = pos - 1 $ pos=f$integer(f$extract(pos,1,pnames)) $ have'pos'=1 $ goto FINDPROC $! $DONEFINDPROC: $! $! Now see which processes are running $ pcnt=1 $ notrunning=0 $PRLOOP: $! $ name=f$element(pcnt,"/",snames) $ if have'pcnt' .eq. 1 then goto DONEPRLOOP $! $! Here process is not running $ write sys$output f$time()," Process ",name," is not running, restarted." $ @mx_exe:mx_start 'name' $ notrunning=1 $! $DONEPRLOOP: $! $ pcnt=pcnt+1 $ if pcnt .le. nmxproc then goto PRLOOP $! $! If all processes running, put out a comforting message $ if notrunning .eq. 0 then - write sys$output f$time()," All MX processes are running." $! $! Wait a bit and do it again $KEEPGOING: $ wait 00:30:00 $! $! See if we should quit $ if f$trnlnm("MX_MONITOR_STOP") .eqs. "" then goto LOOP $ deassign/system mx_monitor_stop $ write sys$output f$time()," Received stop signal, exiting." $ exit ================================================================================ Archive-Date: Fri, 11 Jun 1993 18:17:15 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Every once in a while... Message-ID: <1993Jun11.134928.139@scfb.chinalake.navy.mil> From: Reply-To: MX-List@WKUVX1.BITNET Date: 11 Jun 93 13:49:28 PST To: MX-List@WKUVX1.BITNET In article <1993Jun10.145544.635@kenyon.edu>, oursler@kenyon.edu writes: > However, throughout all this time I have had one annoying > mystery. Periodically, an agent process will disappear. > Typically, it is the Router agent although I have seen > other agents disappear. This only happens every once in [rest deleted] MX has been running at this site like a champ for some time now. Then this message gets posted. The very same morning, our Router agent dies with status 1000000C (access violation). Thanks a lot. You could have at least posted something like "dave wins the lotto!" ;-) dave ----- David S. Goppelt Internet: goppelt@scfe.chinalake.navy.mil ================================================================================ Archive-Date: Fri, 11 Jun 1993 20:51:19 CDT Sender: list-mgr@WKUVX1.BITNET From: John Caruso Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Every once in a while... To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Date: Fri, 11 Jun 93 18:19:47 EDT > > Periodically, an agent process will disappear. > > Typically, it is the Router agent although I have seen > > other agents disappear. This only happens every once in > > a while. > > Happens to me too - once in a while an MX process dies. Happens to us too, and it's always the Router. It happens very regularly-- every 15 days, almost on the nose. I don't have any additional light to shed either, unfortunately...our logfile just shows a normal termination of the router process. Maybe it just feels it's done enough and decides to take a nap. We're running MX V3.1B. ------------------------------------------------------------------------ John Caruso caruso@socrates.umd.edu Unix/VMS System Administrator caruso@UMUC (Bitnet) University of Maryland University College Work: (301) 985-7447 ------------------------------------------------------------------------ ================================================================================ Archive-Date: Fri, 11 Jun 1993 21:15:43 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Every once in a while... Message-ID: <1993Jun11.174208.692@kenyon.edu> From: oursler@kenyon.edu Reply-To: MX-List@WKUVX1.BITNET Date: 11 Jun 93 17:42:08 -0500 To: MX-List@WKUVX1.BITNET In article <1993Jun10.145544.635@kenyon.edu>, oursler@kenyon.edu writes: > Folks: > [...] > However, throughout all this time I have had one annoying > mystery. Periodically, an agent process will disappear. > [...] > Here's the bad part. I have no clues to offer you at all. > I've enabled debugging to no avail. All I end up with > is a log of the last successfully delivered message. Folks: Well, since I apparently need a house to fall on me I want to publicly thank Richard Gilbert for directing me to check the accounting file. I must have been in a fog. Anyway, the termination staus on the Router process when last it died was as follows MX_ROUTER Image Termination --------------------------- Username: MXSYSTEM UIC: [MXSYSTEM] Account: SYSTEM Finish time: 8-JUN-1993 19:36:04.65 Process ID: 2200022C Start time: 27-MAY-1993 12:41:45.27 Owner ID: Elapsed time: 12 06:54:19.38 Terminal name: Processor time: 0 02:26:54.89 Remote node addr: Priority: 2 Remote node name: Privilege <31-00>: 50598025 Remote ID: Privilege <63-32>: 00000000 Queue entry: Final status code: 1024806C Queue name: Job name: Final status text: %STR-F-INSVIRMEM, insufficient virtual memory Page faults: 17415 Direct IO: 6656665 Page fault reads: 505 Buffered IO: 309756 Peak working set: 3000 Volumes mounted: 0 Peak page file: 15000 Images executed: 0 Image name: $1$DIA1:[MXSYSTEM.][EXE]MX_ROUTER.EXE;5 According to the system message manual, the cause is as follows: INSVIRMEM insufficient virtual memory Facility: STR, String Manipulation Facility Explanation: An attempt is made to allocate heap storage for use as dynamic strings, or string temporaries failed. User Action: If you allocate space by calling STR$GET1_DX or LIB$GET_VM, verify, when you finish using the storage, that the storage is released by calling STR$FREE1_DX or LIB$FREE_VM, respectively. If you are using a high-level language and have not directly allocated space, you can cause this error by having a large number of long strings. In this case, make sure to reduce strings to zero length when they are not in use. So... is this just a memory leak? If that were the case, I'd expect more folks to have trouble. Thanks... - Miles - ------------------------------- Miles Oursler Manager of Networks and Systems Kenyon College oursler@kenyon.edu ------------------------------- ================================================================================ Archive-Date: Mon, 14 Jun 1993 13:06:51 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX V3.1 sometimes won't deliver mail Message-ID: <2044@igd.fhg.de> Date: 14 Jun 93 15:31:59 GMT To: MX-List@WKUVX1.BITNET Hello out there, I'm using MX3.1 (I'll upgrade soon) with UCX 1.3 and VMS5.4 (those won't be upgraded). Now I send via batch a larger amount of mails via MX to a specific user foo@igd.fhg.de (which is local in my net). The problem now is that some of the mails won't be delivered with the error-message "igd.fhg.de - no such host". The address of the receiver is identical to the ones of the delivered mail. The ucx-database is identical and the mx-config is so too. So why are some of the mailes undeliverable ? Any help out there ? Mathias Gaertner Fraunhofergesellschaft for Graphics Research Graphics Computer Center Darmstadt, Germany E-Mail: mgaertne@igd.fhg.de ================================================================================ Archive-Date: Mon, 14 Jun 1993 21:22:50 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 15 Jun 1993 12:13:48 +1000 From: bellamy@commerce.uq.edu.au Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096E0FE.FD836480.12733@covax.commerce.uq.oz.au> Subject: Re: Every once in a while... Relay-Version: VMS News - V6.1B7 26/02/93 VAX/VMS; site covax.commerce.uq.oz.au Path: test1.commerce.uq.oz.au!user Newsgroups: comp.mail.mx Subject: Re: Every once in a while... Message-ID: From: bellamy@commerce.uq.edu.au (David Bellamy) Date: 15 Jun 93 12:13:44 +1000 Followup-To: comp.mail.mx References: <1993Jun11.174208.692@kenyon.edu> Distribution: world,local Organization: The University of Queensland Nntp-Posting-Host: test1.commerce.uq.oz.au Lines: 35 In article <1993Jun11.174208.692@kenyon.edu>, oursler%kenyon.edu@ULKYVM.LOUISVILLE.EDU wrote: > Folks: > > Well, since I apparently need a house to fall on me I want > to publicly thank Richard Gilbert for directing me to > check the accounting file. I must have been in a fog. > > Anyway, the termination staus on the Router process > when last it died was as follows > > [accounting information deleted] > Final status text: %STR-F-INSVIRMEM, insufficient virtual memory First off, we do not seem to have this problem and we do process several 100 messages per day - this may be a function of the generous vm quota the processes get. To the problem and not wanting to jump to conclusions but.... As anyone who uses Indiana's excellent IUPOP3 will know that there IS a memory leak bug in DEC's callable mail interface which will eventually cause IUPOP3 to crash with "%STR-F-INSVIRMEM, insufficient virtual memory". Now I don't want to be accused of DEC bashing, but does the router process use the callable mail interface? BTW, DEC say that the memory leak bug in callable mail will be fixed in VMS 6.1J:-( _________________________________________________________________ David Bellamy. Deparment of Commerce. The University of Queensland. Australia. Internet: bellamy@commerce.uq.edu.au ================================================================================ Archive-Date: Tue, 15 Jun 1993 06:59:54 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 15 Jun 1993 06:59:41 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E0D3.1B81A180.19816@WKUVX1.BITNET> Subject: Re: Every once in a while... bellamy@commerce.uq.edu.au writes: > >To the problem and not wanting to jump to conclusions but.... As anyone >who uses Indiana's excellent IUPOP3 will know that there IS a memory leak >bug in DEC's callable mail interface which will eventually cause IUPOP3 to >crash with "%STR-F-INSVIRMEM, insufficient virtual memory". Now I don't >want to be accused of DEC bashing, but does the router process use the >callable mail interface? > The MX Router doesn't, but MX Local does. The callable mail memory leak can cause MX Local to eventually die too. This was documented in the MX V3.3 release notes. >BTW, DEC say that the memory leak bug in callable mail will be fixed in VMS >6.1J:-( > It's only been there since VMS V5.0---now that's speedy.... To try to avoid some of these problems, you might all want to consider stopping and restarting MX daily. I do it because it's recommended for Jnet---when I bring Jnet down, I restart MX to reclaim the queue file and restart the processes. My .COM file is included below---there are others that have been posted to the list. 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 $ wait_loop: $ wait 00:00:15 $! $! Make sure we can open the queue file. If not, some MX process $! hasn't finished processing and shut down yet. $! $ open/read/error=wait_loop tmp mx_flq_dir:system_queue.flq_ctl $ close tmp $! $! The processes are gone, so convert the queue file to make it as $! small as possible again. $! $ 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 $! $! Now restart MX $! $ say "" $ say "Restarting MX" $ submit/user=mxmailer sys$startup:mx_startup.com $ wait 00:00:30 $ exit ================================================================================ Archive-Date: Tue, 15 Jun 1993 07:57:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 15 Jun 1993 15:49:46 EDT From: Esra ESEN Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E11D.297A9900.9874@trboun.bitnet> Subject: VMS-Ultrix mail routing... Hi, We have VMS and Ultrix machines. VMS is connected to BITNET by using Jnet V3.5 and MX V3.0. Ultrix is connected to Internet. We want to combine these two facilities. That is mails coming from BITNET will be routed to Ultrix host. And mails coming from Internet will be routed to VMS host. What is necessary for this configuration. Thanks in advance... ======================================================================== Esra ESEN System Manager Bogazici Universitesi ESEN@TRBOUN.BITNET Bilgisayar Merkezi Telf.:263 15 40 / Ext.:1246 80815 Bebek/Istanbul ========================================================================= ================================================================================ Archive-Date: Tue, 15 Jun 1993 08:50:23 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 15 Jun 1993 15:38:11 EDT From: Herve CHOPLIN - UNIVERSITE FRANCOIS RABELAIS - TOURS Reply-To: MX-List@WKUVX1.BITNET To: mx-list%wkuvx1.bitnet@frmop11.cnusc.fr Message-ID: <0096E11B.8AF866A0.28082@UNIV-TOURS.FR> HELP ================================================================================ Archive-Date: Tue, 15 Jun 1993 11:07:36 CDT Sender: list-mgr@WKUVX1.BITNET To: mgaertne@igd.fhg.de From: "Pasztor Miklos" Reply-To: MX-List@WKUVX1.BITNET Date: 15 Jun 93 15:45:42 GMT+1 Subject: Re: MX V3.1 sometimes won't deliver mail CC: mx-list@WKUVX1.BITNET Message-ID: <2771C5B4E3B@aszi.sztaki.hu> > Hello out there, > I'm using MX3.1 (I'll upgrade soon) with UCX 1.3 and VMS5.4 (those won't be > upgraded). Now I send via batch a larger amount of mails via MX to > a specific user foo@igd.fhg.de (which is local in my net). > > The problem now is that some of the mails won't be delivered with the > error-message "igd.fhg.de - no such host". The address of the receiver > is identical to the ones of the delivered mail. The ucx-database is > identical and the mx-config is so too. > So why are some of the mailes undeliverable ? > Any help out there ? > Mathias Gaertner > Fraunhofergesellschaft for Graphics Research > Graphics Computer Center > Darmstadt, Germany > E-Mail: mgaertne@igd.fhg.de Mathias, I suspect that the domain name system (the UCX resolver, your DNS, or DNS configuration) is guilty. Try the following: DEF PATH igd.fhg.de smtp /route=192.44.32.1 Note that 192.44.32.1 is the address of igd.igd.fhg.de, one of the addresses where the MX record for igd.fhg.de points to. I'm pretty sure, that your mail will get through with no problem. I checked with your DNS and I see, that there are 5 MX records for igd.fhg.de. IMHO that's a bit too much. mail-gw.fhg.de is there two times. Once with preference value 101, and once with preference value 200. I really can not imagine any reason for this. I do not know how, but this may cause the trouble. It's possible that MX gets confused with this too MX records pointing to the very same place with different preferences. Best regards, Miklos ==================================================================== 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, 15 Jun 1993 14:07:08 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: VMS-Ultrix mail routing... Date: 15 Jun 1993 18:38:52 GMT Message-ID: <1vl4vsINNkpe@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096E11D.297A9900.9874@trboun.bitnet>, Esra ESEN writes: =We have VMS and Ultrix machines. VMS is connected to BITNET =by using Jnet V3.5 and MX V3.0. Ultrix is connected to Internet. =We want to combine these two facilities. That is mails coming from =BITNET will be routed to Ultrix host. And mails coming from Internet =will be routed to VMS host. What is necessary for this configuration. =Thanks in advance... Well, first of all you probably want to have at least one protocol that both the Ultrix machine and the VMS machine speak. The two likely candidates are DECnet and TCP/IP. Once you've chosen which protocol you're going to use to let the two machines talk to each other, and provide more specifics about what you're trying to do, you can expect more detailed answers. -------------------------------------------------------------------------------- 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: Tue, 15 Jun 1993 14:43:23 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 15 Jun 1993 20:28:47 EDT From: "Andy, Systems Manager" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: udaa055@elm.cc.kcl.ac.uk Message-ID: <0096E144.23AC0460.31637@elm.cc.kcl.ac.uk> Subject: MX Router hang I'm running MX 3.3 over CMU 6.6-5A on VMS 5.5-2. My veresion of CMU IP is, for as yet unknown reasons, a little unstable and is crashing. Following recovery, some parts of MX do not recover properly. Today for instance, the MX router got itself into an RWAST state waiting for I/O to complete on a now non existent IP device (the I/O would never complete). It also seemed to lock the MX queue completely so that none of our other nodes could access MX! Now, I know this is the old `how do you free a stuck RWAST process' problem but it seems to me that it ought to be possible to write processes, like the MX router, carefull which accept that the IP transport may `go away' underfoot and recover themselves by means of timeouts or somesuch. Can this be done? If so, please add it to the enhancement list for the next release. If not, could someone please explain why? I've taken a great deal of time and trouble trying to make our MX/CMU combination as stable as I can and it's really frustrating when this sort of thing happens. By the way, I could only clear today's hang via a reboot - not nice on a production system. Any thoughts on the matter would be appreciated. Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Tue, 15 Jun 1993 18:12:45 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX not accepting local user address Date: 15 Jun 1993 18:06:40 -0400 Message-ID: <1vlh5gINN7rv@umbc7.umbc.edu> To: MX-List@WKUVX1.BITNET Dear MX'ers, I have MX V3.3 installed on a UCX V2.0b system. This system does not currently have a A record in the DNS system (though it does have a PTR record). The system name is dbug.towson.edu and its IP address is 131.118.1.14. When I try to send an email from my home system to this system, my system sends only the local part of the address (I am discussing this with my system's email administrator to see if it can be changed). MX chokes on this and the message is returned. Example, Trying 131.118.1.14... Connected to 131.118.1.14. Escape character is '^]'. 220 dbug.decus.org MX V3.3 VAX SMTP server ready at Tue, 15 Jun 1993 17:48:37 EDT helo horton.acs.umbc.edu 250 Hello, horton.acs.umbc.edu mail from: 250 MAIL command accepted. rcpt to: 501 Syntax error in address quit 221 dbug.decus.org Service closing transmission channel Connection closed by foreign host. Legal or not, other systems, including unix and other VMS email packages accept such an address. Example: Trying 131.118.70.2... Connected to toe.towson.edu. Escape character is '^]'. 220 toe02.towson.edu -- Server SMTP helo horton.acs.umbc.edu 250 toe02.towson.edu OK. mail from: 250 Address Ok. rcpt to: 250 e7opdan OK. data 354 Enter mail, end with a single ".". this is a test . 250 Ok. quit 221 Bye received. Goodbye. Connection closed by foreign host. The system in question (dbug) is a system run by the local DECUS LUG (read: volunteers). I am sure the information is in the manager's doc somewhere but I am hoping that someone on this list might have a hint on what I can do to fix this (short of "get everybody else to fix their machine"). I have only recently installed and started working with MX on this machine and any help would be appreciated. Dan Daniel A. Dinkin Internet: dinkin@dbug.decus.org Vice-Chair & DBUG Network Manager dan@umbc.edu DECUS Baltimore Users Group BITNET: dan@umbc2 Snail Mail: Academic Computing voice: (410)455-3631 U of MD Baltimore County fax: (410)455-1065 Baltimore, Maryland 21228 Any thoughts in this message are purely random and neither DBUG nor my employer had anything to do with them... especially if I was right. ================================================================================ Archive-Date: Tue, 15 Jun 1993 19:55:02 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 15 Jun 1993 19:54:45 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E13F.6291A5E0.20133@WKUVX1.BITNET> Subject: RE: MX not accepting local user address writes: > >Dear MX'ers, > Aside to Dan: I tried replying to your registration a while back, but it bounced back to me and I had no alternative address to try.... >I have MX V3.3 installed on a UCX V2.0b system. This system does not currently >have a A record in the DNS system (though it does have a PTR record). The >system name is dbug.towson.edu and its IP address is 131.118.1.14. When I try >to send an email from my home system to this system, my system sends only >the local part of the address (I am discussing this with my system's email >administrator to see if it can be changed). MX chokes on this and the message >is returned. Example, [...] >Legal or not, other systems, including unix and other VMS email packages >accept such an address. Example: [...] >The system in question (dbug) is a system run by the local DECUS LUG (read: >volunteers). I am sure the information is in the manager's doc somewhere but >I am hoping that someone on this list might have a hint on what I can do to >fix this (short of "get everybody else to fix their machine"). I have only >recently installed and started working with MX on this machine and any help >would be appreciated. > You won't like my answer then. MX is very picky about RFC821 addresses. And you're right: without the node name, the address is not a valid address, so MX rejects it. I can try to address this in MX V3.4, but that won't be anytime soon. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 16 Jun 1993 02:17:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 16 Jun 1993 09:15:19 -0100 From: DIANA GRILL Reply-To: MX-List@WKUVX1.BITNET To: mx-list@RPIECSVX.BITNET CC: grill@bkfug.kfunigraz.ac.at Message-ID: <0096E1AF.38CA3220.1456@bkfug.kfunigraz.ac.at> Subject: help help ================================================================================ Archive-Date: Wed, 16 Jun 1993 04:22:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 16 Jun 1993 12:25:11 EDT From: Esra ESEN Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E1C9.BF1CA500.13437@trboun.bitnet> Subject: Re: VMS-Ultrix mail routing... >In article <0096E11D.297A9900.9874@trboun.bitnet>, Esra ESEN > writes: >=We have VMS and Ultrix machines. VMS is connected to BITNET >=by using Jnet V3.5 and MX V3.0. Ultrix is connected to Internet. >=We want to combine these two facilities. That is mails coming from >=BITNET will be routed to Ultrix host. And mails coming from Internet >=will be routed to VMS host. What is necessary for this configuration. >=Thanks in advance... >Well, first of all you probably want to have at least one protocol that both >the Ultrix machine and the VMS machine speak. The two likely candidates are >DECnet and TCP/IP. Once you've chosen which protocol you're going to use to We have DECnet and TCP/IP on our machines. They are talking DECnet. There is TCP/IP on Ultrix machine. >let the two machines talk to each other, and provide more specifics about what >you're trying to do, you can expect more detailed answers. -------------------------------------------------------------------------------- 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. ======================================================================== Esra ESEN System Manager Bogazici Universitesi ESEN@TRBOUN.BITNET Bilgisayar Merkezi Telf.:263 15 40 / Ext.:1246 80815 Bebek/Istanbul ========================================================================= ================================================================================ Archive-Date: Wed, 16 Jun 1993 06:41:06 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: VMS-Ultrix mail routing... Date: 16 Jun 1993 10:25:03 GMT Message-ID: <1vmsdvINNctj@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096E1C9.BF1CA500.13437@trboun.bitnet>, Esra ESEN writes: =>In article <0096E11D.297A9900.9874@trboun.bitnet>, Esra ESEN => writes: =>=We have VMS and Ultrix machines. VMS is connected to BITNET =>=by using Jnet V3.5 and MX V3.0. Ultrix is connected to Internet. =>=We want to combine these two facilities. That is mails coming from =>=BITNET will be routed to Ultrix host. And mails coming from Internet =>=will be routed to VMS host. What is necessary for this configuration. =>=Thanks in advance... = =>Well, first of all you probably want to have at least one protocol that both =>the Ultrix machine and the VMS machine speak. The two likely candidates are =>DECnet and TCP/IP. Once you've chosen which protocol you're going to use to = = We have DECnet and TCP/IP on our machines. They are talking DECnet. =There is TCP/IP on Ultrix machine. = =>let the two machines talk to each other, and provide more specifics about what =>you're trying to do, you can expect more detailed answers. OK, you added half the requisite information. Still not enough for a definitive answer, though. How are the messages that are supposed to go to the Ultrix machine via the VMS machine addressed? How about vice-versa? C'mon, if you want help, you've got to make at least a token effort. -------------------------------------------------------------------------------- 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, 16 Jun 1993 11:59:17 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: vms mail -> unix mail Message-ID: <131607@netnews.upenn.edu> Date: 16 Jun 93 15:39:48 GMT To: MX-List@WKUVX1.BITNET Hello, all the unix and vms experts out there, I have a vms-unix mail question which needs your help. I would like to transfer all the files under the [.mail] directory on a VAX machine, which includes all *.mai files, to a unix machine. And is it possible to access these mail messages from unix with all the folder information preserved? I was told that someone has done that successfully. I understand that some conversion or programming could be involved, and will appreciate any hint. Thank you very much. Also could you common copy my account when you reply if possible, thanks again. Jia ================================================================================ Archive-Date: Wed, 16 Jun 1993 13:55:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: 16 Jun 93 09:49:44 EST From: "John M. George" Reply-To: MX-List@WKUVX1.BITNET Subject: VAX Message Router and MX integration To: "Messages MX List" Message-ID: <"3544491416061993/A06763/IKE"@viking.navair.navy.mil> Hello Everyone, Our site is using Digital's Teamlinks mail and would like to integrate it with MX. Has anyone written a Message Router to MX gateway that we could use? Thanks in advance, John George Chief Engineer Naval Air Systems Command HQ Network GEORGEJM.NIMITZ@NAVAIR.NAVY.MIL ================================================================================ Archive-Date: Wed, 16 Jun 1993 21:17:51 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Mail patch wanted for EXTR/NOHEAD Message-ID: <1993Jun16.200910.1@ualr.edu> From: domiller@ualr.edu Reply-To: MX-List@WKUVX1.BITNET Date: 16 Jun 93 20:09:10 CST To: MX-List@WKUVX1.BITNET I realize this is a long shot, but has anyone patched VMS Mail's EXTRACT/NOHEAD function to not put RFC822 headers in the extracted file? I'm constantly fighting the header/noheader battle with our users. Someone complains either way, but this modification would pacify most of them. Dale Dale O. Miller - Systems Programmer University of Arkansas at Little Rock DOMILLER@UALR.EDU ================================================================================ Archive-Date: Thu, 17 Jun 1993 18:16:48 CDT Sender: list-mgr@WKUVX1.BITNET From: bleau@umdsp.umd.edu Subject: Re: vms mail -> unix mail Date: 17 Jun 1993 22:30:50 GMT Message-ID: <1vqraq$esi@umd5.umd.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <131607@netnews.upenn.edu>, wang@anvil.wharton.upenn.edu (jia wang) writes: > > > >Hello, all the unix and vms experts out there, > >I have a vms-unix mail question which needs your help. I would like >to transfer all the files under the [.mail] directory on a VAX >machine, which includes all *.mai files, to a unix machine. And is >it possible to access these mail messages from unix with all the >folder information preserved? I was told that someone has done >that successfully. I understand that some conversion or programming >could be involved, and will appreciate any hint. You should be able to do so, but as you noted above, it'll be a fair amount of programming work. The file mail.mai is an indexed file, and it has pointers to all the messages, folders, etc. So you'll have to find out the internal format and write a C program to decode it. Note that not all mail messages are stored in the mail$*.mai files; these are used only for the larger messages. Smaller messages are kept within mail.mai itself. Another, perhaps less clean, way of transferring the messages is to log onto the vms system, get into the mail utility, and do a dir/folder. Now, for each folder, do a select folder-name extract/all folder-name.list Now the set of *.list files has all the messages for each folder in the normal order. These are normal ascii text files, nothing special. Messages are separated by a character. You can mget *.list these files over to your Unix system. Now write a C program (or shell script) that scans the file for a and breaks out the messages. It can also decode the (fairly simple) vms mail header info and construct the proper header for . When that's done, you should be ready to go. So, while both methods involve a degree of programming, the method I described at least gives you all the messages in a readable format and organized by folders, so a major part of the work is already done. Using the original idea would still involve writing the correct files for your mailer, so you aren't really ahead of the game. The major drawback to the method I've described is that you'll have to issue a lot of commands within vms mail just to get started. Good luck. P.S. If you do decide to use this method, you might think of posting your eventual C code in vmsnet.sources. I know the objection: it doesn't run on vms, so why put it there? The answer is that anyone else encountering your same problem and asking this list could then be directed to an already working solution for his system. >Thank you very much. Also could you common copy my account when you >reply if possible, thanks again. > >Jia Oops; I should have read this before replying to your post. Oh well; I'll email you and let you know there's an answer. Larry Bleau University of Maryland bleau@umdsp.umd.edu 301-405-6223 ================================================================================ Archive-Date: Fri, 18 Jun 1993 20:41:29 CDT Sender: list-mgr@WKUVX1.BITNET Subject: VMSMAIL To: field does not contain original address. Message-ID: <1993Jun18.172807.1@admin.mcc.mass.edu> From: Reply-To: MX-List@WKUVX1.BITNET Date: 18 Jun 93 17:28:07 EST To: MX-List@WKUVX1.BITNET The To: field in VMSMAIL does not reflect the actual To: field in the original mail message sent over SMTP to our vax running MX V3.3, rather it contains my username in capital letters. I would really like to see the original To: field in there, as it might be the name of a distribution list. I know I can set the headers such that the To: field is included in the body of the message. Is there a way to get the VMSMAIL To: field to be "correct"? Chris Palmer palmer@admin.mcc.mass.edu "Colonel Mode" Middlesex Community College Systems Manager work: 508-937-5454-x6418, 617-275-8910-x6418 ================================================================================ Archive-Date: Fri, 18 Jun 1993 21:14:50 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 18 Jun 1993 21:14:27 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E3A6.038DCF60.21214@WKUVX1.BITNET> Subject: RE: VMSMAIL To: field does not contain original address. writes: > >The To: field in VMSMAIL does not reflect the actual To: field in the original >mail message sent over SMTP to our vax running MX V3.3, rather it contains my >username in capital letters. I would really like to see the original To: field >in there, as it might be the name of a distribution list. I know I can set the >headers such that the To: field is included in the body of the message. Is there >a way to get the VMSMAIL To: field to be "correct"? > Not currently, no. I've got on the wish list to look into for the next version.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sat, 19 Jun 1993 00:56:27 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Mail patch wanted for EXTR/NOHEAD Message-ID: <0096E3B2.87C33700@buckie.HSC.Colorado.EDU> Reply-To: MX-List@WKUVX1.BITNET Date: Sat, 19 Jun 1993 04:46:09 GMT To: MX-List@WKUVX1.BITNET In article <1993Jun16.200910.1@ualr.edu>, domiller@ualr.edu writes: >I realize this is a long shot, but has anyone patched VMS Mail's EXTRACT/NOHEAD >function to not put RFC822 headers in the extracted file? I'm constantly >fighting the header/noheader battle with our users. Someone complains either >way, but this modification would pacify most of them. This problem is solved with PMDF, which includes the ability for each user to define which headers they'd like to maintain in their messages, and a user agent that replaces regular VMSmail and provides functions long absent from VMSmail. Alternatively, you can put the headers at the bottom of the messages, which reduces the clutter for those who don't want to see them, but keeps them there for those who want to see them. Both MX and (I believe) PMDF allow headers to be placed at the bottom. However, I noticed you posted your message to four newsgroups, among them the PMDF and MX groups, but you failed to mention which MTA you are using, if, in fact, it is either PMDF or MX. -d -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Sun, 20 Jun 1993 19:12:28 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <930620164129> Date: Sun, 20 JUN 93 16:46 GMT From: rok.vidmar@uni-lj.si Reply-To: MX-List@WKUVX1.BITNET Subject: OPENOUT in Local To: MX-List@WKUVX1.BITNET VMS V5.5-2, MX V3.3 Some LOCAL entries stay in the queue and just increment their error count. Upon QUEUE READY I can notice briefly with repeated QUEUE SHOW/FULL a [no LOCAL_INFO file for this entry] (but there exists version 2 afterwards, which looks OK to me) replaced by the final Last error: %MAIL-E-OPENOUT, error opening !AS as output. MX_LOCAL_LOG.LOG shows: 20-JUN-1993 15:05:40.62 DELIVER: Status=007E81FA from MAIL$ routines 20-JUN-1993 15:05:40.62 DELIVER: --LOGLINK or OPENOUT failure; will retry. Local VMS users does exists and have no quota problems, VMSMail succeeds always. Any clues? Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +38 61 186439 61000 Ljubljana fax: +38 61 186358 Slovenia ================================================================================ Archive-Date: Mon, 21 Jun 1993 03:15:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: 21 Jun 93 08:10:11+0000 From: Fabien Marathee Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9306210810.AA07113(a)eliot.cnes.fr> To: MX-List@WKUVX1.BITNET Subject: MX Env Is there anyone running MX 3.3 / Multinet 3.2 / VMS 5.5-2 ? Thanks, Fabien. ================================================================================ Archive-Date: Mon, 21 Jun 1993 05:17:56 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 21 Jun 93 12:07+0200 To: Fabien Marathee CC: MX-List@WKUVX1.BITNET Subject: RE: MX Env From: Rok Vidmar Reply-To: MX-List@WKUVX1.BITNET Message-ID: <44*rok.vidmar@uni-lj.SI> > Is there anyone running MX 3.3 / Multinet 3.2 / VMS 5.5-2 ? Shure, MX 3.3, Multinet 3.2A, VMS 5.5-2. Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +38 61 186439 61000 Ljubljana fax: +38 61 186358 Slovenia ================================================================================ Archive-Date: Mon, 21 Jun 1993 08:05:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 21 Jun 1993 14:01:32 BST From: David Candlin Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: david@mail.ph.ed.ac.uk Message-ID: <0096E5C5.08F2DB46.20885@mail.ph.ed.ac.uk> Subject: Mailers and headers Edinburgh, 21-JUN-1993 In our department we have a variety of platforms. To present a uniform face, and to avoid telling the world whenever we change a platform, we decided to use the University mailer, so that everyone tells their friends that they are J.Bloggs@ed.ac.uk (or whatever). The mailer then sends the mail on to the address they have registered with it. Fine. Of course when we send mail, it comes "From:" the platform concerned. Some of these are various Unix systems, and some of them belong to our VMS cluster, using MX. This "From:" address is not the same as we told our friends, and can vary. This may or may not be a problem; but it certainly is when you are talking to an automatic list-server, with UNSUBSCRIBE or CONFIRM etc, particularly if you originally registered with a now-obsolete address. Is there a solution? One could perhaps imagine mail-systems which filled the "From:" field by default as at present, but where you could specify "From:" and then the system would put the default origin into "Sender:" instead. Or whatever.... David Candlin ================================================================================ Archive-Date: Mon, 21 Jun 1993 08:33:08 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 21 JUN 93 13:27:35 GMT From: SYSTEM@TEX.AC.UK To: MX-LIST%BITNET.WKUVX1@NSFNET-RELAY.AC.UK Subject: RE: Mailers and headers Message-ID: <000003A4_0007D670.0096E5C0495E5980$20_1@UK.AC.TEX> Reply-To: MX-List@WKUVX1.BITNET In message <0096E5C5.08F2DB46.20885@mail.ph.ed.ac.uk> dated Mon, 21 Jun 1993 14:01:32 BST, David Candlin wrote: > In our department we have a variety of platforms. To present a uniform > face, and to avoid telling the world whenever we change a platform, we > decided to use the University mailer, so that everyone tells their friends > that they are J.Bloggs@ed.ac.uk (or whatever). The mailer then sends the > mail on to the address they have registered with it. > > Fine. Of course when we send mail, it comes "From:" the platform concerned. > Some of these are various Unix systems, and some of them belong to our VMS > cluster, using MX. This "From:" address is not the same as we told our > friends, and can vary. This may or may not be a problem; but it certainly > is when you are talking to an automatic list-server, with UNSUBSCRIBE or > CONFIRM etc, particularly if you originally registered with a now-obsolete > address. > > Is there a solution? One could perhaps imagine mail-systems which filled > the "From:" field by default as at present, but where you could specify > "From:" and then the system would put the default origin into "Sender:" > instead. Or whatever.... How about something which permits your users to insert Reply-To: headers? For a start, this will solve the problem of tagging all mail with the canonical form of mailbox that your site has defined. Secondly, users can make temporary changes so as to UNSUBSCRIBE from their old mailing list subscriptions. (Actually, I prefer *never* to SIGNOFF from a list, just in case I ever end up sending to the list from a former address; instead, I use the SET NOMAIL command to inhibit mailings *to* the old address from the list.) Brian {Hamilton Kelly} System Manager for the UK TeX Archive at Aston University ================================================================================ Archive-Date: Tue, 22 Jun 1993 03:51:31 CDT Sender: list-mgr@WKUVX1.BITNET From: gjo@brt.deakin.edu.au Reply-To: MX-List@WKUVX1.BITNET Subject: MX and 5.5-2 Date: Wed, 23 Jun 93 02:59:02 GMT Message-ID: <206alu$425@sol.deakin.OZ.AU> To: MX-List@WKUVX1.BITNET What version of MX is needed to run under VMS 5.5-2? We are currently at V5.4-2 and running MX3.0A without any major problems. (If it isn't broken don't fix it) Where are the archive sites fot MX these days? Greg O'Sullivan (gjo@brt.deakin.edu.au) ================================================================================ Archive-Date: Tue, 22 Jun 1993 06:29:55 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 22 Jun 1993 06:29:41 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E64F.1392EFC0.22168@WKUVX1.BITNET> Subject: RE: MX and 5.5-2 gjo@brt.deakin.edu.au writes: > >What version of MX is needed to run under VMS 5.5-2? All versions of MX from V3.0 up will run under VMS V5.5-2. >We are currently at V5.4-2 and running MX3.0A without any >major problems. (If it isn't broken don't fix it) > Except new releases usually include a number of bug fixes and lots of enhancements. In your case, you'd see a performance increase by moving to MX V3.3, in addition to quite a few new features that were added since MX V3.0. Plus the fact that *I* don't have MX V3.0 running anywhere, so you're not likely to get much help if you have any problems under MX V3.0---at least not until you go to the current version (V3.3). I heartily recommend that anyone running an old MX should upgrade to MX V3.3.... The installation is painless and your current config files should work without modification. Be sure you read the release notes for any gotchas.... >Where are the archive sites fot MX these days? > You can get MX via anonymous ftp from ftp.spc.edu in [.MX.MX033]. An UNZIP.EXE can be found in [.MX]. You can also get MX via e-mail in 149 VMS_SHARE parts by sending the following commands in the body of a mail message to FILESERV@WKUVX1.BITNET: SEND MX033 SEND MX033_SRC !If you want the sources SEND FILESERV_TOOLS !If you don't have MFTU and UNZIP Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 22 Jun 1993 07:01:50 CDT Sender: list-mgr@WKUVX1.BITNET Date: 22 Jun 1993 13:55:44 -0400 (EDT) From: Matthias Clausen DESY -KRYK- / D-Hamburg Reply-To: MX-List@WKUVX1.BITNET Subject: how to address psi%number::user@vms-host To: MX-List@WKUVX1.BITNET CC: claus@HERACC.desy.de Message-ID: <0096E68D.64125A60.13190@heracc.desy.de> Content-Transfer-Encoding: 7BIT I want to access several VMS services on my VAX via SMTP: psi%number::user@vms-node fax%number@vms-node even when I am writing from UNIX to "psi%number::user"@vms-node from VMS to "'psi%number::user'@vms-node" the % will be changed to @ like "psi@number::user" As far as I understood our main Postmaster, this violates the rules. No changes should be made by MX to an address in quotation marks - true? Since I found MX to be a real good product I am looking for the error on my side.. What am I doing wrong? ---------------------------------------------------------------- Matthias Clausen Deutsches Elektronen Synchrotron Gruppe: KRYK DESY/Hamburg, Germany ================================================================================ Archive-Date: Tue, 22 Jun 1993 07:32:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 22 Jun 1993 14:25:30 EDT From: "Fly like an eagle, crash like a VAX..." Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@CEARN.BITNET Message-ID: <0096E691.8C887D40.30534@europa.rs.ch> Subject: RE: how to address psi%number::user@vms-host I want to access several VMS services on my VAX via SMTP: psi%number::user@vms-node fax%number@vms-node My approach to this was creating a special path for this. e.g. user@number.psi.node.fqdn I did put this into the following rewrite rule REWRITE "<{u}@{h}.psi.node.fqdn>" "<""psi%{h}::{u}""@node.fqdn>" works for psi,decnet. I see no reason, why i should'nt work for a fax application. regards, Ralph Kloess +---------------+---------------------------------------------------------+ I Ralph Kloess I I-Net: Kloess@europa.rs.ch I I I Standard disclaimer applies to all my messages I +---------------+---------------------------------------------------------+ ================================================================================ Archive-Date: Tue, 22 Jun 1993 10:24:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 22 Jun 1993 10:18:37 CST From: Dan Bick Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096E66F.0EDFBA60.370@MNSMC1> Subject: mailshr patch that rm mx%"" Looking over the mailshr patch stuff in [.contrib] of mx 3.3, has anyone been running it on vms 5.5? As included it seems to have been tested up to 5.4 from what I can tell... This patch removes mx%"" syntax requirement on send address To: question. If anyone has any experience with this I would be gratefuly for info, thanks, Dan ============================================================================== Daniel W. Bick St. Mary's College of Minnesota 700 Terrace Heights System Manager and Programmer Computer Center #17 dbick@mnsmc1.mnsmc.edu -or- Winona, MN 55987-1399 dwb@marys.mnsmc.edu (NeXTmail) (507)457-1732 ================================================================================ Archive-Date: Tue, 22 Jun 1993 10:27:11 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 22 Jun 1993 10:26:54 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E670.3749AFA0.22266@WKUVX1.BITNET> Subject: RE: mailshr patch that rm mx%"" Dan Bick writes: > > >Looking over the mailshr patch stuff in [.contrib] of >mx 3.3, has anyone been running it on vms 5.5? As included >it seems to have been tested up to 5.4 from what I can tell... > The patch as distributed works under VMS V5.5-2. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 22 Jun 1993 16:16:39 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: mailshr patch that rm mx%"" Message-ID: <1993Jun22.163137.22882@aragorn.unibe.ch> Reply-To: MX-List@WKUVX1.BITNET Date: Tue, 22 Jun 1993 16:31:37 GMT To: MX-List@WKUVX1.BITNET In article <0096E670.3749AFA0.22266@WKUVX1.BITNET>, Hunter Goatley writes: >Dan Bick writes: Hunter >>Looking over the mailshr patch stuff in [.contrib] of >>mx 3.3, has anyone been running it on vms 5.5? As included >>it seems to have been tested up to 5.4 from what I can tell... >> >The patch as distributed works under VMS V5.5-2. You did great work with the DCL-recall-patch for OpenVMS AXP (patching an image without the DEC patch utility available). Do you have any plans to do the same for the "mx%"-mail-patch (written once by someone at Schlumberger)? Martin ******************************************************************************* Martin Egger, Ph.D., Computing Services - Head of System/User Support Group University of Bern, P.O. Box, Laenggassstrasse 51, CH-3012 Bern, Switzerland Phone: ++41 (0)31 65 38 45, Fax: ++41 (0)31 65 38 65, Telex: 912 643 pibe ch RFC: egger@id.unibe.ch, X.400: S=egger;OU=id;O=unibe;P=switch;A=arcom;C=ch; HEPNET/SPAN: 20579::49202::egger, DECnet (Switzerland): 49202::egger ******************************************************************************* ================================================================================ Archive-Date: Wed, 23 Jun 1993 23:45:43 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Windows E-MAIL Software Message-ID: <923.1274.uupcb@almac.co.uk> Date: 23 Jun 93 13:50:00 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET PC Windows E-MAIL Packages We are currently evaluating Windows E-Mail Packages for a new in-house project that will involve a network of about 150-200 PCs. Could any experienced users of the following packages, or just general E-Mail Experts, recommend, or give comments on, any of the following : MicroSoft Mail BeyondMail for Windows Da Vinci eMAIL Enable Higgins Lotus cc:Mail WordPerfect Office Has anybody had success/failure with using fax/modems to send /recieve faxs and external mail with these systems ? ================================================================================ Archive-Date: Thu, 24 Jun 1993 08:21:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 23 Jun 1993 15:14:26 EDT From: kenm@adhe.arknet.edu Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST%WKUVX1.BITNET@UKCC.UKY.EDU CC: kenm@adhe.arknet.edu Message-ID: <0096E761.8CF663C0.172@adhe.arknet.edu> Subject: INTERNET MAIL INTO ALLIN1 MAIL Is anyone using All-In-1 (v3.0) E-mail and MX. When MX receives mail it sends it to VMS mail. I am trying to find an "easy??" (hopefully automated) way to get the VMS mail messages into a users All-In-1 account. A 'SET FORWARD' in VMS mail does not seem to work. Anyone got any DCL, programming, general tips, or other ideas? THANKS in advance! Ken McCoy (kenm@adhe.arknet.edu) Senior Systems Programmer Arkansas Department of Higher Education ================================================================================ Archive-Date: Thu, 24 Jun 1993 16:05:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 24 Jun 1993 09:55:02 EDT From: Mario Jose Bernardes Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096E7FE.184CE380.5407@ciuc2.uc.pt> HELP ================================================================================ Archive-Date: Thu, 24 Jun 1993 16:08:26 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: VMS-Mail as MX-Site Specific Date: 24 Jun 1993 10:43:03 +0200 Message-ID: <20bpen$rij@sun3.eeam.elin.co.at> To: MX-List@WKUVX1.BITNET Is there anybody who knows to make vms-mail (over p.s.i. [PSI%] and over decnet) to the mx site agent. I like to build an Mail-Gateway from Internet-Mail to VMS-Mail. Other VAX-es don't likr to run MX or does nor have an Decnet-connection permanently over x25. thanks -- Robert KNOTEK R.Knotek@elin.co.at ELIN-Energieanwendung GesmbH (VMS-Mail) Datex-P 0232 26231065::IDEFIX A-1141 Vienna, Austria, Penzingerstr.76 Phone: +43/(0)222/89100-2176 Fax: +43/(0)222/89100-3387 ================================================================================ Archive-Date: Thu, 24 Jun 1993 18:21:24 CDT Sender: list-mgr@WKUVX1.BITNET Date: 24 Jun 93 07:53:06 EST From: "John M. George" Reply-To: MX-List@WKUVX1.BITNET Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL To: "MX-List" , "MX-LIST" CC: "kenm" Message-ID: <"9606531224061993/A17609/IKE"@viking.navair.navy.mil> > > > > Is anyone using All-In-1 (v3.0) E-mail and MX. > > When MX receives mail it sends it to VMS mail. I am trying > to find an "easy??" (hopefully automated) way to get the > VMS mail messages into a users All-In-1 account. > > A 'SET FORWARD' in VMS mail does not seem to work. > > Anyone got any DCL, programming, general tips, or other > ideas? > > THANKS in advance! > > > Ken McCoy (kenm@adhe.arknet.edu) > Senior Systems Programmer > Arkansas Department of Higher Education > This is something I think would benefit alot of folks out there including our site. Some type of integration with DEC's MAILBUS product would obviously fit the bill. Would the developers of MX be willing to do such a thing? John George (GEORGEJM.NIMITZ@NAVAIR.NAVY.MIL) Chief Engineer Information Systems Division Naval Air Systems Command HQ ================================================================================ Archive-Date: Thu, 24 Jun 1993 20:27:14 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 24 Jun 1993 18:24:19 PST From: "David Scott Cunningham, TRIUMF, 604 222-1047" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096E845.3E068300.15641@erich.triumf.ca> Subject: flqu Hello, So I've just finished upgrading to MX 3.3, and there's no FLQU program. Is this no longer supported? If not, why not; I used it a lot. Dave ================================================================================ Archive-Date: Thu, 24 Jun 1993 23:03:13 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Windows E-MAIL Software Message-ID: <1993Jun24.145558.673@janus.arc.ab.ca> From: Date: 24 Jun 93 14:55:57 MDT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <923.1274.uupcb@almac.co.uk>, stuart.brown@almac.co.uk (Stuart Brown) writes: >PC Windows E-MAIL Packages > >We are currently evaluating Windows E-Mail Packages for a new in-house >project that will involve a network of about 150-200 PCs. >Could any experienced users of the following packages, or just general >E-Mail Experts, recommend, or give comments on, any of the following : > >MicroSoft Mail >BeyondMail for Windows >Da Vinci eMAIL >Enable Higgins >Lotus cc:Mail >WordPerfect Office > Take a look at March 1993's BYTE article 'Mixed Messaging'. The look at cc:Mail, Da Vinci eMail, Microsoft Mail, QuickMail and WordPerfect Office. ------------------------------------------------------------------------------- Bob Erkamp --> It Could Happen <-- A L B E R T A R E S E A R C H erkamp@arc.ab.ca "Some people make me pro-nuclear" C O U N C I L ------------------------------------------------------------------------------- ================================================================================ Archive-Date: Fri, 25 Jun 1993 02:31:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 24 Jun 1993 19:15:45 EST From: Richard Kelley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: richk@mbcg.uchc.edu Message-ID: <0096E84C.6D5F0260.2782@mbcg.uchc.edu> Subject: RE: Windows E-MAIL Software >We are currently evaluating Windows E-Mail Packages for a new in-house >project that will involve a network of about 150-200 PCs. >Could any experienced users of the following packages, or just general >E-Mail Experts, recommend, or give comments on, any of the following : >MicroSoft Mail >BeyondMail for Windows >Da Vinci eMAIL >Enable Higgins >Lotus cc:Mail >WordPerfect Office Our site has heavily invested in Microsoft mail as the mail system of choice for pc's and mac's. We have a large installed base of pc's (200+) as well as mac's (50-100) running on everything from Dec Pathworks, Lan Manager, and novell (notice the lower case). The PCSA/Lanman arrangement seemed to suggest that the best solution would be (obviously) a Microsoft product over the others although we have played with cc:mail. The current arrangement is working out extremely well, with the addition of Microsoft's Faxmail and remote email products, and all machines have access to internet mail via msmail's smtp gateway. The only problem that we've noticed is a user's access to the same mailbox (i.e. having the same user with both a mac and pc) not be able to receive email notifications correctly (microsoft should talk to dec about the vms lock manager design). Not a big deal. >Has anybody had success/failure with using fax/modems to send /recieve >faxs and external mail with these systems ? Success. You can add a fax machine as a person's email address if they don't have a real account (mostly dec people) and send them a message at the same time you send cc: via smtp and forward via msmail. Slick. We use zoom, intel, microcom 14.4bis faxmodems all around. N.P. Also, before we put up a T1 line for accessing offsite lanman nets, email was done via faxmodem dialup. Rich Kelley richk@mcc.uchc.edu Network Manager kelley@sun.uchc.edu UConn Health Center Farmington,Ct. 06032 ================================================================================ Archive-Date: Fri, 25 Jun 1993 04:38:04 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: flqu Date: 25 Jun 1993 06:08:19 GMT Message-ID: <20e4ojINNa09@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096E845.3E068300.15641@erich.triumf.ca>, "David Scott Cunningham, TRIUMF, 604 222-1047" writes: =So I've just finished upgrading to MX 3.3, and there's no FLQU program. = =Is this no longer supported? If not, why not; I used it a lot. Because the QUEUE commands to MCP provide the same functionality, when used with the appropriate qualifiers. For example, rather than: $ MCR MX_EXE:FLQU SHOW you can use: $ MCR MX_EXE:MCP QUEUE SHOW/BRIEF -------------------------------------------------------------------------------- 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, 25 Jun 1993 05:10:46 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 25 Jun 93 10:08 GMT From: "UK TeX Archive Manager " Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST%BITNET.WKUVX1@NSFNET-RELAY.AC.UK Subject: RE: flqu In message <0096E845.3E068300.15641@erich.triumf.ca> dated Thu, 24 Jun 1993 18:24:19 PST, "David Scott Cunningham, TRIUMF, 604 222-1047" wrote: >So I've just finished upgrading to MX 3.3, and there's no FLQU program. > >Is this no longer supported? If not, why not; I used it a lot. Funny sort of system manager that installs software without reading the release notes: ----------------------Extract from MX V3.3 Release Notes------------ p.3-3 --- 6 A new qualifier, /BRIEF, was added to the MCP QUEUE SHOW command. When /BRIEF is specified, brief information about all of the entries in the MX system queue are displayed. The output is virtually identical to that produced by the old FLQU utility. ------------------------------------------------------------------------------ (Found in about 10s by saying $ SEARCH/WINDOW MX033.RELEASE_NOTES FLQU There's also a reference in the MGMT_GUIDE.) I believe this was discussed (by the beta testers at least) before the release of V3.2, let alone V3.3: the implication is that MCP now allows this sort of functionality without needing a separate utility program --- surely an advance? Brian {Hamilton Kelly} System Manager for the UK TeX Archive at Aston University ================================================================================ Archive-Date: Fri, 25 Jun 1993 11:38:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 25 Jun 1993 08:33:24 PDT From: "Bob Johns, (604)363-6520" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%wkuvx1.BITNET@cunyvm.cuny.edu Message-ID: <0096E8BB.DBDE3660.22228@ccs.ios.bc.ca> Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL I'll add my support for the request to integrate MX into DEC's Message Router, too. Perhaps like PMDF... Bob Johns (bob@ios.bc.ca) Institute of Ocean Sciences Sidney, B.C. Canada ================================================================================ Archive-Date: Fri, 25 Jun 1993 13:49:05 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 25 Jun 1993 13:48:52 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E8E7.ED69C882.462@WKUVX1.BITNET> Subject: RE: mailshr patch that rm mx%"" writes: > >You did great work with the DCL-recall-patch for OpenVMS AXP (patching an image >without the DEC patch utility available). Thanks! >Do you have any plans to do the same >for the "mx%"-mail-patch (written once by someone at Schlumberger)? > It would be nice, but it'd be *very* difficult, if not impossible. That patch adds a lot of code to MAILSHR---PATCH on the VAX took care of creating the new code area, etc. Plus, it'd be next to impossible to create MACRO-64 code that would do the same stuff and patch it in. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 25 Jun 1993 14:04:49 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 25 Jun 1993 14:39:04 EDT From: "Brian Tillman, Smiths Industries, VAX Support, x8425" Reply-To: MX-List@WKUVX1.BITNET To: WKUVX1.BITNET!MX-list@esseye.si.com Message-ID: <0096E8EE.F0E1F8C0.21236@swdev.si.com> Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL There's been a lot of requests asking for integration of MX-handled mail and All-In-1. This sort of puzzles me. I thought the [.CONTRIB] subdirectory contained examples of how to do this. -- Brian Tillman tillman_brian@si.com ================================================================================ Archive-Date: Fri, 25 Jun 1993 15:00:39 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 25 Jun 1993 14:56:40 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E8F1.65DC57E0.23091@SHSU.edu> Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL On Fri, 25 Jun 1993 14:39:04 EDT, "Brian Tillman, Smiths Industries, VAX Support, x8425" posted: > There's been a lot of requests asking for integration of MX-handled mail > and All-In-1. This sort of puzzles me. I thought the [.CONTRIB] > subdirectory contained examples of how to do this. The stuff in [CONTRIB] deal with getting mail from All-in-1 to a VMSmail gateway (SPECIAL.COM). Unfortunately, getting VMSmail back into All-in-1 automagically isn't as easy (at least I haven't seen the code to do this). --George ================================================================================ Archive-Date: Fri, 25 Jun 1993 16:05:22 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 25 Jun 1993 15:58:23 EDT From: kenm@adhe.arknet.edu Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E8FA.0571A3C0.213@adhe.arknet.edu> Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL If you're running All-In-1 version 3.0, getting VMS mail into All-In-1 turned out to be a "workable?" situation. Version 3 has a "V" option of electronic mail. This option pulls VMS mail into All-In-1 accounts. You have just got to train your users to run this option, even if they have to run it multiple times a day. Ken. ================================================================================ Archive-Date: Fri, 25 Jun 1993 16:13:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 25 Jun 1993 17:08:00 EDT From: Ta Fuh Chiam Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096E903.BF48EE80.23154@VULCAN.CBA.OHIOU.EDU> Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL > >The stuff in [CONTRIB] deal with getting mail from All-in-1 to a VMSmail >gateway (SPECIAL.COM). Unfortunately, getting VMSmail back into All-in-1 >automagically isn't as easy (at least I haven't seen the code to do this). And there is no integration into the Message Router/MAILBUS which is how you get into ALL-IN-1. It would be nice to be able to simply type username@internet.address@MX within ALL-IN-1 or DECMailworks to send messages to MX. ============================================================================ Ta Fuh Chiam Ohio University, College of Business Administration / Phone: (614)593-2088 Management Information Systems FAX: (614)593-0319 Copeland Hall 22 INTERNET : chiam@vulcan.cba.ohiou.edu Athens, Ohio 45701, U.S.A. or : chiam@ouvaxa.cats.ohiou.edu BITNET : CHIAM@OUACCVMB Use my first Internet address if at all possible. Disclaimer: What I have said are my opinions, not of anyone else. ============================================================================ ================================================================================ Archive-Date: Fri, 25 Jun 1993 17:06:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 25 Jun 1993 15:01:57 PDT From: "Bob Johns, (604)363-6520" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%wkuvx1.BITNET@cunyvm.cuny.edu Message-ID: <0096E8F2.23C8F2E0.22503@ccs.ios.bc.ca> Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL Yes, "username@internet.address@smtp" is just the syntax I would like to see for a user sending from Digital Mailworks (or maybe ALL-IN-1, but we don't have that, so I can't comment on it, altho both products use Message Router - so it's probably the same). Bob Johns (bob@ios.bc.ca) Institute of Ocean Sciences Sidney, B.C. Canada ================================================================================ Archive-Date: Fri, 25 Jun 1993 18:02:01 CDT Sender: list-mgr@WKUVX1.BITNET To: bobby@sun3.eeam.elin.co.at, MX-List@WKUVX1.BITNET From: "Pasztor Miklos" Reply-To: MX-List@WKUVX1.BITNET Date: 25 Jun 93 16:05:43 GMT+1 Subject: Re: VMS-Mail as MX-Site Specific Message-ID: <36778A55F8D@aszi.sztaki.hu> > Is there anybody who knows to make vms-mail (over p.s.i. [PSI%] and > over decnet) to the mx site agent. I like to build an Mail-Gateway > from Internet-Mail to VMS-Mail. Other VAX-es don't likr to run MX > or does nor have an Decnet-connection permanently over x25. > > thanks > Robert, You need not use SITE to interface with decnet or PSI mail. First you can address a PSI site from the RFC822 world through MX this way: "PSI%dte::user"@your.mx.host And here is the way from a PSI site to the RFC822 world: psi%your_mx_dte::mx%"user@rfc.822.address" Note that quotes are essential in both cases. Second to make all this work easier you can use rewrite rules. You surely have some examples supplied with the MX distribution. If you do some rewrite rules, you should also enter some MX records in your DNS pointing to your MX machine which could serve this way as a mail gateway for those behind your machine on PSI and/or DECNET. Regards, Miklos ==================================================================== 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: Fri, 25 Jun 1993 20:42:42 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL Message-ID: <1993Jun25.231159.3678@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 25 Jun 1993 23:11:59 GMT To: MX-List@WKUVX1.BITNET Unfortunately (?), I never got around to running Message Router on my system at RPI, which is why a direct MX-MR interface was never developed. I did take a look at the MR programmer's kit documentation once, just to see how easy it would be to do. <> It's not that easy. Since Hunter doesn't run MR right now either (right, Hunter?), an MX-MR interface will largely depend on how much time he has to get it up and running (no small task in itself) and how much desire he has for self- flagellation (to actually try and work with the MRIF$ routines). :-) Not to say that it can't or won't ever be done, it's just that it's no small task; the amount of effort required probably equals the effort he and I have already put into writing the entire package as it currently exists. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Sun, 27 Jun 1993 16:33:23 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 26 Jun 93 18:37 GMT From: "UK TeX Archive Manager " Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST%BITNET.WKUVX1@NSFNET-RELAY.AC.UK Subject: RE: how to address psi%number::user@vms-host In message <0096E68D.64125A60.13190@heracc.desy.de> dated 22 Jun 1993 13:55:44 -0400 (EDT), Matthias Clausen DESY -KRYK- / D-Hamburg wrote: >I want to access several VMS services on my VAX via SMTP: > > psi%number::user@vms-node > fax%number@vms-node > >even when I am writing > >from UNIX to > "psi%number::user"@vms-node >from VMS to > "'psi%number::user'@vms-node" > >the % will be changed to @ like > > "psi@number::user" Ah yes indeed; following the germ of an idea arising from this message, and some other postings concerning use of PSI-Mail (replied to most encouragingly by Miklos in Hungary), I've just been trying this out. I tried sending from a remote (UUCP-connected) node to: <"PSI%dte-number::user"@TeX.ac.uk> and also locally, from the DCL command line, thus: $ MAIL/SUBJ="Testing" NL: MX%"""'PSI%dte-number::user'@TEX.ac.uk""" As Matthias says, in both cases MX chose to rewrite this so that the traffic tried to go out To: <"psi@dte-number::user"> whereupon MX washed its hands of the whole affair! Matthias went on to say: >As far as I understood our main Postmaster, this violates the rules. >No changes should be made by MX to an address in quotation marks - true? >Since I found MX to be a real good product I am looking for the error on my >side.. What am I doing wrong? I had expected some response from Hunter about this? I can definitely confirm what Matthias discovered; and yet Miklos wrote as if it all works for him. Can anyone elucidate? Configuration here includes VMS V5.4-2, MultiNet V3.1D, MX V3.2, PSI V4.3, DECUS UUCP V2.0 (with patch to perform callback even when polling is Never) (I've got MultiNet V3.2B and MX V3.3 waiting to go up: however, I want to backup the system disk before starting this, and the machine is 100 miles away, so it will have to wait until I can get on site to run stand-alone backup --- the rest I manage to do by remote control:-) Brian {Hamilton Kelly} System Manager for the UK TeX Archive at Aston University ================================================================================ Archive-Date: Sun, 27 Jun 1993 23:21:31 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: mailshr patch that rm mx%"" Message-ID: <1993Jun25.091719.196@tachyon.com> Date: 25 Jun 93 09:17:19 CDT To: MX-List@WKUVX1.BITNET In article <0096E670.3749AFA0.22266@WKUVX1.BITNET>, Hunter Goatley writes: > Dan Bick writes: >> >> >>Looking over the mailshr patch stuff in [.contrib] of >>mx 3.3, has anyone been running it on vms 5.5? As included >>it seems to have been tested up to 5.4 from what I can tell... >> > The patch as distributed works under VMS V5.5-2. > > Hunter > ------ If you are running on 5.5-1, as I am, you need to use the patch code for 5.4 instead of for 5.5-2. Also, David Cathey has done the 6.0 patch. -- ============================================================================== 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 ============================================================================== To Sharon: "If I said you had a beautiful body, would you hold it against me?" ================================================================================ Archive-Date: Mon, 28 Jun 1993 04:41:43 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: VMS-Mail as MX-Site Specific Date: 28 Jun 1993 10:46:31 +0200 Message-ID: <20mb57$eet@sun3.eeam.elin.co.at> To: MX-List@WKUVX1.BITNET Pasztor Miklos (PASZTOR@ASZI.SZTAKI.HU) wrote: : > Is there anybody who knows to make vms-mail (over p.s.i. [PSI%] and : > over decnet) to the mx site agent. I like to build an Mail-Gateway : > from Internet-Mail to VMS-Mail. Other VAX-es don't likr to run MX : > or does nor have an Decnet-connection permanently over x25. : > : > thanks : > : Robert, : You need not use SITE to interface with decnet or PSI mail. : First you can address a PSI site from the RFC822 world through MX : this way: : "PSI%dte::user"@your.mx.host : And here is the way from a PSI site to the RFC822 world: : psi%your_mx_dte::mx%"user@rfc.822.address" : Note that quotes are essential in both cases. : Second to make all this work easier you can use rewrite rules. : You surely have some examples supplied with the MX distribution. : If you do some rewrite rules, you should also enter some MX records : in your DNS pointing to your MX machine which could serve this way : as a mail gateway for those behind your machine on PSI and/or DECNET. : Regards, : Miklos I tried it -----> it worked. But a little problem seems to be accounting if you have to make bill's for use of X25. thanks. -- Robert KNOTEK R.Knotek@elin.co.at ELIN-Energieanwendung GesmbH (VMS-Mail) Datex-P 0232 26231065::IDEFIX A-1141 Vienna, Austria, Penzingerstr.76 Phone: +43/(0)222/89100-2176 Fax: +43/(0)222/89100-3387 ================================================================================ Archive-Date: Mon, 28 Jun 1993 07:18:26 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: how to address psi%number::user@vms-host Message-ID: <1993Jun28.072122.1782@dmc.com> Date: 28 Jun 93 07:21:22 EDT To: MX-List@WKUVX1.BITNET > As Matthias says, in both cases MX chose to rewrite this so that the traffic > tried to go out > > To: <"psi@dte-number::user"> > > whereupon MX washed its hands of the whole affair! Brian, As an experiment, try turning off % hacking. MX shouldn't have touched the quoted %, but ... Dick -- Dick Munroe Internet: munroe@dmc.com Doyle, Munroe Consultants, 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, 28 Jun 1993 09:02:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: 28 Jun 1993 15:47:44 -0400 (EDT) From: Matthias Clausen DESY -KRYK- / D-Hamburg Reply-To: MX-List@WKUVX1.BITNET Subject: RE: how to address psi%number::user@vms-host To: MX-List@WKUVX1.BITNET CC: claus@HERACC.desy.de Message-ID: <0096EB54.07F9F3C0.13501@heracc.desy.de> Content-Transfer-Encoding: 7BIT After reading confimation and NON-confirmation to this problem I tried one more time to get it running. After disabeling percent hacking and resetting MX from MCP nothing changed. But now I did it the way I experienced before one has do perform: Shutdown and restart MX otherwise the changes will not be taken over by MX. You will see the changes in the configuration, but they are not executed! Now I did it the durty way... ... and it works fine! Thanks to the colleagues for their help! Matthias Clausen Deutsches Elektronen Synchrotron DESY Gruppe: KRYK / F36H Notkestrasse 85 VXHERA::CLAUS W-2000 Hamburg 52 CLAUS@DESYVAX.BITNET Tel: -49 40 8998-3256 claus@vxhera.desy.de Fax: -49 40 8998-4388 PSI%(0262)45050958002::CLAUS ================================================================================ Archive-Date: Mon, 28 Jun 1993 09:07:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 28 Jun 1993 09:07:08 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096EB1C.10F97203.1065@WKUVX1.BITNET> Subject: RE: how to address psi%number::user@vms-host Matthias Clausen DESY -KRYK- / D-Hamburg writes: > [...] >After disabeling percent hacking and resetting MX from MCP nothing changed. > >But now I did it the way I experienced before one has do perform: >Shutdown and restart MX otherwise the changes will not be taken over >by MX. >You will see the changes in the configuration, but they are not executed! > Sounds like there may still be a problem RESETting the Router. I'll look into this for the next version. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Mon, 28 Jun 1993 11:26:56 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9306252048.AA26480@dretor.dciem.dnd.ca> To: MX-List@WKUVX1.BITNET From: "Daniel R Giles" Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 25 Jun 1993 16:47:44 EST Subject: MX -> DECnet -> Multinet Hi there. I've just installed the MX on our microVAX II here in Toronto. Our other office in Ottawa is running Multinet. The full path for them sending mail to us is as follows: PC -> DiVince Mail -> MHS (Novell) -> Multinet (VAX) -> DECnet -> MX (our VAX) -> Mercury (SMTP gateway) -> PC. The return address is marked as follows: SALTER.PRIORKAN@pcmail.kan.prior.ca. Now, what I want to do is simply to reply to this address and have MX figure out what to do with it. I tried setting up a rewrite rule as "<{user}@{host}.kan.prior.ca>" "<""mars::smtp%{user}@{host}.kan.prior.ca>""""@sol (BTW, mars is their DECnet node, sol is ours) The router then looks at the FIRST '@' and routes it based on pcmail.kan.prior.ca and tries to ship it via SMTP. I then set up a path for *.kan.prior.ca to use local delivery. However, when the local delivery adgent gets it, it only looks at mars::smtp%SALTER.PRIORKAN I tried putting in extra quotes at various locations, but to no avail. I would appreciate any help I can get. Dan Giles dciem!priort!giles PRIOR Data Sciences (416) 670-1225 ---------------------------------------------------------- Dan Giles, Sys Admin dciem!priort!giles PRIOR Data Sciences (416) 670-1225 (fax -1344) ---------------------------------------------------------- ================================================================================ Archive-Date: Mon, 28 Jun 1993 14:55:39 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 28 Jun 93 19:15 GMT From: "UK TeX Archive Manager " Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST%BITNET.WKUVX1@NSFNET-RELAY.AC.UK Subject: RE: how to address psi%number::user@vms-host In message <0096EB1C.10F97203.1065@WKUVX1.BITNET> dated Mon, 28 Jun 1993 09:07:08 CST, "Hunter Goatley, WKU" wrote: #Matthias Clausen DESY -KRYK- / D-Hamburg writes: #> #[...] #>After disabeling percent hacking and resetting MX from MCP nothing changed. #> #>But now I did it the way I experienced before one has do perform: #>Shutdown and restart MX otherwise the changes will not be taken over #>by MX. #>You will see the changes in the configuration, but they are not executed! #> #Sounds like there may still be a problem RESETting the Router. I'll #look into this for the next version. # #Hunter Contrary to what Matthias wrote, I was able to disable the percent-hacking by the following: $ MCP MCP> SET ROUTER/NOPERCENT MCP> »Z This wrote out the changed configuration, but of course, I'd forgotten to reset the router: so another call of $ MCP MCP> RESET ROUTER MCP> »Z fixed that too, and NOW the PSI% isn't corrupted, *and* the mail *does* go through. SO I can't really confirm or deny that the resetting code is working (remember, I'm still on MX V3.2). However, Hunter, you're studiously avoiding the central issue here --- *why* should one need to disable percent-hacking, when whatever is in double quotes is a local-part, in the parlance of RFC-822, and should under no circumstances be changed by the MX MHAs? Brian {Hamilton Kelly} System Manager for the UK TeX Archive at Aston University ================================================================================ Archive-Date: Mon, 28 Jun 1993 15:08:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 28 Jun 1993 15:08:03 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096EB4E.7C8FF88E.1151@WKUVX1.BITNET> Subject: RE: how to address psi%number::user@vms-host "UK TeX Archive Manager " writes: > >However, Hunter, you're studiously avoiding the central issue here --- *why* >should one need to disable percent-hacking, when whatever is in double quotes >is a local-part, in the parlance of RFC-822, and should under no circumstances >be changed by the MX MHAs? > I haven't studiously avoided the central issue, I just haven't had time to look into it. I saw your earlier comment, but haven't even had time to post a message saying that I would look into it. I'd guess that MX is taking an address like "psi%user::node"@LOCALNODE, stripping the LOCALNODE, then processing the "psi%user::node" as a regular address. Off-hand, that does sounds like it shouldn't be messing with the "%" even in that case. I haven't had time, however, to verify that that is indeed the sequence of events. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Mon, 28 Jun 1993 15:57:37 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 28 Jun 1993 14:53:56 -0600 From: Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9306282053.AA12838@umt.umt.edu> To: MX-List%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU Subject: "From" line bug This problem was recently brought to my attention, which I would like to get some advice on. The following message is generated when sending mail from an Ultrix (V4.3) node to a non-existant user on a VMS (V5.5-2) node running MX V3.2. -------------------------------------------------------------------------------- From Fri Jun 25 15:39:59 1993 Date: Fri, 25 Jun 1993 15:36:03 MDT From: Local delivery agent To: Subject: LOCAL delivery error X-Report-Type: Nondelivery; boundary="> Error description:" Status: R Note: this message was generated automatically. An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: nobody@lewis.umt.edu Error-Code: 3 Error-Text: No such local user Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ Received: from umt.umt.edu by LEWIS.UMT.EDU (MX V3.2) with SMTP; Fri, 25 Jun 1993 15:35:59 MDT Received: by umt.umt.edu (5.65/DEC-Ultrix/4.3) id AA05134; Fri, 25 Jun 1993 15:39:46 -0600 Date: Fri, 25 Jun 1993 15:39:46 -0600 From: marsh@umt.umt.edu (Paul Marsh) Message-ID: <9306252139.AA05134@umt.umt.edu> To: nobody@lewis.umt.edu Subject: test test. -------------------------------------------------------------------------------- Notes: 1) The very first mail header (From) contains no return address. This results in one of the following problems on the Ultrix node. a) If the /usr/spool/mail/sender file is empty at the time this message is received, the sender will be informed of new mail arriving, but will not be able to read it with the standard (/usr/ucb/mail) mail utility. (Although, the message will actually exist in the /usr/spool/mail/sender file. Once a new message arrives, it will overwrite this message.) b) If there is mail in the /usr/spool/mail/sender file when the message is received, it will be appended to the last message in the file. (When being read by the standard mail utility.) 2) If I send mail from an Ultrix node, to a VMS node running UCX, I get an appropriate error message, so this leads me to conclude the problem resides in MX. 3) If I send mail from a VMS node running MX to another VMS node running MX, I receive a similar error message on the sending VMS node. There are no problems reading it. (But then, I don't see the first "From" header either.) 4) If I send mail from a VMS node running UCX to a non-existant user on a VMS node running MX, I don't get return mail indicating the error. On this particular node, (running UCX V2.0), I need to restart UCX after sending out one of these messages. (SMTP mail hangs.) Thanks, -Paul Marsh- Paul Marsh - Network Systems Specialist Internet: marsh@selway.umt.edu MUSEnet: selway::marsh US Mail : Paul Marsh, University of Montana Computing and Information Services Missoula, MT 59812-1530 phone : (406) 243-2058 FAX: (406) 243-4076 ================================================================================ Archive-Date: Mon, 28 Jun 1993 17:16:01 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: MX -> DECnet -> Multinet Message-ID: <0096EB31.486B12E0@buckie> Reply-To: MX-List@WKUVX1.BITNET Date: Mon, 28 Jun 1993 17:41:10 GMT To: MX-List@WKUVX1.BITNET In article <9306252048.AA26480@dretor.dciem.dnd.ca>, "Daniel R Giles" writes: >I've just installed the MX on our microVAX II here in Toronto. Our other >office in Ottawa is running Multinet. The full path for them sending mail >to us is as follows: > > PC -> DiVince Mail -> MHS (Novell) -> Multinet (VAX) -> DECnet -> > MX (our VAX) -> Mercury (SMTP gateway) -> PC. > >The return address is marked as follows: > > SALTER.PRIORKAN@pcmail.kan.prior.ca. > >Now, what I want to do is simply to reply to this address and have MX >figure out what to do with it. I tried setting up a rewrite rule as > > "<{user}@{host}.kan.prior.ca>" > "<""mars::smtp%{user}@{host}.kan.prior.ca>""""@sol > >(BTW, mars is their DECnet node, sol is ours) This sortof rewrite, unfortunatly, won't work too hot. I've tried to setup something similar with less-than-perfect results. What about running MX on both the your node and the remote node running Multinet, and using MX's SMTP-over-DECnet functionality to communicate between the nodes? This wouldn't work if anyone uses MM, though, as MM can't currently use MX for outgoing mail. Does Multinet's mailer support SMTP-over-DECnet? If it does, all you'd need to do is configure it to use SMTP-over-DECnet when sending mail to your node, and configure MX on your node to send route mail to kan.prior.ca using SMTP-over-DECnet through MARS::. -dan -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Mon, 28 Jun 1993 19:36:13 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX holding mail Message-ID: Date: Mon, 28 Jun 1993 20:30:27 GMT To: MX-List@WKUVX1.BITNET i had a weird one today: MX couldnt deliver mail to me for some reason that escapes me. it would send mail and get the infamous message, but with no further info. i turned on LOCAL debuging and got: 28-JUN-1993 09:57:38.85 DELIVER: Status=007E81FA from MAIL$ routines 28-JUN-1993 09:57:38.85 DELIVER: --LOGLINK or OPENOUT failure; will retry. 28-JUN-1993 09:57:39.94 Setting up for retry at 28-JUN-1993 10:27:39.94 i finally cleared it by changing my mail file. perhaps it was a compress problem or the directory was full or something. any clues out there? [crossposted to .misc because it happened in DELIVER] -- -- bob pasker -- rbp@netcom.com -- ================================================================================ Archive-Date: Mon, 28 Jun 1993 19:58:12 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: "From" line bug Message-ID: <1993Jun28.213755.23252@news.arc.nasa.gov> From: Date: Mon, 28 Jun 1993 21:37:55 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <9306282053.AA12838@umt.umt.edu>, writes: >This problem was recently brought to my attention, which I would like to >get some advice on. The following message is generated when sending mail >from an Ultrix (V4.3) node to a non-existant user on a VMS (V5.5-2) node >running MX V3.2. > >------------------------------------------------------------------------------- - > >From Fri Jun 25 15:39:59 1993 >Date: Fri, 25 Jun 1993 15:36:03 MDT >From: Local delivery agent >To: >Subject: LOCAL delivery error >X-Report-Type: Nondelivery; boundary="> Error description:" >Status: R [...] >Notes: 1) The very first mail header (From) contains no return address. > This results in one of the following problems on the Ultrix node. [...] This is the ULTRIX system's fault. When MX generates the return message, it specifies an SMTP envelope return address of <>, which is appropriate for error messages (since you don't want error messages to bounce). The first from line is being generated by sendmail (or whatever you're running on the ULTRIX system) from that envelope address, and it's not handling the <> construct like it ought to. > 2) If I send mail from an Ultrix node, to a VMS node running UCX, I > get an appropriate error message, so this leads me to conclude the > problem resides in MX. This is probably because UCX is notifying the ULTRIX system about the non-existent mailbox condition during the SMTP transaction, so your ULTRIX mailer is generating the return message. > 3) If I send mail from a VMS node running MX to another VMS node running > MX, I receive a similar error message on the sending VMS node. There > are no problems reading it. (But then, I don't see the first "From" > header either.) Because that "From" header is generated by the ULTRIX system. > 4) If I send mail from a VMS node running UCX to a non-existant user on > a VMS node running MX, I don't get return mail indicating the error. > On this particular node, (running UCX V2.0), I need to restart UCX > after sending out one of these messages. (SMTP mail hangs.) It wouldn't surprise me if the UCX mailer doesn't handle MAIL FROM:<> either. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Tue, 29 Jun 1993 03:42:20 CDT Sender: list-mgr@WKUVX1.BITNET Date: 29 Jun 1993 10:37:50 -0400 (EDT) From: Matthias Clausen DESY -KRYK- / D-Hamburg Reply-To: MX-List@WKUVX1.BITNET Subject: RE: how to address psi%number::user@vms-host To: MX-List@WKUVX1.BITNET CC: claus@HERACC.desy.de Message-ID: <0096EBF1.E75743E0.13613@heracc.desy.de> Content-Transfer-Encoding: 7BIT Now that mx%"'psi%number::user'" is running I also tried to get MX%"'XYZ%number'@node.x.y" running which failed due to the fact that MX distiguishes VMS-mail by the "::". The workaround is to send to MX%"'XYZ%number::'@node.x.y" In my (DCL)gfax mailer I just remove the "::" from the number and its ok. Maybe MX could check for existing MAIL$PROTOCOL_XYZ logicals to forward these messages to VMS-mail? The FAX behind the GFAX is the commercial Gold-Fax software from DPD(UK). This software also sends Postscript files - which is neat. It would be nice if MX could also support FAX directly.(as PMDF does) Matthias Clausen Deutsches Elektronen Synchrotron DESY Gruppe: KRYK / F36H Notkestrasse 85 VXHERA::CLAUS W-2000 Hamburg 52 CLAUS@DESYVAX.BITNET Tel: -49 40 8998-3256 claus@vxhera.desy.de Fax: -49 40 8998-4388 PSI%(0262)45050958002::CLAUS ---------------------------------------------------------------- Matthias Clausen Deutsches Elektronen Synchrotron Gruppe: KRYK DESY/Hamburg, Germany ================================================================================ Archive-Date: Tue, 29 Jun 1993 11:54:03 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9306291645.AA18957@bali.brooks.af.mil> To: kenm@adhe.arknet.edu CC: MX-LIST%WKUVX1.BITNET@ukcc.uky.edu Subject: INERNET MAIL INTO ALLIN1 MAIL Date: Tue, 29 Jun 93 11:44:57 -0500 From: fh@bali.brooks.af.mil Reply-To: MX-List@WKUVX1.BITNET Ken, We use the "set forward" feature to automatically forward a user's vmsmail to his Allin1 account, via message router. Set the user's forwarding in his vmsmail like this (assume "a1user" is the user's Allin1 account name, and "vmsuser" is his vms account name; usually, these are the same): set forward/user=vmsuser mrgate::"""a1::a1user""" This assumes that the message router jobs are running on every node in a cluster; if this is not the case, you may have to preface the mrgate with a decnet node specification, so that the command will look like this: set forward/user=vmsuser node::mrgate::"""a1::a1user""" This has worked for us for some time. Good luck, Frank Huddleston fh@bali.brooks.af.mil ================================================================================ Archive-Date: Tue, 29 Jun 1993 14:15:17 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 29 Jun 1993 15:13:06 EDT From: Kipp Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET CC: teague@ACAVAX.LYNCHBURG.EDU Message-ID: <0096EC18.5B941500.18702@ACAVAX.LYNCHBURG.EDU> Subject: MX Mailing Lists What am I doing wrong? I've created a mailing list "test", but any attempt to send mail to it or to an associated "-request" address returns a message from Postmaster stating that there is "no such local user". Does a mailing list require a corresponding user account bearing the same name? (there is no mention in the instructions of this). Please respond via E-mail. Thanks. -------------------------------------------------------------------------------- Kipp Teague E-Mail: teague@acavax.lynchburg.edu Lynchburg College, Lynchburg, Virginia Phone: (804) 522-8358 ================================================================================ Archive-Date: Tue, 29 Jun 1993 14:17:50 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 29 Jun 1993 14:17:35 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096EC10.9A3015F0.1381@WKUVX1.BITNET> Subject: RE: MX Mailing Lists Kipp writes: > >What am I doing wrong? I've created a mailing list "test", but any attempt >to send mail to it or to an associated "-request" address returns a message >from Postmaster stating that there is "no such local user". Does a mailing >list require a corresponding user account bearing the same name? (there is no >mention in the instructions of this). Please respond via E-mail. Thanks. Did you do an MCP RESET after you defined the mailing list? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 29 Jun 1993 17:37:21 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL Message-ID: <1993Jun29.171108.3188@inland.com> Date: 29 Jun 93 17:11:08 CST To: MX-List@WKUVX1.BITNET In article <0096E761.8CF663C0.172@adhe.arknet.edu>, kenm@adhe.arknet.edu writes: > When MX receives mail it sends it to VMS mail. I am trying > to find an "easy??" (hopefully automated) way to get the > VMS mail messages into a users All-In-1 account. I have been working with Hunter on some enhancements to the Router to make it easier for MX to act as a gateway/hub to a multiprotocol domain. Some of my changes should make life easier for you as long as you are running MRGATE to get from Mail-11 (DECnet mail) to All-In-1 mail. Basically, I will be using MX as a central hub for an Email domain supporting delivery to and from: - Mail-11 hosts - local SMTP hosts - All-In-1 mail via MRGATE - Microsoft Mail via the Microsoft Mail Gateway to SMTP - The Internet via UUCP - The Internet via SMTP Initially, I am dealing with address rewriting issues to allow inbound addresses of the form mailbox@postoffice.dom.ain to be properly translated to whatever it takes to get the mail delivered in the local network. I am also dealing with the reserve translation issues in the locally generated message headers containing addresses. I am not dealing with any message body conversions, special action headers such as "Return-Receipt-To:" or attachments. Maybe later. I should be releasing these changes to Hunter sometime soon and presume that he may (if he likes what I have done) incorporate them into the next version. --- Tom Tom Allebrandi | Mail guru - DECUS UUCP Development Team Inland Steel Research Labs | NFS grunt - CMU/Tek-IP East Chicago, IN | Chairperson - VMSnet Working Group, DECUS VAX SIG 219 399 6306 | Internet: allebrandi@inland.com DECUServe: allebrandi | UUCP: ...!uunet!inland!allebrandi ================================================================================ Archive-Date: Wed, 30 Jun 1993 02:24:32 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL Message-ID: <1993Jun29.152527.161@echosphere.com> Date: 29 Jun 93 15:25:27 MDT To: MX-List@WKUVX1.BITNET In article <0096E903.BF48EE80.23154@VULCAN.CBA.OHIOU.EDU>, Ta Fuh Chiam writes: >>The stuff in [CONTRIB] deal with getting mail from All-in-1 to a VMSmail >>gateway (SPECIAL.COM). Unfortunately, getting VMSmail back into All-in-1 >>automagically isn't as easy (at least I haven't seen the code to do this). > > And there is no integration into the Message Router/MAILBUS which is how you get > into ALL-IN-1. It would be nice to be able to simply type > > username@internet.address@MX > > within ALL-IN-1 or DECMailworks to send messages to MX. Cal me silly, but why can't you set the VMSMail to autoforward into Allin1 with: MAIL> SET FORW/USER= MRGATE::A1:: And then, from Allin1, send mail to MX with: MX%"user@internet.com"@MRGATE Of course this requires Message Router VMSMail Gateway (MRGATE) software from DEC. We haven't got MX up and running yet, but the above works great with UUCP% instead of MX%. -- Daniel "Zar" Zirin ZiriDan@Echosphere.Com Echosphere Corporation Raptor!ZiriDan@CSN.Org Houston Satellite Systems/EchoStar Satellite/Echo Acceptance/Satellite Source 90 Inverness Circle East, Englewood, CO 80112, USA (303) 799-8222x5399 "...no matter where you go, there you are." - BB **Go Rockies!** 26-48 ================================================================================ Archive-Date: Wed, 30 Jun 1993 03:06:37 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL Message-ID: <1993Jun30.134246.787@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 30 Jun 93 13:42:45 +1000 To: MX-List@WKUVX1.BITNET In article <0096E761.8CF663C0.172@adhe.arknet.edu> kenm@adhe.arknet.edu writes: > Is anyone using All-In-1 (v3.0) E-mail and MX. Yep. > When MX receives mail it sends it to VMS mail. I am trying > to find an "easy??" (hopefully automated) way to get the > VMS mail messages into a users All-In-1 account. We tell users to use the "V" option on the Electronic Mail panel. This imports their VMS mail into their inbox. Carl. ================================================================================ Archive-Date: Wed, 30 Jun 1993 03:06:46 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL Message-ID: <1993Jun30.134809.788@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 30 Jun 93 13:48:09 +1000 To: MX-List@WKUVX1.BITNET In article <0096E8EE.F0E1F8C0.21236@swdev.si.com> "Brian Tillman, Smiths Industries, VAX Support, x8425" There's been a lot of requests asking for integration of MX-handled mail and > All-In-1. This sort of puzzles me. I thought the [.CONTRIB] subdirectory > contained examples of how to do this. No, all it contains is a replacement for the OA$LIB:SPECIAL.COM file which is invoked when you use an underscore as the first part of an address. A proper integration with mailbus would be nicer as currently All-In-1 users have to use the "V" import option on the EM panels to import Internet sourced mail. It sticks a return address on via MRGATE which is useless as MX still has real problems with MRGATE translated All-In-1 address. (Especially if your All-In-1 address has a space in it. :-( ) Carl. ================================================================================ Archive-Date: Wed, 30 Jun 1993 07:00:02 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 30 Jun 1993 07:47:03 EDT From: Ta Fuh Chiam Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096ECA3.35E4A640.23444@VULCAN.CBA.OHIOU.EDU> Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL >> >> within ALL-IN-1 or DECMailworks to send messages to MX. > >Cal me silly, but why can't you set the VMSMail to autoforward into Allin1 with: Ok. :-) Nay, just kidding. :-) > MAIL> SET FORW/USER= MRGATE::A1:: >And then, from Allin1, send mail to MX with: > MX%"user@internet.com"@MRGATE Yes, this will work, sort of. The problem is that when MRGATE sends it out to the Internet, the FROM: line got changed to include "::" in the string and many Internet mail servers cannot handle that kind of address. There is a workaround for this from the CONTRIB directory in MX that fixes this. At any rate, this works with ALL-IN-1 but does not work very well with DECMailworks. In DECMailworks, you need to use many double quotes to enclose the Internet address. Most ALL-IN-1 and DECMailworks users are not computer gurus and cannot handle that kind of address and won't understand why they have to do that either. :-( In DECMailworks, I have to use "MX%""username@internet.com"""@MRGATE@OUCBA as the address string to send mail to Internet via MRGATE and MX. See how ugly it is? :-) >> username@internet.address@MX is a lot easier to deal with. :-) ============================================================================ Ta Fuh Chiam Ohio University, College of Business Administration / Phone: (614)593-2088 Management Information Systems FAX: (614)593-0319 Copeland Hall 22 INTERNET : chiam@vulcan.cba.ohiou.edu Athens, Ohio 45701, U.S.A. or : chiam@ouvaxa.cats.ohiou.edu BITNET : CHIAM@OUACCVMB Use my first Internet address if at all possible. Disclaimer: What I have said are my opinions, not of anyone else. ============================================================================ ================================================================================ Archive-Date: Wed, 30 Jun 1993 07:05:17 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 30 Jun 1993 13:56:54 +0100 From: Per Hogstedt Reply-To: MX-List@WKUVX1.BITNET Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL To: MX-List@WKUVX1.BITNET Message-ID: <0096ECD6.E105AB40.9854@plab.se> >> When MX receives mail it sends it to VMS mail. I am trying >> to find an "easy??" (hopefully automated) way to get the >> VMS mail messages into a users All-In-1 account. > >We tell users to use the "V" option on the Electronic Mail panel. This imports >their VMS mail into their inbox. > >Carl. So far, most users here tend to set forward in VMSmail to All-in-1. We are also using the "V" option. The drawback is that you can only pick up mail from the NEWMAIL folder. We have written a small hack that allow the All-in-1 user to import mail from any VMSmail folder to any document drawer/folder in All-in-1. I think the development effort that was described the other day sounds very promising - keep up the good work! -Per ------- Per Hogstedt Internet: hogstedt@plab.se Lindholmen Utveckling or: hogstedt@ae.chalmers.se P.O. Box 8714 Phone...: +46 31 50 70 50 S-402 75 Gothenburg Fax.....: +46 31 51 53 13 Sweden MiniCall: +46 74 35 68 49 ------- ================================================================================ Archive-Date: Wed, 30 Jun 1993 07:07:32 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 30 Jun 1993 07:07:18 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096EC9D.A8321CB5.1563@WKUVX1.BITNET> Subject: Re: INTERNET MAIL INTO ALLIN1 MAIL A few days ago, Matt wrote: > >Unfortunately (?), I never got around to running Message Router on my system >at RPI, which is why a direct MX-MR interface was never developed. I did >take a look at the MR programmer's kit documentation once, just to see how >easy it would be to do. <> It's not that easy. > Yes, I looked at it back in '87 when I was working for a third-party software company. I was pretty disgusted then and we ended up scrapping our plans to integrate our product with MR. >Since Hunter doesn't run MR right now either (right, Hunter?), Correct. >an MX-MR >interface will largely depend on how much time he has to get it up and >running (no small task in itself) and how much desire he has for self- >flagellation (to actually try and work with the MRIF$ routines). :-) > Not much, for sure! >Not to say that it can't or won't ever be done, it's just that it's no >small task; the amount of effort required probably equals the effort he and I >have already put into writing the entire package as it currently exists. > From what I've seen, I'd say that's an accurate assessment. So what happened to those of you who were talking a few montsh ago about trying to tackle this? 8-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 30 Jun 1993 07:26:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 30 Jun 1993 13:14:28 EDT From: "Andy, Systems Manager" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: udaa055@elm.cc.kcl.ac.uk Message-ID: <0096ECD0.F34C1240.17130@elm.cc.kcl.ac.uk> Subject: Adding header fields Does anyone know if MX (3.3) has the ability to add arbitrary mail header lines to an outgoing message? For example, if I wanted to add an "X-Organisation: " field (that's just an example, not a real requirment!) how could I do it? Having read the manual, the only thing that seems possible is setting the reply-to: field. Any help appreciated Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Wed, 30 Jun 1993 07:29:00 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 30 Jun 1993 07:28:48 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096ECA0.A973D1F6.1571@WKUVX1.BITNET> Subject: RE: Adding header fields "Andy, Systems Manager" writes: > >Does anyone know if MX (3.3) has the ability to add arbitrary mail header lines >to an outgoing message? For example, if I wanted to add an "X-Organisation: " >field (that's just an example, not a real requirment!) how could I do it? > You can't yet. I hope to have *something* in place in the next version. >Having read the manual, the only thing that seems possible is setting the >reply-to: field. > Yes. You can also add info in your PERSONAL_NAME in VMS Mail. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 30 Jun 1993 12:11:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 30 Jun 1993 10:44:21 -0500 (CDT) From: stewart.nichols@dir.texas.gov Reply-To: MX-List@WKUVX1.BITNET Subject: RE: INTERNET MAIL INTO ALLIN1 MAIL To: MX-List@WKUVX1.BITNET CC: NICHOLS_SA@DIR.TEXAS.GOV Message-ID: <01GZZJ2MA9SMGW2AGE@DIR.TEXAS.GOV> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > We have written a small hack that > allow the All-in-1 user to import mail from any VMSmail folder to any > document drawer/folder in All-in-1. > -Per > ------- > Per Hogstedt Internet: hogstedt@plab.se > Lindholmen Utveckling or: hogstedt@ae.chalmers.se > P.O. Box 8714 Phone...: +46 31 50 70 50 > S-402 75 Gothenburg Fax.....: +46 31 51 53 13 > Sweden MiniCall: +46 74 35 68 49 > ------- Can I get a copy (source) of your "small hack"? I was going to write a similar thing myself but if it is already done... If it is REALLY small, please post it to the whole list. There must be a bunch of people out there that could use it. stu stewart.nichols@dir.texas.gov ================================================================================ Archive-Date: Wed, 30 Jun 1993 12:34:40 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 30 Jun 1993 08:18:31 EDT From: fraser_h@qis.dofasco.ca Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096ECA7.9B9623C0.31151@qis.dofasco.ca> Subject: RE: INERNET MAIL INTO ALLIN1 MAIL We went through the mx<->Allin1 mail exchange exercise a while ago. There are several ways to get mail between the systems, but without writing code to interface with mrgate directly, I don't think there's any way of delivering messages back and forth that can be replied to (ie. that have a correct and useable header for the mail readers). We long ago set up routing in MX to deliver mail addressed to a pseudo domain here called allin1, sending it through MRGATE, but replies go through the "foreign protocol" command procedure, which simply allows you to re-mail the message through VMS mail. Great, except that the sender now appears as VMSmail. ================================================================================ Archive-Date: Wed, 30 Jun 1993 16:50:12 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9306301513.AA11367@dretor.dciem.dnd.ca> To: MX-List@WKUVX1.BITNET From: "Daniel R Giles" Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 30 Jun 1993 11:04:00 EST Subject: RE: how to address psi%number::user@vms-host > Date: Mon, 28 Jun 1993 17:08:03 -0400 > From: "Hunter Goatley, WKU" > Reply-to: MX-List@WKUVX1.BITNET > To: MX-List@WKUVX1.BITNET > Subject: RE: how to address psi%number::user@vms-host > "UK TeX Archive Manager " >writes: > > > >However, Hunter, you're studiously avoiding the central issue here --- > > *why* should one need to disable percent-hacking, when whatever is in > >double quotes is a local-part, in the parlance of RFC-822, and should under > >no circumstances be changed by the MX MHAs? > > > I haven't studiously avoided the central issue, I just haven't had > time to look into it. I saw your earlier comment, but haven't even > had time to post a message saying that I would look into it. > > I'd guess that MX is taking an address like > "psi%user::node"@LOCALNODE, stripping the LOCALNODE, then > processing the "psi%user::node" as a regular address. Off-hand, that does > sounds like it shouldn't be messing with the "%" even in that case. > I haven't had time, however, to verify that that is indeed the > sequence of events. > > Hunter Just to let you know, I too had to disable percent-hacking under similar conditions. As well, the MCP RESET does not work: I have to shut the system down and then restart it. ---------------------------------------------------------- Dan Giles, Sys Admin dciem!priort!giles PRIOR Data Sciences (416) 670-1225 (fax -1344) ---------------------------------------------------------- ================================================================================ Archive-Date: Wed, 30 Jun 1993 18:17:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 01 Jul 1993 01:13:12 +0100 From: Per Hogstedt Reply-To: MX-List@WKUVX1.BITNET Subject: RE: INTERNET MAIL INTO ALLIN1 MAIL To: MX-List@WKUVX1.BITNET Message-ID: <0096ED35.5AEC8CE0.9960@plab.se> >> We have written a small hack that allow the All-in-1 user to import.. > >> -Per > >Can I get a copy (source) of your "small hack"? [...] If it >is REALLY small, please post it to the whole list. There must >be a bunch of people out there that could use it. > >stu You were right Stu. Judging from the requests, quite a few sites are using MX and All-in-1. So for you and the other ones that requested a copy, you'll find it below (since I think it is really small). Note that it was written for a LLV (i.e. swedish). I only made a sloppy translation of the form to "swinglish" so you get the idea. The named data looks like: Form: GET_MAIL Library: A1DISK:[ALLIN1.SITE.LIB_SWEDISH]SITEOAFORM.FLB; -------------------------------------------------------------------------------- ;;.TYPE;; ARG /OVERLAY/HARD="Import VMS-mail from any folder"/ POST="ifexit\vmsmail import_folder #vmsfolder,#a1mapp /all" ;;VMSFOLDER;; /HARD="VMS-mail foldername"/post='get #vmsfolder = vmsfolder' ;;FOLDER;; /PUT_SAVE=#FOLDER/GET_SAVE=#FOLDER/RECOG=CAB$.FOLDER;GET folder=OA$SEL_KEY\ OA$FLD_NEXT/UNIQUE/USE_FORM=DOCRECOG/HARD="All-in-1 folder" /post='get #a1mapp = folder' And the form (Get_Mail) looks like this after a quick translation from swedish :-) ----------------------------------------------------------------------- Select VMSmail folder to import and All-in-1 destination folder Import from VMSmail folder: _____________________________________ Put it in All-in-1 folder: _____________________________________ Fyll i ny information och tryck pe ------------------------------------------------------------------------ Note that you can use the "Find"-key on the All-in-1 folder line, but not on the VMSmail folder line. If you make improvements, please let me know. By the way, there must be a better way of distributing All-in-1 hacks than this, i.e sending off the entire form FLB or something. Could someone enlighten me? Regards, Per ------- Per Hogstedt Internet: hogstedt@plab.se Lindholmen Utveckling or: hogstedt@ae.chalmers.se P.O. Box 8714 Phone...: +46 31 50 70 50 S-402 75 Gothenburg Fax.....: +46 31 51 53 13 Sweden MiniCall: +46 74 35 68 49 ------- ================================================================================ Archive-Date: Wed, 30 Jun 1993 20:02:15 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9306301513.AA11367@dretor.dciem.dnd.ca> To: MX-List@WKUVX1.BITNET From: "Daniel R Giles" Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 30 Jun 1993 11:04:00 EST Subject: RE: how to address psi%number::user@vms-host > Date: Mon, 28 Jun 1993 17:08:03 -0400 > From: "Hunter Goatley, WKU" > Reply-to: MX-List@WKUVX1.BITNET > To: MX-List@WKUVX1.BITNET > Subject: RE: how to address psi%number::user@vms-host > "UK TeX Archive Manager " >writes: > > > >However, Hunter, you're studiously avoiding the central issue here --- > > *why* should one need to disable percent-hacking, when whatever is in > >double quotes is a local-part, in the parlance of RFC-822, and should under > >no circumstances be changed by the MX MHAs? > > > I haven't studiously avoided the central issue, I just haven't had > time to look into it. I saw your earlier comment, but haven't even > had time to post a message saying that I would look into it. > > I'd guess that MX is taking an address like > "psi%user::node"@LOCALNODE, stripping the LOCALNODE, then > processing the "psi%user::node" as a regular address. Off-hand, that does > sounds like it shouldn't be messing with the "%" even in that case. > I haven't had time, however, to verify that that is indeed the > sequence of events. > > Hunter Just to let you know, I too had to disable percent-hacking under similar conditions. As well, the MCP RESET does not work: I have to shut the system down and then restart it. ---------------------------------------------------------- Dan Giles, Sys Admin dciem!priort!giles PRIOR Data Sciences (416) 670-1225 (fax -1344) ---------------------------------------------------------- ================================================================================ Archive-Date: Wed, 30 Jun 1993 20:03:03 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9306301536.AA12949@dretor.dciem.dnd.ca> To: MX-List@WKUVX1.BITNET From: "Daniel R Giles" Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 30 Jun 1993 11:29:01 EST Subject: MX Router crashing I need help _real_ quick. I have aliases set up locally in the form "first_name.last_name". A _lot_ if time, but not always, mail coming in through DECnet addressed to, say, andre.stavri, causes the router to bomb out. This is what's in the mx_router_log.log file when it happens: 30-JUN-1993 10:24:39.38 %PROCESS, Processing entry number 769 30-JUN-1993 10:24:39.74 %PROCESS, Status from READ_INFO was 00000001 30-JUN-1993 10:24:39.74 %PROCESS, Message originated in VMS Mail. 30-JUN-1993 10:24:39.79 %PROCESS, will run domain expander on envelope addresses. 30-JUN-1993 10:24:39.79 %PROCESS, Processing address: 30-JUN-1993 10:24:40.20 %PROCESS, ... address now reads: 30-JUN-1993 10:24:40.20 %PROCESS, will run domain expander on message headers. $ If I run mx_router interactively, this is the error message I get: %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=804EB010, PC=80000010, PSL=03C00004 Improperly handled condition, image exit forced. What's happening here. And more importantly, the jobs which were being processed whenever the router bombed are now stuck in the queue :-(. How do I get the router to re-process these? (Stopping and starting the system DOES NOT help.) I need these things cleared out PROMPTO. Thanx in advance for any help. ---------------------------------------------------------- Dan Giles, Sys Admin dciem!priort!giles PRIOR Data Sciences (416) 670-1225 (fax -1344) ---------------------------------------------------------- ================================================================================ Archive-Date: Wed, 30 Jun 1993 20:54:54 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 30 Jun 1993 20:54:38 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096ED11.3C5198C6.1833@WKUVX1.BITNET> Subject: RE: MX Router crashing "Daniel R Giles" writes: > >I need help _real_ quick. I have aliases set up locally in the form >"first_name.last_name". A _lot_ if time, but not always, mail coming in >through DECnet addressed to, say, andre.stavri, causes the router to bomb >out. This is what's in the mx_router_log.log file when it happens: > You're using PathWay---apparently PathWay's UCX emulation isn't 100%, since you're at least the second person using PathWay that has had problems with the MX Router crashing. >What's happening here. And more importantly, the jobs which were being >processed whenever the router bombed are now stuck in the queue :-(. How >do I get the router to re-process these? (Stopping and starting the system >DOES NOT help.) I need these things cleared out PROMPTO. > You can use MCP QUEUE READY to force the entries to be reprocessed. Aside from that, I don't know what can be done about the Router crashing---neither Matt nor I have access to PathWay, though I've tried to talk to TWG about it a few times. If NETLIB actually supported PathWay, it'd be a different problem. But it sounds like, as I said above, that PathWay's UCX emulation isn't. Perhaps Matt or I could get a guest account on your system? Anybody else out there with PathWay that can help? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU)