Archive-Date: Sat, 01 May 1993 00:06:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 01 May 1993 00:06:19 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096BD3C.E82625E0.32702@WKUVX1.BITNET> Subject: MX-LIST Administrivia: Monthly Post Last modified: 2-JUL-1992 00:40 01:26 (Created) 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. 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 LISTSERV@WKUVX1.BITNET: SIGNOFF MX-List LISTSERV 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: Sun, 02 May 1993 00:41:44 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, shuford@CS.UTK.EDU Subject: Re: America OnLine creates infinite mail loop (repost) Date: 2 May 1993 05:14:36 GMT Message-ID: <1rvlbsINNqfg@CS.UTK.EDU> Keywords: RFC822, RFC821, SMTP, headers, America OnLine, AOL, mailing list, MX To: MX-List@WKUVX1.BITNET In article <0frJ7c_SMUgERMYkgc@transarc.com>, Craig_Everhart@transarc.com writes: > > Excerpts from netnews.comp.mail.misc: 26-Apr-93 Re: America OnLine > creates .. Jason Haar@csc.canterbur (554) > > > In <1rhlt4INNirb@CS.UTK.EDU> Richard Shuford (shuford@cs.utk.edu) wrote: > > > > > Maintainers of automated electronic mailing lists should beware that > > > the Internet e-mail gateway of the America OnLine commercial > > > conferencing system does NOT honor the RFC822 "Errors-To:" header. > > > > Just a wee point here - Errors-To is _not_ mentioned in RFC822 - in fact, > > ...if you're using SMTP, you're to use the SMTP ``RCPT TO:'' [sic] > argument as the address to which errors are to be reported. > (I call this the ``envelope from'' address.) > > I don't know if AOL.COM mail errors are sent to the RCPT TO: address for > incoming SMTP mail. In any case, the Errors-To: is in no protocol > document other than perhaps an old Sendmail manual and an > experimental/obsolete parenthetical remark in RFC 1035. All right, already. I've been flamed by mail and derogated in the newsgroup. And between the news system being down a day here and having a life other than running mailing lists, I have not gotten back to you about this thing. I do thank Hunter Goatley for making some effort to clarify what was going on. I made a little mistake. But AOL first made a bigger mistake. In my fatigue and haste on Monday afternoon, in my posting I mixed up the description of which header lines should be used for mail errors and which header line America OnLine is in fact using for mail errors. And I posted something Friday that is now cancelled (except for the BITNET folks...) in which I made the further mistake of thoughtlessly copying verbatim something somebody sent to me. But a better authority has sent me some e-mail, from which I'll quote below. ------------------------------- There are several ways a mail agent might plausibly respond to an error condition. I mentioned several of these in the now-cancelled posting. But where the Simple Mail Transfer Protocol is involved, John Klensin was kind enough to inform that errors about mail messages being undeliverable should be sent to: | ... the [SMTP] "envelope from" address ... "MAIL FROM" | | If the delivering SMTP server is correct/conforming, it places this | address into the RFC822 header as "Return-path" just before dropping | the mail in the local mailbox or handing it off to the Mail User Agent. | | For an SMTP server, that is where you stop. No other places, no | fallbacks to any RFC822 fields. This isn't just protocol convention: | there is an important technical loop-preventing issue. | | The RFC822 [header] comes into play if, and only if, transport and the | delivery attempt that stimulated the bounce did not occur over SMTP. | Even then, if SMTP was involved at some point in the transaction, and | you have a legitimate Return-path field, that is where the bounce ought | to go. What America OnLine actually does use is neither the envelope "MAIL From" information nor any of the plausible addresses from the RFC822 header. America OnLine, at least as of Monday, uses the RFC822 "Reply-To:" address Here follows the first of the many error messages AOL bounced back. \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ | Received: from hp81.prod.aol.net by MIKE.LRC.EDU (MX V3.2) with SMTP; | Sun, 25 Apr 1993 14:11:19 EDT | Received: from sco1.prod.aol.net by hp81.prod.aol.net with SMTP | (1.37.109.4/16.2) id AA15733; Sun, 25 Apr 93 14:14:37 -0400 | From: Postmaster@aol.com | X-Mailer: America Online Mailer | To: Info-Stratus@mike.lrc.edu | Subject: Returned Mail Unknown Member | Date: Sun, 25 Apr 93 14:10:18 EDT | Message-Id: <9304251410.tn89536@aol.com> | | The mail you sent could not be delivered; it was addressed to an unknown | user. The text you sent follows... | | I recently heard that version of FTX below 2.0 will support s$ calls for | moving from VOS to UNIX. If this is true, then could someone mention | the downside such as performance and possible conflicts. | | | ----------------------- Headers ------------------------ | >From uupsi7!mike.lrc.edu!owner-info-stratus Sun Apr 25 14:10:06 1993 remote | from aolsys | Received: from uupsi7 by aolsys.aol.com id aa05034; Sun, 25 Apr 93 14:06:45 | EDT | Received: from mike.lrc.edu by uu7.psi.com (5.65b/4.0.071791-PSI/PSINet) | via SMTP; | id AA01400 for jonschmidt; Sun, 25 Apr 93 13:58:53 -0400 | X-Listname: "Gatewayed with comp.sys.stratus." | Warnings-To: <> | Errors-To: owner-info-stratus@mike.lrc.edu | Sender: owner-info-stratus@mike.lrc.edu | Received: by mike.lrc.edu (MX V3.2) with SITE; Sun, 25 Apr 1993 13:46:53 EDT | To: | Subject: ftx support s$ calls | Message-Id: <1993Apr23.112341.20569@porthos.cc.bellcore.com> | From: dante@decoy.cc.bellcore.com (dante,joseph e) | Reply-To: Info-Stratus@mike.lrc.edu | Date: Fri, 23 Apr 93 11:23:41 GMT | Organization: Bellcore, Livingston, NJ | \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ During SMTP transmission, the MX software presented this envelope line MAIL From which is typically copied into the "Return-Path:" header. As you can see from the preserved headers, the address appears ONLY in the "To:" and the "Reply-To:" headers. America OnLine's gateway had to work pretty hard to find this address. But the AOL gateway did find the address, so it did dispatch the error message to the entire mailing list, and then the gateway worked equally hard each time the list host distributed the message to the entire mailing list, including the sad, nonfunctional "joeuser@AOL.COM". (Names have been changed to protect the presumed innocent.) Upon receiving each message distributed to the list, AOL.COM immediately generated a new error message in which THE ENTIRE PREVIOUS error message was embedded, and sent it back to Info-Stratus@mike.lrc.edu. This was an infinite loop of missives of ever increasing size. The fact that "joeuser@AOL.COM" was near the tail end of the mailing list slowed the frequency of bouncing. (I'm sure glad the mailing list is not alphabetized by hostname!) Otherwise the incident would have gotten even worse than it was before I could stop it. John Klensin's further commentary: | The rule is that, when a nondelivery message is sent out by mail, the | MAIL FROM address (you remember, the envelope) on that message--the | one AOL sends back to you (the list in this case)--is required to be | written as: | | MAIL FROM: <> | | That is a null address. It documents the important principle that | sending error messages in response to error messages usually produces | bad effects. And the reason for not looking past MAIL FROM in figuring | out where to send error replies is precisely that--a null address in | the envelope from address tells you to just forget it, not to look further. I thought that the community of people who use network e-mail would like to be warned about this. Last Monday I caused a complaint regarding this behavior to be dispatched to "postmaster@AOL.COM", but I have detected no reply as of yet. -- ...Richard S. Shuford | "A prudent man sees danger and takes refuge, ...shuford@cs.utk.edu | but the simple keep going and suffer for it." ...Info-Stratus Coord. | Proverbs 22:3 NIV ================================================================================ Archive-Date: Sun, 02 May 1993 16:04:15 CDT Sender: list-mgr@WKUVX1.BITNET Date: 30 Apr 1993 08:53:45 -0600 (MDT) From: "Louis B. Moore" Reply-To: MX-List@WKUVX1.BITNET, MOORE.LOUIS@TCHDEN.ORG Subject: RE: Wanted: new name for MX's ListServ To: MX-List@WKUVX1.BITNET Message-ID: <0096BCBD.6C343500.24912@tchden.org> Content-Transfer-Encoding: 7BIT Sign me up for MXserver. 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: Mon, 03 May 1993 08:18:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 03 May 1993 09:00:14 EDT From: "Brian Tillman, Smiths Industries, VAX Support, x8425" Reply-To: MX-List@WKUVX1.BITNET, tillman@SWDEV.SI.COM To: WKUVX1.BITNET!MX-List@esseye.si.com Message-ID: <0096BF19.D3111C80.5571@swdev.si.com> Subject: RE: OK. "MXserver" it is. >After seeing your comments (thanks!) and seeing the choices, I've >decided to go with MXserver. But what about the file server? How will people know if MXserver is the list server or the file server? ================================================================================ Archive-Date: Mon, 03 May 1993 08:23:47 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 03 May 1993 08:23:14 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, tillman@SWDEV.SI.COM Message-ID: <0096BF14.A7E12640.5708@WKUVX1.BITNET> Subject: RE: OK. "MXserver" it is. "Brian Tillman, Smiths Industries, VAX Support, x8425" writes: > >>After seeing your comments (thanks!) and seeing the choices, I've >>decided to go with MXserver. > >But what about the file server? How will people know if MXserver is the list >server or the file server? There is no default name for the file server (the component itself is the MX MLF). Though most people use FILESERV, there is no default name---I run FILESERV, ARCHIVES, and DSJ. (I did have an MXSERVER file server once, but that was just me.) The name MXserver will show up on replies from the mailing list processor. File server replies will continue to use whatever the name of the file server is. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Mon, 03 May 1993 13:32:03 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: OK. "MXserver" it is. Message-ID: <1993May3.165236.29341@news.arc.nasa.gov> From: Date: Mon, 3 May 1993 16:52:36 GMT Reply-To: MX-List@WKUVX1.BITNET, madison@tgv.com To: MX-List@WKUVX1.BITNET In article <0096BF19.D3111C80.5571@swdev.si.com>, "Brian Tillman, Smiths Industries, VAX Support, x8425" writes: >>After seeing your comments (thanks!) and seeing the choices, I've >>decided to go with MXserver. > >But what about the file server? How will people know if MXserver is the list >server or the file server? You give a file server its own name when you create it. There should be no confusion (unless somebody has a file server they've created with the name MXSERVER). -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Mon, 03 May 1993 22:32:15 CDT Sender: list-mgr@WKUVX1.BITNET From: brodie@fps.mcw.edu Reply-To: MX-List@WKUVX1.BITNET, brodie@FPS.MCW.EDU Subject: MX(3.1) and DECUS UUCP(2.0) gotchas? Message-ID: <1993May3.162038.744@fps.mcw.edu> Date: 3 May 93 16:20:38 CST To: MX-List@WKUVX1.BITNET A quick question-- I *finally* upgraded decus uucp to V2.0. (whew). what, if any, are the gotchas with MX 3.1? (and decus uucp 2.0). I already now use the uucp_uuxqt_rmail_mx (or whatever it is) logical.... anything else I need to know? Kent C. Brodie ---==|==--- *--------- (brodie@fps.mcw.edu) Sr. Systems & Network Manager \ / (uucp: fps!brodie) Faculty Physicians & Surgeons -)======~ (fax: +1-414-266-5043) Medical College of Wisconsin "Ahead Warp Factor 1" (voice:+1-414-266-5080) ================================================================================ Archive-Date: Tue, 04 May 1993 05:54:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 04 May 1993 05:54:10 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, brodie@FPS.MCW.EDU Message-ID: <0096BFC8.FF9DE260.6052@WKUVX1.BITNET> Subject: RE: MX(3.1) and DECUS UUCP(2.0) gotchas? brodie@fps.mcw.edu writes: > >A quick question-- > >I *finally* upgraded decus uucp to V2.0. (whew). what, if any, are >the gotchas with MX 3.1? (and decus uucp 2.0). > Aside from the fact that V3.2 is the current version and V3.3 is due RSN..... 8-) >I already now use the uucp_uuxqt_rmail_mx (or whatever it is) logical.... >anything else I need to know? > There is a bug in the UUCP UUCP_MAILSHR.EXE that can cause problems with MX if a binary file is sent through. Note that this is a problem with UUCP and has nothing to do with MX. From the MX release notes: 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. Attempts to SHUTDOWN the MX uucp intfc will fail; you must use STOP/ID to kill the process, CANCEL the message, then restart the UUCP agent. According to the DECUS UUCP developers, this will be fixed in the next release of DECUS UUCP. That's all that I'm aware of. I hope to have V3.3 out by the end of the week. You may want to wait and upgrade to that. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Tue, 04 May 1993 12:41:47 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 04 May 93 13:20:31 EDT From: Leonardo Lazarte Reply-To: MX-List@WKUVX1.BITNET, LLAZARTE@BRUNB.BITNET Subject: MX halts the system To: mx-list@WKUVX1.BITNET We have installed MX as it is in the tape distribution by CMU (the manual says it's version 2.2). Sometimes it works, but, sooner or later, it halts the whole system, and we have to reboot it. 1. Is this a known bug, or something I have done wrong with installation? 2. How/where could I get newer versions? Thanks for any help, Leonardo Lazarte Dep. de Matematica Univ. de Brasilia - Brazil. ================================================================================ Archive-Date: Tue, 04 May 1993 12:47:00 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 04 May 1993 12:46:44 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, LLAZARTE@BRUNB.BITNET Message-ID: <0096C002.A1C66600.6262@WKUVX1.BITNET> Subject: RE: MX halts the system Leonardo Lazarte writes: > >We have installed MX as it is in the tape distribution by CMU (the manual >says it's version 2.2). > That's pretty old stuff. >Sometimes it works, but, sooner or later, it halts the whole system, and >we have to reboot it. > I sincerely doubt this is an MX problem, since MX doesn't have any privileged (inner-mode) code in it. >1. Is this a known bug, or something I have done wrong with installation? > Sounds like it could be a CMU problem. >2. How/where could I get newer versions? > The current version of MX is V3.2 (V3.3 is due real soon). You can get MX via anonymous ftp from ftp.spc.edu in [.MX]. You can also get it via e-mail by sending the following commands in the body of a mail message to FILESERV@WKUVX1.BITNET: SEND MX032 SEND FILESERV_TOOLS Also, note that the MX-List address is now MX-List@WKUVX1.BITNET. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Wed, 05 May 1993 01:11:51 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, munroe@DMC.COM Subject: Multiple TCP/IP implementations in a cluster... Message-ID: <1993May4.131446.1550@dmc.com> Date: 4 May 93 13:14:46 EDT To: MX-List@WKUVX1.BITNET I'm planning on running two different TCP/IP implementations at my site. One copy of Multinet, for performance and reliability, on my gateway machine to the rest of the world. CMUIP on all the other machines because its free. I'ld like to play with the SMTP configuration. Is it possible to run SMTP on two clustered machines and pretend that the cluster really doesn't exist? If so, roughly, how do you go about doing it? -- 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, 05 May 1993 07:05:05 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 05 May 1993 07:04:48 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, munroe@DMC.COM Message-ID: <0096C09C.07A23320.6527@WKUVX1.BITNET> Subject: RE: Multiple TCP/IP implementations in a cluster... writes: > >I'm planning on running two different TCP/IP implementations at >my site. One copy of Multinet, for performance and reliability, >on my gateway machine to the rest of the world. CMUIP on all the >other machines because its free. > >I'ld like to play with the SMTP configuration. Is it possible to >run SMTP on two clustered machines and pretend that the cluster >really doesn't exist? If so, roughly, how do you go about doing >it? It is if you don't set up an MX cluster. The easiest way is to just install separate MX directories for the two nodes. It's still doable if they share the MX directory, but you'll have to play with some logical definitions, etc. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Wed, 05 May 1993 10:24:35 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Multiple TCP/IP implementations in a cluster... Message-ID: <1s8i7dINNgr9@gap.caltech.edu> From: Date: 5 May 1993 14:16:13 GMT Reply-To: MX-List@WKUVX1.BITNET, carl@SOL1.GPS.CALTECH.EDU To: MX-List@WKUVX1.BITNET In article <1993May4.131446.1550@dmc.com>, munroe@dmc.com (Dick Munroe) writes: =I'ld like to play with the SMTP configuration. Is it possible to =run SMTP on two clustered machines and pretend that the cluster =really doesn't exist? If so, roughly, how do you go about doing =it? Sure. You install the software in system-specific directory trees. You may have to put both DCLTABLES.EXE and HELPLIB.HLB in the system-specific directories, too, in order to avoid conflicts between the two TCP/IP packages, though the newer releases of MULTInet have the standard TCP/IP utilities defined as syntaxes of the MULTINET command to avoid such conflicts. -------------------------------------------------------------------------------- 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, 05 May 1993 19:34:37 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 05 May 1993 08:23:11 CDT From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET, bed_gdg@SHSU.BITNET To: MX-List@WKUVX1.BITNET CC: munroe@dmc.com Message-ID: <0096C0A6.FB065A00.25371@SHSU.edu> Subject: RE: Multiple TCP/IP implementations in a cluster... On 4 May 93 13:14:46 EDT, Dick Munroe posted: > I'm planning on running two different TCP/IP implementations at my site. > One copy of Multinet, for performance and reliability, on my gateway > machine to the rest of the world. CMUIP on all the other machines because > its free. > > I'ld like to play with the SMTP configuration. Is it possible to run SMTP > on two clustered machines and pretend that the cluster really doesn't > exist? If so, roughly, how do you go about doing it? We run such as setup here with MultiNet on one node (VAXcluster name FREYA; Internet name Niord.SHSU.edu; the VAXcluster name NIORD is another Internet name -- don't ask why...) and UCX on the others. We have successfully have been doing so for a few years now. All that we have done is to modify the SYS$STARTUP:NETLIB_STARTUP.COM to read (note areas marked by $!!): $! SYS$STARTUP:NETLIB_STARTUP.COM $! Startup command procedure for NETLIB library routines. $! $ DEFINE/SYSTEM/EXEC/NOLOG NETLIB_DIR SYS$COMMON:[SYSLIB] $! $ IF F$TRNLNM ("NETLIB_SHRXFR") .NES. "" THEN - IF F$FILE_ATTR ("NETLIB_SHRXFR:.EXE","KNOWN") THEN - INSTALL REMOVE NETLIB_SHRXFR $ IF F$TRNLNM ("NETLIB_SHR") .NES. "" THEN - IF F$FILE_ATTR ("NETLIB_SHR:.EXE","KNOWN") THEN - INSTALL REMOVE NETLIB_SHR $! $ DEFINE/SYSTEM/EXEC/NOLOG NETLIB_SHRXFR NETLIB_DIR:NETLIB_SHRXFR $ CALL DO_INSTALL NETLIB_SHRXFR:.EXE $!! $!! ODIN runs UCX, so DEFINE NETLIB_SHR properly $!! $ IF F$GETSYI("NODENAME") .EQS. "ODIN" THEN - DEFINE/SYSTEM/EXEC/NOLOG NETLIB_SHR NETLIB_DIR:NETLIB_UCX_SHR $!! $!! FREYA runs MultiNet, so DEFINE NETLIB_SHR properly $!! $ IF F$GETSYI("NODENAME") .EQS. "FREYA" THEN - DEFINE/SYSTEM/EXEC/NOLOG NETLIB_SHR NETLIB_DIR:NETLIB_MULTINET_SHR $!! $!! NIORD runs UCX, so DEFINE NETLIB_SHR properly $!! $ IF F$GETSYI("NODENAME") .EQS. "NIORD" THEN - DEFINE/SYSTEM/EXEC/NOLOG NETLIB_SHR NETLIB_DIR:NETLIB_UCX_SHR $ CALL DO_INSTALL NETLIB_DIR:NETLIB_UCX_SHR.EXE $ CALL DO_INSTALL NETLIB_DIR:NETLIB_MULTINET_SHR.EXE $ EXIT $! $DO_INSTALL: SUBROUTINE $ CMD := CREATE $ IF F$FILE_ATTRIBUTES (P1,"KNOWN") THEN CMD := REPLACE $ INSTALL 'CMD'/OPEN/SHARE/HEADER 'P1 $ ENDSUBROUTINE The main trick to this is to BE SURE to have a copy of this laying around whenever you do a new installation of NETLIB if you tell VMSINSTAL to purge existing files. After that, it's just start MX normally and you're done as NETLIB does the work for you once properly defined. You can run SMTP and SMTP Server processes on each machine without problems this way. 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: Wed, 05 May 1993 22:32:36 CDT Sender: list-mgr@WKUVX1.BITNET From: meregalli@cesi.it Reply-To: MX-List@WKUVX1.BITNET, meregalli@CESI.IT Subject: MX aliases and Pathworks PCmail Message-ID: <1993May5.112723.81@cesi.it> Date: 5 May 93 11:27:23 +0200 To: MX-List@WKUVX1.BITNET I have MX 3.2, VMS 5.5-2, Pathworks/VMS 4.1-1, Pathworks/DOS 4.0 I have defined MX aliases and successfully used from VMS Mail. >mxalias dir/full amico > >Alias: AMICO ^^^^^ >Desc: l'indirizzo di amico >Address: somebody@somewhere.world Then I have tried to use from a PCmail session. The session goes on well, but then I get first the message I've sent, I think as a CC >From: MEREGALLI "Alberto Meregalli (SIC)" 5-MAY-1993 10:13 >To: MX%AMICO ^^^^^^^^ >CC: MEREGALLI >Subj: prova > > >prova prova and immediately the following >From: MX%"Postmaster@cesi.it" 5-MAY-1993 10:13 >To: MEREGALLI >CC: >Subj: LOCAL delivery error > >Return-Path: <> >Date: Wed, 05 May 1993 10:13:28 +0200 >From: Local delivery agent >To: >Subject: LOCAL delivery error >X-Report-Type: Nondelivery; boundary="> Error description:" > >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: amico@cesi.it ^^^^^^^^^^^^^ >Error-Code: 3 >Error-Text: No such local user > >Error-End: 1 error detected > >------------------------------ Rejected message ------------------------------ >Received: by cesi.it (MX V3.2) id 11187; Wed, 05 May 1993 10:13:24 +0200 >Date: Wed, 05 May 1993 10:13:21 +0200 >From: Alberto Meregalli (SIC) >To: amico@cesi.it ^^^^^^^^^^^^^ >CC: meregalli@cesi.it >Message-ID: <0096C0B6.5EED76C0.11187@cesi.it> >Subject: prova > > >prova prova > Am I doing some mistake? or is there a workaround to this behaviour? (we expect to install shortly Pathworks/DOS 4.1). Thanks in advance --------------------------------------------------------------------------- Alberto Meregalli, SIC tel. +39 2 2125 249 CESI, Centro Elettrotecnico Sperimentale Italiano fax +39 2 2125 520 Via Rubattino, 54 - I 21034 Milano E-mail: meregalli@cesi.it ================================================================================ Archive-Date: Thu, 06 May 1993 08:18:14 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 06 May 1993 08:17:41 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, meregalli@CESI.IT Message-ID: <0096C16F.60F50780.6970@WKUVX1.BITNET> Subject: RE: MX aliases and Pathworks PCmail meregalli@cesi.it writes: > >I have MX 3.2, VMS 5.5-2, Pathworks/VMS 4.1-1, Pathworks/DOS 4.0 > >I have defined MX aliases and successfully used from VMS Mail. > [...] >Then I have tried to use from a PCmail session. >The session goes on well, but then I get first the message I've sent, I >think as a CC > >>From: MEREGALLI "Alberto Meregalli (SIC)" 5-MAY-1993 10:13 >>To: MX%AMICO > ^^^^^^^^ This is VMS Mail's doing---MX doesn't have anything to do with automatic CC's. It just uses whatever To: line was given. [...] >and immediately the following > [...] >>--> Error description: >>Error-For: amico@cesi.it > ^^^^^^^^^^^^^ >>Error-Code: 3 >>Error-Text: No such local user >> I don't know why this happened. It worked for me, but then I'm running Pathworks/DOS v4.1. >Am I doing some mistake? or is there a workaround to this behaviour? >(we expect to install shortly Pathworks/DOS 4.1). > If my experience is any indication, you won't have the problem after you go to 4.1. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Thu, 06 May 1993 11:32:02 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, dunnett@MALA.BC.CA Subject: Can MX warn user about delivery problems sooner Message-ID: <1993May5.213922.1765@mala.bc.ca> Date: 5 May 93 21:39:22 -0700 To: MX-List@WKUVX1.BITNET Is there any way to get MX to notify the sender that it's having trouble delivering a message? The problem is that people often send messages with incorrect addresses, but because our Internet link is sometimes unreliable ( it's been out for several days at a time ) I've got the "retry" limits set to 4 or 5 days. This means that it takes that long for the sender to be informed that their message couldn't be sent. It would be nice if MX could send the user a notification after a small number of failures ( eg 3 ) that it was having trouble delivering the message, and that it would retry for N days ( or whatever ). This would alert the user that there was a problem, and they could be alerted to check for correct addressing. The final "non-delivery" report would still be delivered when the message expired. Is it possible to set MX us to do this, if not is this a reasonable thing to ask for in a future release? -- ============================================================================= Malcolm Dunnett Malaspina College Email: dunnett@mala.bc.ca Computer Services Nanaimo, B.C. CANADA V9R 5S5 Tel: (604)755-8738 ================================================================================ Archive-Date: Thu, 06 May 1993 11:41:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 06 May 1993 11:40:59 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, dunnett@MALA.BC.CA Message-ID: <0096C18B.C7574A80.7024@WKUVX1.BITNET> Subject: RE: Can MX warn user about delivery problems sooner writes: > > Is there any way to get MX to notify the sender that it's having trouble >delivering a message? > Not currently, no. > It would be nice if MX could send the user a notification after a small >number of failures ( eg 3 ) that it was having trouble delivering the >message, and that it would retry for N days ( or whatever ). This would >alert the user that there was a problem, and they could be alerted to >check for correct addressing. The final "non-delivery" report would still >be delivered when the message expired. > > Is it possible to set MX us to do this, if not is this a reasonable thing >to ask for in a future release? > Yes. I hope to add that for MX V3.4, a few months down the road.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Fri, 07 May 1993 07:56:56 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 07 May 1993 07:50:48 EDT From: "Russell O. Redman" Reply-To: MX-List@WKUVX1.BITNET, redman@HIARAS.HIA.NRC.CA To: MX-LIST@WKUVX1.BITNET Message-ID: <0096C234.CA266440.10124@hiaras.hia.nrc.ca> Subject: RE: Can MX warn user about delivery problems sooner Malcolm Dunnet writes: > Is there any way to get MX to notify the sender that it's having trouble > delivering a message? > . . . > It would be nice if MX could send the user a notification after a small > number of failures ( eg 3 ) that it was having trouble delivering the > message, and that it would retry for N days ( or whatever ). This would > alert the user that there was a problem, and they could be alerted to > check for correct addressing. The final "non-delivery" report would still > be delivered when the message expired. I would like to second this motion! It often happens that mail is delayed for several days, sometimes through a bad address, but often just because a server is down somewhere on the route. It also often happens that the mail requires timely delivery. If the receiving party gets the note too late to be of use, or does not get it at all, guess who hears about it! :-( Just knowing that the message had been delayed would be a great help. Cheers, Russell O. Redman ================================================================================ Archive-Date: Fri, 07 May 1993 11:31:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 07 May 1993 11:14:49 EDT From: "Stanley J. McCaslin" Reply-To: MX-List@WKUVX1.BITNET, mccaslin@PSCCS1.PERU.EDU To: MX-List@WKUVX1.BITNET Message-ID: <0096C251.49E9D880.6478@PSCCS1.PERU.EDU> Subject: RE: Can MX warn user about delivery problems sooner > Is there any way to get MX to notify the sender that it's having trouble > delivering a message? > . . . >is down somewhere on the route. It also often happens that the mail requires >timely delivery. If the receiving party gets the note too late to be of use, or >does not get it at all, guess who hears about it! :-( Just knowing that the >message had been delayed would be a great help. It seems to me that the mailqueue utility provides this service, although on an ask-for basis rather than as an error notification. I set up the following in each mail user's login.com (I suppose it could have as easily gone into sylogin.com) -- mailqueue :== run mx_exe:mailqueue when a user wants to know if his/her messages have been delayed, the command $ mailqueue gives that information. Stanley J. McCaslin Inet: mccaslin@psccs1.peru.edu Assistant Professor, Computer Science Phone:402/872-2208 Peru State College, Peru, NE 68421 Home: 402/872-7595 ================================================================================ Archive-Date: Fri, 07 May 1993 12:42:20 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 07 May 1993 13:29:05 EDT From: "Tim McKee, 803-366-2620" Reply-To: MX-List@WKUVX1.BITNET, mckeetr@CVSE.CORTEX.PROSPECT.COM To: MX-List@WKUVX1.BITNET Message-ID: <0096C264.0BBAAD60.7622@cvse.cortex.prospect.com> Subject: RE: Can MX warn user about delivery problems sooner The use of the MAILQUEUE mechanism is fine for experience and/or computer literate users, however, ..... There are many of us out here whose users are not and never will be... We need a 'proactive' system that automatically warns them. They will never use it if it isn't automatic! (But guess who still catches the political fallout when a critical message is late!) tim ================================================================================ Timothy R. McKee | Senior Consultant - VAX/VMS Internals Cortex Corp. - SouthEast Field Office | mckeetr@cvse.cortex.prospect.com Phone: (803) 366-2620 | FAX: (803) 366-6517 ================================================================================ ================================================================================ Archive-Date: Fri, 07 May 1993 13:12:56 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, lesher@LACERTA.UNM.EDU Subject: MX writing domain wrong is fixed! Date: 7 May 1993 15:20:40 GMT Message-ID: <1sduo8INN9c0@lynx.unm.edu> To: MX-List@WKUVX1.BITNET Hi, The problem with MX writing the domain wrong is fixed now. Thanks to Dan Wing, Carl J Lydick, John F. Sandhoff, Hunter Goatley, Chris Higgins and Earle Ake for helping me. The problem had to do with UCX instead of MX. Once I set the host to be libra.unm.edu in UCX, everything started working correctly. Thanks again! Kelly Lesher lesher@unm.edu ================================================================================ Archive-Date: Fri, 07 May 1993 15:41:34 CDT Sender: list-mgr@WKUVX1.BITNET From: system@dmc.com Reply-To: MX-List@WKUVX1.BITNET, system@DMC.COM Subject: Re: Help with name resolution problem... Message-ID: <1993May7.134251.1563@dmc.com> Date: 7 May 93 13:42:51 EDT To: MX-List@WKUVX1.BITNET I forgot to mention the configuration information: VMS 5.5-2 CMUIP 6.6-5A with the latest namres MX 3.3 beta 6 (I'll go to full 3.3 once I'm on the air with my DDS-2 line.) Dick Munroe ================================================================================ Archive-Date: Fri, 07 May 1993 16:40:00 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, system@CONDOR.NAVSSES.NAVY.MIL Subject: MX V3.3? Message-ID: <1993May7.153909.572@condor.navsses.navy.mil> Date: 7 May 93 15:39:09 -0600 To: MX-List@WKUVX1.BITNET Has MX V3.3 been OFFICIALLY released or is it still in BETA? If it is still in beta when is it expected to be released? -- Mike Jacobi NAVSSES VAXCluster system manager System@Eagle.Navsses.Navy.Mil System@Condor.Navsses.Navy.Mil Disclaimer - I speak for myself. No-one else. ================================================================================ Archive-Date: Fri, 07 May 1993 20:52:06 CDT Sender: list-mgr@WKUVX1.BITNET From: system@dmc.com Reply-To: MX-List@WKUVX1.BITNET, system@DMC.COM Subject: Help with name resolution problem... Message-ID: <1993May7.133902.1562@dmc.com> Date: 7 May 93 13:39:02 EDT To: MX-List@WKUVX1.BITNET I'm not quite sure whose this is, so I'm posting to both. I'm running CMUIP/MX on one machine MULTINET/MX on the other. Mail from CMU to MULTINET happens: 7-MAY-1993 13:26:09.01 Processing queue entry number 16 on node QUICK 7-MAY-1993 13:26:09.68 Recipient: , route=dmc.com 7-MAY-1993 13:26:09.68 SMTP_SEND: looking up host name dmc.com 7-MAY-1993 13:26:09.72 SMTP_SEND: Attempting to start session with DMC.COM [1 92.0.0.1] 7-MAY-1993 13:26:09.74 SMTP_SEND: Connected 7-MAY-1993 13:26:10.19 SMTP_SEND: Rcvd: 220 dmc.com MX V3.3 VAX SMTP server r ... And proceeds to completion. The next attempt to send mail always gets the following: 7-MAY-1993 13:27:58.92 Processing queue entry number 18 on node QUICK 7-MAY-1993 13:27:59.34 Recipient: , route=dmc.com 7-MAY-1993 13:27:59.35 Recipient: , route=dmc.com 7-MAY-1993 13:27:59.35 SMTP_SEND: looking up host name dmc.com 7-MAY-1993 13:27:59.37 SMTP_SEND: Failed, sts=00000134 7-MAY-1993 13:27:59.37 SMTP send failed, sts=0C27804A, sts2=00000134 7-MAY-1993 13:27:59.37 Recipient status=0C27804A for 7-MAY-1993 13:27:59.39 Recipient status=0C27804A for 7-MAY-1993 13:27:59.95 2 rcpts need retry, next try 7-MAY-1993 13:57:59.95 7-MAY-1993 13:28:00.00 *** End of processing pass *** If I stop/start the CMUIP/MX pair, everything goes ok. Interestingly enough, SMTP the other way continues to function. So, I have several question: 1. What is it trying to tell me? (134 = invalid media address). 2. What do I have to provide you folks to help me debug this? (I'm a bit new to the TCP/IP world in general and the CMUIP world in particular). Dick Munroe ================================================================================ Archive-Date: Sat, 08 May 1993 05:20:44 CDT Sender: list-mgr@WKUVX1.BITNET From: millerh@CCVAX4.CCS.CSUS.EDU Subject: Re: Help with name resolution problem... Message-ID: <0096C2D2.1E7739AA@CCVAX4.CCS.CSUS.EDU> Reply-To: MX-List@WKUVX1.BITNET, millerh@CCVAX4.CCS.CSUS.EDU Date: Sat, 8 May 1993 11:37:01 GMT To: MX-List@WKUVX1.BITNET In article <1993May7.133902.1562@dmc.com>, system@dmc.com writes: >I'm not quite sure whose this is, so I'm posting to both. I'm running CMUIP/MX >on one machine MULTINET/MX on the other. Mail from CMU to MULTINET happens: > > 7-MAY-1993 13:26:09.01 Processing queue entry number 16 on node QUICK > 7-MAY-1993 13:26:09.68 Recipient: , route=dmc.com > 7-MAY-1993 13:26:09.68 SMTP_SEND: looking up host name dmc.com > 7-MAY-1993 13:26:09.72 SMTP_SEND: Attempting to start session with DMC.COM >[1 >92.0.0.1] > 7-MAY-1993 13:26:09.74 SMTP_SEND: Connected > 7-MAY-1993 13:26:10.19 SMTP_SEND: Rcvd: 220 dmc.com MX V3.3 VAX SMTP server >r >.... > >And proceeds to completion. > >The next attempt to send mail always gets the following: > > 7-MAY-1993 13:27:58.92 Processing queue entry number 18 on node QUICK > 7-MAY-1993 13:27:59.34 Recipient: , route=dmc.com > 7-MAY-1993 13:27:59.35 Recipient: , route=dmc.com > 7-MAY-1993 13:27:59.35 SMTP_SEND: looking up host name dmc.com > 7-MAY-1993 13:27:59.37 SMTP_SEND: Failed, sts=00000134 > 7-MAY-1993 13:27:59.37 SMTP send failed, sts=0C27804A, sts2=00000134 > 7-MAY-1993 13:27:59.37 Recipient status=0C27804A for > 7-MAY-1993 13:27:59.39 Recipient status=0C27804A for > 7-MAY-1993 13:27:59.95 2 rcpts need retry, next try 7-MAY-1993 13:57:59.95 > 7-MAY-1993 13:28:00.00 *** End of processing pass *** > >If I stop/start the CMUIP/MX pair, everything goes ok. > >Interestingly enough, SMTP the other way continues to function. > >So, I have several question: > >1. What is it trying to tell me? (134 = invalid media address). > >2. What do I have to provide you folks to help me debug this? (I'm a bit new >to the TCP/IP world in general and the CMUIP world in particular). > >Dick Munroe Dick, Could you send me a copy of your NAMRES.CONFIG, your INTERNET.CONFIG and your IP_STARTUP.COM? -HWM ---------- Henry W. Miller Assistant Systems and Network Manager U.S. Bureau of Reclamation Mid Pacific Region 2800 Cottage Way MP1100 ================================================================================ Archive-Date: Sat, 08 May 1993 08:34:57 CDT Sender: list-mgr@WKUVX1.BITNET From: system@dmc.com Reply-To: MX-List@WKUVX1.BITNET, system@DMC.COM Subject: Re: Help with name resolution problem... Message-ID: <1993May8.071019.1567@dmc.com> Date: 8 May 93 07:10:19 EDT To: MX-List@WKUVX1.BITNET In article <1993May7.133902.1562@dmc.com>, system@dmc.com writes: A couple more details, 1. I'm not directly connected to the internet yet (My DDS-2 line is installed, but not tested yet), so the root name servers aren't available. 2. I'm using DMC.COM as my domain name server, here is NAMRES$CONFIG: Domain_Server:.:DMC.COM:192.0.0.1:53 Domain_Suffix:. Logging:0 Variable:DEBUG:0 3. Stopping and starting NAMRES doesn't clear the problem. 4. Stopping the network and restarting it DOES. Dick Munroe ================================================================================ Archive-Date: Sat, 08 May 1993 12:44:03 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Help with name resolution problem... Date: 8 May 1993 16:56:58 GMT Message-ID: <1sgooqINN3pi@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET, carl@SOL1.GPS.CALTECH.EDU To: MX-List@WKUVX1.BITNET In article <1993May7.133902.1562@dmc.com>, system@dmc.com writes: =1. What is it trying to tell me? (134 = invalid media address). If I recall correctly, that status under CMU-TEK TCP/IP v6.4 meant that you were unable to assign a channel to a net device. You'd typically have to restart the TCP/IP package. =2. What do I have to provide you folks to help me debug this? (I'm a bit new =to the TCP/IP world in general and the CMUIP world in particular). I'm not very familiar with the CMUIP v6.6, but you might want to have a look at CMUIP_ROOT:[SYSMGR]TCP_ACTIVITY.LOG. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Sat, 08 May 1993 12:44:07 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: Can MX warn user about delivery problems sooner Date: 8 May 1993 16:46:31 GMT Message-ID: <1sgo57INN3pi@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET, carl@SOL1.GPS.CALTECH.EDU To: MX-List@WKUVX1.BITNET In article <0096C234.CA266440.10124@hiaras.hia.nrc.ca>, "Russell O. Redman" writes: =I would like to second this motion! It often happens that mail is delayed for =several days, sometimes through a bad address, but often just because a server =is down somewhere on the route. It also often happens that the mail requires =timely delivery. If the receiving party gets the note too late to be of use, or =does not get it at all, guess who hears about it! :-( Just knowing that the =message had been delayed would be a great help. Until this feature is added, teach your users about MAILQUEUE. In particular, train them to use it a few minutes after sending a time-critical message. Or you COULD even have SYS$SYLOGIN run it automatically. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Sat, 08 May 1993 19:23:17 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 08 May 1993 19:22:55 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, system@CONDOR.NAVSSES.NAVY.MIL Message-ID: <0096C35E.A450CFA0.8231@WKUVX1.BITNET> Subject: RE: MX V3.3? writes: > >Has MX V3.3 been OFFICIALLY released or is it still in BETA? If it is still in >beta when is it expected to be released? >-- It has not yet been released, though it is coming early next week. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Sun, 09 May 1993 06:15:54 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 07 May 1993 08:44:34 0200 From: Mircea Giurgiu Reply-To: MX-List@WKUVX1.BITNET, mgiurgiu%roimar.dnet@ROEARN.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096C23C.4CE37600.1623@roimar.bitnet> subscribe Mircea Giurgiu ================================================================================ Archive-Date: Sun, 09 May 1993 06:22:10 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: To: Mx-List@WKUVX1.BITNET From: "Pasztor Miklos" Reply-To: MX-List@WKUVX1.BITNET, PASZTOR@ASZI.SZTAKI.HU Date: 7 May 93 15:33:11 GMT+1 Subject: Multiple site agents ? Mx-ers, I use multiple instances of MX processes recently. It is really a nice feature which improves performance. The Manager's manual ( at page 9-3 ) states, that "components that support multiple instances per node are ROUTER, LOCAL, SMTP, DNSMTP, JNET, UUCP and SITE". I suspected that this sentence was not updated since X.25 SMTP is in place so I tried multiple instances of this, and it works fine. However I cannot get SITE working with multiple instances. The second site process does not start up. I checked the Programmer's Guide also to see if I should create another SITE_DELIVER.COM or such but this didn't help. What am I missing ? Or is this a bug ? Please help. Thanks in advance. 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: Mon, 10 May 1993 05:33:28 CDT Sender: list-mgr@WKUVX1.BITNET From: millerh@CCVAX4.CCS.CSUS.EDU Subject: Re: Help with name resolution problem... Message-ID: <0096C465.C470FF5A@CCVAX4.CCS.CSUS.EDU> Reply-To: MX-List@WKUVX1.BITNET, millerh@CCVAX4.CCS.CSUS.EDU Date: Mon, 10 May 1993 11:46:27 GMT To: MX-List@WKUVX1.BITNET In article <1sgooqINN3pi@gap.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: >In article <1993May7.133902.1562@dmc.com>, system@dmc.com writes: >=1. What is it trying to tell me? (134 = invalid media address). > >If I recall correctly, that status under CMU-TEK TCP/IP v6.4 meant that you >were unable to assign a channel to a net device. You'd typically have to >restart the TCP/IP package. > >=2. What do I have to provide you folks to help me debug this? (I'm a bit new >=to the TCP/IP world in general and the CMUIP world in particular). > >I'm not very familiar with the CMUIP v6.6, but you might want to have a look at >CMUIP_ROOT:[SYSMGR]TCP_ACTIVITY.LOG. >------------------------------------------------------------------------------- - >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. Carl, An error of this type could occur if IPACP crashed. But, as we all know, 6.6-5A is much less prone to crashing! Also, the IOSB changed a little between 6.4 and 6.5/6.6, as did the numbering of the error messages. But the 134 is a system message, not an IPACP message. I think your theory about not being able to assing a net device carries a lot of water - a site in Germany reports that TRACEROUTE fails to work after IPACP runs "for a long time", and I suspect that the IP device numbers may not be getting recycled properly. Thanks for adding some credence to my theory - I'll check it out this week, meteors, floods and earthquakes notwithstanding. -HWM ---------- Henry W. Miller Assistant Systems and Network Manager U.S. Bureau of Reclamation Mid Pacific Region 2800 Cottage Way MP1100 ================================================================================ Archive-Date: Mon, 10 May 1993 15:12:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 10 May 1993 13:16:53 EDT From: Ian Vaz Reply-To: MX-List@WKUVX1.BITNET, ian@MARS.SENECAC.ON.CA To: mx-list@WKUVX1.BITNET Message-ID: <0096C4BD.D6E9ADA0.16534@mars.senecac.on.ca> Subject: Sending e-mail on command line: mx% Hi, In VMS one can do as follows: $ mail filename.txt username If the user is on the local machine, no problem: the e-mail in file "filename.txt" is sent to "username". However, what if I wanted to use the MX mailer ? I have tried: $ mail filename.txt mx%"username@destination" and $ mail filename.txt "mx%"username@destination"" No go. Is my need do-able ? Thanks in advance for all answers to this query. Regards, Ian Vaz, Seneca College, Ph:(416) 491-5050, Ext. 7252 e-mail: ian@mars.senecac.on.ca OR ian@phobos.senecac.on.ca ================================================================================ Archive-Date: Mon, 10 May 1993 15:17:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 10 May 1993 15:17:36 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, ian@MARS.SENECAC.ON.CA Message-ID: <0096C4CE.B3C90080.8657@WKUVX1.BITNET> Subject: RE: Sending e-mail on command line: mx% Ian Vaz writes: > >Hi, > >In VMS one can do as follows: > > $ mail filename.txt username > >If the user is on the local machine, no problem: the e-mail in file >"filename.txt" is sent to "username". However, what if I wanted to use >the MX mailer ? I have tried: > [...] Use: $ mail filename.txt "mx%""username@destination""" Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Mon, 10 May 1993 15:20:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 10 May 1993 15:20:11 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096C4CF.104AA480.8659@WKUVX1.BITNET> Subject: MX V3.3 is now available!! Message Exchange (MX) V3.3 is hereby officially released. MX is electronic mail software for VMS that supports Internet mail, BITNET mail, UUCP mail, and mailing list and file serving functions. MX V3.3 includes the following new features: o OpenVMS AXP V1.0 and higher is now supported by MX. The MX port is 100% native-mode code---there are no VESTed images in MX V3.3. o Binary files can now be sent using MAIL/FOREIGN to other MX V3.3 sites, as well as sites running PMDF V4.1 or higher or MultiNet v3.2 or higher. o BITNET messages can now be sent in NETDATA format in additon to PUNCH. o MX now allows multiple VMS Mail "From:" addresses if there are multiple "Reply-To:" addresses. o Lots more, of course! A full list of new features and bug fixes can be found in the MX V3.3 release notes. HOW TO GET MX V3.3 VIA ANONYMOUS FTP ==================================== You can get MX V3.3 via anonymous ftp from ftp.spc.edu in [.MX.MX033]. The file MX033.ZIP is a Zip archive that contains the VMSINSTAL kits for MX V3.3. The sources for MX can be found in MX033_SRC.ZIP. If you prefer to start with just the documentation, that can be found in MX033_DOCS_ONLY.ZIP. FTP note: these files are also available via anonymous ftp from niord.shsu.edu in [.MX033.ZIPSETS]. A third ftp site is riscy.cc.utexas.edu in [.MX033]. Riscy.cc.utexas.edu is a temporary site set up to alleviate the strain on the other two sites. HOW TO GET MX V3.3 VIA E-MAIL ============================= You can get MX via e-mail too, but be warned: it comes in 149 60-block parts!! It's huge.... Because my BITNET links upstream are still clogged, MX033 will temporarily *not* be available from WKUVX1.BITNET. It is available from FILESERV@SHSU.BITNET (FILESERV@Niord.SHSU.EDU) and from FILESERV@RISCY.CC.UTEXAS.EDU. SPECIAL NOTE TO BITNET SITES: MX V3.3 is also available from Eric Thomas's VMS Store. If you're on BITNET, this is the best way for you to go---the files are sent in VMSDUMP format. From SEARN: Send the following commands in the body of a mail message to LISTSERV@SEARN.BITNET: GET MX033.ZIP GET MX033_SRC.ZIP From SHSU: Send the following commands in the body of a mail message to FILESERV@SHSU.BITNET (or FILESERV@NIORD.SHSU.EDU): SEND MX033 SEND UNZIP !If you don't have UnZip for VMS SEND UNZIP_VMS !If you don't have UnZip for VMS SEND MFTU !If you don't have MFTU From riscy.cc.utexas.edu: Send the following commands in the body of a mail message to FILESERV@Riscy.cc.utexas.edu: SEND MX033 SEND FILESERV_TOOLS Special thanks to Terry Kennedy, Eric Thomas, George Greenwade, and David Barkelew for their help in distributing MX V3.3. Thanks too to all of my MX field testers for their patience and help. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Mon, 10 May 1993 16:03:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 10 May 1993 16:03:03 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096C4D5.0D650200.8675@WKUVX1.BITNET> Subject: A couple of notes about MX V3.3 Just to expand a little on the MX V3.3 announcement: > o Binary files can now be sent using MAIL/FOREIGN to other MX V3.3 > sites, as well as sites running PMDF V4.1 or higher or MultiNet v3.2 > or higher. > When /FOREIGN is used, the outgoing file is encoded using Base64 and mailed as a MIME-compliant message. This is currently the only MIME functionality in MX. Incoming messages in this special format are automatically decoded by MX and sent to the user as a foreign file. Note that MX V3.3, PMDF V4.1+, or MultiNet V3.2+ is required on the other end for the file to be usable. Also note that of the three, only MX can properly encode all VMS file types. PMDF and MultiNet cannot send indexed files, though both *can* successfully decode such files sent from MX. This will be fixed in a future release of MultiNet. I assume the same will be true for PMDF. > o BITNET messages can now be sent in NETDATA format in additon to PUNCH. > This requires that you have and maintain a copy of BITEARN NODES. More info is included the MX documentation. > o MX now allows multiple VMS Mail "From:" addresses if there are > multiple "Reply-To:" addresses. > This is site-configurable. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Mon, 10 May 1993 18:03:11 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, dhuddles@GANDALF.CA Subject: Re: MX V3.3? Message-ID: <1993May10.193702.6728@gandalf.ca> Date: Mon, 10 May 1993 19:37:02 GMT To: MX-List@WKUVX1.BITNET In <0096C35E.A450CFA0.8231@WKUVX1.BITNET> Hunter Goatley writes: >It has not yet been released, though it is coming early next week. >Hunter >------ Do you have any feeling as to whether the official (!) release will be changed at all from the V3.3 that I "grabbed" off ftp.spc.edu last Wednesday?? Oh, and just a simple question. I have V3.1C already running. Should I install MX 3.3 as a fresh installation into a NEW directory, or can I specify the existing directory structure of 3.1C. (Will I retain my MXCONFIG files etc. is what I am trying to say here!!) Thanks, David (hoping to put in TGV 3.2B and MX 3.3 on Thursday evening) Huddleson -- dhuddles@gandalf.ca David J. Huddleson Gandalf Data Ltd., Nepean, Ontario (613) 723-6500 Days (613) 822-1315 Otherwise ================================================================================ Archive-Date: Mon, 10 May 1993 18:34:05 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 10 May 1993 17:00:13 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET, dragon@NSCVAX.PRINCETON.EDU To: MX-List@WKUVX1.BITNET CC: ian@mars.senecac.on.ca Message-ID: <0096C4DD.09E334A0.19316@nscvax.princeton.edu> Subject: RE: Sending e-mail on command line: mx% Ian Vaz writes: > >In VMS one can do as follows: > > $ mail filename.txt username > >If the user is on the local machine, no problem: the e-mail in file >"filename.txt" is sent to "username". However, what if I wanted to use >the MX mailer ? I have tried: > > $ mail filename.txt mx%"username@destination" > and > $ mail filename.txt "mx%"username@destination"" > > No go. > >Is my need do-able ? > Try: $ MAIL FILENAME.TXT "MX%""username@destination""" ************************************************************************* * * * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Tue, 11 May 1993 00:04:41 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 10 May 1993 11:54:16 CDT From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET, bed_gdg@SHSU.BITNET To: MX-List@WKUVX1.BITNET CC: mckeetr@default-gateway Message-ID: <0096C4B2.4C3EB840.20557@SHSU.edu> Subject: RE: Can MX warn user about delivery problems sooner On Fri, 07 May 1993 13:29:05 EDT, "Tim McKee, 803-366-2620" posted: > The use of the MAILQUEUE mechanism is fine for experience and/or computer > literate users, however, ..... > > There are many of us out here whose users are not and never will be... We > need a 'proactive' system that automatically warns them. They will never > use it if it isn't automatic! (But guess who still catches the political > fallout when a critical message is late!) Fine and understood. Assuming you have a LOGIN.COM template, include: $ MAILQUEUE :== MX_EXE:MAILQUEUE $ MAILQUEUE $ write sys$output "To check on delivery status of mail you have sent, type:" $ write sys$output " MAILQUEUE at the system prompt (probably $)." in the template. This way, it's automagic and they are reminded of this each time they login. If they choose to ignore it, that's their problem and the real political issue becomes why Johnny and Susie can't read. Carl suggested including this in the SYS$SYLOGIN.COM file (or a file called by it). Certainly, this is a possibility and this would certainly make the pass universal. However, be sure to include something which allows it to be turned off by privileged users. I would HATE to go through our queue everytime I logged in and, if I'm not mistaken, even LOGIN/NOCOMMAND still reads the SYS$SYLOGIN file. Of course, this falls apart for users who login and never logout, but I would expect that the class of users who might be guilty of this aren't your usual users who would bitch about this problem anyway. Food for thought, 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: Tue, 11 May 1993 06:04:08 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 12:46:12 MEZ ( +0200) From: Peter Kobe Reply-To: MX-List@WKUVX1.BITNET, Peter.Kobe@Uni-Bonn.De To: MX-List@WKUVX1.BITNET Message-ID: <0096C582.B7FB04A0.4010@pib1.physik.uni-bonn.de> Subject: RE: Sending e-mail on command line: mx% Ian Vaz,ian@phobos.senecac.on.ca has the normal MX problem: >In VMS one can do as follows: > $ mail filename.txt username >If the user is on the local machine, no problem: the e-mail in file >"filename.txt" is sent to "username". However, what if I wanted to use >the MX mailer ? I have tried: > $ mail filename.txt mx%"username@destination" and > $ mail filename.txt "mx%"username@destination"" "mx%"username@destination"" > No go. >Is my need do-able ? GO with the 1-2-3 rule $ mail filename.txt "mx%""username@destination""" 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: Tue, 11 May 1993 06:31:37 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 10 May 93 22:04:28 EDT From: "prof. Leonardo Lazarte" Reply-To: MX-List@WKUVX1.BITNET, LLAZARTE@BRUNB.BITNET Subject: Re: MX V3.3 is now available!! To: MX-List@WKUVX1.BITNET On Mon, 10 May 1993 15:20:11 CDT Hunter Goatley said: >Message Exchange (MX) V3.3 is hereby officially released. Congratulations, and Thanks. Now let me do a very basic question. Hunter said: >You can get MX V3.3 via anonymous ftp from ftp.spc.edu in [.MX.MX033]. >The file MX033.ZIP is a Zip archive.... But, (blush) How do I use "unzip.exe" in VMS? If I "run" it, I get only a screen saying how it should be used. If I use /input and /output, I get the same screen, now in the output file. If I do "run unzip.exe etc" I get a "try with less parameters" message. Which is the correct syntax? Thanks for any help, Leonardo ================================================================================ Archive-Date: Tue, 11 May 1993 06:48:28 CDT Sender: list-mgr@WKUVX1.BITNET Date: 11 May 1993 13:42:40 -0400 (EDT) From: Matthias Clausen DESY -KRYK- / D-Hamburg Reply-To: MX-List@WKUVX1.BITNET, claus@HERACC.DESY.DE Subject: no RFC header on mail from listserver To: MX-List@WKUVX1.BITNET CC: claus@HERACC.desy.de Message-ID: <0096C58A.9B5201C0.11449@heracc.desy.de> Content-Transfer-Encoding: 7BIT Many colleagues are complaining about the set of RFC header informations even when they receive a mail from the local MX distribution list. Is there a way to leave out all these informations or -at least- place them at the end of the message? 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: Tue, 11 May 1993 07:16:31 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 09:03:48 -0300 (ADT) From: Greg Bishop Subject: Re: MX V3.3 is now available!! To: MX-List@WKUVX1.BITNET Reply-To: MX-List@WKUVX1.BITNET, gbishop@ac.nsac.ns.ca Message-ID: <0096C563.A6286DE0.14017@ac.nsac.ns.ca> Content-Transfer-Encoding: 7BIT > On Mon, 10 May 1993 15:20:11 CDT Hunter Goatley said: >>Message Exchange (MX) V3.3 is hereby officially released. > Congratulations, and Thanks. > Now let me do a very basic question. Hunter said: >>You can get MX V3.3 via anonymous ftp from ftp.spc.edu in [.MX.MX033]. >>The file MX033.ZIP is a Zip archive.... > But, (blush) How do I use "unzip.exe" in VMS? > If I "run" it, I get only a screen saying how it should be used. > If I use /input and /output, I get the same screen, now in the > output file. If I do "run unzip.exe etc" I get a "try with less > parameters" message. Which is the correct syntax? Here's a copy of a file called UNZIP.WHERE that I downloaded from NIORD.SHSU.EDU this morning. The backup saveset of UNZIP for VMS in the UNZIP directory on Niord works for me. The listing below may show you some closer sites. Greg -------------------------------------------------------------------------- %%% Save file as: Where Source: FILESERV@SHSU.BITNET %%% This is a file from the 21 August 1992 (version 5.0) of UNZIP %%% NOTE: Save this file in UNZIP's root directory %%% The following checksum includes all SHSU-generated topmatter. %%% checksum = "52024 127 540 4707" __________________________________________________________________________ This is the Info-ZIP file ``Where,'' last updated on 20 August 1992. __________________________________________________________________________ SITE OWNERS: If you're listed in here but the information is not correct (or if you're a big site but aren't listed at all), please let us know! E-mail to zip-bugs at the address given in Readme and we'll update this file. Basic source-archive names for Info-ZIP's portable Zip, UnZip, and related utilities (on some ftp sites, the .zip files may have a .zoo equivalent in zoo 2.10 format): zip19.zip Zip 1.9 (includes zipnote and zipsplit) zip19.tar.Z ditto, compress'd tar format unzip50.zip UnZip 5.0 (includes zipinfo and funzip) unzip50.tar.Z ditto, compress'd tar format wunz12sr.zip WizUnZip 1.2 support files for Windows 3.1, UnZip 5.0 zcrypt19.zip encryption/decryption support (includes zipcloak) Related archives and files: UnzpHist.zip changes history of UnZip, back to 2.0 zip19x.zip MSDOS executables and docs for zip, zipnote, zipsplit unzip50.exe MSDOS executable for unzip zip19_16.zip OS/2 1.x 16-bit executables and docs zip19_32.zip OS/2 2.x 32-bit executables and docs unz50_16.exe OS/2 1.x 16-bit executable unz50_32.exe OS/2 2.x 32-bit executable zip19vms.zip VMS executables and docs for zip, zipnote, zipsplit unz50vms.exe VMS executable for unzip zip_unzip.hqx Macinstosh executables (zip 1.0 only, 1.9 not ready) winunz12.zip Windows 3.1 executables (zip 1.0 only, 1.9 not ready) pkz110eu.exe MS-DOS PKZIP/PKUNZIP 1.1 (self-extracting archive) pkz193a.exe MS-DOS PKZIP/PKUNZIP beta 1.93 (self-extracting) pkz102-2.exe OS/2 PKZIP/PKUNZIP 1.02 (self-extracting) ftp sites for the US-exportable sources and executables. Look for the file names given above in the following directories. Some sites like to use slightly different names, such as zip-1.9.tar-z instead of zip19.tar.Z. wuarchive.wustl.edu:/packages/compression/... wuarchive.wustl.edu:/mirrors/misc/unix/... wuarchive.wustl.edu:/mirrors/misc/vaxvms/... wuarchive.wustl.edu:/mirrors/msdos/zip/... wuarchive.wustl.edu:/mirrors/msdos/windows3/... ftp.uu.net:/pub/zip/... ftp-os2.nmsu.edu:/pub/os2/2.0/archivers/... ftp-os2.nmsu.edu:/pub/os2/all/archivers/... Zip 1.9 and UnZip 5.0 will also be available at any comp.sources.misc archive site as soon as they are posted. wuarchive.wustl.edu:/mirrors/msdos/zip/pkz110eu.exe ux1.cso.uiuc.edu:/pc/exec-pc/pkz193a.exe [128.174.5.59] ftp sites for the encryption and decryption sources: NOTE: Non-US users, please do NOT ftp from the US site (US regulations and all that). Likewise, US users, please do not ftp from the European sites (it's not illegal, but it sure is a waste of expensive bandwidth). From the US: wuarchive.wustl.edu:/mirrors3/garbo.uwasa.fi/arcutil/zcrypt19.zip Outside the US: garbo.uwasa.fi:/pc/arcutil/zcrypt19.zip ftp.win.tue.nl:/pub/compression/zip/zcrypt19.zip ftp.inria.fr:/system/arch-compr/zcrypt19.zip ftp.informatik.tu-muenchen.de:/pub/utils/archiver/zcrypt19.zip (mail server at ftp-mailer@ftp.informatik.tu-muenchen.de) To find other ftp sites: The "archie" ftp database utility can be used to find an ftp site near you. If you don't know how to use it, DON'T ASK US--check the Usenet groups news.newusers.questions or news.answers or some such, or ask your system administrator. UUCP sites: uunet!~/pub/zip/ ... Mail servers: If you don't have anonymous FTP capability, you can mail one of the following commands (in the body of an e-mail message) to listserv@vm1.nodak.edu or listserv@vm.ecs.rpi.edu in order to get a copy via e-mail: /pdget mail pd:unzip50.tar-z uuencode /pdget mail pd:zip19.zip uuencode or: /pdget mail pd:zip19.tar-z uuencode To get the encryption source by email, send the following commands to ftp-mailer@ftp.informatik.tu-muenchen.de: get /pub/utils/archiver/zcrypt19.zip quit __________________________________________________________________________ Again, if someone repackages any of the source or executable archives in VMS-, Mac- or Atari-specific formats, please let us know (send e-mail to zip-bugs at the address listed in README). __________________________________________________________________________ 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: Tue, 11 May 1993 07:42:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 07:41:48 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, dhuddles@GANDALF.CA Message-ID: <0096C558.3198F4A0.8931@WKUVX1.BITNET> Subject: Re: MX V3.3? writes: > >Do you have any feeling as to whether the official (!) release will be changed >at all from the V3.3 that I "grabbed" off ftp.spc.edu last Wednesday?? > There were a couple of minor modifications made on Friday, May 7. The kits were not touched after that date. >Oh, and just a simple question. I have V3.1C already running. Should I install >MX 3.3 as a fresh installation into a NEW directory, or can I specify the >existing directory structure of 3.1C. (Will I retain my MXCONFIG files etc. is >what I am trying to say here!!) > You can install it over the existing 3.1C. At least, you're *supposed* to be able to.... 8-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Tue, 11 May 1993 08:05:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 08:05:27 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, LLAZARTE@BRUNB.BITNET Message-ID: <0096C55B.7F557080.8961@WKUVX1.BITNET> Subject: Re: MX V3.3 is now available!! "prof. Leonardo Lazarte" writes: > >Now let me do a very basic question. Hunter said: >>You can get MX V3.3 via anonymous ftp from ftp.spc.edu in [.MX.MX033]. >>The file MX033.ZIP is a Zip archive.... > > But, (blush) How do I use "unzip.exe" in VMS? > If I "run" it, I get only a screen saying how it should be used. >If I use /input and /output, I get the same screen, now in the >output file. If I do "run unzip.exe etc" I get a "try with less >parameters" message. Which is the correct syntax? > You must define a foreign symbol: $ unzip :== $dev:[dir]unzip.exe where dev:[dir] is the device and directory in which unzip.exe is located. Then just: $ unzip mx033 UNZIP.EXE can be found on ftp.spc.edu in [.MX] (and [.MACRO32]). Sources and .EXEs for ZIP19P1 and UNZIP50P1 for VMS can be found on ftp.spc.edu in [.MACRO32.SAVESETS] as ZIP19P1.ZIP and UNZIP50P1.ZIP. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Tue, 11 May 1993 08:08:28 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 08:08:15 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096C55B.E35CBD40.8965@WKUVX1.BITNET> Subject: Another ftp site Henry Miller has graciously put MX up on his FTP server too (thanks, Henry!). If you live in the Western U.S., you can find it on SACUSR or SACWMS.MP.USBR.GOV under [.ANONYMOUS.MX033]. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Tue, 11 May 1993 08:09:22 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 08:09:03 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, claus@HERACC.DESY.DE Message-ID: <0096C55C.0029C940.8967@WKUVX1.BITNET> Subject: RE: no RFC header on mail from listserver Matthias Clausen DESY -KRYK- / D-Hamburg writes: > >Many colleagues are complaining about the set of RFC header informations >even when they receive a mail from the local MX distribution list. >Is there a way to leave out all these informations or -at least- place >them at the end of the message? > You can use MCP SET LOCAL to specify that headers should be placed at the end of incoming messages instead of at the top.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Tue, 11 May 1993 08:16:56 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, ake@DAYTON.SAIC.COM Subject: Re: MX V3.3 is now available!! Date: 11 May 1993 08:55:00 -0400 Message-ID: <1so7n4$rgf@dayub.dayton.saic.com> To: MX-List@WKUVX1.BITNET prof. Leonardo Lazarte (LLAZARTE@BRUNB.BITNET) wrote: : On Mon, 10 May 1993 15:20:11 CDT Hunter Goatley said: : >Message Exchange (MX) V3.3 is hereby officially released. : Congratulations, and Thanks. : Now let me do a very basic question. Hunter said: : >You can get MX V3.3 via anonymous ftp from ftp.spc.edu in [.MX.MX033]. : >The file MX033.ZIP is a Zip archive.... : But, (blush) How do I use "unzip.exe" in VMS? : If I "run" it, I get only a screen saying how it should be used. : If I use /input and /output, I get the same screen, now in the : output file. If I do "run unzip.exe etc" I get a "try with less : parameters" message. Which is the correct syntax? Define unzip as a foreign command. Let's say unzip resides in the directory disk1:[zip]unzip.exe. You define the command as: $ unzip :== $disk1:[zip]unzip The dollar sign in front of the device name is important. You then execute the unzip program as: $ unzip mx033.zip -Earle -- Earle Ake Science Applications International Corporation - Dayton Ohio ----------------------------------------------------------------------- Internet: NSI-DECnet (SPAN): 28276::ake ================================================================================ Archive-Date: Tue, 11 May 1993 08:26:15 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 09:17:11 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET, dragon@NSCVAX.PRINCETON.EDU To: MX-List@WKUVX1.BITNET CC: LLAZARTE@BRUNB.BITNET Message-ID: <0096C565.84AB8380.19434@nscvax.princeton.edu> Subject: Re: MX V3.3 is now available!! Prof. Leonardo Lazarte writes: On Mon, 10 May 1993 15:20:11 CDT Hunter Goatley said: >>Message Exchange (MX) V3.3 is hereby officially released. > > > > Congratulations, and Thanks. > >Now let me do a very basic question. Hunter said: >>You can get MX V3.3 via anonymous ftp from ftp.spc.edu in [.MX.MX033]. >>The file MX033.ZIP is a Zip archive.... > > But, (blush) How do I use "unzip.exe" in VMS? > If I "run" it, I get only a screen saying how it should be used. >If I use /input and /output, I get the same screen, now in the >output file. If I do "run unzip.exe etc" I get a "try with less >parameters" message. Which is the correct syntax? > Define it as a "foreign" command; e.g. $ UNZIP:==$SYS$LOGIN:UNZIP.EXE Note that the '$' preceding the file specification is required. You can't use RUN because the RUN command takes exactly one parameter, the name of the image to be run. A foreign command can take any number of parameters. ************************************************************************* * * * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Tue, 11 May 1993 08:52:34 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 09:47:36 EDT From: Ian Vaz Reply-To: MX-List@WKUVX1.BITNET, ian@MARS.SENECAC.ON.CA To: mx-list@WKUVX1.BITNET CC: ian@mars.senecac.on.ca Message-ID: <0096C569.C48B4D60.17193@mars.senecac.on.ca> Subject: Sending mail on the command line-->Thanx! Hello, Just a short note of thanx together with the compiled responses for all those who are interested. Question: How to do: $ mail filename.txt username Using MX: $ mail filename.txt "mx%""username@domain""" (Method 1) THANX: Hunter Goately and Richard Gilbert. Using MX: $ mail filename.txt mx%"""username@domain""" (Method 2) THANX: Dan Wing Regards, Ian Vaz, Seneca College, Ph:(416) 491-5050, Ext. 7252 e-mail: ian@mars.senecac.on.ca OR ian@phobos.senecac.on.ca ================================================================================ Archive-Date: Tue, 11 May 1993 10:06:39 CDT Sender: list-mgr@WKUVX1.BITNET From: makinc@hhcs.gov.au Reply-To: MX-List@WKUVX1.BITNET, makinc@HHCS.GOV.AU Subject: Mail<->News fixes. Message-ID: <1993May11.140144.745@hhcs.gov.au> Date: 11 May 93 14:01:44 +1000 To: MX-List@WKUVX1.BITNET The mail<->news gateway included as part of the [.contrib] directory has a small problem. It can't handle mail messages with no Message-ID: header. Not all mailers include a message id in the message. I'm using Eudora and it certainly doesn't. :-( News barfs when it gets a "news" batch that doesn't have a Message-ID: field. I have modified GATEMAIL.C to produce a message id and add it to the message if the message doesn't already have one. The message id created is made up from the time() function converted to hex and the contents of the logical MX_GATE-ID. I have this logical set on my system to "mail-to-news.hhcs.gov.au" so that there is no chance of an overlap of IDs with NEWS or anything else. Below is the output of a DIFF run on GATEMAIL.C-OLD which is the GATEMAIL from the MX v3.1c distribution and GATEMAIL.C which has my mods. The SITE_DELIVER.COM file also has a problem. It is for MX v2.3 and the "Pn" parameters delivered to the SITE-DELIVER.COM file have changed. P1 is now P2 and so on. If anyone is interested I'll bottle up my system where I have both the news<->mail gateway and the digest software working and make it available. The GATEMAIL diff. -+ V --------- Cut Here ---------------------------------------------- $ diff gatemail.c gatemail.c-old ************ File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C;20 16 #include time 17 #include unixlib 18 ****** File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C-OLD;1 16 ************ ************ File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C;20 22 static unsigned mpid; 23 24 main(int argc, char **argv) { ****** File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C-OLD;1 20 main(int argc, char **argv) { ************ ************ File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C;20 71 mpid = 0; 72 while (get_head(line)) { /* look for first null line */ ****** File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C-OLD;1 67 while (get_head(line)) { /* look for first null line */ ************ ************ File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C;20 75 if (strncmp(line,"Message-ID: ", 12) == 0 ) { 76 fputs(line,bfd); 77 mpid = 1; 78 continue; } 79 if (strncmp(line,"Received: ", 10) == 0 )continue; ****** File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C-OLD;1 70 if (strncmp(line,"Received: ", 10) == 0 )continue; ************ ************ File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C;20 85 if (!mpid) 86 fprintf(bfd, 87 "Message-ID: <%x@%s>\n",time(NULL),getenv("MX_GATE_ 88 89 fputs("\n",bfd); /* mark end of headers */ ****** File DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C-OLD;1 76 fputs("\n",bfd); /* mark end of headers */ ************ Number of difference sections found: 5 Number of difference records found: 13 DIFFERENCES /IGNORE=()/MERGED=1- DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C;20- DISK$USER_UUCP:[UUCP.WORK.MAIL-NEWS]GATEMAIL.C-OLD;1 ----------- End ------------------------------------------- Carl. ================================================================================ Archive-Date: Tue, 11 May 1993 10:47:27 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, munroe@DMC.COM Subject: Re: MX V3.3? Message-ID: <1993May11.071529.1588@dmc.com> Date: 11 May 93 07:15:29 EDT To: MX-List@WKUVX1.BITNET In article <1993May10.193702.6728@gandalf.ca>, dhuddles@gandalf.ca (David Huddleson) writes: > Oh, and just a simple question. I have V3.1C already running. Should I install > MX 3.3 as a fresh installation into a NEW directory, or can I specify the > existing directory structure of 3.1C. (Will I retain my MXCONFIG files etc. is > what I am trying to say here!!) I installed MX 3.3 on top of an existing 3.1 installation with no problems. Your milage may vary. -- 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: Tue, 11 May 1993 10:59:33 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 10:59:08 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096C573.C2F75B60.9020@WKUVX1.BITNET> Subject: Another ftp thing If you have trouble getting the MX033.ZIP file, I've broken out the pieces into separate .ZIP files on riscy.cc.utexas.edu under [.MX033.SAVESETS]. For example, MX033.A is MX033-A.ZIP, etc. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Tue, 11 May 1993 11:26:11 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <27543.9305111540@diana.ecs.soton.ac.uk> Date: Tue May 11 15:38:10 1993 From: M.Zwolinski@ecs.soton.ac.uk Reply-To: MX-List@WKUVX1.BITNET, M.Zwolinski@ECS.SOTON.AC.UK To: mx-list@WKUVX1.BITNET Subject: unsubscribe UNSUBSCRIBE -- Dr Mark Zwolinski mz@ecs.soton.ac.uk Department of Electronics and Computer Science Tel. (0703) 593528 University of Southampton Fax. (0703) 593045 Southampton SO9 5NH, UK ================================================================================ Archive-Date: Tue, 11 May 1993 16:30:11 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: Can MX warn user about delivery problems sooner Date: 11 May 1993 17:13:32 GMT Message-ID: <1somrsINN5h9@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET, carl@SOL1.GPS.CALTECH.EDU To: MX-List@WKUVX1.BITNET In article <0096C4B2.4C3EB840.20557@SHSU.edu>, "George D. Greenwade" writes: =Carl suggested including this in the SYS$SYLOGIN.COM file (or a file called =by it). Certainly, this is a possibility and this would certainly make the =pass universal. However, be sure to include something which allows it to =be turned off by privileged users. I have the command: $ IF F$SEARCH("SYS$LOGIN:LOGIN.NO") .NES. "" THEN EXIT early in SYS$SYLOGIN. =I would HATE to go through our queue =everytime I logged in and, if I'm not mistaken, even LOGIN/NOCOMMAND still =reads the SYS$SYLOGIN file. That's correct. -------------------------------------------------------------------------------- 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, 11 May 1993 22:46:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 17:06:03 CDT From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET, bed_gdg@SHSU.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096C5A7.04F0D220.30890@SHSU.edu> Subject: Re: MX V3.3 is now available!! On Tue, 11 May 1993 08:05:27 CDT, Hunter Goatley posted (among others, but I elect to pick on Hunter for this one specifically): > > But, (blush) How do I use "unzip.exe" in VMS? > > If I "run" it, I get only a screen saying how it should be used. > >If I use /input and /output, I get the same screen, now in the > >output file. If I do "run unzip.exe etc" I get a "try with less > >parameters" message. Which is the correct syntax? > > > You must define a foreign symbol: > > $ unzip :== $dev:[dir]unzip.exe > > where dev:[dir] is the device and directory in which unzip.exe is located. > Then just: > > $ unzip mx033 > > UNZIP.EXE can be found on ftp.spc.edu in [.MX] (and [.MACRO32]). Sources > and .EXEs for ZIP19P1 and UNZIP50P1 for VMS can be found on ftp.spc.edu in > [.MACRO32.SAVESETS] as ZIP19P1.ZIP and UNZIP50P1.ZIP. As a good rule of thumb (which can save enormous grief, IMO), you should use either the -t or -v options prior to plain and away using UNZIP FILE. Eiter of these will (a) give you a listing of the files and directories to be created, and (b) verify (especially with the -t option) that the files will unzip properly. Files sometimes get corrupted in ftp transfers for all sorts of bizarre reasons (primarily from forgetting to set the mode to binary prior to the download for zip files). Also, while I trust Hunter's distributions (always right, it seems), I still like to look at them to see what to expect since ZIP can really compress stuff and killing off a quota isn't exactly fun stuff. As we handle an enormous amount of traffic here, files which we accept into our archives which we coordinate with two oter sites are generally tested in at least this rudimentary step. It's my guess that we see about 10% of the submissions which are corrupt before we even see them for archiving purposes. Thus, my strongly recommended steps are to define it as a foriegn symbol (as discussed), then $ unzip -t file $ unzip -v file $ unzip file Off of my soapbox for now (but trying to make your life a little easier), 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 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% (and yes, I will update the ZIP.WHERE file and all others which haven't been updated on Niord tomorrow -- sorry about that, slipped through the cracks somehow). ================================================================================ Archive-Date: Wed, 12 May 1993 00:27:02 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Can MX warn user about delivery problems sooner Message-ID: <1993May11.213605.1@molbiol.ox.ac.uk> From: jasper@molbiol.ox.ac.uk Reply-To: MX-List@WKUVX1.BITNET, jasper@MOLBIOL.OX.AC.UK Date: 11 May 93 21:36:05 BST To: MX-List@WKUVX1.BITNET In article <1993May5.213922.1765@mala.bc.ca>, dunnett@mala.bc.ca (Malcolm Dunnett) writes: > > Is there any way to get MX to notify the sender that it's having trouble > delivering a message? > > The problem is that people often send messages with incorrect addresses, > but because our Internet link is sometimes unreliable ( it's been out > for several days at a time ) I've got the "retry" limits set to 4 or 5 > days. This means that it takes that long for the sender to be informed that > their message couldn't be sent. For this particular one (ie wrong address) why not set the number of DNS failure retries for the SMTP agent to be 0? then if the address is wrong the mail bounces back immediately (assuming you don't send it all out to a mailserver). Of course if the remote node has dropped out of your DNS then you will get this too, but our discerning users decided this was preferable to a two day wait for typo's! How well this works for you depends on the quality of you local DNS service I guess. Over here it can be a problem sometimes. Looking at you statement again, I guess your Internet link is a much bigger problem than ours.... time to find a new phone company I guess. > It would be nice if MX could send the user a notification after a small > number of failures ( eg 3 ) that it was having trouble delivering the > message, and that it would retry for N days ( or whatever ). This would > alert the user that there was a problem, and they could be alerted to > check for correct addressing. The final "non-delivery" report would still > be delivered when the message expired. > > Is it possible to set MX us to do this, if not is this a reasonable thing > to ask for in a future release? Sounds good to me too, but I don't see how you will ever differentiate a mistyped address from a DNS problem. Though I like this solution better than my above suggestion. > -- > ============================================================================= > Malcolm Dunnett Malaspina College Email: dunnett@mala.bc.ca > Computer Services Nanaimo, B.C. CANADA V9R 5S5 Tel: (604)755-8738 Jasper Rees Oxford University Molecular Biology Data Centre and The Sir William Dunn School of Pathology jasper@molbiol.ox.ac.uk ================================================================================ Archive-Date: Wed, 12 May 1993 19:13:33 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 12 May 93 14:00:48 -0400 Message-ID: <9305121800.AA03944@genrad.com> From: Reply-To: MX-List@WKUVX1.BITNET, dongray@GENRAD.COM X-MX-Warning: Warning -- Invalid "To" header. To: "mx-list%wkuvx1.bitnet@cunyvm.cuny.edu" Subject: Forcing the correct From: address via a gateway? OK, the problem is this... My machines are not directly connected to Internet so I have to use a gateway machine, which means I have to use addresses like... co6301::"mx-list%wkuvx1.bitnet@cunyvm.cuny.edu" Now I had hoped that by a combination of rewrite rule... define rewrite "<{user}@{host}.bitnet>" - "<""co6301::\""{user}%{host}.bitnet@cunyvm.cuny.edu\""""@cd3101>" ... and disabling percent-hack handling in the router, I could just use... mx-list@wkuvx1.bitnet The problem is that the rewritten address is unacceptable to the gateway, over which I have no control. The generated error (which I had to pull out of [queue.*]) is > ----- Transcript of session follows ----- ><<< RCPT To: ><<< DATA >>>> MAIL From: ><<< 501 Syntax Error. Special chars only with Escape Char >554 ... Remote protocol error: Bad file number > > ----- Unsent message follows ----- >Received: from CD3101.DECnet MAIL11D_V3 by genrad.com (5.57) > id AA03814; Wed, 12 May 93 13:50:07 -0400 >Date: Wed, 12 May 93 13:50:05 -0400 >Message-Id: <9305121750.AA03814@genrad.com> >From: cd3101::MX%"dongray@cd3101" >To: "MX-LIST%WKUVX1.bitnet@cunyvm.cuny.edu" >Subject: Rewrite rules > > [text] Obviously, it doesn't like the From: address. Is there any way I can force MX 3.3 (I'm about to upgrade from 3.2) to generate an address without the MX% in it, i.e. just CD3101::DONGRAY instead of CD3101::MX%"dongray@cd3101"? Or any other suggestion? (Other than just carry on specifying the addresses in full!) BTW, the reason I had to pull the message out of the [QUEUE.*] was that MX decided it couldn't deliver it and was in the process of bouncing it back to CO6301::MAILER-DAEMON ... >Note: this message was generated automatically. > >Problem occurred during message routing for the following: > >Address: (originally: ) >Error: Invalid address. > >Message follows. > >Received: by cd3101 (MX V3.2) id 1345; Wed, 12 May 1993 18:50:35 BST >Sender: "co6301::\"MAILER-DAEMON\""@cd3101 >Date: Wed, 12 May 1993 18:50:31 BST >From: Mail Delivery Subsystem <"co6301::\"MAILER-DAEMON\""@cd3101> >X-MX-Warning: Warning -- Invalid "To" header. >To: >X-VMSmail-To: >Message-ID: <0096C67E.C72A0919.1345@cd3101> >Subject: Returned mail: Remote protocol error > > ----- Transcript of session follows ----- ><<< RCPT To: [etc.] Oh, the joys of mail systems ... :-) -------------------------------------------------------------------------------- Name :Derek Dongray, Systems Manager, GenRad Ltd. Phone :061 486 1511 InterNet : Dongray@GenRad.com UKnet : Derek.Dongray@GenRad.co.uk PSS : 234261600119::Dongray CompuServe : 70374,2745 Address : Monmouth House, Monmouth Road, Cheadle Hulme, Cheshire, SK8 7AY, UK. ================================================================================ Archive-Date: Wed, 12 May 1993 20:44:49 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET, shuford@CS.UTK.EDU Subject: Re: America OnLine creates infinite mail loop Date: 12 May 1993 21:17:24 GMT Message-ID: <1srph4INN5c7@CS.UTK.EDU> Keywords: RFC822, RFC821, SMTP, headers, America OnLine, AOL, mailing list, MX To: MX-List@WKUVX1.BITNET Brief recap of a situation: I maintain the Info-Stratus mailing list, which is based on an Internet host. An America OnLine user was subscribed to the Info-Stratus list. For some reason, during a recent weekend his mailbox became unavailable for delivery of electronic mail. When the inbound message from the mailing list was bounced back, it was sent back to the RFC822 "Reply-To:" address. This was set up to be the address of the mailing list, so an infinite mail loop occurred, which required manual intervention to stop. The looped messages were also propagated automatically into the Usenet newsgroup "comp.sys.stratus". It seems that the America OnLine Internet e-mail gateway violates protocol and convention in this behavior, and initially the technical staff of AOL did not respond to my complaint. In article <9305102232.AA05775@dave.dial.intercon.com>, dave@intercon.com (Dave Saunders) writes: > > One item to note is that AOL asked users to not subscribe to *any* > mailing list mail when they announced their Internet Mail gateway. I have now received an UNofficial communication about the policies of America OnLine (AOL) and the "aol.com" domain. This comes from Mike Ward , who is the "Internet Mail Gateway Discussion Board host", which I suppose is equivalent to a "sysop" or "conference moderator" in the parlance of some other commercial online systems. He is therefore not an on-site member of the AOL staff. Mike sent the following: | | Here's the text on the topic in the AOL Internet mail help area - | | "America Online does not support Internet mailing lists because of the | large volume of incoming mail these lists generate. Please do not | subscribe to any mailing lists using your America Online address." Regardless of this user policy, it is still uncivilized to violate the protocols of the network. Mike did agree to forward my complaint to the people who maintain the AOL gateway. Dave Saunders also writes: > > AOL is not *on* the Internet, but has either a UUCP or SLIP account with > PSI to get their mail. Judging from the SMTP mail headers, it must be SLIP. > This is not high speed networking folks and they should not be expected to > handle that kind of mail traffic for their customers. Of course they should > fix their mailer, but on the other hand they never said you could safely use > mailing lists now did they? As a mere mailing-list maintainer, I have no practical way to find out what the gateway capacities or administrative policies of America OnLine are. Nevertheless, I have dropped all subscriptions to AOL users, and I suggest that all mailing-list maintainers on the Internet be similarly prudent, if your list address appears in the "Reply-To:" field. -- ...Richard S. Shuford | "A prudent man sees danger and takes refuge, ...shuford@cs.utk.edu | but the simple keep going and suffer for it." ...Info-Stratus contact| Proverbs 22:3 NIV ================================================================================ Archive-Date: Wed, 12 May 1993 21:46:38 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 12 May 1993 21:46:12 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET To: fsupdate@WKUVX1.BITNET CC: mx-list@WKUVX1.BITNET, macro32@WKUVX1.BITNET, info-zip@WKUVX1.BITNET Message-ID: <0096C697.51FA06E0.9638@WKUVX1.BITNET> Subject: WKU Internet gateway change In an effort to help alleviate problems we've had with BITNET backlogs, I've changed WKU's Internet gateway from UKCC to ULKYVM. If you're on the Internet, mail from here will now be percent-hacked with a return address of xxx%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU. While ugly, the address should satisfy Internet purists who say .BITNET addresses should never reach the Internet unless they're hacked. In any case, the change eliminates one BITNET hop, the one that's been responsible for the delays for the past week and a half. ULKYVM is the next BITNET node from WKU, so the mail delays should be significantly reduced. There are plans to increase the speed of the line from 9600 baud to a whopping 19.2K in the next few weeks. Unfortunately, that's the highest speed we can do with the current equipment. Still, every little bit helps, and I suspect that the combination should help dramatically. FILESERV@WKUVX1 should be in operation again Thursday afternoon, if all goes well. Thanks for your patience! Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Thu, 13 May 1993 04:37:08 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 13 May 1993 19:30:59 +10:00:00 From: bellamy@commerce.uq.edu.au Reply-To: MX-List@WKUVX1.BITNET, bellamy@COMMERCE.UQ.EDU.AU To: mx-list@WKUVX1.BITNET Message-ID: <0096C74D.98FE24C0.6748@covax.commerce.uq.oz.au> Subject: MX033 on ftp.spc.edu corrupt ?? 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: MX033 on ftp.spc.edu corrupt ?? Message-ID: From: bellamy@commerce.uq.edu.au (David Bellamy) Date: 13 May 93 19:30:55 +1000 Followup-To: comp.mail.mx Distribution: world,local Organization: The University of Queensland Nntp-Posting-Host: test1.commerce.uq.oz.au Lines: 42 I have tried a couple of times to get mx033.zip from ftp.spc.edu. Initially did the right thing by or satellite link and used the Alex server on archie.au, that failed with a corrupt .zip. Then got it directly and it still failed. Yes, I did a binary transfer! Several times :-) This is the sort of thing I get $unzip mx033 [mx033.zip] comment: Message Exchange V3.3 [7-MAY-1993] Copyright 1993 by MadGoat Software. All rights reserved. (VMS file attributes saved---use UnZip v5.x+ to unzip) (You can ignore any version mismatch warnings from Un warning: extra 42 bytes at beginning or within zipfile (attempting to process anyway) file #0: bad zipfile offset (can't find local header sig) file #1: bad zipfile offset (can't find local header sig) file #2: bad zipfile offset (can't find local header sig) file #3: bad zipfile offset (can't find local header sig) file #4: bad zipfile offset (can't find local header sig) file #5: bad zipfile offset (can't find local header sig) file #6: bad zipfile offset (can't find local header sig) And so on. The only file that is OK is the release notes (the last one??) The zip is the one on ftp.spc.edu (98 blocks long). I also tried an older version which had definitely worked before - no dice. Any ideas? _________________________________________________________________ David Bellamy. Deparment of Commerce. The University of Queensland. Australia. Internet: bellamy@commerce.uq.edu.au ================================================================================ Archive-Date: Thu, 13 May 1993 04:58:20 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 13 May 93 9:51 GMT From: "UK TeX Archive Manager " Reply-To: MX-List@WKUVX1.BITNET, SYSTEM@TEX.AC.UK To: MX-LIST%BITNET.WKUVX1@NSFNET-RELAY.AC.UK Subject: RE: WKU Internet gateway change In message <0096C697.51FA06E0.9638@WKUVX1.BITNET> dated Wed, 12 May 1993 21:46:12 CDT (to, inter alia, the MX-List), Hunter Goatley wrote: >In an effort to help alleviate problems we've had with BITNET >backlogs, I've changed WKU's Internet gateway from UKCC to ULKYVM. >If you're on the Internet, mail from here will now be percent-hacked >with a return address of xxx%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU. >While ugly, the address should satisfy Internet purists who say >.BITNET addresses should never reach the Internet unless they're >hacked. I had already realized that something had happened, because mail from the MX-List had started to arrive with only the list's name as the return address, whereas (ever since Hunter's modifications of last month, which introduced a sensible Reply-To) all other recent postings had included both the list's name and that of the message originator. However, something has gone wrong with this percent-hack: either MLF can't generate the requisite Reply-To, or there was something wrong with the percent hacking algorithm. I've included the complete headers as received here at the end of this message, but most relevant are these lines: >Reply-To: MX-List@BITNET.WKUVX1 >PP-Warning: Parse error in original version of preceding line >Original-Reply-To: MX-List%WKUVX1.BITNET, > @ULKYVM.LOUISVILLE.EDU goathunter@WKUVX1.BITNET Looks like the comma is being inserted at the wrong place (just before the '@') and NOT being inserted where it should (between the two mailboxes). I'll say again one observation I made when MLF first started generating the dual-address Reply-Tos: it ought to do this only if the originator of the message is known not to be a subscriber to the list. That way, any replies sent in response to an incoming message will just go back to the list (and thence to the originator, as a subscriber). On the other hand, if the originator *isn't* subscribed, then the dual address will ensure that replies go back to him/her as well as to all the subscribers to the list (who will have received copies of the original message, of course). My main objection to the practice of always including the originator's address is that he/she then receives TWO copies of every response to his/her original message: a waste of bandwidth, and time spent reading!! Anyway, following my signature are the RFC-822 headers (actually, Grey-Book Mail, following processing in the Internet<->Janet gateway, which has big- endian'ed most addresses) of Hunter's original posting, as recirculated by MLF. Brian {Hamilton Kelly} System Manager for the UK TeX Archive at Aston University --------------------------------------------------------------------------- Via: UK.AC.NSFNET-RELAY; Thu, 13 May 93 2:55 GMT Received: from ulkyvm.louisville.edu by sun3.nsfnet-relay.ac.uk with Internet SMTP id ; Thu, 13 May 1993 03:53:45 +0100 Received: from ULKYVM.LOUISVILLE.EDU by ULKYVM.LOUISVILLE.EDU (IBM VM SMTP V2R1) with BSMTP id 2527; Wed, 12 May 93 22:51:50 EDT Received: from WKUVX1.BITNET by ULKYVM.LOUISVILLE.EDU (Mailer R2.08 R208004) with BSMTP id 8100; Wed, 12 May 93 22:51:49 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: list-mgr@BITNET.WKUVX1 Original-Sender: list-mgr Date: Wed, 12 May 1993 21:46:12 CDT From: Hunter Goatley Reply-To: MX-List@BITNET.WKUVX1 PP-Warning: Parse error in original version of preceding line Original-Reply-To: MX-List%WKUVX1.BITNET, @ULKYVM.LOUISVILLE.EDU goathunter@WKUVX1.BITNET To: fsupdate@BITNET.WKUVX1 CC: mx-list@BITNET.WKUVX1, macro32@BITNET.WKUVX1, info-zip@BITNET.WKUVX1 Message-ID: <0096C697.51FA06E0.9638@WKUVX1.BITNET> Subject: WKU Internet gateway change Sender: list-mgr%BITNET.WKUVX1@EDU.LOUISVILLE.ULKYVM ================================================================================ Archive-Date: Thu, 13 May 1993 07:05:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 13 May 1993 07:04:41 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, SYSTEM@TEX.AC.UK Message-ID: <0096C6E5.572129C0.9744@WKUVX1.BITNET> Subject: RE: WKU Internet gateway change "UK TeX Archive Manager " writes: > >However, something has gone wrong with this percent-hack: either MLF can't >generate the requisite Reply-To, or there was something wrong with the percent >hacking algorithm. I've included the complete headers as received here at the >end of this message, but most relevant are these lines: > >>Reply-To: MX-List@BITNET.WKUVX1 >>PP-Warning: Parse error in original version of preceding line >>Original-Reply-To: MX-List%WKUVX1.BITNET, >> @ULKYVM.LOUISVILLE.EDU goathunter@WKUVX1.BITNET > >Looks like the comma is being inserted at the wrong place (just before the '@') >and NOT being inserted where it should (between the two mailboxes). > Thanks for letting me know---I hadn't seen this because, naturally, my mail doesn't go that way. The problem is definitely caused by the mailer at ULKYVM. I've contacted the mail guy there to see about getting it fixed (or to have the percent-hacking disabled). In the meantime, assuming they can/will fix it, I've changed MX-List so that replies only go back to the list. >My main objection to the >practice of always including the originator's address is that he/she then >receives TWO copies of every response to his/her original message: a waste of >bandwidth, and time spent reading!! > Noted. That's something I wanted to experiment with. The *best* thing would be if VMS Mail asked you if you wanted to reply to all addresses or not. Oh well. I haven't had time to write my VMS Mail replacement.... 8-) Thanks again for letting me know about the problem! Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Thu, 13 May 1993 07:08:41 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 13 May 1993 07:08:19 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET, bellamy@COMMERCE.UQ.EDU.AU Message-ID: <0096C6E5.D91F0E60.9746@WKUVX1.BITNET> Subject: RE: MX033 on ftp.spc.edu corrupt ?? bellamy@commerce.uq.edu.au writes: > >I have tried a couple of times to get mx033.zip from ftp.spc.edu. >Initially did the right thing by or satellite link and used the Alex server >on archie.au, that failed with a corrupt .zip. Then got it directly and it >still failed. > >Yes, I did a binary transfer! Several times :-) > Strange then. Have you tried niord.shsu.edu or riscy.cc.utexas.edu? The .ZIP file on ftp.spc.edu is OK.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Fri, 14 May 1993 06:12:20 CDT Sender: list-mgr@WKUVX1.BITNET Date: 13 May 1993 20:41:57 -0400 (EDT) From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Forcing the correct From: address via a gateway? To: mx-list%wkuvx1.bitnet@garnet.nist.gov, dongray@GENRAD.COM CC: hardis@garnet.nist.gov Message-ID: <0096C757.82890B60.13479@garnet.nist.gov> Content-Transfer-Encoding: 7BIT > OK, the problem is this... My machines are not directly connected to > Internet so I have to use a gateway machine, which means I have to use > addresses like... > > co6301::"mx-list%wkuvx1.bitnet@cunyvm.cuny.edu" > > Now I had hoped that by a combination of rewrite rule... > > define rewrite "<{user}@{host}.bitnet>" - > "<""co6301::\""{user}%{host}.bitnet@cunyvm.cuny.edu\""""@cd3101>" > > ... and disabling percent-hack handling in the router, I could just use... > > mx-list@wkuvx1.bitnet Am I missing something? If is a good address on your system, then why isn't: DEFINE REWRITE "<{user}@{host}.bitnet>" - "" the corresponding rewrite rule? Remember, it would have to come before a generic rewrite rule for Internet addresses, such as: DEFINE REWRITE "<{user}@{host}>" "" There are two points I don't understand, though. I don't see how MX can handle an address of the form . Perhaps this is because I don't use DECNet. Also, I don't understand what you mean by disabling percent-hacking in the router. ================================================================================ Archive-Date: Fri, 14 May 1993 07:28:02 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 14 May 93 08:22:06 -0400 Message-ID: <9305141222.AA14533@genrad.com> From: Reply-To: MX-List@WKUVX1.BITNET X-MX-Warning: Warning -- Invalid "To" header. To: "mx-list%wkuvx1.bitnet@cunyvm.cuny.edu" CC: Subject: Re: Forcing the correct From: address via a gateway? > Am I missing something? If > is a good address on your system, then why isn't: > > DEFINE REWRITE "<{user}@{host}.bitnet>" - > "" > > the corresponding rewrite rule? Remember, it would have to come before a > generic rewrite rule for Internet addresses, such as: > > DEFINE REWRITE "<{user}@{host}>" "" > > There are two points I don't understand, though. I don't see how MX can > handle an address of the form . MX normally seems to successfully recognize NODE::{anything} addresses as LOCAL and deliver them via DECnet. the problem is that with the following (only) rewrite rule Rewrite "<{user}@{host}.bitnet>" => "" and the following paths Domain-to-path mappings: Domain="cd3101", Path=Local Domain="*", Path=DECnet_SMTP, Route="CD4201" I get ... 14-MAY-1993 13:03:58.93 %PROCESS, Processing entry number 1439 14-MAY-1993 13:03:59.02 %PROCESS, Status from READ_INFO was 00000001 14-MAY-1993 13:03:59.02 %PROCESS, Message originated in VMS Mail. 14-MAY-1993 13:03:59.70 %PROCESS, Finished VMSmail-origin preprocessing. 14-MAY-1993 13:03:59.70 %PROCESS, Recipient #0: 14-MAY-1993 13:03:59.73 %REWRITE, Applying rewrite rule: <{user}@{host}.bitnet> => 14-MAY-1993 13:03:59.74 %FINDPATH, domain name matched path pattern * 14-MAY-1993 13:03:59.75 %PROCESS, Rewrote as - next hop CD4201, path 8 14-MAY-1993 13:04:00.02 %PROCESS, Adding to DNSMTP path: . 14-MAY-1993 13:04:00.43 %PROCESS, Path DNSMTP gets 1 rcpts, entry number 1440 I beleive that MX is mindlessly splitting the address at the "@", ignoring the fact that it's in quotes, and decides that a 'host' of 'cunyvm.cuny.edu"' matches the wildcard. Hence the attempt to rewrite the address with @cd3101 on it so that it gets recognised as Local. > Perhaps this is > because I don't use DECNet. Also, I don't understand what you mean by > disabling percent-hacking in the router. With percant hacking enabled (the default) a "%" will get converted to "@". This breaks the above rewrite rule because the point at which it gets applied seems to convert into which is invalid because it's got 2 "@"s. -------------------------------------------------------------------------------- Name :Derek Dongray, Systems Manager, GenRad Ltd. Phone :061 486 1511 InterNet : Dongray@GenRad.com UKnet : Derek.Dongray@GenRad.co.uk PSS : 234261600119::Dongray CompuServe : 70374,2745 Address : Monmouth House, Monmouth Road, Cheadle Hulme, Cheshire, SK8 7AY, UK. ================================================================================ Archive-Date: Fri, 14 May 1993 07:40:03 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 14 May 93 08:26:19 -0400 Message-ID: <9305141226.AA14627@genrad.com> From: Reply-To: MX-List@WKUVX1.BITNET X-MX-Warning: Warning -- Invalid "To" header. To: "mx-list%wkuvx1.bitnet@cunyvm.cuny.edu" Subject: Re: Forcing the correct From: address via a gateway? Actually can someone explaine why with the paths ... Domain-to-path mappings: Domain="cd3101", Path=Local Domain="CD*", Path=DECnet_SMTP Domain="DUMPY", Path=DECnet_SMTP Domain="*", Path=DECnet_SMTP, Route="CD4201" ... the following rewrite fails to match with cd3101? I thought that rewrite rules were applied before the search for a path, or have I missed something? 14-MAY-1993 13:23:24.38 %PROCESS, Processing entry number 1443 14-MAY-1993 13:23:25.05 %PROCESS, Status from READ_INFO was 00000001 14-MAY-1993 13:23:25.06 %PROCESS, Message originated in VMS Mail. 14-MAY-1993 13:23:26.01 %PROCESS, Finished VMSmail-origin preprocessing. 14-MAY-1993 13:23:26.01 %PROCESS, Recipient #0: 14-MAY-1993 13:23:26.02 %REWRITE, Applying rewrite rule: <{user}@{host}.bitnet> => <'co6301::"{user}%{host}.bitnet@cunyvm.cuny.edu"'@cd3101> to: 14-MAY-1993 13:23:26.03 %FINDPATH, domain name matched path pattern * 14-MAY-1993 13:23:26.03 %PROCESS, Rewrote as <'co6301::"XXX%XXX.bitnet@cunyvm.cuny.edu"'@cd3101> - next hop CD4201, path 8 14-MAY-1993 13:23:26.16 %PROCESS, Adding to DNSMTP path: <'co6301::"XXX%XXX.bitnet@cunyvm.cuny.edu"'@cd3101>. 14-MAY-1993 13:23:26.49 %PROCESS, Path DNSMTP gets 1 rcpts, entry number 1444 -------------------------------------------------------------------------------- Name :Derek Dongray, Systems Manager, GenRad Ltd. Phone :061 486 1511 InterNet : Dongray@GenRad.com UKnet : Derek.Dongray@GenRad.co.uk PSS : 234261600119::Dongray CompuServe : 70374,2745 Address : Monmouth House, Monmouth Road, Cheadle Hulme, Cheshire, SK8 7AY, UK. ================================================================================ Archive-Date: Fri, 14 May 1993 08:08:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 14 May 1993 08:00:35 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: goathunter@WKUVX1.BITNET Message-ID: <0096C7B6.503ABB40.11905@SHSU.edu> Subject: MX033 sets on Niord.SHSU.edu In addition to having the MX033 files available for retrieval from FILESERV@SHSU.BITNET (FILESERV@SHSU.edu) [SENDME MX033 in a mail message to our FILESERV will retrieve the 149-part distribution, as Hunter noted previously], we also have the ZIP sets available for ftp retrieval from Niord.SHSU.edu (192.92.115.8) in [FILESERV.MX033.ZIPSETS]. Prior to installing 3.3 yesterday, I UNZIP'ped the file MX033.ZIP (which has the VMSINSTAL'lable backup savesets in it; MX033.A, MX033.B,...,MX033.M in it) and went ahead and made these available in the anonymous ftp area, [FILESERV.MX], as well as the UNZIP'ped sources which reside in the directory tree rooted there. Niord is a MultiNet-based machine, which has Ehud Gavron's MODE LZ callable LZ Compress/Decompress module available for use with compatible hosts. The sources for this module (which is usable with VMS and AXP) are available in the directory [FILESERV.MULTINET_FTP_MODE_LZ] as individual files, or all collected into a single ZIP archive, FTP_MODE_LZ.ZIP. Finally, if you want to retrieve the one-file MFTU'ed ZIP archive, include: SENDME MULTINET_FTP_MODE_LZ in the body of a mail message to FILESERV@SHSU.BITNET (FILESERV@SHSU.edu). Finally, one aspect I forgot to tell Hunter about -- you can also get to the SHSU archives via SPAN. The host path to get to the directories is: UTSPAN::UTADNX::SHSU::MX_ROOT:[fileserv_directories_identified_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, 14 May 1993 09:17:09 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 14 May 1993 10:12:12 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: <0096C7C8.B3C335E0.13543@garnet.nist.gov> Subject: Re: Forcing the correct From: address via a gateway? > From: "Jonathan E. Hardis" Ouch!! > To: mx-list%wkuvx1.bitnet@garnet.nist.gov, dongray@GENRAD.COM EEE-Ah!! ================================================================================ Archive-Date: Fri, 14 May 1993 10:37:54 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 14 May 1993 10:37:40 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096C7CC.42300EE0.10165@WKUVX1.BITNET> Subject: Percent-hacking at UofL I'm still working with UofL to disable the percent-hacking that's going on. Does anyone here know how to disable percent-hacking in the Columbia Mailer (Mailer 2.08)? They're willing, but the guy doesn't know how to disable it. I assume that it can be done? Also (I don't know if I mentioned it or not): work is progressing to upgrade these BITNET links from 9600 to 19.2K. If the UofL problem has not been resolved by then, I'll probably switch back to UKCC. 19.2K: hoo-boy! We're moving now..... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Fri, 14 May 1993 15:45:44 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Percent-hacking at UofL Message-ID: Date: Fri, 14 May 1993 19:20:39 GMT To: MX-List@WKUVX1.BITNET Hunter Goatley writes: >Also (I don't know if I mentioned it or not): work is progressing to >upgrade these BITNET links from 9600 to 19.2K. If the UofL problem >has not been resolved by then, I'll probably switch back to UKCC. >19.2K: hoo-boy! We're moving now..... hunter, will a pair of high-speed modems help? lets have a benefit for the sake of hunter and WKUVX1. i will start by putting up the first $25 towards the purchase of a pair of fast modems for hunter's and his neighbor's machines. -- -- bob pasker -- rbp@netcom.com -- ================================================================================ Archive-Date: Sat, 15 May 1993 06:44:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 14 May 1993 23:42:40 +0200 From: pizzorno@vms.gmd.de Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096C839.EC26B84A.1882@vms.gmd.de> Subject: MX Shutdown Hello, Hunter, how about copying a file like this to sys$startup when MX is installed? Of course, it doesn't do much, but it makes it simpler and more "vms-style" when adding to system shutdown... (If more than one person takes care of the system(s), not every one has to know the details of each product... having a startup and a shutdown routine in the right directory makes some things easier...) .. Juan -----cut---- $! Shuts down the MX Message Exchange servers $ mcp :== $mx_exe:mcp $ mcp shutdown 'p1 ================================================================================ Archive-Date: Sat, 15 May 1993 07:05:48 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX V3.3 is now available!! Message-ID: <1993May11.215138.155@centurylub.com> Date: 12 May 93 02:51:38 GMT To: MX-List@WKUVX1.BITNET In article <12617751@MVB.SAIC.COM>, "prof. Leonardo Lazarte" writes: > But, (blush) How do I use "unzip.exe" in VMS? > If I "run" it, I get only a screen saying how it should be used. > If I use /input and /output, I get the same screen, now in the > output file. If I do "run unzip.exe etc" I get a "try with less > parameters" message. Which is the correct syntax? $ unzip :== $unzip.exe $ unzip etc WordMan -- -------------------------+------------------------------------------------------ Bret D. Wortman | "Is this the value you humans call...friendship?" wortman@centurylub.com | "Don't give me this Star Trek crap, it's too early wortman@decus.org | in the morning." Dave Lister, to Kryten. -------------------------+------------------------------------------------------ ================================================================================ Archive-Date: Sat, 15 May 1993 07:06:48 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX V3.3? Message-ID: <1993May12.111119.157@centurylub.com> Date: 12 May 93 16:11:19 GMT To: MX-List@WKUVX1.BITNET In article <0096C558.3198F4A0.8931@WKUVX1.BITNET>, Hunter Goatley writes: > writes: > >>Oh, and just a simple question. I have V3.1C already running. Should I install >>MX 3.3 as a fresh installation into a NEW directory, or can I specify the >>existing directory structure of 3.1C. (Will I retain my MXCONFIG files etc. is >>what I am trying to say here!!) >> > You can install it over the existing 3.1C. At least, you're > *supposed* to be able to.... 8-) > > Hunter Did it last night while watching DS9. Worked slicker than a whistle. Sure am glad *someone* knows how to make KITs that install correctly every time. Thanks, Hunter! How 'bout teaching a class for DECUS -- maybe some Digits would even show up.... ;-) WordMan -- -------------------------+------------------------------------------------------ Bret D. Wortman | "Is this the value you humans call...friendship?" wortman@centurylub.com | "Don't give me this Star Trek crap, it's too early wortman@decus.org | in the morning." Dave Lister, to Kryten. -------------------------+------------------------------------------------------ ================================================================================ Archive-Date: Sat, 15 May 1993 12:32:13 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 15 May 1993 12:32:01 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096C8A5.66272980.10597@WKUVX1.BITNET> Subject: Re: Percent-hacking at UofL writes: > >Hunter Goatley writes: >>Also (I don't know if I mentioned it or not): work is progressing to >>upgrade these BITNET links from 9600 to 19.2K. If the UofL problem >>has not been resolved by then, I'll probably switch back to UKCC. >>19.2K: hoo-boy! We're moving now..... > >hunter, will a pair of high-speed modems help? > Unforunately, probably not. Here's the deal: we have a 56K line to UofL that's split up into the 9600 baud line for BITNET and several interactive terminal lines. 19.2K is the fastest our current equipment (on both ends) can do. I suppose higher-speed modems that would work with our ISN (I think that's it) would work, but.... >lets have a benefit for the sake of hunter and WKUVX1. i will start >by putting up the first $25 towards the purchase of a pair of fast >modems for hunter's and his neighbor's machines. > 8-) I keep hoping that we'll get on the Internet soon. That's a long, sordid, political tale involving other schools in the state and an NSF grant proposal. No one wants to spend what little school money we have ($7 million of state funds cut from our budget in the last two school years) if there's a chance the NSF will cover it. But no one has any idea when or if the NSF will make up its mind. So here we sit. That's what I get for deciding to run my own FILESERV and some popular mailing lists while being far out on the BITNET fringe. 8-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Mon, 17 May 1993 20:21:44 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Missing Message-ID tags Message-ID: <1993May17.180612.182@kenyon.edu> From: oursler@kenyon.edu Reply-To: MX-List@WKUVX1.BITNET Date: 17 May 93 18:06:12 -0500 To: MX-List@WKUVX1.BITNET Hullo, Recently, while gatewaying several mailing-lists into local newsgroups for my convenience, I encountered a problem. It seems that messages from one of the lists (PMAIL) do not have message-id tags associated with them. This causes ANU News to be very unhappy and the messages cannot be posted. All of my other mailing list messages have message-ids tags. In fact, all my other Internet mail messages seem to have message-ids tags. I assume that it must be something the mailer at the other end does or doesn't do. Could someone explain who generates the message-id tags and the consequences of not having them? (Not much I'd imagine since the mail gets delivered just fine). Thanks in advance for any info.... - Miles - ------------------------------- Miles Oursler Manager of Networks and Systems Kenyon College oursler@kenyon.edu ------------------------------- ================================================================================ Archive-Date: Tue, 18 May 1993 01:13:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 18 May 1993 16:08:26 +1000 From: bellamy@commerce.uq.edu.au Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096CB1F.20CE15C0.7487@covax.commerce.uq.oz.au> Subject: Re: Missing Message-ID tags 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: Missing Message-ID tags Message-ID: From: bellamy@commerce.uq.edu.au (David Bellamy) Date: 18 May 93 16:08:22 +1000 Followup-To: comp.mail.mx References: <1993May17.180612.182@kenyon.edu> Distribution: world,local Organization: The University of Queensland Nntp-Posting-Host: test1.commerce.uq.oz.au Lines: 39 In article <1993May17.180612.182@kenyon.edu>, oursler%kenyon.edu@ULKYVM.LOUISVILLE.EDU wrote: > > Hullo, > > > Recently, while gatewaying several mailing-lists into > local newsgroups for my convenience, I encountered a problem. > > It seems that messages from one of the lists (PMAIL) do > not have message-id tags associated with them. This > causes ANU News to be very unhappy and the messages > cannot be posted. > > All of my other mailing list messages have message-ids > tags. In fact, all my other Internet mail messages seem > to have message-ids tags. I assume that it must be > something the mailer at the other end does or doesn't do. > > Could someone explain who generates the message-id tags > and the consequences of not having them? (Not much I'd > imagine since the mail gets delivered just fine). > This is perhaps a problem better addressed in news.software.anu-news, but since the solution is easy and it _may_ affect MX users using the mail<->news gateway: Just add the /genid qualifier to the add batch command. This will generate an id if the "Message-ID:" header is missing. This option was introduced in about 6.0-2 (about 3 to 4 years ago). The Message-ID: is generated by the sending mailer and supposed to be unique. ANU-News needs this as a key for its newsitem "database". _________________________________________________________________ David Bellamy. Deparment of Commerce. The University of Queensland. Australia. Internet: bellamy@commerce.uq.edu.au ================================================================================ Archive-Date: Wed, 19 May 1993 00:44:48 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Missing Message-ID tags Message-ID: <1993May19.132929.756@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 19 May 93 13:29:29 +1000 To: MX-List@WKUVX1.BITNET In article <0096CB1F.20CE15C0.7487@covax.commerce.uq.oz.au> , bellamy%commerce.uq.edu.au@ULKYVM.LOUISVILLE.EDU writes: > Just add the /genid qualifier to the add batch command. This will generate > an id if the "Message-ID:" header is missing. This option was introduced > in about 6.0-2 (about 3 to 4 years ago). I didn't know this option existed. :-( 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: Wed, 19 May 1993 00:44:53 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX Name Conversion Interface. Message-ID: <1993May19.133232.757@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 19 May 93 13:32:31 +1000 To: MX-List@WKUVX1.BITNET I've been playing with the Name Conversion interface in MX v3.1c. I'm a little confused as to what gets called when. I'm trying to rewrite addresses in the form CBR::MAKINC to makinc@cbr.hhcs.gov.au so I have to use the FULL_CONVERT function instead of just CONVERT however CONVERT is still needed. If I have both CONVERT and FULL_CONVERT which one gets called when? I assume CONVERT gets called for the "alias->username" conversion and FULL_CONVERT gets called for the "username->alias" conversion? Is this correct? Is this all that happens? 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: Wed, 19 May 1993 00:57:38 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Missing Message-ID tags Message-ID: <1993May19.132707.755@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 19 May 93 13:27:07 +1000 To: MX-List@WKUVX1.BITNET In article <1993May17.180612.182@kenyon.edu> , oursler@kenyon.edu writes: > Recently, while gatewaying several mailing-lists into > local newsgroups for my convenience, I encountered a problem. > > It seems that messages from one of the lists (PMAIL) do > not have message-id tags associated with them. This > causes ANU News to be very unhappy and the messages > cannot be posted. I had the same problem a coupel of weeks ago. > All of my other mailing list messages have message-ids > tags. In fact, all my other Internet mail messages seem > to have message-ids tags. I assume that it must be > something the mailer at the other end does or doesn't do. Message IDs are generated by the mailer. MX generates them for mail entering from VMS MAIL and the majority of Internet mailers generate them as well, however, I'm using Eudora on a Mac and it doesn't. :-( To fix it I changed the gatemail.c file so that if the message didn't have a message id it created one. I used a logical MX_GATE_ID to define the psuedo news node the ID comes from and I make it different to the ANU News node name to make sure it is unique. Here is the complete GATEMAIL.C file with the update; /* * Gatemail - a program to convert Mail messages from a mailing list into * News articles suitable for input to the ANU-NEWS ADD FILE * command. * * Copyright 1989 by Robert R. Sloane . * Permission is granted to anyone to make or distribute copies * of this program, provided that this copyright notice is * preserved. * * Updated to support MX by Ted Nieland * March 1991 * * Updated May 1993 to generate Message-ID's for messages that don't * have them. Carl Makin * */ #include #include #include time #include unixlib FILE *mfd; /* MAIL file */ FILE *bfd; /* NEWS Batch file */ static unsigned mpid; main(int argc, char **argv) { char line[1024]; int i; /* * make sure user gave us both file names and the newsgroup name. */ if (argc < 2) { printf("Usage: gtmail \n"); exit(SS$_NORMAL); } if (argc < 5) exit(SS$_INSFARG); /* * now open the input file */ if ( !(mfd=fopen(argv[1],"r")) ) { perror("can't open input file:"); exit(SS$_ABORT); } /* * and the output file */ if ( !(bfd=fopen(argv[2],"a")) ) { perror("can't open output file:"); exit(SS$_ABORT); } /* * now Start processing the mail message */ while ( get_head(line) ) { /* * check to see if this is the start of a new mail message * and if it is, process it. MX will Start the message with the * "Received: " part of the header */ if ( strncmp(line,"Received: ",10) == 0 ) { /* * now output the headers we want to keep */ fputs("#! rnews ???\n",bfd); /* output batch separator */ fputs("Path: ",bfd); fputs(argv[3],bfd); fputs("\n",bfd); fputs("Newsgroups: ",bfd); fputs(argv[4],bfd); fputs("\n",bfd); /* * go through the rest of the header of the message * drop any Path headers, received headers, and such that will * confuse NEWS. Any others just copy into the output file. */ mpid = 0; while (get_head(line)) { /* look for first null line */ if (strncmp(line,"Return-path: ",13) == 0 )continue; if (strncmp(line,"Newsgroups: ", 12) == 0 )continue; if (strncmp(line,"Message-ID: ", 12) == 0 ) { fputs(line,bfd); mpid = 1; continue; } if (strncmp(line,"Received: ", 10) == 0 )continue; if (strncmp(line,"X-To: ", 6) == 0 )continue; if (strncmp(line,"Path: ", 6) == 0 )continue; if (strncmp(line,"To: ", 4) == 0 )continue; fputs(line,bfd); } if (!mpid) fprintf(bfd, "Message-ID: <%x@%s>\n",time(NULL),getenv("MX_GATE_ID")); fputs("\n",bfd); /* mark end of headers */ } /* * if we get here, the headers are done, so copy each line of the text */ else { /* * Check each line, and if it looks like and NEWS Batch file separator, * put a > in front of is, so NEWS won't get confused. */ if (!strncmp(line,"#! rnews ",9)) fputs(">",bfd); fputs(line,bfd); } } while (get_line(line)) { /* look for first null line */ fputs(line,bfd); } } /* * get_line: get one line of text from the input file, exit on EOF. * If the line consists of just a form feed, concatenate the * next line on the end. Makes looking for \f\nFrom:\t that * separates mail messages easier to find. */ get_line( char *line ) { int status; extern char *mygets(); /* * read the next line from the file */ if ( !mygets(line,1024,mfd) ) { fclose(bfd); exit(SS$_NORMAL); } /* * if this line is just a FORMFEED, Combine it with the next line */ if ( line[0] == '\f' && line[1] == '\n' ) { if ( !mygets(line+2,1022,mfd) ) { /* get the next line */ fclose(bfd); /* trailing formfeeds ignored */ exit(SS$_NORMAL); } } return 1; } /* * get_head: routine to get a single header line from the input file. * RFC822 standard continuation lines are concatenated together * to make processing easier. I assume that no header line will * be longer than 1024 characters. */ get_head( char *line ) { int ch; extern char *mygets(); /* * read the header line */ if ( !mygets(line,1024,mfd) ) { fclose(bfd); /* close off the output file */ exit(SS$_ENDOFFILE); /* error in header, exit */ } /* * if this line is just a newline, then we have reached the end of the * headers. */ if ( *line == '\n' ) return 0; /* * if the next line begins with a blank, then it is a continuation * of this line. Append it to the end of the current line. */ while ( ungetc(getc(mfd),mfd) == ' ' ) if ( !mygets(line+strlen(line),1024-strlen(line),mfd) ) { fclose(bfd); exit(SS$_ENDOFFILE); } return 1; } /* * You may have been wondering why I used mygets rather than the standard * C library routine gets. I started out that way, but there seems to be * a problem in the C library when using ungetc, getc, and gets together * on the same file. It was easier to just write my own than try to find * out what the problem was with DEC's routine. */ char *mygets( char *line, int max, FILE *fd ) { int i,ch; /* * read up to max characters from the input file */ for ( i=0; i From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 19 May 93 13:55:27 +1000 To: MX-List@WKUVX1.BITNET I defined a couple of mailing lists a couple of weeks ago, setup the mail<->news gateway and the digest software and managed to get it all working. As of last week sometime MX stopped passing messages to the Mailing List process. I can't work out why. At the time I was playing with the NAME CONVERSION interface however I've backed that out and it still doesn't work. I've redone the path and rewrite statements and checked everything I can think of but to no avail. I defined the MX_ROUTER_DEBUG, ..MLF.., ..SITE.. and ..LOCAL.. debug logicals and it shows that the Router is passing the messages to the Local delivery agent which is then failing to find the mailing list address. The SITE process and the MLF process arn't generating any logs. I get the same error if I try and mail to LISTSERV. Here is my setup. Bounced message. -------------------------------------- Date: Wed, 19 May 93 12:43:23 From: postmaster@cnb09w.hhcs.gov.au Subject: LOCAL delivery error To: makinc Cc: X-From: MX%"Postmaster@cnb09w.hhcs.gov.au" X-Server: CNB09W iupop3 v1.7 X-ID: 312 Return-Path: <> Date: Wed, 19 May 1993 12:43:18 EDT From: Local delivery agent To: Subject: LOCAL delivery error Note: this message was generated automatically. The following error(s) occurred during local delivery of your message. Error delivering to user "TEST-REQUEST": user unknown Message follows. Received: by cnb09w.hhcs.gov.au (MX V3.1C) id 4113; Wed, 19 May 1993 12:43:14 EDT Date: Wed, 19 May 1993 12:43:12 EDT From: makinc@cnb09w.hhcs.gov.au To: test-request@cnb09w.hhcs.gov.au Message-ID: <0096CBCB.9FCCD800.4113@cnb09w.hhcs.gov.au> Subject: sub subscribe --------------------------------------- MX_ROUTER_LOG.LOG ----------------- 19-MAY-1993 12:51:46.15 %PROCESS, Processing entry number 4117 19-MAY-1993 12:51:46.26 %PROCESS, Status from READ_INFO was 00000001 19-MAY-1993 12:51:46.26 %PROCESS, Message originated in VMS Mail. 19-MAY-1993 12:51:46.28 %PROCESS, will run domain expander on envelope addresses. 19-MAY-1993 12:51:46.28 %PROCESS, Processing address: 19-MAY-1993 12:51:46.59 %PROCESS, ... address now reads: 19-MAY-1993 12:51:46.59 %PROCESS, will run domain expander on message headers. 19-MAY-1993 12:51:48.07 %PROCESS, Finished VMSmail-origin preprocessing. 19-MAY-1993 12:51:48.07 %PROCESS, Recipient #0: 19-MAY-1993 12:51:48.09 %REWRITE, Applying rewrite rule: <{to}@cnb09w.hhcs.gov.au> => <"{to}"@cnb09w.hhcs.gov.au> to: 19-MAY-1993 12:51:48.40 %FINDPATH, Site-spec expand on cnb09w.hhcs.gov.au err=00000000 19-MAY-1993 12:51:48.40 %FINDPATH, domain name CNB09W.HHCS.GOV.AU matched path pattern CNB09W.HHCS.GOV.AU 19-MAY-1993 12:51:48.40 %PROCESS, Rewrote as <"test-request"@cnb09w.hhcs.gov.au> - next hop cnb09w.hhcs.gov.au, path 1 19-MAY-1993 12:51:48.40 %FINDALIAS, no alias found for "test-request" 19-MAY-1993 12:51:48.40 %PROCESS, no alias found for "test-request" 19-MAY-1993 12:51:48.41 %PROCESS, this is just a local delivery 19-MAY-1993 12:51:48.50 %PROCESS, Adding to LOCAL path: "test-request". 19-MAY-1993 12:51:48.72 %PROCESS, Path LOCAL gets 1 rcpts, entry number 4118 ---------------------------------------- MX_LOCAL_LOG.LOG ---------------- 19-MAY-1993 12:51:49.06 Processing queue entry number 4118 19-MAY-1993 12:51:49.32 Checking local name: test-request 19-MAY-1993 12:51:49.46 Don't know what this is. 19-MAY-1993 12:51:50.68 All done with this entry. ---------------------------------------- Rewrite rules ------------- Address-rewriting rules: Rewrite "" => "" Rewrite "<{to}@cnb09w.hhcs.gov.au>" => "<""{to}""@cnb09w.hhcs.gov.au>" Rewrite "<{to}@DIGEST.SITE>" => "<""{to}""@DIGEST.SITE>" Rewrite "<{to}@cnb07v.hhcs.gov.au>" => "<""{to}""@cnb07v.hhcs.gov.au>" Rewrite "<{to}@cnb07v.dnet.hhcs.gov.au>" => "<""{to}""@cnb07v.dnet.hhcs.gov.au>" Rewrite "<{to}@cnb09w.dnet.hhcs.gov.au>" => "<""{to}""@cnb09w.dnet.hhcs.gov.au>" Rewrite "<{to}@{node}.hhcs.gov.au>" => "<""{node}::{to}""@cnb09w.hhcs.gov.au>" Rewrite "<{to}%{node}.dnet@cnb09w.hhcs.gov.au>" => "<""{node}::{to}""@cnb09w.hhcs.gov.au>" ----------------------------------------- Path rules ---------- Domain-to-path mappings: Domain="cnb09w.hhcs.gov.au", Path=Local Domain="[163.127.2.31]", Path=Local Domain="cnb09w.dnet.hhcs.gov.au", Path=Local Domain="cnb07v.dnet.hhcs.gov.au", Path=DECnet_SMTP, Route="cnb07v" Domain="cnb07v.hhcs.gov.au", Path=DECnet_SMTP, Route="cnb07v" Domain="DIGEST.SITE", Path=Site, Route="DIGEST" Domain="hhcs.gov.au", Path=DECnet_SMTP, Route="CNB07V" Domain="*.SITE", Path=Site, Route="NEWS" Domain="*", Path=UUCP ------------------------------------------ Alias rules ----------- Aliases: LocalName="Postmaster", Address="makinc@hhcs.gov.au" LocalName="POSTMAST", Address="makinc@hhcs.gov.au" LocalName="gate-ausradio", Address="ausradio@cnb09w.hhcs.gov.au.site" LocalName="gate-ausradio-packet", Address="ausradio-packet@cnb09w.hhcs.gov.au.site" ------------------------------------------ sh logical mx* -------------- (LNM$SYSTEM_TABLE) "MX_DEVICE" = "CNB09W$DKA400:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DNSMTP_DIR" = "MX_ROOT:[DNSMTP]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_DOMAIN_FOR_ALIAS_EXPAND" = "hhcs.gov.au" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_GATE_ID" = "mail-to-news.hhcs.gov.au" "MX_LOCAL_DEBUG" = "dd" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MLF_DEBUG" = "ddd" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "cnb09w.hhcs.gov.au" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DEBUG" = "ddd" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DEBUG" = "ddd" "MX_SITE_DIR" = "MX_ROOT:[SITE]" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_UUCP_DIR" = "MX_ROOT:[UUCP]" "MX_UUCP_HOST_NAME" = "hhcs.gov.au" "MX_VMSMAIL_LOCALHOST" = "@cnb09w.hhcs.gov.au" -------------------------------------------- Mailing Lists ------------- Mailing lists: Name: ausradio Owner: "makinc@HHCS.GOV.AU" Reply-to: NOList, Sender Description: Gatewayed to aus.radio Errors-to: makinc@hhcs.gov.au Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) Name: ausradio-packet Owner: "makinc@HHCS.GOV.AU" Reply-to: NOList, Sender Description: Gatewayed to aus.radio.packet. Errors-to: makinc@hhcs.gov.au Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) Name: ausradio-digest Owner: "makinc@HHCS.GOV.AU" Reply-to: NOList, Sender Description: digest of gatewayed newsgroup aus.radio Errors-to: makinc@hhcs.gov.au Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) Name: ausradio-packet-digest Owner: "makinc@HHCS.GOV.AU" Reply-to: NOList, Sender Description: digest of gatewayed newsgroup aus.radio.packet Errors-to: makinc@hhcs.gov.au Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) Name: test Owner: "makinc@HHCS.GOV.AU" Reply-to: NOList, Sender Description: Test Mailing List Errors-to: makinc@hhcs.gov.au Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) ------------------------------------------------------------------------- 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: Wed, 19 May 1993 07:41:42 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 19 May 1993 07:41:29 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096CBA1.799CF0E0.11738@WKUVX1.BITNET> Subject: RE: Mailling List woes Carl Makin writes: > >As of last week sometime MX stopped passing messages to the Mailing >List process. I can't work out why. At the time I was playing with >the NAME CONVERSION interface however I've backed that out and it >still doesn't work. Probably a stupid question, but I assume that you restarted MX (or did a RESET) at some point after the MCP changes? >19-MAY-1993 12:51:48.40 %FINDALIAS, no alias found for "test-request" >19-MAY-1993 12:51:48.40 %PROCESS, no alias found for "test-request" >19-MAY-1993 12:51:48.41 %PROCESS, this is just a local delivery The Router is the thing that figures out that this is a list -request address. Sounds like the Router isn't running with the latest MX configuration. I didn't see anything else obvious.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Wed, 19 May 1993 09:42:09 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: MX Name Conversion Interface. Message-ID: <1993May19.142103.29159@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 19 May 1993 14:21:03 GMT To: MX-List@WKUVX1.BITNET In article <1993May19.133232.757@hhcs.gov.au>, Carl Makin writes: >I've been playing with the Name Conversion interface in MX v3.1c. > >I'm a little confused as to what gets called when. > >I'm trying to rewrite addresses in the form >CBR::MAKINC >to >makinc@cbr.hhcs.gov.au > >so I have to use the FULL_CONVERT function instead of just CONVERT >however CONVERT is still needed. > >If I have both CONVERT and FULL_CONVERT which one gets called when? In converting usernames to aliases, FULL_CONVERT gets called first. If it returns a success status, CONVERT is skipped; otherwise, CONVERT is called. >I assume CONVERT gets called for the "alias->username" conversion >and FULL_CONVERT gets called for the "username->alias" conversion? >Is this correct? Is this all that happens? You are correct in that FULL_CONVERT is not called for alias->username conversions. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Wed, 19 May 1993 09:42:21 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Mailling List woes Message-ID: <1993May19.142341.29288@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 19 May 1993 14:23:41 GMT To: MX-List@WKUVX1.BITNET In article <1993May19.135527.758@hhcs.gov.au>, Carl Makin writes: >I defined a couple of mailing lists a couple of weeks ago, setup the >mail<->news gateway and the digest software and managed to get it >all working. > >As of last week sometime MX stopped passing messages to the Mailing >List process. I can't work out why. At the time I was playing with >the NAME CONVERSION interface however I've backed that out and it >still doesn't work. I've redone the path and rewrite statements and >checked everything I can think of but to no avail. I defined the >MX_ROUTER_DEBUG, ..MLF.., ..SITE.. and ..LOCAL.. debug logicals and >it shows that the Router is passing the messages to the Local delivery >agent which is then failing to find the mailing list address. There was a bug in V3.1C Router which prevented it from loading new configuration data on a RESET command. That sounds like what happened to you. Try shutting down and restarting the Router. Hunter fixed that bug in V3.2, I believe. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Wed, 19 May 1993 10:18:24 CDT Sender: list-mgr@WKUVX1.BITNET From: John Caruso Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Mailling List woes To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Date: Wed, 19 May 93 11:13:19 EDT CC: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU madison@tgv.com writes: > > There was a bug in V3.1C Router which prevented it from loading new > configuration data on a RESET command. That sounds like what happened > to you. Try shutting down and restarting the Router. > > Hunter fixed that bug in V3.2, I believe. I ran into this bug several weeks ago while trying to make MX recognize some newly-created mailing lists. I eventually discovered that a single RESET wouldn't work but several in quick succession had the desired effect. We're still on V3.1B, so it looks like it's time to upgrade. ------------------------------------------------------------------------ John Caruso caruso@socrates.umd.edu Unix/VMS System Administrator caruso@UMUC (Bitnet) University of Maryland University College Work: (301) 985-7447 ------------------------------------------------------------------------ ================================================================================ Archive-Date: Wed, 19 May 1993 11:14:31 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 19 May 93 12:07:24 -0400 Message-ID: <9305191607.AA01129@genrad.com> From: Reply-To: MX-List@WKUVX1.BITNET X-MX-Warning: Warning -- Invalid "To" header. To: "mx-list%wkuvx1.bitnet@ukcc.uky.edu" CC: Subject: Can percent-hacking be made more 'intelligent'? In order to make use of the message queueing and retry feature of MX, I have all of my 'remote' accounts forwarding to MX%"dongray@cd3101". Today, I got a message from DSN via one of the nodes which had a from address of MX%"'cd3101::dsn%srq.531880033g1uvo'@CDCLU2". I replied to this, but it seems that the MX router hacked the percent resulting in an invalid address. Can the next (or a future) version of the ROUTER have code that will only modify percents that occur outside paired quotes? > Note: this message was generated automatically. > > Problem occurred during message routing for the following: > > Address: (originally: <"cd3101::dsn@srq.531880033g1uvo">) > Error: Invalid address. > > Message follows. > > Received: from CD3101 (CD3101::MXMAILER) by CD4201 (MX V3.2) with SMTP (DECnet); Wed, 19 May 1993 16:45:11 BST > Received: by cd3101 (MX V3.2) id 1633; Wed, 19 May 1993 16:45:02 BST > Sender: dongray@cd3101 > Date: Wed, 19 May 1993 16:44:59 BST > From: Derek Dongray > To: "cd3101::dsn%srq.531880033g1uvo"@CDCLU2 > CC: dongray@cd3101 > Message-ID: <0096CBED.66ADC030.1633@cd3101> > Subject: RE: SDD V1.6 Service Request - No Analysis Available On further thought, I think the percent-hack algorithm might need to be smarter than that. For now, I've just disabled percent-hacking! -------------------------------------------------------------------------------- Name :Derek Dongray, Systems Manager, GenRad Ltd. Phone :061 486 1511 InterNet : Dongray@GenRad.com UKnet : Derek.Dongray@GenRad.co.uk PSS : 234261600119::Dongray CompuServe : 70374,2745 Address : Monmouth House, Monmouth Road, Cheadle Hulme, Cheshire, SK8 7AY, UK. ================================================================================ Archive-Date: Wed, 19 May 1993 11:26:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 19 May 1993 11:23:52 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096CBC0.8A4C1640.11821@WKUVX1.BITNET> Subject: RE: Can percent-hacking be made more 'intelligent'? writes: > >In order to make use of the message queueing and retry feature of MX, I have >all of my 'remote' accounts forwarding to MX%"dongray@cd3101". Today, I got a >message from DSN via one of the nodes which had a from address of >MX%"'cd3101::dsn%srq.531880033g1uvo'@CDCLU2". I replied to this, but it seems >that the MX router hacked the percent resulting in an invalid address. > >Can the next (or a future) version of the ROUTER have code that will only >modify percents that occur outside paired quotes? > I intend to look into this area for the next version. Note that there are two other problems with this particular address: o MX changes the "$" is SRQ$xxxxxx to a ".". As discussed here before, this is done to prevent UNIX systems (shells) from processing the dollar sign and evaluating the remainder as a UNIX command. o Mail sent from DSNlink through MX oftentimes causes an access violation. I've never been able to determine if that's coming from DSNlink (whom I suspect) or MX. Flash mail, SRQ mail, etc., seems to work fine, but mail notification of patch delivery seems to always cause access violations. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Wed, 19 May 1993 12:08:56 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 19 May 93 12:34:39 -0400 Message-ID: <9305191634.AA01695@genrad.com> From: Reply-To: MX-List@WKUVX1.BITNET X-MX-Warning: Warning -- Invalid "To" header. To: "mx-list%wkuvx1.bitnet@ukcc.uky.edu" CC: Subject: RE: Can percent-hacking be made more 'intelligent'? > writes: >> >>In order to make use of the message queueing and retry feature of MX, I have >>all of my 'remote' accounts forwarding to MX%"dongray@cd3101". Today, I got a >>message from DSN via one of the nodes which had a from address of >>MX%"'cd3101::dsn%srq.531880033g1uvo'@CDCLU2". I replied to this, but it seems >>that the MX router hacked the percent resulting in an invalid address. >> >>Can the next (or a future) version of the ROUTER have code that will only >>modify percents that occur outside paired quotes? >> > I intend to look into this area for the next version. Note that there > are two other problems with this particular address: > > o MX changes the "$" is SRQ$xxxxxx to a ".". As discussed here > before, this is done to prevent UNIX systems (shells) from processing > the dollar sign and evaluating the remainder as a UNIX command. I missed that discussion (or forgot it). It explains why when I 'manually' replied, DSN still wouldn't accept it; I was sending to DSN%SQR.xxx. :-} Of course, it could be argued that munging the address like this should be done by the Unix system, since, as in my case, it's only effect to to produce a completely invalid address! Is there some way to switch it off? > o Mail sent from DSNlink through MX oftentimes causes an access > violation. I've never been able to determine if that's coming > from DSNlink (whom I suspect) or MX. Flash mail, SRQ mail, etc., > seems to work fine, but mail notification of patch delivery seems > to always cause access violations. Fortunately, the node where I request patches is the only one that doesn't forward my mail through MX. > Hunter > ------ > Hunter Goatley, VMS Systems Programmer, Western Kentucky University > goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) -------------------------------------------------------------------------------- Name :Derek Dongray, Systems Manager, GenRad Ltd. Phone :061 486 1511 InterNet : Dongray@GenRad.com UKnet : Derek.Dongray@GenRad.co.uk PSS : 234261600119::Dongray CompuServe : 70374,2745 Address : Monmouth House, Monmouth Road, Cheadle Hulme, Cheshire, SK8 7AY, UK. ================================================================================ Archive-Date: Wed, 19 May 1993 12:23:56 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 19 May 1993 12:23:04 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096CBC8.CF8E36E0.11847@WKUVX1.BITNET> Subject: RE: Can percent-hacking be made more 'intelligent'? writes: > >I missed that discussion (or forgot it). It explains why when I 'manually' >replied, DSN still wouldn't accept it; I was sending to DSN%SQR.xxx. :-} > Yep! >Of course, it could be argued that munging the address like this should be done >by the Unix system, since, as in my case, it's only effect to to produce a >completely invalid address! Is there some way to switch it off? > No, there's not. I'll try to add that in MX V3.4. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Wed, 19 May 1993 12:51:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 19 May 93 13:46:45 -0400 Message-ID: <9305191746.AA02920@genrad.com> From: Reply-To: MX-List@WKUVX1.BITNET X-MX-Warning: Warning -- Invalid "To" header. To: "mx-list%wkuvx1.bitnet@ukcc.uky.edu" CC: Subject: RE: Can percent-hacking be made more 'intelligent'? >>Of course, it could be argued that munging the address like this should be done >>by the Unix system, since, as in my case, it's only effect to to produce a >>completely invalid address! Is there some way to switch it off? >> > No, there's not. I'll try to add that in MX V3.4. Thanks in advance. > Hunter > ------ > Hunter Goatley, VMS Systems Programmer, Western Kentucky University > goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) -------------------------------------------------------------------------------- Name :Derek Dongray, Systems Manager, GenRad Ltd. Phone :061 486 1511 InterNet : Dongray@GenRad.com UKnet : Derek.Dongray@GenRad.co.uk PSS : 234261600119::Dongray CompuServe : 70374,2745 Address : Monmouth House, Monmouth Road, Cheadle Hulme, Cheshire, SK8 7AY, UK. ================================================================================ Archive-Date: Wed, 19 May 1993 13:46:09 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 19 May 1993 11:42:29 PDT From: "Mike Johnson, Harris/Farinon - (415) 594-3530" Reply-To: MX-List@WKUVX1.BITNET To: mx-list%wkuvx1.bitnet@ukcc.uky.edu CC: mcjohnson@wizard.farinon.harris.com Message-ID: <0096CBC3.24565FA0.6582@wizard.farinon.harris.com> Subject: Protocol error from MX ? I am having a problem mailing a message to one person. MX is reporting the "Last error:" as: %MX-E-PROTOERR, protocol error? The address I am using is the return from the senders header. Doing a "nslookup" on the system name resulted in no available records. Talking to the sender I got an expaned system name and tried a "traceroute" and "nslookup" to that. I get information back, but sending mail using the expanded name results in the same error. I am new at this so I am lost. Can anyone provide some advise on determining what the problem is. Thanks Mike Johnson ------------------------------------------------------------------------------- Michael Johnson Harris Corp./Farinon Div. 1691 Bayport Ave., San Carlos, CA 94070-5307 (Voice) 415 594-3530 (FAX) 415 594-3777 (Internet) mcjohnson@wizard.farinon.harris.com ------------------------------------------------------------------------------ ================================================================================ Archive-Date: Thu, 20 May 1993 08:00:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 11 May 1993 14:40:03 +0100 From: "Fly like an eagle, crash like a VAX..." Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@CEARN.BITNET, LLAZARTE%BRUNB.BITNET@CEARN.BITNET Message-ID: <0096C592.9F0C9F20.26337@europa.rs.ch> Subject: Re: MX V3.3 is now available!! > But, (blush) How do I use "unzip.exe" in VMS? > If I "run" it, I get only a screen saying how it should be used. You define it as an foreign command. Eg UNZIP:==$tools:UNZIP.EXE To extract unzip the MX033 Zip-file then type: UNZIP MX033 Regards, Ralph +---------------+---------------------------------------------------------+ I Ralph Kloess I I-Net: Kloess@europa.rs.ch I I I Standard disclaimer applies to all my messages I +---------------+---------------------------------------------------------+ ================================================================================ Archive-Date: Thu, 20 May 1993 12:50:21 CDT Sender: list-mgr@WKUVX1.BITNET Reply-To: MX-List@WKUVX1.BITNET Date: Thu, 20 May 1993 11:25:30 MDT From: I Hate When That Happens To: MX-List@RPIECSVX.BITNET CC: jpsmith@atmel.com Message-ID: <0096CC89.EFAD5B60.16340@BONSAI.ATMEL.COM> Subject: SMTP Delivery agent I am having problems with uudecode ('short file' error) on a uuencoded message being received by the MX SMTP agent under V3.1c. After some trial and error I found that this agent strips trailing white spaces from the uuencoded file when it is received. I haven't had the problem with the stripping of white spaces when I send a file (using MX) or when using the MX local agent. When I bypass MX from the SMTP receiving end, I can successfully send/receive uuencoded mail without the above mentioned problem. Is this a known problem in V3.1c? What about V3.3? --Jody Smith ***************************************************************************** * Jody Smith * * jpsmith@atmel.com * * * * ATMEL Corporation * * 1150 E. Cheyenne Mtn Blvd * * Colorado Springs, Colorado 80906 * ***************************************************************************** ================================================================================ Archive-Date: Thu, 20 May 1993 13:43:01 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 20 May 1993 13:33:05 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096CC9B.C238D4E0.12333@WKUVX1.BITNET> Subject: RE: SMTP Delivery agent I Hate When That Happens writes: > >I am having problems with uudecode ('short file' error) on a uuencoded message >being received by the MX SMTP agent under V3.1c. After some trial and error I >found that this agent strips trailing white spaces from the uuencoded file >when it is received. I haven't had the problem with the stripping of white >spaces when I send a file (using MX) or when using the MX local agent. When I >bypass MX from the SMTP receiving end, I can successfully send/receive >uuencoded mail without the above mentioned problem. > >Is this a known problem in V3.1c? What about V3.3? > MX used to strip trailing blanks. MX V3.3 does not. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Thu, 20 May 1993 14:38:03 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 20 May 1993 11:45:15 PDT From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: jpsmith@atmel.com, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <0096CC8C.B1ADBB9A.17527@CCVAX.CCS.CSUS.EDU> Subject: RE: SMTP Delivery agent > After some trial and error I found that this agent strips trailing white > spaces from the uuencoded file when it is received... > > Is this a known problem in V3.1c? What about V3.3? Yes, as a matter of fact it is :-) I don't know if it's been fixed in 3.3; it is *not* fixed as of 3.2. The workaround, discussed last July, is to get a more intelligent uudecode program. I haven't checked to make sure these are still available, but from some old archives I found these notes: At black.cerritos.edu, in [.mailserv.uuencode_decode], there is a vms_share file with VAX-C source for uuencode and uudecode. The uuencode is smart enough to put a guard character (lower-case 'a') after the last meaningful letter on each uuencoded line, to avoid blank-stripping in the first place, while the uuencode seems to be smart enough to handle stripped blanks... I believe that Earle Ake mirrored these files to dayton.saic.com, as well as providing an executable linked against VMS v4.7. Look for UUDECODE.C, UUDECODE.EXE, UUENCODE.C, UUENCODE.EXE and UU_MAKE.COM. Also: Hunter apparently made several versions available in his UUCODE package, available from ftp.spc.edu in the file [.MACRO32.SAVESETS]UUCODE.BCK_Z. You'll also need [.MACRO32]LZDCMP.EXE and [.MACRO32]AAAREADME.TXT. John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu ================================================================================ Archive-Date: Thu, 20 May 1993 14:38:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 20 May 1993 14:17:35 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: jpsmith@atmel.com Message-ID: <0096CCA1.F985E0E0.9800@SHSU.edu> Subject: RE: SMTP Delivery agent On Thu, 20 May 1993 11:25:30 MDT, Jody Smith posted: > I am having problems with uudecode ('short file' error) on a uuencoded > message being received by the MX SMTP agent under V3.1c. After some trial > and error I found that this agent strips trailing white spaces from the > uuencoded file when it is received. I haven't had the problem with the > stripping of white spaces when I send a file (using MX) or when using the > MX local agent. When I bypass MX from the SMTP receiving end, I can > successfully send/receive uuencoded mail without the above mentioned > problem. > > Is this a known problem in V3.1c? What about V3.3? In SYS$HELP:MX033.RELEASE_NOTES: > MX V3.3 provides the following fixes to bugs in V3.2: >..... > 5 The MX UUCP interface and the SMTP servers (SMTP, > DNSMTP, and XSMTP) stripped trailing blanks off of > lines on incoming messages from MX. The blanks are > no longer removed. Which I'm glad was fixed, but..... Why not upgrade your UU*CODE suite so that it always generates lines of the same length with padding if necessary? I know that this won't help for files which you receive from elsewhere, but it will help you geerate files which other mailers/gateways/processors decide to strip (and give you software to pass along to others). We have such a UU*CODE suite on our FILESERV, as well as via anonymous ftp. Via e-mail, include: SENDME UUCODE in the body of a mail message to FILESERV@SHSU.BITNET (FILESERV@SHSU.edu). Via anonymous ftp, come to Niord.SHSU.edu (192.92.115.8) and look in [FILESERV.UUCODE]. Related to this, I hope that the VV*CODE suite may soon be available, which will really give us a powerful tool to avoid probems such as this, as well as automagically concatenating the files in proper order for us. I've been playing with the betas of it for quite some time now (well over 18 months, as I recall) and it is supported in nearly every platform you can imagine. Maybe Brian {Hamilton Kelly} can fill us in on the schedule for an official release?? 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, 21 May 1993 01:57:10 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Mailling List woes Message-ID: <1993May21.145929.761@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 21 May 93 14:59:29 +1000 To: MX-List@WKUVX1.BITNET Hi Matt, Thanks for the reply. In article <1993May19.142341.29288@news.arc.nasa.gov> Matt Madison, madison@tgv.com writes: > There was a bug in V3.1C Router which prevented it from loading new > configuration data on a RESET command. That sounds like what happened > to you. Try shutting down and restarting the Router. I've tried that a number of times. I just tried it again. No luck. It's just like the router has forgotten that there are active mailing lists! The MLF agent never gets called. > Hunter fixed that bug in V3.2, I believe. I'm going to upgrade to 3.3 and see if that makes any difference. 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: Fri, 21 May 1993 02:11:05 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9305210759.AA02707@bogart.mpib-tuebingen.mpg.de> To: MX-List@WKUVX1.BITNET, goathunter@WKUVX1.BITNET Subject: Re: MX V3.3 is now available!! Date: Fri, 21 May 93 08:59:12 +0100 From: boerner@bogart Reply-To: MX-List@WKUVX1.BITNET Hi, > MX033_SRC.ZIP;1 > Error: zipfile is in variable-length record format. Please > run "bilf l mx033_src.zip;1" to convert the zipfile to stream-LF > record format. (Bilf.exe, bilf.c and make_bilf.com are included > in the VMS UnZip source distribution.) Where can i find Bilf.* ??????????? ciao rudi email: boerer@bogart.mpib-tuebingen.mpg.de ================================================================================ Archive-Date: Fri, 21 May 1993 08:58:43 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 21 May 1993 08:52:10 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: boerer@bogart.mpib-tuebingen.mpg.de Message-ID: <0096CD3D.AE5B0C20.13613@SHSU.edu> Subject: Re: MX V3.3 is now available!! On Fri, 21 May 93 08:59:12 +0100, () posted: > > MX033_SRC.ZIP > > > Error: zipfile is in variable-length record format. Please > > run "bilf l mx033_src.zip" to convert the zipfile to stream-LF > > record format. (Bilf.exe, bilf.c and make_bilf.com are included > > in the VMS UnZip source distribution.) > > Where can i find Bilf.* ??????????? First, you may want to look into how you are reporting your Internet node name on your mailer as it doesn't appear that you are reporting a FQDN). But on to your question. If you want the files via e-mail, include: SENDME UNZIP_VMS.*BILF* in the body of a mail message to FILESERV@SHSU.BITNET (FILESERV@SHSU.edu). This will return: UNZIP_VMS.BILF_C UNZIP_VMS.BILF_EXE_UUE UNZIP_VMS.MAKE_BILF_COM If you want to get the files via anonymous ftp, you can come to Niord.SHSU.edu (192.92.115.8) and look in [FILESERV.UNZIP.UNZ50P1.VMS.BILF] 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, 21 May 1993 10:42:29 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: handling mailing list bounces Message-ID: <1993May21.125732.4217@samba.oit.unc.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 21 May 1993 12:57:32 GMT To: MX-List@WKUVX1.BITNET I'm running what has become a surprisingly active mailing list using MX 3.3. I'm not having any trouble with the software, but I'm not sure where else to ask this question, so here we go... How do those of you running mailing lists handle subscriptions that bounce? Specifically, I've had several people attempt to subscribe and had their acknowledgement messages, along with everything else, bounce. I usually see a "no such host" more or less error message. It appears to me their mailer is poorly configured, and is not putting a good address wherever MLF is looking for it -- the one that happened today (and prompted this message) shows up on a REVIEW of the list as user@HOST (not a quote -- name's changed to protect the innocent), with no domain. I've tried contacting this user directly assuming .BITNET, but that bounced too. So how do you handle this situation? Any ideas how to contact the user? Anything I can change in the MLF configuration? Is there a log I can turn on that may trap this and give me an address to contact? Of course, there's no telling when a subscription like this may come in. My first clue is a bounce in my mailbox. Suggestions welcome! Thanks. -- Dennis R. Sherman Triangle Research Libraries Network dennis_sherman@unc.edu Univ. of North Carolina - Chapel Hill ================================================================================ Archive-Date: Fri, 21 May 1993 11:09:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 21 May 1993 11:09:35 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096CD50.E089BF80.12822@WKUVX1.BITNET> Subject: RE: handling mailing list bounces writes: > >How do those of you running mailing lists handle subscriptions that >bounce? Specifically, I've had several people attempt to subscribe >and had their acknowledgement messages, along with everything else, >bounce. I usually see a "no such host" more or less error message. >It appears to me their mailer is poorly configured, and is not putting >a good address wherever MLF is looking for it -- the one that happened >today (and prompted this message) shows up on a REVIEW of the list as >user@HOST (not a quote -- name's changed to protect the innocent), >with no domain. I've tried contacting this user directly assuming >.BITNET, but that bounced too. So how do you handle this situation? >Any ideas how to contact the user? What I usually do is, if it bounces when I'm in, is search the incoming files still in the MX_FLQ_DIR directory tree to see if I can locate the original SUBSCRIBE message. It usually contains enough info to piece together the header. >Anything I can change in the MLF >configuration? Is there a log I can turn on that may trap this and >give me an address to contact? No, but I hope to look into that down the road.... >Of course, there's no telling when a >subscription like this may come in. My first clue is a bounce in my >mailbox. > Yep. My method only works if the bounce comes while I'm logged in. Otherwise, when the list posts themselves start bouncing, I usually just remove the user and wait for them to contact me or try again. Yes, it's a pain.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Fri, 21 May 1993 15:46:54 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: MX V3.3 is now available!! Date: 21 May 1993 16:56:14 GMT Message-ID: <1tj1jeINNan5@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <9305210759.AA02707@bogart.mpib-tuebingen.mpg.de>, boerner%bogart@ULKYVM.LOUISVILLE.EDU writes: => MX033_SRC.ZIP;1 = => Error: zipfile is in variable-length record format. Please => run "bilf l mx033_src.zip;1" to convert the zipfile to stream-LF => record format. (Bilf.exe, bilf.c and make_bilf.com are included => in the VMS UnZip source distribution.) = = =Where can i find Bilf.* ??????????? Why not just ftp MX033_SRC.ZIP again, this time in image mode? -------------------------------------------------------------------------------- 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, 21 May 1993 16:10:50 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: handling mailing list bounces Message-ID: From: Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 21 May 1993 17:41:34 GMT To: MX-List@WKUVX1.BITNET of course, hunter, what we're all waiting for is MX to start processing the bounces and automatically unsubscribing the offenders :-) -- -- bob pasker -- rbp@netcom.com -- ================================================================================ Archive-Date: Sat, 22 May 1993 09:03:15 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Can MX be used with DECnet delivery? Message-ID: <1993May21.085026.2022@elcsci.com> Date: 21 May 93 08:50:26 PST To: MX-List@WKUVX1.BITNET Is there any straight forward way to get incomming DECnet mail messages to be routed through MX? I have a an asynch DECnet link to a Macintosh acting as a gateway between MicroSoft Mail and VMS Mail. I'd like to be able to pass these messages through MX so that I massage the Macintosh address (which tend to be long with lots of embedded spaces). It would also be nice to pass message going from the VAX to the Macintosh via DECnet through MX so that RFC 822 headers would be inserted. With just the VMS mail through DECnet, the Macintosh reciepient doesn't see all the CCed user that may have received the message on the VAX. I think I could solve these problems if I could get the message to pass through MX. Thanks, Chuck ================================================================================ Archive-Date: Sat, 22 May 1993 09:24:23 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <0096CDFC.B3946D20.38@uwwvax.uww.edu> Date: Sat, 22 May 1993 07:39:33 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.BITNET Subject: Disappearing mail To: mx-list@WKUVX1.BITNET This user can recieve local mail but anything passing through MX disappears. The trace is below and it is different from others on the system. What is happening? => 22-MAY-1993 07:34:00.18 Processing queue entry number 37 => 22-MAY-1993 07:34:00.79 Checking local name: HOLMANJ => 22-MAY-1993 07:34:01.09 This is a delivery to MM. => 22-MAY-1993 07:34:01.17 DELIVER_MM: Delivering to HOLMANJ => 22-MAY-1993 07:34:02.16 PERFORM_MM_DELIVERY returned status 00000001 => 22-MAY-1993 07:34:02.27 All done with this entry. Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Sat, 22 May 1993 10:52:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 22 May 1993 10:25:19 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096CE13.DBE4BDE0.13324@WKUVX1.BITNET> Subject: RE: Disappearing mail hunterl@uwwvax.uww.edu writes: > >This user can recieve local mail but anything passing through MX >disappears. The trace is below and it is different from others on the >system. What is happening? > >=> 22-MAY-1993 07:34:00.18 Processing queue entry number 37 >=> 22-MAY-1993 07:34:00.79 Checking local name: HOLMANJ >=> 22-MAY-1993 07:34:01.09 This is a delivery to MM. >=> 22-MAY-1993 07:34:01.17 DELIVER_MM: Delivering to HOLMANJ >=> 22-MAY-1993 07:34:02.16 PERFORM_MM_DELIVERY returned status 00000001 >=> 22-MAY-1993 07:34:02.27 All done with this entry. > MX is delivering the message to MultiNet's MM, not VMS Mail. The only way this *should* be happening is if the user ran MM once and told it to have all incoming mail delivered to MM. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Sat, 22 May 1993 12:27:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 22 May 1993 12:22:10 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Message-ID: <0096CE24.2E7A2620.335@uwwvax.uww.edu> Subject: RE: Disappearing mail => hunterl@uwwvax.uww.edu writes: => > => >This user can recieve local mail but anything passing through MX => >disappears. The trace is below and it is different from others on the => >system. What is happening? => > => >=> 22-MAY-1993 07:34:00.18 Processing queue entry number 37 => >=> 22-MAY-1993 07:34:00.79 Checking local name: HOLMANJ => >=> 22-MAY-1993 07:34:01.09 This is a delivery to MM. => >=> 22-MAY-1993 07:34:01.17 DELIVER_MM: Delivering to HOLMANJ => >=> 22-MAY-1993 07:34:02.16 PERFORM_MM_DELIVERY returned status 00000001 => >=> 22-MAY-1993 07:34:02.27 All done with this entry. => > => MX is delivering the message to MultiNet's MM, not VMS Mail. The only => way this *should* be happening is if the user ran MM once and told it => to have all incoming mail delivered to MM. => => Hunter => ------ => Hunter Goatley, VMS Systems Programmer, Western Kentucky University Thanks, the problem is solved. Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Sun, 23 May 1993 19:09:08 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Modifying outgoing addresses Message-ID: <1tp4u0INN18j@zephyr.grace.cri.nz> From: srchopr@chv.lincoln.cri.nz Reply-To: MX-List@WKUVX1.BITNET Date: Sun, 23 May 93 22:36:30 GMT To: MX-List@WKUVX1.BITNET First, I'd like to say I installed MX 3.3 last week and it went very smoothly - a hearty "Well done!" to the authors. Now, a query/something for the wish-list ... if I'm watching the MCP QUEUE and there's a message sitting there waiting to go out with what is obviously a wrong address (eg a typo - LINCOLN.CIR.NZ for LINCOLN.CRI.NZ) is there a way to change the outgoing address, short of getting the user to resend the message? A command like MCP QUEUE MODIFY DESTINATION= for instance? Regards Sue Knight /~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\ ! Sue Knight KNIGHTS@CHV.LINCOLN.CRI.NZ ! ! NZ Institute for Crop & Food Research Ltd. ! ! Private Bag 4704 Tel 64 3 325 2511 ! ! Christchurch Fax 64 3 325 2074 ! ! ! ! Canterbury Ag & Science Centre, PSI 05301 4600000080::KNIGHTS ! ! Gerald St, Lincoln ! `~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' ================================================================================ Archive-Date: Mon, 24 May 1993 09:40:27 CDT Sender: list-mgr@WKUVX1.BITNET From: teague@acavax.lynchburg.edu Reply-To: MX-List@WKUVX1.BITNET Subject: How to set NEWS Mail transport to MX? Message-ID: <1993May24.101445.236@acavax.lynchburg.edu> Date: 24 May 93 10:14:45 -0500 To: MX-List@WKUVX1.BITNET How do I set the mail transport prefix used by ANU NEWS to "MX%"? For some reason, when I use the REPLY feature, NEWS uses the prefix "IN%" -------------------------------------------------------------------------------- Kipp Teague E-Mail: teague@acavax.lynchburg.edu Lynchburg College, Lynchburg, Virginia Phone: (804) 522-8358 ================================================================================ Archive-Date: Mon, 24 May 1993 09:42:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 24 May 1993 09:42:12 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096CFA0.2A7C3AE0.13643@WKUVX1.BITNET> Subject: RE: How to set NEWS Mail transport to MX? teague@acavax.lynchburg.edu writes: > > >How do I set the mail transport prefix used by ANU NEWS to "MX%"? For some >reason, when I use the REPLY feature, NEWS uses the prefix "IN%" > Look at the file NEWS_MANAGER:NEWS_ADDRESS.CNF. Ours contains the following line: * mx%"\001" Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Mon, 24 May 1993 13:03:00 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 24 May 1993 13:57:59 -0400 (EDT) From: "Clay M. Denton - THE SIG" Reply-To: MX-List@WKUVX1.BITNET Subject: SMTP delivery agent errors To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Message-ID: <01GYK0X056XU002Z5U@Eisner.DECUS.Org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT I am running MX 3.3 on a VMS 5.5-2 cluster with UCX 2.0. When starting the SMTP delivery agent I get this message in the MX_SMTP_node log file: 24-MAY-1993 12:34:51.10: MX SMTP (pid 3F405A5C) starting 24-MAY-1993 12:37:31.20: MX SMTP (pid 3F405A5C) exiting, status = 1000000C Any idea what the error status means? Clay Denton McDonnell Douglas Aerospace (713) 244-4884 ================================================================================ Archive-Date: Mon, 24 May 1993 13:34:22 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 24 May 1993 14:30:37 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: DENTON_C@Eisner.DECUS.Org Message-ID: <0096CFC8.753959A0.21325@nscvax.princeton.edu> Subject: RE: SMTP delivery agent errors Clay M. Denton writes: > >I am running MX 3.3 on a VMS 5.5-2 cluster with UCX 2.0. When starting the >SMTP delivery agent I get this message in the MX_SMTP_node log file: > >24-MAY-1993 12:34:51.10: MX SMTP (pid 3F405A5C) starting >24-MAY-1993 12:37:31.20: MX SMTP (pid 3F405A5C) exiting, status = 1000000C > >Any idea what the error status means? > >Clay Denton >McDonnell Douglas Aerospace >(713) 244-4884 It means means that the deliver agent failed with an access violation. This is due to an error in the code somewhere. You probably did something to provoke it so double check the way you installed/configured things. Further translation: the code tried to access memory that didn't belong to it. It shouldn't have done this no matter you did or failed to do. If it weren't for the error in the code (not checking input for validity?) it still wouldn't have worked but might have given a more meaningful error message. ************************************************************************* * * * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Mon, 24 May 1993 14:42:16 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 24 May 1993 12:32:53 PDT From: "W. Todd Wipke" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096CFB8.02D8E7A0.24208@SECS.UCSC.EDU> Subject: controlled mailing lists I am running some restricted lists that only subscribers can post to and that control fileservers. We have recently had a shift to using MX records to give nice looking domain names like chemistry.ucsc.edu instead of hydrogen.ucsc.edu. Unfortunately this means people are no longer recognized as being on the list. If MX looked at the MX records and checked for equivalent addresses, most of this problem would go away. Has anyone code that does this? I am running MX3.1C. -todd Wipke wipke@secs.ucsc.edu ================================================================================ Archive-Date: Mon, 24 May 1993 16:05:58 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 24 May 1993 16:01:43 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096CFD5.2F25F9C0.25020@SHSU.edu> Subject: RE: SMTP delivery agent errors On Mon, 24 May 1993 14:30:37 EDT, Mighty Firebreather posted: > Clay M. Denton writes: > > > >I am running MX 3.3 on a VMS 5.5-2 cluster with UCX 2.0. When starting the > >SMTP delivery agent I get this message in the MX_SMTP_node log file: > > > >24-MAY-1993 12:34:51.10: MX SMTP (pid 3F405A5C) starting > >24-MAY-1993 12:37:31.20: MX SMTP (pid 3F405A5C) exiting, status = 1000000C > > > >Any idea what the error status means? > > > >Clay Denton > >McDonnell Douglas Aerospace > >(713) 244-4884 > > It means means that the deliver agent failed with an access violation. This > is due to an error in the code somewhere. You probably did something to > provoke it so double check the way you installed/configured things. > > Further translation: the code tried to access memory that didn't belong to > it. It shouldn't have done this no matter you did or failed to do. If it > weren't for the error in the code (not checking input for validity?) it > still wouldn't have worked but might have given a more meaningful error > message. Unless the UCX SMTP agents are running; in which case the ports couldn't be reallocated and the MX SMTP agents couldn't start up (or that's what I recall happening to us here many moons ago -- I'm pretty sure this is documented in the MX_DOC_DIR). Check to see that UCX isn't handling SMTP transactions and that MX is. 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: Tue, 25 May 1993 02:13:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 25 May 1993 09:03:21 MEZ ( +0200) From: Peter Kobe Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET Message-ID: <0096D063.E775DFC0.11470@pib1.physik.uni-bonn.de> Subject: MCP output MX agents run on 2 nodes (PIB1/PIB3) in the cluster. I stopped/cluster MX on node PIB3 all agents disappeared except MCP> status PID Node Process name Agent type -------- ------ --------------- ------------ 22E04615 PIB1 MX SMTP SMTP delivery agent I checked the MCP status on node PIB1 and got each possible/impossible agent on node PIB3 31 times displayed. Some time after editing this mesage-file, MCP> status gave the correct answer . The SMTP delivery agent will not stop/vanish =================================================== Peter PIB1_$ mcp MCP> status PID Node Process name Agent type -------- ------ --------------- ------------ 20E003F9 PIB3 _FTA87: Router agent 30 lines deleted 20E003F9 PIB3 _FTA87: Local delivery agent 30 lines deleted 20E003F9 PIB3 _FTA87: Mailing list/file server 30 lines deleted 20E003F9 PIB3 _FTA87: SMTP delivery agent 30 lines deletd 20E003F9 PIB3 _FTA87: Jnet interface agent 30 lines deleted. This has never been activated 20E003F9 PIB3 _FTA87: UUCP interface agent 30 lines deleted. This has never been activated 20E003F9 PIB3 _FTA87: Site-specific delivery agent 30 lines deleted. This has never been activated 20E003F9 PIB3 _FTA87: Site-specific delivery agent 30 lines deleted 20E003F9 PIB3 _FTA87: SMTP-over-DECnet delivery agent 30 lines deleted 20E003F9 PIB3 _FTA87: SMTP-over-X.25 delivery agent 30 lines deleted ===================================================================== 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, 25 May 1993 08:46:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 25 May 1993 08:46:13 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D061.833CBF80.13875@WKUVX1.BITNET> Subject: RE: MCP output Peter Kobe writes: > >MX agents run on 2 nodes (PIB1/PIB3) in the cluster. >I stopped/cluster MX on node PIB3 >all agents disappeared except >MCP> status > PID Node Process name Agent type >-------- ------ --------------- ------------ >22E04615 PIB1 MX SMTP SMTP delivery agent > The agents won't go away immediately if they're processing a message. >I checked the MCP status on node PIB1 and got each possible/impossible >agent on node PIB3 31 times displayed. Yes, this is a bug that I forgot to document in the release notes. If two processes run MCP STATUS at the same time on the same cluster, the MCP doesn't process the lock information correctly for some reason. When I saw it happen, it was showing the PID of the other process running MCP. In any case, it repeats entries and shows agents that aren't there. I hope to have it fixed in the next version. >Some time after editing this mesage-file, >MCP> status >gave the correct answer >. >The SMTP delivery agent will not stop/vanish I have seen the MX Jnet process ignore SHUTDOWN commands. Sending it again when it is idle should work. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Tue, 25 May 1993 15:48:44 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX SMTP and TELNET Message-ID: <1993May25.160143.1664@dmc.com> Date: 25 May 93 16:01:43 EDT To: MX-List@WKUVX1.BITNET Running Multinet and MX SMTP, should I be able to telnet to port 25? I had a problem with SMTP that I was trying to trouble shoot and I couldn't do it. I kept getting a connection rejected due to "confusion". 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: Tue, 25 May 1993 16:12:10 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 25 May 1993 16:11:56 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D09F.C6FC4F40.14097@WKUVX1.BITNET> Subject: RE: MX SMTP and TELNET writes: > >Running Multinet and MX SMTP, should I be able to telnet to port >25? I had a problem with SMTP that I was trying to trouble shoot >and I couldn't do it. I kept getting a connection rejected due >to "confusion". > Yes, it'll work: Recording initiated at 25-MAY-1993 16:10:27.71 Log file is HUNTER$USER:[HUNTER]PHOTO.LOG;1 16:09> telnet hunter/por=25 Trying... Connected to HUNTER.WKU.EDU, a VAXSTATION-4000 running VMS. 220 hunter.wku.edu MX V3.3 VAX SMTP server ready at Tue, 25 May 1993 16:10:34 CDT QUIT 221 hunter.wku.edu Service closing transmission channel. Connection closed by Foreign Host 16:09> photo/off Recording finished at 25-MAY-1993 16:10:43.03 Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@UKCC.UKY.EDU) ================================================================================ Archive-Date: Tue, 25 May 1993 16:46:26 CDT Sender: list-mgr@WKUVX1.BITNET From: system@dmc.com Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX SMTP and TELNET Message-ID: <1993May25.165519.1665@dmc.com> Date: 25 May 93 16:55:19 EDT To: MX-List@WKUVX1.BITNET In article <1993May25.160143.1664@dmc.com>, munroe@dmc.com (Dick Munroe) writes: > Running Multinet and MX SMTP, should I be able to telnet to port > 25? I had a problem with SMTP that I was trying to trouble shoot > and I couldn't do it. I kept getting a connection rejected due > to "confusion". Well, the confusion was mine, at least about the error message. You CAN telnet to port 25 AND the connection is indeed rejected. There APPEARS to be a problem with Multinet (3.2B) in that if I stop MX and bring it back up, I STILL can't get to the SMTP server. I have to restart the multinet server, THEN bring up SMTP. Anybody seen this before? or anything like it? Any hints about how to debug the situation? Having my SMTP link just die on me is a little disconcerting. Dick Munroe ================================================================================ Archive-Date: Tue, 25 May 1993 17:35:04 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: MX SMTP and TELNET Date: 25 May 1993 21:53:26 GMT Message-ID: <1tu4gmINNg06@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993May25.160143.1664@dmc.com>, munroe@dmc.com (Dick Munroe) writes: =Running Multinet and MX SMTP, should I be able to telnet to port =25? I had a problem with SMTP that I was trying to trouble shoot =and I couldn't do it. I kept getting a connection rejected due =to "confusion". I have no trouble doing it: $ telnet/port=25 sol1.gps.caltech.edu Trying... Connected to SOL1.GPS.CALTECH.EDU. 220 SOL1.GPS.CALTECH.EDU MX V3.3 VAX SMTP server ready at Tue, 25 May 1993 13:52:07 PST HELO SOL1.GPS.CALTECH.EDU 250 Hello, SOL1.GPS.CALTECH.EDU -------------------------------------------------------------------------------- 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, 25 May 1993 22:29:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 93 00:20:58 EST From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX stops Vax To: mx-list@WKUVX1.BITNET Message-ID: <9305260320.AA04675@rnpdf2.cnpq.br> After a couple of hours of starting MX, people are prevented of entering our machine. The only solution is, if someone is logged in, to STOP mx-related processes. Otherwise, switching the machine off and on. We were running CMU/Tek 6.6_5 and MX 2.2, as distributed in the CMU tapes. It was suggested that we upgraded to CMUopenVMS 6.6_5A, which was quite easy to do, and to MX 3.3, which was a bit harder, because of the size of the whole package (Thanks, Hunter, by pointing to a source of separate, zipped, kits). Anyway, the problem persists with the upgrade. Any hints as to the source of the problem? -- Could it be lack of memory or some other hardware or system limit? -- Could it be some incompatibility with DECnet or other parameters? -- What kind of things could be misconfigured in MX to provoke such a behaviour? -- Is it possible that there is some loop somewhere? (even when MX is or should be, idle) After stopping MX, sometimes processes with the name MAILER... or similar, are shown. Thanks for any help, Leonardo Lazarte - LLazarte@cnpq.br Dep.Matematica - Univ. de Brasilia - Brazil ================================================================================ Archive-Date: Wed, 26 May 1993 03:26:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 10:16:02 +0200 From: pizzorno@vms.gmd.de Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D137.3939DBC0.2114@vms.gmd.de> Subject: RE: MX stops Vax >After a couple of hours of starting MX, people are prevented of >entering our machine. The only solution is, if someone is logged >in, to STOP mx-related processes. Otherwise, switching the machine >off and on. What error message (if at all) is displayed when your users try to log into the machine? .. Juan ================================================================================ Archive-Date: Wed, 26 May 1993 05:35:48 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: MX SMTP and TELNET Date: 26 May 1993 09:42:21 GMT Message-ID: <1tve1tINN2k6d@rs1.rrz.Uni-Koeln.DE> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993May25.165519.1665@dmc.com>, system@dmc.com writes: >Well, the confusion was mine, at least about the error message. >You CAN telnet to port 25 AND the connection is indeed rejected. >There APPEARS to be a problem with Multinet (3.2B) in that if I >stop MX and bring it back up, I STILL can't get to the SMTP >server. I have to restart the multinet server, THEN bring up >SMTP. Have you switched off Multinet's SMTP server via MULTINET CONFIGURE /SERVER ? -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ KOSMA = Koelner Observatorium fuer SubMillimeter-Astronomie Andreas Moravec TEL +49 (221) 470 3558 I. Physikalisches Institut FAX +49 (221) 470 5162 Universitaet zu Koeln TELEX 888 2291 UNIK D Zuelpicher Str. 77 INTERNET moravec@ph1.Uni-Koeln.DE 5000 Koeln 41, Germany X.400 S=Moravec;OU=Ph1;P=Uni-Koeln;A=DBP;C=DE ================================================================================ Archive-Date: Wed, 26 May 1993 08:41:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 09:36:08 -0400 (EDT) From: "Clay M. Denton - THE SIG" Reply-To: MX-List@WKUVX1.BITNET Subject: More on MX-SMTP problem To: MX-List@WKUVX1.BITNET Message-ID: <01GYMKDV5TXU003B7Y@Eisner.DECUS.Org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Here is some more info on my problem. 2 weeks ago I upgraded from MX 3.1 to 3.3. Mail locally or inbound works great. Outbound mail through the MX - SMTP delivery agent doesn't work. MX_SMTP accvio's when it runs. The configuration is: VMS 5.5-2 UCX 2.0 MX 3.3 I reinstalled MX and even rebooted the systems. SMTP is disabled in UCX. I'm running out of things to look for and have over 100 messages waiting to go out. Help! Clay Denton McDonnell Douglas Aerospace (713) 244-4884 ================================================================================ Archive-Date: Wed, 26 May 1993 09:15:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 09:54:54 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: <0096D134.46016700.31962@swdev.si.com> Subject: RE: More on MX-SMTP problem Clay Denton writes: > The configuration is: > > VMS 5.5-2 > UCX 2.0 > MX 3.3 Have you applied the UCX V2.0B patches? Word is that UCX V2.0 without patches is quite unstable. Brian Tillman tillman_brian@si.com ================================================================================ Archive-Date: Wed, 26 May 1993 10:13:02 CDT Sender: list-mgr@WKUVX1.BITNET Return-Path: Date: Wed, 26 May 1993 17:06:52 EDT From: Why not ? Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D170.9E581398.15790@cal.enst.fr> Subject: MX records lookup after canonicalisation ? I have a problem in a SMTP/IP configuration... Two antagonist system so-called managers built a mail system where - a machine is called res, maintained by one system manager. - res is translated to dameron.res.enst.fr by the internet DNS - there is a MX record for res pointing to, of course, another machine when i try to send mail to somebody at res, the name is expanded into dameron.res.Enst.fr and then translated to dameron.res, using rewriting rules. The message is given to an external mailer, since the domain contains a dot. The external mailer, maintained by the other system non-manager, bombs since this machine is not in the configuration file ... the question is: should the canonicalisation be done before the MX search ? i disabled the canonicalisation. Can this cause a problem when all external mails are processed by another (non mx) router ? ================================================================================ Archive-Date: Wed, 26 May 1993 10:49:09 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 11:37:35 -0400 (EDT) From: "Clay M. Denton - THE SIG" Reply-To: MX-List@WKUVX1.BITNET Subject: Re: More on MX-SMTP problem To: MX-List@WKUVX1.BITNET Message-ID: <01GYMOMOJASY003GXV@Eisner.DECUS.Org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT I am running UCX 2.0B Clay Denton ================================================================================ Archive-Date: Wed, 26 May 1993 13:03:28 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Quoting DECnet user, NODE::"USER NAME" Message-ID: <1993May25.160206.2026@elcsci.com> Date: 25 May 93 16:02:06 PST To: MX-List@WKUVX1.BITNET I'm having a problem with getting the proper sets of quotation marks inserted into a local message. I have a Macintosh that is running Alisa's MailMate/MM to provide a DECnet mail link to my VAX which is running MX 3.3. The Macintosh user name can contain spaces or other strange characters. The Macintosh is defined as DECnet node MCMAIL, so directly from VMS mail I can send to MCMAIL::"Network^Manager". While this works, I had wanted to route these messages through MX so that the Macintosh receipient could see all the headers such as the CC receipients on the VAX. Alisa only passes on the names of people on the Macintosh that received the message. Unfortunately, I can't seem to get MX to properly quote the Network^Manager string. Below is a sample of one of my failed attempts. Is there re-write rule or something else simple that I'm missing that will allow MX to deliver a local message that is of the form NODE::"qutoed user"? Thanks for any pointers. Chuck Lewis ---------------------------Example follows------------------------------ From: MX%"Postmaster@TENOR" 25-MAY-1993 15:50:16.60 To: LEWISC CC: Subj: LOCAL delivery error Return-Path: <> Date: Tue, 25 May 1993 15:50:11 PST From: Local delivery agent To: Subject: LOCAL delivery error X-Report-Type: Nondelivery; boundary="> Error description:" 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: mcmail::network^manager@TENOR Error-Code: 2 Error-Text: Error in delivery to user mcmail::Network^Manager %MAIL-E-USERSPEC, invalid user specification '^MANAGER' <<<<<<< ^^^^^^^^^^^^^^^^^^ <<<<<<< Note that there are no quotes around Network^Manager <<<<<<< Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ Received: by TENOR.ELCSCI.COM (MX V3.3 VAX) id 7093; Tue, 25 May 1993 15:50:08 PST Sender: lewisc@TENOR Date: Tue, 25 May 1993 15:50:07 PST From: Chuck Lewis Reply-To: lewisc@tenor.elcsci.com To: "mcmail::""Network^Manager"""@tenor.elcsci.com <<<<<<< ^^^^^^^^^^^^^^^^^^^ <<<<<<< Note that there are quotes around Network^Manager here! <<<<<<< Message-ID: <0096D09C.BAE8E860.7093@TENOR.ELCSCI.COM> Subject: test ______________________________________________________________________________ |Chuck Lewis, Electro Scientific Industries |Internet: lewisc@elcsci.com |13900 NW Science Park, Portland Or 97229 |Compuserve: 71140,2271 ================================================================================ Archive-Date: Wed, 26 May 1993 13:32:17 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 19:22:21 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: <0096D183.8C62BB00.11949@elm.cc.kcl.ac.uk> Subject: SMTP server crashing out ... I'm running MX 3.3 on a VAX 8800 under VMS 5.5-2 and the SMTP server seems to be seriously unstable. In the last few days, it has crashed about 10 times for no obvious reason. Does anyone know if there are any quotas that might cause this; or any bugs? More usefully, whats the best way to gain clues? I can tunr on SMTP tracing but I'm note sure I can risk filling my disk up with all the logs! The one things that's recently gained popularity here is the indiana University POP3 server and thats being used quite heavily on the node that crashes. On other nodes (2 8700's) with a similar software config, there seem to be no problems. Does anyone know if POP3 (which uses the MX SMTP server when sending mail) might have some bug? (Its version 1.7 of the IUPOP3 code I believe). All software runs over CMU 6.6-5A. Thanks for any hints or tips. Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Wed, 26 May 1993 14:10:28 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 14:10:06 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D157.EC8CAA80.14505@WKUVX1.BITNET> Subject: MX SMTP and UCX domain lookup problems Jerry Storrs of NCSU has a problem that has me stumped. He's running MX V3.3 and UCX V1.3. All MX SMTP domain lookups are failing. Here's a log that is typical of all of them: >21-MAY-1993 15:18:32.88 Processing queue entry number 1000 >21-MAY-1993 15:18:33.13 Recipient: , route=CCVAX1.CC.NCSU.EDU >21-MAY-1993 15:18:33.13 SMTP_SEND: looking up host name CCVAX1.CC.NCSU.EDU >21-MAY-1993 15:18:33.50 SMTP_SEND: Failed, sts=00000870 >21-MAY-1993 15:18:33.50 SMTP send failed, sts=0C278024, sts2=00000870 >21-MAY-1993 15:18:33.50 Recipient status=0C278024 for He does have a name server defined, and TELNET, etc., works just fine. But MX always returns this. Do any of you have any suggested courses of action? His UCX host info looked fine to me, as did the name server(s). The name servers are defined using the IP addresses, and the UCX$BIND_SERVER00x logicals look OK. Thanks for any suggestions. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 26 May 1993 15:13:32 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 16:03:10 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: goathunter@WKUVX1.BITNET Message-ID: <0096D167.B84A1D60.21742@nscvax.princeton.edu> Subject: RE: MX SMTP and UCX domain lookup problems Hunter Goatley writes: > >Jerry Storrs of NCSU has a problem that has me stumped. He's running >MX V3.3 and UCX V1.3. All MX SMTP domain lookups are failing. Here's >a log that is typical of all of them: > >>21-MAY-1993 15:18:32.88 Processing queue entry number 1000 >>21-MAY-1993 15:18:33.13 Recipient: , > route=CCVAX1.CC.NCSU.EDU >>21-MAY-1993 15:18:33.13 SMTP_SEND: looking up host name CCVAX1.CC.NCSU.EDU >>21-MAY-1993 15:18:33.50 SMTP_SEND: Failed, sts=00000870 >>21-MAY-1993 15:18:33.50 SMTP send failed, sts=0C278024, sts2=00000870 >>21-MAY-1993 15:18:33.50 Recipient status=0C278024 for > > >He does have a name server defined, and TELNET, etc., works just fine. >But MX always returns this. Do any of you have any suggested courses of >action? His UCX host info looked fine to me, as did the name >server(s). The name servers are defined using the IP addresses, and >the UCX$BIND_SERVER00x logicals look OK. > Not a clue Hunter, but I do have a question. Is there some reason why MX (and CMUOpenVMS..etc) write these "status=hexgibberish" messages to the logs? Translating gibberish to English is something that computers are so good at and people are so poor at.... 870 translates to "end of file" while C278024 translates to "no name-nomessage" which means, I guess, that I'm supposed to figure out which message file I need and then do a SET MESSAGE.... ************************************************************************* * * * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Wed, 26 May 1993 15:21:43 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 15:21:19 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D161.DF256080.14557@WKUVX1.BITNET> Subject: RE: MX SMTP and UCX domain lookup problems Mighty Firebreather writes: > > Hunter Goatley writes: >>>21-MAY-1993 15:18:33.50 SMTP_SEND: Failed, sts=00000870 >>>21-MAY-1993 15:18:33.50 SMTP send failed, sts=0C278024, sts2=00000870 > Not a clue Hunter, but I do have a question. Is there some reason >why MX (and CMUOpenVMS..etc) write these "status=hexgibberish" messages to the >logs? Translating gibberish to English is something that computers are so >good at and people are so poor at.... > This is already on my "next version" list. > 870 translates to "end of file" while C278024 translates to "no >name-nomessage" which means, I guess, that I'm supposed to figure out which >message file I need and then do a SET MESSAGE.... > I think the SS$_ENDOFFILE is returned when the name servers don't return any information for the remote node. The question here is why is no info returned for MX when it is for Telnet, etc. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 26 May 1993 15:25:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 15:24:43 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D162.59175560.14561@WKUVX1.BITNET> Subject: RE: SMTP server crashing out ... "Andy, Systems Manager" writes: > >I'm running MX 3.3 on a VAX 8800 under VMS 5.5-2 and the SMTP server seems to >be seriously unstable. In the last few days, it has crashed about 10 times for >no obvious reason. > That's not good. >Does anyone know if there are any quotas that might cause this; or any bugs? > There are no bugs that I know of, beyond anything documented in the MX release notes. >More usefully, whats the best way to gain clues? I can tunr on SMTP tracing but >I'm note sure I can risk filling my disk up with all the logs! > You could SET FILE/VERSION=10 or so on the MX_SMTP_DIR:MX_SMTP_LOG.LOG file. Since the server's crashing, the last log file should be the right one. What shows up in the MX_SMTP_DIR:MX_SMTP_node.LOG file as the exit status? >The one things that's recently gained popularity here is the indiana University >POP3 server and thats being used quite heavily on the node that crashes. On >other nodes (2 8700's) with a similar software config, there seem to be no >problems. Does anyone know if POP3 (which uses the MX SMTP server when sending >mail) might have some bug? (Its version 1.7 of the IUPOP3 code I believe). > I don't know of anyone else using POP3 with MX, so I don't have any idea. Anyone else? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 26 May 1993 15:44:46 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 13:06:03 -0700 (PDT) From: Phil Rand Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX SMTP and UCX domain lookup problems To: MX discussion Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 26 May 1993, Hunter Goatley wrote: > Date: Wed, 26 May 1993 14:10:06 CDT > From: Hunter Goatley > To: mx-list@WKUVX1.BITNET > Subject: MX SMTP and UCX domain lookup problems > > Jerry Storrs of NCSU has a problem that has me stumped. He's running > MX V3.3 and UCX V1.3. All MX SMTP domain lookups are failing. Here's > a log that is typical of all of them: > > >21-MAY-1993 15:18:32.88 Processing queue entry number 1000 > >21-MAY-1993 15:18:33.13 Recipient: , > route=CCVAX1.CC.NCSU.EDU > >21-MAY-1993 15:18:33.13 SMTP_SEND: looking up host name CCVAX1.CC.NCSU.EDU > >21-MAY-1993 15:18:33.50 SMTP_SEND: Failed, sts=00000870 > >21-MAY-1993 15:18:33.50 SMTP send failed, sts=0C278024, sts2=00000870 > >21-MAY-1993 15:18:33.50 Recipient status=0C278024 for > > > He does have a name server defined, and TELNET, etc., works just fine. > But MX always returns this. Do any of you have any suggested courses of > action? His UCX host info looked fine to me, as did the name > server(s). The name servers are defined using the IP addresses, and > the UCX$BIND_SERVER00x logicals look OK. > Here's a transcript of my attempt to look at his Domain Name System records (from my Ultrix/VAX 4.3 system). Notice that I could find the IP address for CCVAX1.CC.NCSU.EDU, but no records for NCSU.EDU: Script started on Wed May 26 13:03:47 1993 Wed May 26 13:03:48 PDT 1993 You have mail. # nslookup Default Server: Address: 192.220.250.1 > ls ncsu.edu [] Host or domain name Internet address *** Error during listing of ncsu.edu: No information > ccvax1.cc.ncsu.edu Server: Address: 192.220.250.1 Non-authoritative answer: Name: ccvax1.cc.ncsu.edu Address: 152.1.13.4 > # exit # script done on Wed May 26 13:04:35 1993 I don't know much about DNS, and maybe I wasn't using nslookup properly, but I'm suspicious that the problem may lie in his nameserver. I also tried telnetting to ccvax1.cc.ncsu.edu, port 25, and there was the MX 3.3 SMPT server, so that's not the problem... --Phil // Phil Rand prand@paul.spu.edu // Computer & Information Systems (206) 281-2428 // Seattle Pacific University, 3307 3rd Ave W, Seattle, WA 98119 ================================================================================ Archive-Date: Wed, 26 May 1993 15:58:29 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 16:51:07 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: goathunter@WKUVX1.BITNET Message-ID: <0096D16E.6B007C00.21761@nscvax.princeton.edu> Subject: RE: MX SMTP and UCX domain lookup problems Hunter Goatley writes: >Mighty Firebreather writes: >> >>logs? Translating gibberish to English is something that computers are so >>good at and people are so poor at.... >> >This is already on my "next version" list. > >> 870 translates to "end of file" while C278024 translates to "no >>name-nomessage" which means, I guess, that I'm supposed to figure out which >>message file I need and then do a SET MESSAGE.... >> >I think the SS$_ENDOFFILE is returned when the name servers don't >return any information for the remote node. The question here is why >is no info returned for MX when it is for Telnet, etc. > All right, I'll play straight man. :-) Actually there is not one question, there are two subquestions. Is the problem somehow with the server? Or with MX? The fact that telnet works suggests that the server is responding properly. The possibilities include the following: a. The query is never being sent at all, or b. The query is being directed to the wrong server, or c. The query is somehow defective without causing the server to do more than return SS$_ENDOFFILE, or d. MX is misinterpreting the response, or e. MX is looking at something other than the response to the current query, or ????? Does anyone have MX 3.3 working with UCX 1.3? ************************************************************************* * * * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Wed, 26 May 1993 16:19:28 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 17:09:50 EDT From: ANIL KHULLAR Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D171.086236BC.3943@cunyvms1.gc.cuny.edu> Subject: RE: SMTP server crashing out ... > I don't know of anyone else using POP3 with MX, so I don't have any > idea. Anyone else? > I have /and am running POP3 (multinet) and MX. No problem that I have been made aware of. POP3 only fetchs mail from the mailbox it is SMTP server that the client interacts to send mail. The clients we have successfully tested with are NuPOP, and POPmail. I do remember a memory leak in callable mail that iupop3 people mentioned a while ago. It should not however crash the MX server. Run DEBUG on MX SMTP server and send *many* messages via your POP client to see if the client is behaving normally. Anil ================================================================================ Archive-Date: Wed, 26 May 1993 17:30:36 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: SMTP server crashing out ... Message-ID: <1993May26.220437.25250@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 26 May 1993 22:04:37 GMT To: MX-List@WKUVX1.BITNET In article <0096D183.8C62BB00.11949@elm.cc.kcl.ac.uk>, "Andy, Systems Manager" writes: >I'm running MX 3.3 on a VAX 8800 under VMS 5.5-2 and the SMTP server seems to >be seriously unstable. In the last few days, it has crashed about 10 times for >no obvious reason. > >Does anyone know if there are any quotas that might cause this; or any bugs? > >More usefully, whats the best way to gain clues? I can tunr on SMTP tracing but >I'm note sure I can risk filling my disk up with all the logs! > >The one things that's recently gained popularity here is the indiana University >POP3 server and thats being used quite heavily on the node that crashes. On >other nodes (2 8700's) with a similar software config, there seem to be no >problems. Does anyone know if POP3 (which uses the MX SMTP server when sending >mail) might have some bug? (Its version 1.7 of the IUPOP3 code I believe). It's possible that the POP client software is presenting the SMTP server with a mal-formed SMTP transaction of some kind (POP is used only for reading mail; the client uses SMTP to send a message). And it could be the SMTP server isn't handling that case gracefully. I'd recommend turning on the SMTP server logs and trying to reproduce the problem: $ DEFINE/SYSTEM/EXE MX_SMTP_SERVER_DEBUG TRUE (log file will be MX_SMTP_DIR:SMTP_SERVER_LOG.LOG). Also, looking in the SMTP_SERVER_nodename.LOG file for a traceback or other information might help in figuring out what's going on. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Wed, 26 May 1993 17:30:42 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: MX SMTP and UCX domain lookup problems Message-ID: <1993May26.220111.25132@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 26 May 1993 22:01:11 GMT To: MX-List@WKUVX1.BITNET In article <0096D157.EC8CAA80.14505@WKUVX1.BITNET>, Hunter Goatley writes: >Jerry Storrs of NCSU has a problem that has me stumped. He's running >MX V3.3 and UCX V1.3. All MX SMTP domain lookups are failing. Here's >a log that is typical of all of them: > >>21-MAY-1993 15:18:32.88 Processing queue entry number 1000 >>21-MAY-1993 15:18:33.13 Recipient: , > route=CCVAX1.CC.NCSU.EDU >>21-MAY-1993 15:18:33.13 SMTP_SEND: looking up host name CCVAX1.CC.NCSU.EDU >>21-MAY-1993 15:18:33.50 SMTP_SEND: Failed, sts=00000870 >>21-MAY-1993 15:18:33.50 SMTP send failed, sts=0C278024, sts2=00000870 >>21-MAY-1993 15:18:33.50 Recipient status=0C278024 for > > >He does have a name server defined, and TELNET, etc., works just fine. >But MX always returns this. Do any of you have any suggested courses of >action? His UCX host info looked fine to me, as did the name >server(s). The name servers are defined using the IP addresses, and >the UCX$BIND_SERVER00x logicals look OK. I would recommend defining NETLIB_DEBUG as well as MX_SMTP_DEBUG as TRUE then re-starting the SMTP delivery agent. The debug log will then include the MX lookup debugging information as well as the SMTP debugging information. That might shed some light on what's going on. What should be happening is that the SMTP agent should be doing an MX lookup on CCVAX1.CC.NCSU.EDU, which should fail, then it should be asking UCX for an address for that host. The address lookup call (which uses the UCX IO$_ACPCONTROL QIO) is probably what is returning the end-of-file indicator (which is what UCX uses to mean that the lookup failed). -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Wed, 26 May 1993 18:32:42 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 93 18:56:22 EST From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: MX stops Vax To: MX-List@WKUVX1.BITNET Message-ID: <9305262156.AA06880@rnpdf2.cnpq.br> =>>After a couple of hours of starting MX, people are prevented of =>>entering our machine. The only solution is, if someone is logged =>>in, to STOP mx-related processes. Otherwise, switching the machine =>>off and on. => =>What error message (if at all) is displayed when your users try to =>log into the machine? =>.. Juan It says: "JBC-F-PRCREAT, error creating process" Leonardo ================================================================================ Archive-Date: Wed, 26 May 1993 20:47:53 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 17:54:02 CST From: Mike Frohme Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D177.35138AAC.8@thorin.ceri.memst.edu> Subject: RE: MX SMTP and UCX domain lookup problems > From: MX%"MX-List@WKUVX1.BITNET" 26-MAY-1993 15:57:30.79 > Subj: RE: MX SMTP and UCX domain lookup problems > Mighty Firebreather writes: > Hunter Goatley writes: > >Mighty Firebreather writes: > >> > > > Does anyone have MX 3.3 working with UCX 1.3? > Yep... though just barely. Multinet is being installed this week 8-). VMS V5.5-1 UCX V1.3A (patched to current patch level, ~4/93 -------------------------------------------------------------------------------- Michael K. Frohme Internet: m-frohme@memst.edu Center for Earthquake Research & Information (or) frohme@ceri.memst.edu Memphis State University Bitnet: frohmemk@memstvx1 Memphis, TN 38152 Phone: 901/678-2007 FAX: 901/323-2857 ================================================================================ Archive-Date: Wed, 26 May 1993 21:00:40 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: MX SMTP and UCX domain lookup problems Message-ID: <1993May26.223856.26428@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 26 May 1993 22:38:56 GMT To: MX-List@WKUVX1.BITNET In article <0096D161.DF256080.14557@WKUVX1.BITNET>, Hunter Goatley writes: >> 870 translates to "end of file" while C278024 translates to "no >>name-nomessage" which means, I guess, that I'm supposed to figure out which >>message file I need and then do a SET MESSAGE.... >> >I think the SS$_ENDOFFILE is returned when the name servers don't >return any information for the remote node. The question here is why >is no info returned for MX when it is for Telnet, etc. Right. NETLIB tries to use UCX status codes regardless of which TCP/IP package you're using -- it translates package-specific codes into UCX codes whenever it can. If you've got a copy of the UCX docs, you should find an explanation for SS$_ENDOFFILE. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Wed, 26 May 1993 21:27:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 21:27:27 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D195.055FDFE0.14663@WKUVX1.BITNET> Subject: RE: MX stops Vax writes: > >=>>After a couple of hours of starting MX, people are prevented of >=>>entering our machine. The only solution is, if someone is logged >=>>in, to STOP mx-related processes. Otherwise, switching the machine >=>>off and on. >=> >=>What error message (if at all) is displayed when your users try to >=>log into the machine? >=>.. Juan > >It says: "JBC-F-PRCREAT, error creating process" > Sounds like you may not have enough process slots available. Try increasing the SYSGEN parameters BALSETCNT and MAXPROCESSCNT and rebooting. Since MX does create several processes, depending on the agents installed, this sounds like the solution to your problem. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 26 May 1993 21:51:16 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 26 May 1993 22:07:01 -0300 (ADT) From: Greg Bishop Subject: MX delivering mail to the wrong DECnet node To: mx-list@WKUVX1.BITNET Reply-To: MX-List@WKUVX1.BITNET Message-ID: <0096D19A.8BFD4B00.18605@ac.nsac.ns.ca> Content-Transfer-Encoding: 7BIT I'm having a problem with MX sending my mail to the wrong node. Mailing from my account on ac.nsac.ns.ca to my account on pam.nsac.ns.ca works fine if I use the complete address (ie. gb@pam.nsac.ns.ca). ----- From: MX%"gbishop@ac.nsac.ns.ca" 26-MAY-1993 21:17:02.78 To: GB CC: Subj: testing from ac to pam.nsac.ns.ca Return-Path: Received: from AC (AC::MAILER) by PAM (MX V3.3 VAX) with SMTP (DECnet); Wed, 26 May 1993 21:16:55 ADT Received: by ac.nsac.ns.ca (MX V3.3 VAX) id 18583; Wed, 26 May 1993 21:16:45 ADT Date: Wed, 26 May 1993 21:16:44 ADT From: Greg Bishop Reply-To: gbishop@ac.nsac.ns.ca To: gb@pam.nsac.ns.ca Message-ID: <0096D193.8611A760.18583@ac.nsac.ns.ca> Subject: testing from ac to pam.nsac.ns.ca testing ----- However if I try to send to "gb@pam" the mail arrives at my account on gus.nsac.ns.ca as shown in the message below. ------ From: MX%"gbishop@ac.nsac.ns.ca" 26-MAY-1993 21:18:25.71 To: GB CC: Subj: testing from ac to pam Return-Path: Received: from AC (AC::MAILER) by GUS (MX V3.3 VAX) with SMTP (DECnet); Wed, 26 May 1993 21:18:19 AST Received: by ac.nsac.ns.ca (MX V3.3 VAX) id 18587; Wed, 26 May 1993 21:18:16 ADT Date: Wed, 26 May 1993 21:18:14 ADT From: Greg Bishop Reply-To: gbishop@ac.nsac.ns.ca To: gb@gus.nsac.ns.ca < **** weirdness *****> Message-ID: <0096D193.BBDFC340.18587@ac.nsac.ns.ca> Subject: testing from ac to pam testing ----- Why is MX doing this to me? It causes some really nasty mail loops if I try to send somethimg from my account on Pam to my account on Gus. (Actually I haven't tried since I upgraded to v3.3. I haven't gotten up the courage to intentionally start another one of these loops just to test the new mail loop detection code that MX is supposed to have now.) I've included my domain-to-path mappings on ac.nsac.ns.ca below. Any help would be much appreciated. ----- Domain-to-path mappings: Domain="ac.nsac.ns.ca", Path=Local Domain="[192.75.138.1]", Path=Local Domain="AC", Path=Local Domain="gus.nsac.ns.ca", Path=DECnet_SMTP, Route="Gus" Domain="[192.75.138.2]", Path=DECnet_SMTP, Route="Gus" Domain="GUS", Path=DECnet_SMTP, Route="Gus" Domain="pam.nsac.ns.ca", Path=DECnet_SMTP, Route="Pam" Domain="[192.75.138.3]", Path=DECnet_SMTP, Route="Pam" Domain="PAM", Path=DECnet_SMTP, Route="Pam" Domain="*.BITNET", Path=SMTP, Route="AC.DAL.CA" Domain="*.UUCP", Path=SMTP, Route="UUNET.UU.NET" Domain="*", Path=SMTP ----- 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: Wed, 26 May 1993 21:55:52 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 12:31:25 +1000 From: bellamy@commerce.uq.edu.au Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D213.4DB94F00.9128@covax.commerce.uq.oz.au> Subject: Re: SMTP server crashing out ... 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: SMTP server crashing out ... Message-ID: From: bellamy@commerce.uq.edu.au (David Bellamy) Date: 27 May 93 12:31:19 +1000 Followup-To: comp.mail.mx References: <1993May26.220437.25250@news.arc.nasa.gov> Distribution: world,local Organization: The University of Queensland Nntp-Posting-Host: test1.commerce.uq.oz.au Lines: 45 In article <1993May26.220437.25250@news.arc.nasa.gov>, wrote: > > In article <0096D183.8C62BB00.11949@elm.cc.kcl.ac.uk>, "Andy, Systems Manager" > writes: > >I'm running MX 3.3 on a VAX 8800 under VMS 5.5-2 and the SMTP server seems to > >be seriously unstable. In the last few days, it has crashed about 10 times for > >The one things that's recently gained popularity here is the indiana University > >POP3 server and thats being used quite heavily on the node that crashes. On > >other nodes (2 8700's) with a similar software config, there seem to be no > >problems. Does anyone know if POP3 (which uses the MX SMTP server when sending > >mail) might have some bug? (Its version 1.7 of the IUPOP3 code I believe). > Very unlikely to be the POP server. There is basically no interaction between IUPOP3 and MX. IUPOP3 only interacts with a client POP client (Eudora here) for the delivery of mail from the post box to the client (effectively the same as login and read mail via vax-mail). IUPOP3 does NOT send mail, it is up to the POP3 client to pass mail directly to the SMTP host - MX in out case. Our setup: VMS 5.5-2 MX 3.3 IUPOP3 1.7 UCX 2.0 (some patched version that seems to work most of the time :-) The only problem we have had with IUPOP3 is the memory leak in the callable mail interface which will (eventually) cause IUPOP3 to fail with insufficient virtual memory. A problem which has taken DEC about two years to admit that even exists and the best that they say is "will be fixed in VMS 6.1". Not even a suggestion of a patch to 5.5-2 or 6.0. I'd check for a quota problem and don't forget UCX resources such as sockets - make sure you have enough for MX and your telnet sessions (I seem to recall that this was a problem with early versions of UCX 1.3) Cheers. _________________________________________________________________ David Bellamy. Deparment of Commerce. The University of Queensland. Australia. Internet: bellamy@commerce.uq.edu.au ================================================================================ Archive-Date: Thu, 27 May 1993 02:51:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 09:48:36 +0200 From: pizzorno@vms.gmd.de Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D1FC.8E9825C0.2201@vms.gmd.de> Subject: RE: MX stops Vax > writes: >> >>It says: "JBC-F-PRCREAT, error creating process" >> >Sounds like you may not have enough process slots available. Try >increasing the SYSGEN parameters BALSETCNT and MAXPROCESSCNT and >rebooting. Since MX does create several processes, depending on the >agents installed, this sounds like the solution to your problem. > >Hunter My guess too. Should that really be the problem, running sys$update:autogen.com is probably a good idea... (If you're running out of PCBs, I'd bet other "dials" need some turning, too.) .. Juan ================================================================================ Archive-Date: Thu, 27 May 1993 06:31:14 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 12:24:13 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: <0096D212.4C046880.12762@elm.cc.kcl.ac.uk> Subject: SMTP crashing out ... My thanks to all who gave particularly helpful suggestions about my SMTP server crashing out. There are various tricks one can apply here. 1. Look in the accounting file for the termination code of the smtp server process. 2. Turn on SMTP tracing BUT add a /VERSION limit to the tracing log file. This will limit the amount of disk space needed but still preserve the last one active when a crash occurs. In fact, the accounting log status code solved my problem. It seems that the underlying IP transport (CMU 6.6-5A in my case) was crashing. The SMTP server is the only one of the MX modules that also went away when the network did. Could I suggest, for the `next release' that none of the MX processes go away if the IP ransport does? This avoids human intervention to restart everything. Thanks to all who responded. Now i have to sort out why CMU keeps crashing... Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Thu, 27 May 1993 08:54:11 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 09:32:55 EDT From: "Brian Tillman, Smiths Industries, VAX Support, x8425" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D1FA.5E47EE80.228@swdev.si.com> Subject: Documentation won't print any more I extracted the PostScript documentation for MX V3.3 from the .K save set so I could print it prior to installation. This is what I did for V3.2. However, while I could print V3.2's docs just fine, my printer will not print V3.3's docs. It bombs with the message: Error: undefined OffendingCommand: ISOLatin1Encoding What can I do to make the PostScript printable? -----------------------------+-------------------------------- 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, 27 May 1993 09:32:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 09:23:01 CST From: Howard Meadows Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D1F8.FBA53040.16460@cslvax.weeg.uiowa.edu> Subject: RE: Documentation won't print any more Brian Tillman wrote: > >I extracted the PostScript documentation for MX V3.3 from the .K save set so I >could print it prior to installation. This is what I did for V3.2. However, >while I could print V3.2's docs just fine, my printer will not print V3.3's >docs. It bombs with the message: > >Error: undefined >OffendingCommand: ISOLatin1Encoding > >What can I do to make the PostScript printable? > You don't happen to have a Talaris T2090 Printstation do you? This same error happened to me using that printer, and it turned out they had a setup module for their text library that enabled printing of ISOLatin1Encoding PostScript docs. If this is the printer you have, contact Talaris for the module. They should be able to email it to you (that's what they did for me). -Howard *************************************************************************** * Howard Meadows Sr. Systems Programmer Weeg Computing Center * * University Of Iowa Iowa City, Iowa 52242 Phone: 319-335-5519 * * email: howard-meadows@uiowa.edu * *************************************************************************** ================================================================================ Archive-Date: Thu, 27 May 1993 09:55:52 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <9305271553.AA06623@bogart.mpib-tuebingen.mpg.de> To: MX-List@WKUVX1.BITNET CC: boerner@bogart.mpib-tuebingen.mpg.de Subject: MGMT_GUIDE.PS;2 Date: Thu, 27 May 93 16:53:19 +0100 From: boerner@bogart.mpib-tuebingen.mpg.de Reply-To: MX-List@WKUVX1.BITNET Hi, could it be, that the postsciptfile MGMT_GUIDE.PS;2 have a bug ???? :-( After overview of Message .... 1-2 there is no output. gruss rudi ================================================================================ Archive-Date: Thu, 27 May 1993 10:21:20 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 10:20:59 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D201.15351900.14931@WKUVX1.BITNET> Subject: RE: MGMT_GUIDE.PS;2 boerner@bogart.mpib-tuebingen.mpg.de writes: > >could it be, that the postsciptfile MGMT_GUIDE.PS;2 have a bug ???? :-( >After overview of Message .... 1-2 there is no output. > The file checks out just fine with Ghostscript. I must confess that I've never printed it out myself. However, I think this problem may be that page 1-3 contains a graphic figure showing the relationships among the various pieces of MX. Perhaps some printers are lacking in memory to handle it? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 27 May 1993 10:29:47 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 11:23:15 EDT From: "Tim McKee, 803-366-2620" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D209.C7A02BE0.8346@cvse.cortex.prospect.com> Subject: RE: MGMT_GUIDE.PS;2 It prints just fine using an LN06 with the DEC CPS042 software... tim ================================================================================ Timothy R. McKee | Senior Consultant - VAX/VMS Internals Cortex Corp. - SouthEast Field Office | mckeetr@cvse.cortex.prospect.com Phone: (803) 366-2620 | FAX: (803) 366-6517 ================================================================================ ================================================================================ Archive-Date: Thu, 27 May 1993 10:49:59 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 10:40:02 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D203.BE0A9DA0.7987@SHSU.edu> Subject: RE: MGMT_GUIDE.PS;2 On Thu, 27 May 1993 10:20:59 CDT, Hunter Goatley posted: > boerner@bogart.mpib-tuebingen.mpg.de writes: > > > >could it be, that the postsciptfile MGMT_GUIDE.PS;2 have a bug ???? :-( > >After overview of Message .... 1-2 there is no output. > > > The file checks out just fine with Ghostscript. I must confess that I've > never printed it out myself. However, I think this problem may be that > page 1-3 contains a graphic figure showing the relationships among the > various pieces of MX. Perhaps some printers are lacking in memory to > handle it? I don't know if that has anything to do with it or not, but the changebars in the MX_ROOT:[DOC]*.TXT files (as well as a few other characters) are misplaced as if they were mis-translated (rather than kill trees and use toner, I prefer to use the *.TXT files as I don't have the hardware for bookreader format). Could it be that the docs didn't get converted right across everything? --George ================================================================================ Archive-Date: Thu, 27 May 1993 10:57:32 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 17:50:10 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: <0096D23F.D4D686C0.27480@europa.rs.ch> Subject: RE: MGMT_GUIDE.PS;2 >It prints just fine using an LN06 with the DEC CPS042 >software... Same on an LN05R with DEC CPS041 Ralph +---------------+---------------------------------------------------------+ I Ralph Kloess I I-Net: Kloess@europa.rs.ch I I I Standard disclaimer applies to all my messages I +---------------+---------------------------------------------------------+ ================================================================================ Archive-Date: Thu, 27 May 1993 11:54:56 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 11:54:38 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D20E.2A6781C0.14991@WKUVX1.BITNET> Subject: RE: MGMT_GUIDE.PS;2 "George D. Greenwade" writes: > >I don't know if that has anything to do with it or not, but the changebars >in the MX_ROOT:[DOC]*.TXT files (as well as a few other characters) are >misplaced as if they were mis-translated (rather than kill trees and use >toner, I prefer to use the *.TXT files as I don't have the hardware for >bookreader format). Could it be that the docs didn't get converted right >across everything? > The .TXT change-bar problem is apparently a bug in VAX DOCUMENT V2.2. I was too lazy to go back to V2.1 before generating the docs. I suppose that there could be some other PS change in V2.2. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 27 May 1993 12:17:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 10:48:46 CST From: Howard Meadows Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D204.F6DBCAE0.16484@cslvax.weeg.uiowa.edu> Subject: RE: MGMT_GUIDE.PS;2 Hunter Goatley writes: >boerner@bogart.mpib-tuebingen.mpg.de writes: >> >>could it be, that the postsciptfile MGMT_GUIDE.PS;2 have a bug ???? :-( >>After overview of Message .... 1-2 there is no output. >> >The file checks out just fine with Ghostscript. I must confess that >I've never printed it out myself. However, I think this problem may >be that page 1-3 contains a graphic figure showing the relationships >among the various pieces of MX. Perhaps some printers are lacking in >memory to handle it? > and "Tim McKee, 803-366-2620" writes: > >It prints just fine using an LN06 with the DEC CPS042 >software... > I really think this is a problem with the printer. The docs were created with VAX DOCUMENT. Newer versions of DOCUMENT have this "ISOLATIN1 encoding". The same thing exists with DEC docs from their CDDOC distribution. I had a printer that used to print them just fine, but suddenly failed with the same message about the "ISOLATIN1 encoding", but they'd print fine on a DEC printer. After receiving a setup module from the printer manufacturer to handle the "ISOLATIN1" stuff, it worked fine... -Howard *************************************************************************** * Howard Meadows Sr. Systems Programmer Weeg Computing Center * * University Of Iowa Iowa City, Iowa 52242 Phone: 319-335-5519 * * email: howard-meadows@uiowa.edu * *************************************************************************** ================================================================================ Archive-Date: Thu, 27 May 1993 13:15:38 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 13:54:46 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: <0096D21E.F2812480.702@swdev.si.com> Subject: RE: ISOLATIN1Encoding As I had said earlier, my PostScript printer failed on all of the V3.3 docs with an error reference to ISOLATIN1Encoding. Howard Meadows of the U of I wrote that said he had the same problem with a Talaris 2090 printer. In fact, that's exactly the printer I was trying to use. Howard also said Talaris supplied him with a short PostScript program that could be prepended to the docs to make them work. I called Talaris and they emailed me the module as well. Here it is. There were no copyright notices on it, so I feel safe about posting it. %!PS-Adobe mark /ISOLatin1Encoding 8#000 1 8#054 {StandardEncoding exch get} for /minus 8#056 1 8#217 {StandardEncoding exch get} for /dotlessi 8#301 1 8#317 {StandardEncoding exch get} for /space /exclamdown /cent /sterling /currency /yen /brokenbar /section /dieresis /copyright /ordfeminine /guillemotleft /logicalnot /hyphen /registered /macron /degree /plusminus /twosuperior /threesuperior /acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright /onequarter /onehalf /threequarters /questiondown /Agrave /Aacute /Acircumflex /Atilde /Adieresis /Aring /AE /Ccedilla /Egrave /Eacute /Ecircumflex /Edieresis /Igrave /Iacute /Icircumflex /Idieresis /Eth /Ntilde /Ograve /Oacute /Ocircumflex /Otilde /Odieresis /multiply /Oslash /Ugrave /Uacute /Ucircumflex /Udieresis /Yacute /Thorn /germandbls /agrave /aacute /acircumflex /atilde /adieresis /aring /ae /ccedilla /egrave /eacute /ecircumflex /edieresis /igrave /iacute /icircumflex /idieresis /eth /ntilde /ograve /oacute /ocircumflex /otilde /odieresis /divide /oslash /ugrave /uacute /ucircumflex /udieresis /yacute /thorn /ydieresis /ISOLatin1Encoding where not {256 array astore def} if cleartomark -----------------------------+-------------------------------- 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, 27 May 1993 17:57:02 CDT Sender: list-mgr@WKUVX1.BITNET Subject: More on Mailing List woes. Message-ID: <1993May26.152706.764@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 26 May 93 15:27:05 +1000 To: MX-List@WKUVX1.BITNET Well, I managed to get the mailing lists working again. I deleted all the REWRITE rules. Further investigation seems to show that if the address is matched at all during the rewrite phase of router processing then the router doesn't pick up that it is a mailing list message and delivers it to the LOCAL agent, via the PATH rule. It also looks like it bypasses the ALIAS translation function as well. This behaviour is identical in both MX 3.1c and 3.3. This is a pain as I want the local users to be able to use addresses in the form @.hhcs.gov.au and the UUCP/MX node is called cnb09w.hhcs.gov.au so it, of course, matches that rewrite rule, MLF and ALIAS get ignored, it gets routed to LOCAL which bounces back an error saying that there is no local user. Now I'm trying to figure out work-arounds. :-( 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: Thu, 27 May 1993 20:32:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 20:31:40 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D256.64CBD9E0.15194@WKUVX1.BITNET> Subject: RE: More on Mailing List woes. Carl Makin writes: > >Well, I managed to get the mailing lists working again. > >I deleted all the REWRITE rules. > You shouldn't need to use REWRITE_RULES to do what you want. Looking back at your original message, I see that the problem is caused by an incorrect REWRITE_RULE. You have (had?): > Rewrite "<{to}@cnb09w.hhcs.gov.au>" => "<""{to}""@cnb09w.hhcs.gov.au>" The debug log you posted shows: >19-MAY-1993 12:51:48.09 %REWRITE, Applying rewrite rule: > <{to}@cnb09w.hhcs.gov.au> => <"{to}"@cnb09w.hhcs.gov.au> > to: [...] >19-MAY-1993 12:51:48.40 %PROCESS, Rewrote as > <"test-request"@cnb09w.hhcs.gov.au> >- next hop cnb09w.hhcs.gov.au, path 1 >19-MAY-1993 12:51:48.40 %FINDALIAS, no alias found for "test-request" >19-MAY-1993 12:51:48.40 %PROCESS, no alias found for "test-request" >19-MAY-1993 12:51:48.41 %PROCESS, this is just a local delivery >19-MAY-1993 12:51:48.50 %PROCESS, Adding to LOCAL path: "test-request". Your problems are caused by the quotes in the rewritten version ("{to}"). Note the %PROCESS line above that shows was rewritten as <"test-request"....>. MX then checked MLF and ALIAS info for "test-request", which failed because the quotes were present. In fact, you don't need REWRITE_RULES like that one above anyway. Just make sure you have a PATH defined for the local node(s). Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 28 May 1993 06:12:12 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX rewrite rules? Message-ID: <1993May27.225044.155@rygel.anorad.com> Date: 27 May 93 22:50:44 EST To: MX-List@WKUVX1.BITNET Can somebody please post a sample rewrite rule to correctly transform an address from "NODE::USER" to "user@node.domain.org"? We have three machines on our network. Sending mail from any machine except for the machine that has MX running on it comes up with a return address like "USER%NODE.dnet@domain.org". I've tried getting rid of NAME_CONVERSION, but this results in an address of "USER::NODE@node.domain.org" ( where the second "node" is the machine with MX on it ). These machines are NOT clustered, just DECnet-ed. I've been fighting with this for days and can't seem to get it right. Any help would be appreciated. +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mikel Beck - Senior Business Programmer, Anorad Corporation | | E-Mail: mikel@rygel.anorad.com | | "Excellence In Motion" | +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ ================================================================================ Archive-Date: Fri, 28 May 1993 09:58:22 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 27 May 1993 14:58:07 PST From: Chuck Lewis Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D227.CC0474C0.7357@TENOR.ELCSCI.COM> Subject: DECNET -> SITE interface? Has anyone every developed a SITE interface for incoming DECnet mail? I have a couple of problem with addressing that I could probably solve if DECnet mail received on my VAX went through MX just like SMTP messages. Before I rush out an replace all the DECnet mail links with new SMTP software, I thought it was worth while to see if anyone had replaced the standard DEC DECnet object that receives mail with something that would feed the SITE IN capability of MX. Thanks, ______________________________________________________________________________ |Chuck Lewis, Electro Scientific Industries |Internet: lewisc@elcsci.com |13900 NW Science Park, Portland Or 97229 |Compuserve: 71140,2271 ================================================================================ Archive-Date: Fri, 28 May 1993 10:13:35 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: using MX with mx Message-ID: <1993May28.101819.597@condor.navsses.navy.mil> Date: 28 May 93 10:18:19 -0600 To: MX-List@WKUVX1.BITNET I have a need to have MX V3.3 act as a message exchanger (via the DNS MX resource record) for a few hosts in my local domain. Is this possible? If so how do I set this up? I just tried this and I came up with a mail loop on my VAXen. Thanks. -- Mike Jacobi NAVSSES VAXCluster system manager System@Eagle.Navsses.Navy.Mil System@Condor.Navsses.Navy.Mil Disclaimer - I speak for myself. No-one else. ================================================================================ Archive-Date: Fri, 28 May 1993 10:23:39 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: MX SMTP and UCX domain lookup problems Date: 28 May 1993 13:23:47 GMT Message-ID: <1u53p3$qo9@samba.oit.unc.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Mighty Firebreather writes: > Does anyone have MX 3.3 working with UCX 1.3? Yes. MX 3.3, UCX 1.3, VMS 5.4-3. Just look at all those trailing 3's... :-) -- Dennis R. Sherman Triangle Research Libraries Network dennis_sherman@unc.edu Univ. of North Carolina - Chapel Hill ================================================================================ Archive-Date: Fri, 28 May 1993 10:56:52 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MGMT_GUIDE.PS;2 Date: 28 May 1993 15:30:59 GMT Message-ID: <1u5b7jINNc08@CS.UTK.EDU> Keywords: MX, Postscript To: MX-List@WKUVX1.BITNET In article <9305271553.AA06623@bogart.mpib-tuebingen.mpg.de>, boerner@bogart.mpib-tuebingen.mpg.de writes: > > [does the] Postscipt file MGMT_GUIDE.PS;2 have a bug ???? :-( > After overview of Message .... 1-2 there is no output. The first time I printed this manual, I used the "Freedom of Press" software Postscript interpreter running on a relatively old MS-DOS machine, possessing no 80x87 math co-processor, driving a Hewlett- Packard Deskjet 500. Pages 1 and 2 printed, then a LONG pause... (of about 15 minutes) and I too thought something was broken, but then the printer started up and page 3 came out bearing the impression of the graphical image. It can just take longer than you expect for Postscript to make sense of the diagram. ("Freedom of Press"--without "the"--is a product sold by Colorsoft. "Freedom of the press" is a civil right accruing to persons that own printing presses, or the logical equivalents thereof.) -- ...Richard S. Shuford | "When the righteous triumph, there is great elation; ...shuford@cs.utk.edu | but when the wicked rise to power, men go into ...Info-Stratus contact| hiding." Proverbs 28:12 NIV ================================================================================ Archive-Date: Fri, 28 May 1993 11:10:31 CDT Sender: list-mgr@WKUVX1.BITNET From: bg@dymaxion.ns.ca Reply-To: MX-List@WKUVX1.BITNET Subject: Subscribing one mailing list to another Message-ID: <1993May28.084827.1636@dymaxion.ns.ca> Date: 28 May 93 08:48:27 AST To: MX-List@WKUVX1.BITNET Why can't I subscribe a mailing list to another mailing list with MX 3.1 and 3.3? Here's what happens: >From: MX%"Postmaster@dymaxion.ns.ca" 17-MAY-1993 15:42:50.05 >To: BG >CC: >Subj: Mailing list or file server error > >Return-Path: <> >Date: Mon, 17 May 1993 15:42:41 ADT >From: Mailing list & file server >To: >Subject: Mailing list or file server error > >Note: this message was generated automatically. > >The following error(s) occurred during local delivery of your message. > >Error in delivery to mailing list MUG-L: > access denied; send subscription requests to MUG-L-Request@dymaxion.ns.ca >Message follows. > >Errors-To: bg@DYMAXION.NS.CA >X-ListName: Medianet media management system discussion group >Received: from bingsuns.cc.binghamton.edu (bingsuns.cc.binghamton.edu) by dymaxion.ns.ca (MX V3.1C) with SMTP; Mon, 17 May 1993 15:41:50 ADT >Received: by bingsuns.cc.binghamton.edu (4.1/SMI-4.0) id AA13061; Mon, 17 May 93 14:38:08 EDT >From: jdonahue@bingsuns.cc.binghamton.edu (jdonahue) >Reply-To: Medianet-L@dymaxion.ns.ca >Message-ID: <9305171838.AA13061@bingsuns.cc.binghamton.edu > >Subject: New platform? >To: medianet-l@dymaxion.ns.ca (medianet-l) >Date: Mon, 17 May 93 14:38:07 EDT >X-Mailer: ELM [version 2.3 PL11] > >Greetings, > [ body of message deleted ] MUG-L (a user group list) subscribes to Medianet-L (a general interest list). I have no desire to subscribe each and every member of MUG-L individually to Medianet-L. 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: Fri, 28 May 1993 12:07:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: 28 May 1993 12:58:15 -0400 (EDT) From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Subscribing one mailing list to another To: MX-List@WKUVX1.BITNET CC: bg@dymaxion.ns.ca, hardis@garnet.nist.gov Message-ID: <0096D2E0.37C282C0.14755@garnet.nist.gov> Content-Transfer-Encoding: 7BIT > Why can't I subscribe a mailing list to another mailing list with > MX 3.1 and 3.3? > Here's what happens: >>Error in delivery to mailing list MUG-L: >> access denied; send subscription requests to MUG-L-Request@dymaxion.ns.ca Huh?? I don't understand the context. Are you saying that a mail message was sent from an account with the _same name_ as a mailing list on the _same host_ with a SUBSCRIBE command, and it was rejected? Are you saying that the list manager is unable to add a mailing list address onto his list? Are you saying that the list privileges should allow the list address to be added, yet it can't be? ================================================================================ Archive-Date: Fri, 28 May 1993 12:20:26 CDT Sender: list-mgr@WKUVX1.BITNET Date: 28 May 1993 13:09:04 -0400 (EDT) From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET Subject: RE: using MX with mx To: MX-List@WKUVX1.BITNET CC: system@condor.navsses.navy.mil, hardis@garnet.nist.gov Message-ID: <0096D2E1.BA874460.14759@garnet.nist.gov> Content-Transfer-Encoding: 7BIT > I have a need to have MX V3.3 act as a message exchanger (via the DNS MX > resource record) for a few hosts in my local domain. Is this possible? > If so how do I set this up? I just tried this and I came up with a mail > loop on my VAXen. Please specify the problem better. Let's say you want mail destined for a.navy.mil, b.navy.mil, and c.navy.mil to all be sent to x.navy.mil, and you set up MX records that say so. Now, mail comes in for b.navy.mil to x.navy.mil. How is x.navy.mil actually supposed to get the mail to b.navy.mil? Are both hosts on an IP network? If so, how is x.navy.mil supposed to bypass the name server (which would only tell it to send the mail to itself)? Do you intend to hard-code in IP addresses? Is there an alternate name for b.navy.mil that doesn't have an MX record pointing to x.navy.mil? If so, why are you using MX records in the first place? Are both hosts on some other kind of network? Etc. ================================================================================ Archive-Date: Fri, 28 May 1993 12:24:37 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 28 May 1993 14:15:46 ADT From: Ben Armstrong Reply-To: MX-List@WKUVX1.BITNET To: hardis@garnet.nist.gov CC: mx-list@WKUVX1.BITNET, bg@dymaxion.ns.ca Message-ID: <0096D2EB.0BEC9540.6020@dymaxion.ns.ca> Subject: RE: Subscribing one mailing list to another >From: MX%"hardis@garnet.nist.gov" 28-MAY-1993 14:02:34.86 >To: BG >Subj: RE: Subscribing one mailing list to another >> Why can't I subscribe a mailing list to another mailing list with >> MX 3.1 and 3.3? > >> Here's what happens: > >>>Error in delivery to mailing list MUG-L: >>> access denied; send subscription requests to MUG-L-Request@dymaxion.ns.ca > >Huh?? I don't understand the context. > >Are you saying that a mail message was sent from an account with the _same >name_ as a mailing list on the _same host_ with a SUBSCRIBE command, and it >was rejected? No. This message was sent by a member of Medianet-L to Medianet-L@dymaxion.ns.ca which was subsequently distributed by the MLF server to everyone on the list including MUG-L@dymaxion.ns.ca. This rejection message was sent to me when MX MLF failed to send the message to MUG-L@dymaxion.ns.ca (which was originally subscribed to the list via an "ADD" command since that list is semi-private). >Are you saying that the list manager is unable to add a mailing list >address onto his list? In short, I can add the list address "A" to list "B", but whenever messages are relayed from list "B" to "A" by the server, they bounce. >Are you saying that the list privileges should allow the list address to be >added, yet it can't be? As I stated above, adding the list address is not the problem; getting messages to go to the address is. 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: Fri, 28 May 1993 12:32:55 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: SMTP server crashing out ... Message-ID: <1993May28.175453.7947@rz-berlin.mpg.de> Date: 28 May 93 17:54:53 +0100 To: MX-List@WKUVX1.BITNET Hunter Goatley writes: > "Andy, Systems Manager" writes: > >>More usefully, whats the best way to gain clues? I can tunr on SMTP >>tracing but >>I'm note sure I can risk filling my disk up with all the logs! >> > You could SET FILE/VERSION=10 or so on the MX_SMTP_DIR:MX_SMTP_LOG.LOG > file. Since the server's crashing, the last log file should be the > right one. What shows up in the MX_SMTP_DIR:MX_SMTP_node.LOG file as > the exit status? A little word of warning here. There is a bug (in version 3.1, dunno about current version), which causes SMTP_SERVER to crash, when a log file can't be opened, because its version limit implies to purge an older version, which is still open by another thread. A single thread may last forever, if it gets a long mail from a slow remote host. So when you turn MX_SMTP_SERVER_DEBUG on and run the SMTP_SERVER with more than one thread (default=4), you allways habe a chance of your SMTP_SERVER dying. Symptoms: SMTP_SERVER dies (accvio - but never show anywhere) SMTP_SERVER_node.LOG just says "SMTP Server exiting" SMTP_SERVER_LOG.LOG is at its version limit SMTP_SERVER_LOG.LOG;-0 (the oldest) shows an incomplete transaction Also, when you turn MX_*_DEBUG on, mind the maximum file version, which is ;32767. If this has not been fixed in the current version, can the maintainer of MX (Hunter ?) please put it on the wish-list ? mail-copies of followups welcome, because I'm going into holiday :-) Ciao Donald -- Donald Buczek buczek@FHI-Berlin.MPG.DE "It's a Boo..." ================================================================================ Archive-Date: Fri, 28 May 1993 13:15:13 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 28 May 1993 13:12:04 CDT From: Don Walter <"uvax2::walter"@sebac.jsu.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096D2E2.25FD5680.24048@sebac.jsu.edu> Subject: RE: SMTP server crashing out ... ================================================================================ Archive-Date: Fri, 28 May 1993 13:16:55 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX SMTP and UCX domain lookup problems Message-ID: <1993May28.184900.7948@rz-berlin.mpg.de> Date: 28 May 93 18:49:00 +0100 To: MX-List@WKUVX1.BITNET In article <0096D157.EC8CAA80.14505@WKUVX1.BITNET>, Hunter Goatley writes: > Jerry Storrs of NCSU has a problem that has me stumped. He's running > MX V3.3 and UCX V1.3. All MX SMTP domain lookups are failing. Here's > a log that is typical of all of them: > >>21-MAY-1993 15:18:32.88 Processing queue entry number 1000 >>21-MAY-1993 15:18:33.13 Recipient: , > route=CCVAX1.CC.NCSU.EDU >>21-MAY-1993 15:18:33.13 SMTP_SEND: looking up host name CCVAX1.CC.NCSU.EDU >>21-MAY-1993 15:18:33.50 SMTP_SEND: Failed, sts=00000870 >>21-MAY-1993 15:18:33.50 SMTP send failed, sts=0C278024, sts2=00000870 >>21-MAY-1993 15:18:33.50 Recipient status=0C278024 for > > > He does have a name server defined, and TELNET, etc., works just fine. > But MX always returns this. Do any of you have any suggested courses of > action? His UCX host info looked fine to me, as did the name > server(s). The name servers are defined using the IP addresses, and > the UCX$BIND_SERVER00x logicals look OK. > > Thanks for any suggestions. Im also using UCX 1.3 I got this twice: Nameserver works fine, no configuration changes, but MX suddenly fails to resolve any name. restarting the MX SMTP agent fixes it. The first time it hit me, I restarted MX SMTP and just wondered. The next time, I was absent and someone else rebootet the system. Another way to fix it ;-) But I was told, that some time before the second event, our primary nameserver failed. They told me, nslookup on a sun produced a core dump. So the nameserver was not off totaly, but produced answers, which this high quality nslookup couldn't parse. So they rebooted the host with the nameserver on it (lots of reboots, if i am away...) Now I could imagine the following events: - nameserver goes crazy - MX wants to send a mail and asks the nameserver for MX-records - nameserver answers junk (eg. bad name compression) - MX caches junk as MX-forwarder (with high TTL) Even when the nameserver gets back to normal, MX will still find junk MX-records in its cache and ask the UCX resolver for the address of an invalid forwarder. UCX will of course answer with %X870. If I look at SMTP_OUT.B32 I see > ... > TRACE (' SMTP_SEND: looking up host name !AS', HOSTNM); > ... > STATUS = DNS_MXLOOK (HOSTNM, %REF (MXR_MAX), MXRCNT, MXR); > ... > STATUS = NET_GET_ADDRESS (TCPCTX, SDSC, 32, ADRLST, ADRCNT); > ... > IF .STATUS THEN > ... > END; > IF .STATUS THEN EXITLOOP .STATUS; > TRACE (' SMTP_SEND: Failed, sts=!XL', .STATUS); > ... So an invalid cached MX-record would never show up in the log. Perhaps another TRACE before or after NET_GET_ADDRESS could give us a clue. Just an idea. I'd love to investigate this, but my holliday is only some minutes away. I would very much appreciate followup or solutions to this problem forwarded to me by mail, because I won't be able to read news the next week. -- Donald Buczek buczek@FHI-Berlin.MPG.DE "It's a Boo..." ================================================================================ Archive-Date: Fri, 28 May 1993 14:26:06 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: Subscribing one mailing list to another Date: 28 May 1993 18:36:58 GMT Message-ID: <1u5m4aINNru@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096D2EB.0BEC9540.6020@dymaxion.ns.ca>, Ben Armstrong writes: =>Huh?? I don't understand the context. => =>Are you saying that a mail message was sent from an account with the _same =>name_ as a mailing list on the _same host_ with a SUBSCRIBE command, and it =>was rejected? = =No. This message was sent by a member of Medianet-L to =Medianet-L@dymaxion.ns.ca which was subsequently distributed by the =MLF server to everyone on the list including MUG-L@dymaxion.ns.ca. =This rejection message was sent to me when MX MLF failed to send the =message to MUG-L@dymaxion.ns.ca (which was originally subscribed to =the list via an "ADD" command since that list is semi-private). = =>Are you saying that the list manager is unable to add a mailing list =>address onto his list? = =In short, I can add the list address "A" to list "B", but whenever =messages are relayed from list "B" to "A" by the server, they bounce. = =>Are you saying that the list privileges should allow the list address to be =>added, yet it can't be? = =As I stated above, adding the list address is not the problem; getting =messages to go to the address is. To clarify things: It appears that the list MUG-L is restricted. Only members of the list can mail to it. Ben subscribed Medianet-L to MUG-L. Someone subscribed to Medianet-L sent mail to that list. Medianet-L dutifully forwarded it to MUG-L. MUG-L saw a message from the subscriber to Medianet-L (not from Medianet-L itself) and bounced it. 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. -------------------------------------------------------------------------------- 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, 28 May 1993 14:29:58 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: using MX with mx Message-ID: <1993May28.145609.599@condor.navsses.navy.mil> Date: 28 May 93 14:56:09 -0600 To: MX-List@WKUVX1.BITNET In article <0096D2E1.BA874460.14759@garnet.nist.gov>, "Jonathan E. Hardis" writes: >> I have a need to have MX V3.3 act as a message exchanger (via the DNS MX >> resource record) for a few hosts in my local domain. Is this possible? >> If so how do I set this up? I just tried this and I came up with a mail >> loop on my VAXen. > > Please specify the problem better. > > Let's say you want mail destined for a.navy.mil, b.navy.mil, and c.navy.mil > to all be sent to x.navy.mil, and you set up MX records that say so. > > Now, mail comes in for b.navy.mil to x.navy.mil. How is x.navy.mil > actually supposed to get the mail to b.navy.mil? Are both hosts on an IP > network? If so, how is x.navy.mil supposed to bypass the name server > (which would only tell it to send the mail to itself)? Do you intend to > hard-code in IP addresses? Is there an alternate name for b.navy.mil that > doesn't have an MX record pointing to x.navy.mil? If so, why are you using > MX records in the first place? Are both hosts on some other kind of > network? Etc. What I wanted to do was to use the VAXen as a forwarder for a machine that might not always be there. What I have is something like this: ---------- | | | | VAX |-----------------| | (EAGLE)| | ------------- ----------- ---------- | | | | DaVinci | |------------| Mailgate |----| | | | | | MHS | ---------- | ------------- ----------- | | | | VAX |-----------------| |(CONDOR)| | ---------- ---------- |Internet| ---------- MAILGATE is a PC that is running an SMTP<-->MHS gateway. This gateway is SINGLE THREADED. As the amount of traffic going through MAILGATE is growing we are starting to see messages returned beacuse the connection could not be made. What I want to do is to have CONDOR or EAGLE receive all incoming mail for MAILGATE and forward it to MAILGATE when it is available. I have been able to get mail for MAILGATE to go to the VAXen but I have not been able to figure out how to get the VAXen to then forward the mail to MAILGATE. My question is how do I set this up using MX. -- Mike Jacobi NAVSSES VAXCluster system manager System@Eagle.Navsses.Navy.Mil System@Condor.Navsses.Navy.Mil Disclaimer - I speak for myself. No-one else. ================================================================================ Archive-Date: Fri, 28 May 1993 16:11:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: 28 May 1993 17:00:49 -0400 (EDT) From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Subscribing one mailing list to another To: MX-List@WKUVX1.BITNET CC: hardis@garnet.nist.gov Message-ID: <0096D302.1A4C4600.14785@garnet.nist.gov> Content-Transfer-Encoding: 7BIT > To clarify things: It appears that the list MUG-L is restricted. Only > members of the list can mail to it. Ben subscribed Medianet-L to MUG-L. > Someone subscribed to Medianet-L sent mail to that list. Medianet-L > dutifully forwarded it to MUG-L. MUG-L saw a message from the subscriber > to Medianet-L (not from Medianet-L itself) and bounced it. 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. If all that's involved is diddling with the From: field, then the SITE agent could do that. However, I suspect there's more to it than that, since it would be a security breach to rely solely on the From: header for user authentication. ================================================================================ Archive-Date: Fri, 28 May 1993 16:28:37 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: using MX with mx Date: 28 May 1993 20:49:35 GMT Message-ID: <1u5tsvINN68n@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993May28.145609.599@condor.navsses.navy.mil>, system@condor.navsses.navy.mil (Mike Jacobi; NAVSSES 012C; VAX SYSTEM MANAGER) writes: =MAILGATE is a PC that is running an SMTP<-->MHS gateway. This gateway is =SINGLE THREADED. As the amount of traffic going through MAILGATE is growing we =are starting to see messages returned beacuse the connection could not be made. =What I want to do is to have CONDOR or EAGLE receive all incoming mail for =MAILGATE and forward it to MAILGATE when it is available. I have been able to =get mail for MAILGATE to go to the VAXen but I have not been able to figure out =how to get the VAXen to then forward the mail to MAILGATE. My question is how =do I set this up using MX. Or, more concisely, how does one force MX to ignore the MX records for a system and use the A record instead. I would've thought that something like: MCP> DEFINE PATH fubar.where SMTP/ROUTE=fubar.where would do this, but it does not. It would (in my opinion) be nice if it did. -------------------------------------------------------------------------------- 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, 28 May 1993 18:49:23 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Any update on MX --> DECUS UUCP bug? Message-ID: <1993May28.160219.1821@mala.bc.ca> Date: 28 May 93 16:02:19 -0700 To: MX-List@WKUVX1.BITNET From the MX V3.3 release notes: > 5.3 DECUS UUCP UUCP_MAILSHR Bug > > 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. Attempts to SHUTDOWN the MX uucp intfc will fail; > you must use STOP/ID to kill the process, CANCEL the > message, then restart the UUCP agent. > > According to the DECUS UUCP developers, this will be > fixed in the next release of DECUS UUCP. We've been bitten by this bug a couple of times lately ( at least I assume it's this bug ). The "MX uucp intfc process" is compute bound and it's creating a MAIL.TXT file of ever increasing size ( the last one got to 250,000 blocks before I found and stopped it ). This temp file is not created in a directory. 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 ) -- ============================================================================= Malcolm Dunnett Malaspina College Email: dunnett@mala.bc.ca Computer Services Nanaimo, B.C. CANADA V9R 5S5 Tel: (604)755-8738 ================================================================================ Archive-Date: Sat, 29 May 1993 19:00:09 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 28 May 93 15:03:37 +0100 From: Reply-To: MX-List@WKUVX1.BITNET Message-ID: <9305281403.AA00441@bogart.mpib-tuebingen.mpg.de> To: mx-list@WKUVX1.BITNET, system@zappa Subject: Re: mx033 on cluster. CC: boerner@bogart.mpib-tuebingen.mpg.de subscribe mx-list "rudi boerner" ================================================================================ Archive-Date: Sun, 30 May 1993 20:02:27 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: SMTP server crashing out ... Message-ID: <1993May28.165409.768@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 28 May 93 16:54:09 +1000 To: MX-List@WKUVX1.BITNET In article <0096D162.59175560.14561@WKUVX1.BITNET> Hunter Goatley, goathunter@WKUVX1.BITNET writes: > I don't know of anyone else using POP3 with MX, so I don't have any > idea. Anyone else? I'm using IUPOP3 with MX on a 3100 under 5.5-2 with no problems, however the load is low. Only 1 pop node. 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: Mon, 31 May 1993 00:47:09 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: MX rewrite rules? Message-ID: <1993May31.135131.770@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 31 May 93 13:51:31 +1000 To: MX-List@WKUVX1.BITNET In article <1993May27.225044.155@rygel.anorad.com> Mikel Beck, mikel@rygel.anorad.com writes: > Can somebody please post a sample rewrite rule to correctly > transform an address from "NODE::USER" to "user@node.domain.org"? There isn't a rewrite rule to do it. > up with a return address like "USER%NODE.dnet@domain.org". I've > tried getting rid of NAME_CONVERSION, but this results in an > address of "USER::NODE@node.domain.org" ( where the second 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. The REWRITE section of MX only rewrites the "envelope" TO address on messages. 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: Mon, 31 May 1993 00:47:12 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: More on Mailing List woes. Message-ID: <1993May31.134636.769@hhcs.gov.au> From: Carl Makin Reply-To: MX-List@WKUVX1.BITNET Date: 31 May 93 13:46:36 +1000 To: MX-List@WKUVX1.BITNET In article <0096D256.64CBD9E0.15194@WKUVX1.BITNET> Hunter Goatley, goathunter@WKUVX1.BITNET writes: > Looking back at your original message, I see that the problem is > caused by an incorrect REWRITE_RULE. You have (had?): >> Rewrite "<{to}@cnb09w.hhcs.gov.au>" => "<""{to}""@cnb09w.hhcs.gov.au>" Ahhh, the MLF and ALIAS lookup includes the quotes while the LOCAL agent can handle them. Ok. > In fact, you don't need REWRITE_RULES like that one above anyway. Just > make sure you have a PATH defined for the local node(s). Well, I did need them because the local node was cnb09w.hhcs.gov.au and it was getting caught in the later rewrite rule for "<{to}@{node}.hhcs.gov.au>" which caught addresses in the format makinc@cbr.hhcs.gov.au and reformatted them to go to the cluster and other nodes. I've changed all that now and the mail node is just hhcs.gov.au so it doesn't get caught. Thanks for the answer. I have some rewrite rule changes to make. :-) 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: Mon, 31 May 1993 11:08:41 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX rewrite rules? Message-ID: <1993May31.100747.158@anorad.com> Date: 31 May 93 10:07:47 EST To: MX-List@WKUVX1.BITNET >> >>> Can somebody please post a sample rewrite rule to correctly >>> transform an address from "NODE::USER" to "user@node.domain.org"? >> >> There isn't a rewrite rule to do it. That's probably why I can't get it to work properly. ;-) >>> up with a return address like "USER%NODE.dnet@domain.org". I've >>> tried getting rid of NAME_CONVERSION, but this results in an >>> address of "USER::NODE@node.domain.org" ( where the second >> >> 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. >> >> The REWRITE section of MX only rewrites the "envelope" TO address >> on messages. 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... +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mikel Beck - Senior Business Programmer, Anorad Corporation | | E-Mail: mikel@rygel.anorad.com | | "Excellence In Motion" | +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ ================================================================================ Archive-Date: Mon, 31 May 1993 11:11:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 31 May 1993 11:11:06 CDT From: Hunter Goatley Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096D52C.BF244160.16132@WKUVX1.BITNET> Subject: MX BOF at DECUS FYI, I'm planning to try to schedule an MX BOF meeting at DECUS in Atlanta next week. I'm hoping to get it scheduled for sometime Wednesday or Thursday. If so, both Matt Madison and I will be there. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Mon, 31 May 1993 13:38:38 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: <1993May31.085205.1729@dymaxion.ns.ca> Date: 31 May 93 08:52:05 AST To: MX-List@WKUVX1.BITNET In article <1u5m4aINNru@gap.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: > In article <0096D2EB.0BEC9540.6020@dymaxion.ns.ca>, Ben Armstrong writes: > =>Huh?? I don't understand the context. > => > =>Are you saying that a mail message was sent from an account with the _same > =>name_ as a mailing list on the _same host_ with a SUBSCRIBE command, and it > =>was rejected? > = > =No. This message was sent by a member of Medianet-L to > =Medianet-L@dymaxion.ns.ca which was subsequently distributed by the > =MLF server to everyone on the list including MUG-L@dymaxion.ns.ca. > =This rejection message was sent to me when MX MLF failed to send the > =message to MUG-L@dymaxion.ns.ca (which was originally subscribed to > =the list via an "ADD" command since that list is semi-private). > = > =>Are you saying that the list manager is unable to add a mailing list > =>address onto his list? > = > =In short, I can add the list address "A" to list "B", but whenever > =messages are relayed from list "B" to "A" by the server, they bounce. > = > =>Are you saying that the list privileges should allow the list address to be > =>added, yet it can't be? > = > =As I stated above, adding the list address is not the problem; getting > =messages to go to the address is. > > To clarify things: It appears that the list MUG-L is restricted. > Only members of the list can mail to it. True. I failed to mention that fact. > Ben subscribed Medianet-L to MUG-L. Not exactly. MUG-L is subscribed to Medianet-L. From the following explanation, it looks like that is what you meant, anyway. > Someone subscribed to Medianet-L sent mail to that list. Medianet-L dutifully > forwarded it to MUG-L. MUG-L saw a message from the subscriber to Medianet-L > (not from Medianet-L itself) and bounced it. That is more or less my problem. > 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. Actually, what I *REALLY* want to know is whether or not I can maintain a restricted list as a subset of an unrestricted list without manually duplicating all additions to and removals from the restricted list's membership. I could care less how we achieve that. > Offhand, the answer appears to be, No. Incidentally, MX's new multiple-from capability wouldn't help, would it? 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