Archive-Date: Tue, 11 Jul 2000 14:44:17 -0700 Return-Path: From: bleau@umtof.umd.edu (Lawrence Bleau) Subject: MX 4.2 won't rebuild, what's missing? Date: 11 Jul 2000 21:39:33 GMT Message-ID: <8kg46l$mnq$1@hecate.umd.edu> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU I've copied the NORELAY patch for MX 4.2 to a system that has the BLISS compiler. I'm still having problems compiling it, though. When I do a MMS in the MX_SRC:[MX.SMTP] directory, to which I've copied the LOAD_RELAY.C and revised SMTP_SERVER.B32 files, I get: BLISS /LIBRARY=[MX.COMMON]AGENT.L32 /NOLIST [MX.COMMON]AGENT.R32 LIBRARY 'FLQ'; ........^ %BLS32-E-M_OPENIN, error opening FLQ as input -BLS32-E-FNF, file not found at line number 38 in file MX_SRC:[MX.COMMON]AGENT.R32;1 I'm running V1.8-028 of the BLISS compiler (I did a ^T and it displayed BLISS32EN, so I did a ANAL/IMAGE on it to get the version). I've never programmed or used BLISS. I'm on OpenVMS AXP 7.1-2. Thinking I just needed another library, I went to the [MX.FLQ] directory and tried doing a MMS there, but I got this error: BLISS /LIBRARY=FLQ_PRIVATE_DEFS.L32 /NOLIST FLQ_PRIVATE_DEFS.R32 LIBRARY 'SYS$LIBRARY:STARLET'; ............^ %BLS32-E-M_OPENIN, error opening SYS$LIBRARY:STARLET as input -BLS32-E-FNF, file not found at line number 23 in file MX_SRC:[MX.FLQ]FLQ_PRIVATE_DEFS.R32;1 Sure enough, there isn't a STARLET.B32 (or whatever it's supposed to be called) in SYS$LIBRARY:. I do have STARLET.INCLUDE;1 STARLET.MLB;1 STARLET.OLB;4 STARLET.PREFIX;1 STARLET.R64;1 STARLET.REQ;1 Any suggestions? Was this file supposed to have been installed when I installed the BLISS compiler ages ago (don't even recall when)? I can get access to the Freeware CD (don't remember which version); is it on there? If it's available online, that'd be even faster, as someone else has the CD. Or is this a wild goose chase? Is there a better way of getting the FLQ library? Are there any other libraries I'll need? Next, recalling that I have to remake the LOCAL component, I went to MX_SRC:[MX.LOCAL] and did an MMS. I got the same error as with FLQ: BLISS /LIBRARY=MX.L32 /NOLIST MX.R32 LIBRARY 'SYS$LIBRARY:STARLET'; ............^ %BLS32-E-M_OPENIN, error opening SYS$LIBRARY:STARLET as input -BLS32-E-FNF, file not found at line number 9 in file MX_SRC:[MX.COMMON]MX.R32;1 So, does anyone who has remade MX 4.2 have any suggestion? NOTE: This isn't a norelay patch question per se, it's a question of how to rebuild MX 4.2 from sources, something I should already be able to do. Lawrence Bleau University of Maryland Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu ================================================================================ Archive-Date: Tue, 11 Jul 2000 17:01:58 -0700 Date: Tue, 11 Jul 2000 19:02:10 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <000711190210.202000c3@goatley.com> Subject: RE: MX 4.2 won't rebuild, what's missing? bleau@umtof.umd.edu (Lawrence Bleau) writes: > >I've copied the NORELAY patch for MX 4.2 to a system that has the BLISS >compiler. I'm still having problems compiling it, though. > >When I do a MMS in the MX_SRC:[MX.SMTP] directory, to which I've copied the >LOAD_RELAY.C and revised SMTP_SERVER.B32 files, I get: > There are more pieces you have to build first. There should be a README in the top-level source directory that tells you how to build it from scratch. In fact, there should be an .MMS file that does it for you. >Thinking I just needed another library, I went to the [MX.FLQ] directory and >tried doing a MMS there, but I got this error: > >BLISS /LIBRARY=FLQ_PRIVATE_DEFS.L32 /NOLIST FLQ_PRIVATE_DEFS.R32 > > LIBRARY 'SYS$LIBRARY:STARLET'; >............^ >%BLS32-E-M_OPENIN, error opening SYS$LIBRARY:STARLET as input >-BLS32-E-FNF, file not found >at line number 23 in file MX_SRC:[MX.FLQ]FLQ_PRIVATE_DEFS.R32;1 > >Sure enough, there isn't a STARLET.B32 (or whatever it's supposed to be called) >in SYS$LIBRARY:. I do have > >STARLET.INCLUDE;1 STARLET.MLB;1 STARLET.OLB;4 STARLET.PREFIX;1 >STARLET.R64;1 STARLET.REQ;1 > You need the STARLET.L32 (or .L32E) library. The VAX BLISS installation creates it automatically, but the Alpha installation does not. You can create the necessary files using these commands: $ set def sys$common:[syslib] $ bliss/library starlet.req $ bliss/librar=lib.l32 starlet.req+lib.req >Or is this a wild goose chase? Is there a better way of getting the FLQ >library? Are there any other libraries I'll need? > Building the [.FLQ] and [.COMMON] stuff is required before you try to build the SMTP stuff. >NOTE: This isn't a norelay patch question per se, it's a question of how to >rebuild MX 4.2 from sources, something I should already be able to do. > Correct. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Wed, 12 Jul 2000 10:50:47 -0700 Return-Path: From: bleau@umtof.umd.edu (Lawrence Bleau) Subject: RE: MX 4.2 won't rebuild, what's missing? Date: 12 Jul 2000 17:41:59 GMT Message-ID: <8kial7$spc$1@hecate.umd.edu> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU In article <000711190210.202000c3@goatley.com>, Hunter Goatley writes: >> >>Sure enough, there isn't a STARLET.B32 (or whatever it's supposed to be called) >>in SYS$LIBRARY:. I do have >> >>STARLET.INCLUDE;1 STARLET.MLB;1 STARLET.OLB;4 STARLET.PREFIX;1 >>STARLET.R64;1 STARLET.REQ;1 >> >You need the STARLET.L32 (or .L32E) library. The VAX BLISS >installation creates it automatically, but the Alpha installation does >not. You can create the necessary files using these commands: > > $ set def sys$common:[syslib] > $ bliss/library starlet.req > $ bliss/librar=lib.l32 starlet.req+lib.req Great! I compiled STARLET.REQ and got the following two informationals; are they anything to worry about? Is there a switch I need? literal PR$M_PS_MBZ_62 = %X'4000000000000000'; ...........................^ %BLS32-I-TEXT, Numeric literal overflow at line number 12248 in file SYS$COMMON:[SYSLIB]STARLET.REQ;1 literal PR$M_PS_MBZ_63 = %X'8000000000000000'; ...........................^ %BLS32-I-TEXT, Numeric literal overflow at line number 12249 in file SYS$COMMON:[SYSLIB]STARLET.REQ;1 When I compiled starlet.req+lib.req, though, I got many, many, many more informationals, all of them appear to be the same as above, though. I guess the same answer applies to both questions. >Building the [.FLQ] and [.COMMON] stuff is required before you try to >build the SMTP stuff. Oh. So much for the norealy instructions saying "just rebuild SMTP", or words to that effect. I suppose the author assumed I'd have a completely built MX package lying around :-) One more readme for me to read. Thanks! Lawrence Bleau University of Maryland Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu ================================================================================ Archive-Date: Wed, 12 Jul 2000 10:57:27 -0700 Date: Wed, 12 Jul 2000 12:57:36 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <000712125736.202000c3@goatley.com> Subject: RE: MX 4.2 won't rebuild, what's missing? bleau@umtof.umd.edu (Lawrence Bleau) writes: > >> $ set def sys$common:[syslib] >> $ bliss/library starlet.req >> $ bliss/librar=lib.l32 starlet.req+lib.req > >Great! I compiled STARLET.REQ and got the following two informationals; are >they anything to worry about? Is there a switch I need? > >literal PR$M_PS_MBZ_62 = %X'4000000000000000'; >...........................^ >%BLS32-I-TEXT, Numeric literal overflow >at line number 12248 in file SYS$COMMON:[SYSLIB]STARLET.REQ;1 > [...] >When I compiled starlet.req+lib.req, though, I got many, many, many more >informationals, all of them appear to be the same as above, though. I guess >the same answer applies to both questions. > Just ignore them. As the error says, Digital added some 64-bit literal to the 32-bit BLISS .REQ files. In any case, they're not things you'll be using, so the messages can be safely ignored. >>Building the [.FLQ] and [.COMMON] stuff is required before you try to >>build the SMTP stuff. > >Oh. So much for the norealy instructions saying "just rebuild SMTP", or words >to that effect. I suppose the author assumed I'd have a completely built MX >package lying around :-) Doesn't everybody? 8-) > One more readme for me to read. Thanks! > No problem! Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Wed, 12 Jul 2000 11:35:16 -0700 Return-Path: From: bleau@umtof.umd.edu (Lawrence Bleau) Subject: More errors on full build attempt of MX 4.2 Date: 12 Jul 2000 18:29:24 GMT Message-ID: <8kide4$ths$1@hecate.umd.edu> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU A couple other problems in trying to rebuild MX 4.2 on Alpha. I noticed the admonishon in ther readme file to build FLQ before COMMON, so I started that way. Doing a MMS in the [MX.FLQ] directory gave me: BLISS /OBJ=FLQ_OPEN.OBJ/TERM=STAT/NOLIST/NODEBUG/VAR="" FLQ_OPEN.B32 %DCL-W-IVKEYW, unrecognized keyword - check validity and spelling \STAT\ %MMS-F-ABORT, For target FLQ_OPEN.OBJ, CLI returned abort status: %X00038060. -CLI-W-IVKEYW, unrecognized keyword - check validity and spelling I assume this is a minor problem and just removed the /TERM=STAT from the BFLAGS lines, then invoked MMS again. This time, though, I got a slew of errors on the module FLQ_VECTOR.MAR: MACRO /OBJ=FLQ_VECTOR.OBJ/NODEBUG FLQ_VECTOR.MAR ROUTINE FLQ_OPEN ^ %AMAC-W-DIRTRANS, .TRANSFER directive is not supported -MACRO-I-ATEXPLINE, at macro expansion line 3 at line number 29 in file MX_SRC:[MX.FLQ]FLQ_VECTOR.MAR;1 .TRANSFER FLQ_OPEN ROUTINE FLQ_OPEN ^ %AMAC-E-DIRMASK, .MASK directive is not supported -MACRO-I-ATEXPLINE, at macro expansion line 4 at line number 29 in file MX_SRC:[MX.FLQ]FLQ_VECTOR.MAR;1 .MASK FLQ_OPEN ROUTINE FLQ_OPEN ^ %AMAC-E-BLKEXPNABS, block expression not absolute -MACRO-I-ATEXPLINE, at macro expansion line 4 at line number 29 in file MX_SRC:[MX.FLQ]FLQ_VECTOR.MAR;1 [snip] .END ^ %AMAC-E-PREVERROR, previous errors prevent further analysis at line number 42 in file MX_SRC:[MX.FLQ]FLQ_VECTOR.MAR;1 I tried the above using the /MIGRATION qualifier and got the same results. I checked the help file and found this: MACRO /MIGRATION Support_of_VAX_MACRO_Assembler_Directives The compiler supports most of the standard VAX MACRO assembler directives. However, the following directives that are supported by the VAX MACRO assembler do not make sense for compiled code. Consequently, the compiler flags them and continues execution. You can disable the flagging of these directives by specifying /NOFLAG=DIRECTIVES. [snip] o .TRANSFER o .MASK [snip] So it seems the directives really aren't needed for Alphas. Does this mean I can change the FLQ's DESCRIP.MMS file to use /MIGRATION/NOFLAG=DIRECTIVES and just rerun MMS? Or are the above messages really errors? Lawrence Bleau University of Maryland Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu ================================================================================ Archive-Date: Wed, 12 Jul 2000 11:38:42 -0700 Date: Wed, 12 Jul 2000 13:38:53 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <000712133854.20200505@goatley.com> Subject: RE: More errors on full build attempt of MX 4.2 bleau@umtof.umd.edu (Lawrence Bleau) writes: > >So it seems the directives really aren't needed for Alphas. Does this mean I >can change the FLQ's DESCRIP.MMS file to use /MIGRATION/NOFLAG=DIRECTIVES >and just rerun MMS? Or are the above messages really errors? > Do: $ MMS/MACRO=(__ALPHA__=1) I think that'll take care of it all. Or use MMK to build it. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Wed, 12 Jul 2000 11:42:49 -0700 Date: Wed, 12 Jul 2000 13:42:48 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <000712134248.20200505@goatley.com> Subject: RE: More errors on full build attempt of MX 4.2 Hunter Goatley writes: > >bleau@umtof.umd.edu (Lawrence Bleau) writes: >> >>So it seems the directives really aren't needed for Alphas. Does this mean I >>can change the FLQ's DESCRIP.MMS file to use /MIGRATION/NOFLAG=DIRECTIVES >>and just rerun MMS? Or are the above messages really errors? >> >Do: > > $ MMS/MACRO=(__ALPHA__=1) > >I think that'll take care of it all. > >Or use MMK to build it. > I could have been a bit more verbose.... The .MMS files are set up to compile for both VAX and Alpha. When you use .MMS, the symbol __ALPHA__ is not automatically defined for you, so MMS was executing the VAX build instructions, which is why you saw all the errors. Either use MMK (which defines it automatically), or use the MMS command above. Actually, while I think it will build with MMS, you should probably use MMK anyway. ftp://ftp.madgoat.com/madgoat/mmk.zip Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Wed, 12 Jul 2000 11:58:47 -0700 Return-Path: From: bleau@umtof.umd.edu (Lawrence Bleau) Subject: Re: More errors on full build attempt of MX 4.2 Date: 12 Jul 2000 18:47:00 GMT Message-ID: <8kief4$ths$2@hecate.umd.edu> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU In article <8kide4$ths$1@hecate.umd.edu>, bleau@umtof.umd.edu (Lawrence Bleau) writes: >A couple other problems in trying to rebuild MX 4.2 on Alpha. I noticed the >admonishon in ther readme file to build FLQ before COMMON, so I started that >way. Doing a MMS in the [MX.FLQ] directory gave me: > >BLISS /OBJ=FLQ_OPEN.OBJ/TERM=STAT/NOLIST/NODEBUG/VAR="" FLQ_OPEN.B32 >%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling > \STAT\ >%MMS-F-ABORT, For target FLQ_OPEN.OBJ, CLI returned abort status: %X00038060. >-CLI-W-IVKEYW, unrecognized keyword - check validity and spelling I think I found the reason for this. There's a macro __ALPHA__ that is tested in the DESCRIP.MMS file for FLQ (and probably elsewhere as well). The readme file doesn't say anything about setting/defining this macro. When I defined it, though, using /MACRO=__ALPHA__=1, it didn't give me any errors. As a matter of fact, it didn't compile FLQ_VECTOR.MAR at all! I used the following command MMS/MACRO=__ALPHA__=1/NOACTION/OUT=X./FROM/DESCRIP=DESCRIP.MMS;1 to ensure the original makefile was used, to force all compilations to be done again (in case some were compiled incorrectly), and to get a list of the commands that would be done. The MACRO command doesn't even appear now! The problem I now have, though, is that the module FLQ_VECTOR.OBJ is listed in the options file MX_FLQ_SHR.OPT which is specified on the LINK command. Since I cleaned up the directory (ie, deleted old .OBJ files), and MACRO is no longer invoked, LINK now fails due to a missing file. I'll try compiling FLQ_VECTOR.MAR with the qualifiers I mentioned in my last post. Meanwhile, what *is* the correct answer? Lawrence Bleau University of Maryland Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu ================================================================================ Archive-Date: Wed, 12 Jul 2000 12:04:24 -0700 Date: Wed, 12 Jul 2000 14:04:36 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: BLEAU@UMTOF.UMD.EDU Message-ID: <000712140436.20200505@goatley.com> Subject: Re: More errors on full build attempt of MX 4.2 bleau@umtof.umd.edu (Lawrence Bleau) writes: > >I think I found the reason for this. There's a macro __ALPHA__ that is tested >in the DESCRIP.MMS file for FLQ (and probably elsewhere as well). The readme Right. See the reply I posted to MX-List..... >file doesn't say anything about setting/defining this macro. When I defined >it, though, using /MACRO=__ALPHA__=1, it didn't give me any errors. As a >matter of fact, it didn't compile FLQ_VECTOR.MAR at all! And it shouldn't be, as that's a VAX-only file. >The problem I now have, though, is that the module FLQ_VECTOR.OBJ is listed in >the options file MX_FLQ_SHR.OPT which is specified on the LINK command. Since >I cleaned up the directory (ie, deleted old .OBJ files), and MACRO is no longer >invoked, LINK now fails due to a missing file. > >I'll try compiling FLQ_VECTOR.MAR with the qualifiers I mentioned in my last >post. Meanwhile, what *is* the correct answer? > With __ALPHA__ defined, it should be using MX_FLQ_SHR.ALPHA_OPT on Alpha. MX V4.2 may not build correctly with MMS. It's been eons since I've used MMS for anything. Try MMK and see how it goes. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Wed, 12 Jul 2000 12:29:51 -0700 Return-Path: From: bleau@umtof.umd.edu (Lawrence Bleau) Subject: Re: More errors on full build attempt of MX 4.2 Date: 12 Jul 2000 19:25:18 GMT Message-ID: <8kigmu$svr$1@hecate.umd.edu> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU In article <000712140436.20200505@goatley.com>, Hunter Goatley writes: > >>file doesn't say anything about setting/defining this macro. When I defined >>it, though, using /MACRO=__ALPHA__=1, it didn't give me any errors. As a >>matter of fact, it didn't compile FLQ_VECTOR.MAR at all! > >And it shouldn't be, as that's a VAX-only file. OK, that's good to know. [snip] >>Meanwhile, what *is* the correct answer? >> >With __ALPHA__ defined, it should be using MX_FLQ_SHR.ALPHA_OPT on >Alpha. Ah ha! I just tried the LINK command with the alternate options file,and it worked - sort of. It tried to link against the library MX_FLQ_SHR.ALPHA_OLB, which didn't exist. the name looked familiar, though: the makefile had just built MX_FLQ_SHR.OLB. I renamed it and LINK was very happy. Sp there are three things I should look out for with all the other makes: always specify /MACRO=__ALPHA__=1, using *.ALPHA_OPT in place of *.OPT, and using *.ALPHA_OLB in place of *.OLB. >MX V4.2 may not build correctly with MMS. It's been eons since I've >used MMS for anything. Try MMK and see how it goes. I'll load MMK if absolutely necessary, else I prefer keeping the number of s/w packages to a minimum (and what happens if MMK doesn't install correctly?). You're right, though, this (MX 4.2) hasn't been tested with MMS or the above errors would've been detected. Lawrence Bleau University of Maryland Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu ================================================================================ Archive-Date: Wed, 12 Jul 2000 12:32:45 -0700 Date: Wed, 12 Jul 2000 14:32:51 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <000712143251.20200505@goatley.com> Subject: Re: More errors on full build attempt of MX 4.2 bleau@umtof.umd.edu (Lawrence Bleau) writes: > >I'll load MMK if absolutely necessary, else I prefer keeping the number of s/w >packages to a minimum (and what happens if MMK doesn't install correctly?). There's nothing to MMK except a simple LINK.COM. >You're right, though, this (MX 4.2) hasn't been tested with MMS or the above >errors would've been detected. > I stopped using MMS when MMK V1.0 was released. It's much better than MMS, IMO. Matt did a great job with it. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Wed, 12 Jul 2000 13:11:33 -0700 Return-Path: From: bleau@umtof.umd.edu (Lawrence Bleau) Subject: Another missing BLISS lirbary Date: 12 Jul 2000 20:06:46 GMT Message-ID: <8kij4m$tm1$1@hecate.umd.edu> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU I hit another BLISS related error while trying to build MX 4.2 on OpenVMS AXP 7.1-2. $ BLISS /OBJ=XSMTP_OUT.OBJ/NOMACHINE/NOLIST/VAR="" XSMTP_OUT.B32 LIBRARY 'SYS$LIBRARY:PSILIB'; ............^ %BLS32-E-M_OPENIN, error opening SYS$LIBRARY:PSILIB as input -BLS32-E-FNF, file not found at line number 26 in file MX_SRC:[MX.SMTP]XSMTP_OUT.B32;1 I tried the usual trick of going to SYS$COMMON:[SYSLIB] and doing a BLISS/LIBRARY=name name to create a library out of this module, but PSILIB doesn't exist with any extension. There are no *PSI* files in that directory. Any ideas? Lawrence Bleau University of Maryland Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu ================================================================================ Archive-Date: Wed, 12 Jul 2000 13:15:20 -0700 Date: Wed, 12 Jul 2000 15:15:32 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <000712151532.20200505@goatley.com> Subject: RE: Another missing BLISS lirbary bleau@umtof.umd.edu (Lawrence Bleau) writes: > >to create a library out of this module, but PSILIB doesn't exist with any >extension. There are no *PSI* files in that directory. Any ideas? > Don't worry about it, unless you have X.25 support. XSMTP is SMTP over X.25. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Wed, 12 Jul 2000 13:43:31 -0700 Return-Path: From: bleau@umtof.umd.edu (Lawrence Bleau) Subject: Relay control file Date: 12 Jul 2000 20:36:22 GMT Message-ID: <8kiks6$t8p$1@hecate.umd.edu> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU OK, I finally got everything compiled that needs to be compiled. I copied the new .EXEs into the MX_EXE: area. My next step is to create the RELAY.DAT file, which is the subject of this posting. (Btw, I'm running MX 4.2 on OpenVMS 7.1-2.) I'd like to disable relay from every blasted system inthe universe!! Is there a simple way to do this? I looked at the (somehwat meager) instructions and examples. The examples are: enable ludens.elte.hu enable faber.elte.hu disable csirke.inf.elte.hu disable sult.inf.elte.hu disable 157.181.3.0 with mask 255.255.255.0 enable 157.181.0.0 with mask 255.255.0.0 Given the above, would you say that the rule below would accomplish my purpose of disallowing any, all, and every relay attempt? disable 0.0.0.0 with mask 0.0.0.0 Or would this trigger a special case in the code? Thanks. Lawrence Bleau University of Maryland Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu ================================================================================ Archive-Date: Wed, 12 Jul 2000 13:51:04 -0700 Return-Path: From: bleau@umtof.umd.edu (Lawrence Bleau) Subject: RE: Another missing BLISS lirbary Date: 12 Jul 2000 20:40:43 GMT Message-ID: <8kil4b$t8p$2@hecate.umd.edu> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU In article <000712151532.20200505@goatley.com>, Hunter Goatley writes: >bleau@umtof.umd.edu (Lawrence Bleau) writes: >> >>to create a library out of this module, but PSILIB doesn't exist with any >>extension. There are no *PSI* files in that directory. Any ideas? >> >Don't worry about it, unless you have X.25 support. XSMTP is SMTP >over X.25. Great. I'll just comment out the lines that deal with X25 or XSMTP. (Actually, I've already done this; see post I just submitted on configuring RELAY.DAT). Lawrence Bleau University of Maryland Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu ================================================================================ Archive-Date: Wed, 12 Jul 2000 19:42:59 -0700 Date: Wed, 12 Jul 2000 21:41:19 CDT From: Ravi Kochhar Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009ECFD2.60914AA0.7@physiology.wisc.edu> Subject: RE: Relay control file >I'd like to disable relay from every blasted system inthe universe!! Is there >a simple way to do this? I looked at the (somehwat meager) instructions and >examples. The examples are: > > enable ludens.elte.hu > enable faber.elte.hu > disable csirke.inf.elte.hu > disable sult.inf.elte.hu > disable 157.181.3.0 with mask 255.255.255.0 > enable 157.181.0.0 with mask 255.255.0.0 > >Given the above, would you say that the rule below would accomplish my purpose >of disallowing any, all, and every relay attempt? > >disable 0.0.0.0 with mask 0.0.0.0 > >Or would this trigger a special case in the code? Thanks. It _should_ do what you want. Here is the relay.dat file that is working well for us: enable 128.104.0.0 with mask 255.255.0.0 disable 0.0.0.0 with mask 0.0.0.0 Ravi Kochhar Univ. of Wisconsin ================================================================================ Archive-Date: Wed, 19 Jul 2000 11:40:50 -0700 Message-ID: <20000719184038.26874.qmail@wwcst271.netaddress.usa.net> Date: 19 Jul 00 13:40:37 CDT From: Michael Angello Reply-To: MX-List@MadGoat.com To: MX-LIST@MADGOAT.COM Subject: MXSUM usage MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello, I need to get some statistics about MX usage, I have already gotte= n = the MXSUM, but I can't find the way it should be used. Any comments about it will be appreciated. Thanks in advance!. Mike. ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webm= ail.netscape.com. ================================================================================ Archive-Date: Wed, 19 Jul 2000 11:44:32 -0700 Date: Wed, 19 Jul 2000 13:44:54 -0500 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <000719134454.202000c0@goatley.com> Subject: RE: MXSUM usage Michael Angello writes: > >Hello, I need to get some statistics about MX usage, I have already gotten >the MXSUM, but I can't find the way it should be used. > I doubt that MXSUM works correctly with modern versions of MX. It's been a long time since that program was updated. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www.goatley.com/hunter/ ================================================================================ Archive-Date: Tue, 25 Jul 2000 06:50:02 -0700 Date: Tue, 25 Jul 2000 15:49:36 +0200 From: "Remi Jolin - Telintrans" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: remi.jolin@telintrans.fr Message-ID: <009ED9D8.659B4BCE.99@telintrans.fr> Subject: no more dns error with mx5.0a We have just upgraded to MX V5.0a and we don't get anymore DNS errors even if the recipient domain name does not exist in the DNS. (it was working fine with MX 4.2). All the errors are now MX-W-NOCONTACT example : Entry: 32, Origin: [SMTP] Status: IN-PROGRESS, size: 174 bytes Created: 25-JUL-2000 14:51:52.00, expires 24-AUG-2000 15:21:53.69 Last modified 25-JUL-2000 15:21:53.69 SMTP entry #35, status: READY, size: 174 bytes, waiting for retry until 25-JUL-2000 15:51:54.39 Created: 25-JUL-2000 14:51:52.73, expires 24-AUG-2000 15:21:54.39 Last modified 25-JUL-2000 15:21:54.39 Recipient #1: , Route=ATOS_GROUP.COM Error count=2 Last error: %MX-W-NOCONTACT, could not establish contact with any mail servers for this destination Our domain is telintrans.fr. We have an MX record for *.telintrans.fr and, under tcpip (ucx) v5.0, when we do a show mx whatever.whatever we get our own MX record. Of course if you do a show mx whatever.whatever. you get a %TCPIP-W-NORECORD, information not found Would MX query the DNS without the final dot of the full domain name ?? ================================================================================ Archive-Date: Tue, 25 Jul 2000 07:19:30 -0700 Date: Tue, 25 Jul 2000 16:19:15 +0200 From: "Remi Jolin - Telintrans" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: remi.jolin@telintrans.fr Message-ID: <009ED9DC.8A2769D7.14@telintrans.fr> Subject: no more dns error with mx5.1-a Ooup... Should read MX 5.1-A not 5.0-a... I've also heard from DEC that TCPIP V5 had a problem with MX requests... It add the local domain name to the request if it does not get an answer or if the requested domain has no final dot... But it does not help ! -------------------------------------------------------------- We have just upgraded to MX V5.0a and we don't get anymore DNS errors even if the recipient domain name does not exist in the DNS. (it was working fine with MX 4.2). All the errors are now MX-W-NOCONTACT example : Entry: 32, Origin: [SMTP] Status: IN-PROGRESS, size: 174 bytes Created: 25-JUL-2000 14:51:52.00, expires 24-AUG-2000 15:21:53.69 Last modified 25-JUL-2000 15:21:53.69 SMTP entry #35, status: READY, size: 174 bytes, waiting for retry until 25-JUL-2000 15:51:54.39 Created: 25-JUL-2000 14:51:52.73, expires 24-AUG-2000 15:21:54.39 Last modified 25-JUL-2000 15:21:54.39 Recipient #1: , Route=ATOS_GROUP.COM Error count=2 Last error: %MX-W-NOCONTACT, could not establish contact with any mail servers for this destination Our domain is telintrans.fr. We have an MX record for *.telintrans.fr and, under tcpip (ucx) v5.0, when we do a show mx whatever.whatever we get our own MX record. Of course if you do a show mx whatever.whatever. you get a %TCPIP-W-NORECORD, information not found Would MX query the DNS without the final dot of the full domain name ?? ================================================================================ Archive-Date: Tue, 25 Jul 2000 07:29:02 -0700 Sender: madison@MadGoat.Com Date: Tue, 25 Jul 2000 07:28:55 -0700 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: rejmi.jolin@telintrans.fr Message-ID: <009ED992.744061D4.7@MadGoat.Com> Subject: RE: no more dns error with mx5.1-a >Should read MX 5.1-A not 5.0-a... Right. >I've also heard from DEC that TCPIP V5 had a problem with MX requests... It add >the local domain name to the request if it does not get an answer or if the >requested domain has no final dot... But it does not help ! None of the DNS requests that MX generates add a final dot. However, it does not append your local domain name to its requests if the name being looked up contains a dot. This behavior is consistent with the DNS protocol specs; old versions of MX/NETLIB may not have been fully compliant. If you have a wildcard MX RR in your DNS zone (and it looks like you do), and your name server is automatically tacking on the domain name for you, there isn't much that can be done -- the pending entries will eventually be returned to sender, just not with exactly the same error as you saw before. -Matt > >-------------------------------------------------------------- > >We have just upgraded to MX V5.0a and we don't get anymore DNS errors even if >the recipient domain name does not exist in the DNS. (it was working fine with >MX 4.2). > >All the errors are now MX-W-NOCONTACT >example : >Entry: 32, Origin: [SMTP] > Status: IN-PROGRESS, size: 174 bytes > Created: 25-JUL-2000 14:51:52.00, expires 24-AUG-2000 15:21:53.69 > Last modified 25-JUL-2000 15:21:53.69 > SMTP entry #35, status: READY, size: 174 bytes, waiting for retry until >25-JUL-2000 15:51:54.39 > Created: 25-JUL-2000 14:51:52.73, expires 24-AUG-2000 15:21:54.39 > Last modified 25-JUL-2000 15:21:54.39 > Recipient #1: , Route=ATOS_GROUP.COM > Error count=2 > Last error: %MX-W-NOCONTACT, could not establish contact with any mail >servers for this destination > > >Our domain is telintrans.fr. We have an MX record for *.telintrans.fr and, >under tcpip (ucx) v5.0, when we do a >show mx whatever.whatever >we get our own MX record. > >Of course if you do a >show mx whatever.whatever. >you get a %TCPIP-W-NORECORD, information not found > >Would MX query the DNS without the final dot of the full domain name ?? -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Tue, 25 Jul 2000 07:41:07 -0700 Message-ID: <06e701bff646$516ffaa0$2d9065d8@WILKINSONNT> From: "James Wilkinson" Reply-To: MX-List@MadGoat.com To: References: <009ED992.744061D4.7@MadGoat.Com> Subject: Re: no more dns error with mx5.1-a Date: Tue, 25 Jul 2000 07:40:45 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Has anyone rebuilt MX v4.2 in the following configuration: OpenVMS Alpha V7.2-1 Digital TCP/IP V5.0A NETLIB 2.2G Bliss 1.8 I've had problems with the above build, however not with the following: OpenVMS Alpha V7.1-2 Digital TCP/IP V4.2 NETLIB 2.2G Bliss 1.8 James ----- Original Message ----- From: "Matt Madison" To: Cc: Sent: Tuesday, July 25, 2000 7:28 AM Subject: RE: no more dns error with mx5.1-a > >Should read MX 5.1-A not 5.0-a... > > Right. > > >I've also heard from DEC that TCPIP V5 had a problem with MX requests... It add > >the local domain name to the request if it does not get an answer or if the > >requested domain has no final dot... But it does not help ! > > None of the DNS requests that MX generates add a final dot. However, it does > not append your local domain name to its requests if the name being looked up > contains a dot. This behavior is consistent with the DNS protocol specs; > old versions of MX/NETLIB may not have been fully compliant. > > If you have a wildcard MX RR in your DNS zone (and it looks like you do), > and your name server is automatically tacking on the domain name for you, > there isn't much that can be done -- the pending entries will eventually > be returned to sender, just not with exactly the same error as you saw > before. > > -Matt > > > > >-------------------------------------------------------------- > > > >We have just upgraded to MX V5.0a and we don't get anymore DNS errors even if > >the recipient domain name does not exist in the DNS. (it was working fine with > >MX 4.2). > > > >All the errors are now MX-W-NOCONTACT > >example : > >Entry: 32, Origin: [SMTP] > > Status: IN-PROGRESS, size: 174 bytes > > Created: 25-JUL-2000 14:51:52.00, expires 24-AUG-2000 15:21:53.69 > > Last modified 25-JUL-2000 15:21:53.69 > > SMTP entry #35, status: READY, size: 174 bytes, waiting for retry until > >25-JUL-2000 15:51:54.39 > > Created: 25-JUL-2000 14:51:52.73, expires 24-AUG-2000 15:21:54.39 > > Last modified 25-JUL-2000 15:21:54.39 > > Recipient #1: , Route=ATOS_GROUP.COM > > Error count=2 > > Last error: %MX-W-NOCONTACT, could not establish contact with any mail > >servers for this destination > > > > > >Our domain is telintrans.fr. We have an MX record for *.telintrans.fr and, > >under tcpip (ucx) v5.0, when we do a > >show mx whatever.whatever > >we get our own MX record. > > > >Of course if you do a > >show mx whatever.whatever. > >you get a %TCPIP-W-NORECORD, information not found > > > >Would MX query the DNS without the final dot of the full domain name ?? > > -- > Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA > madison@madgoat.com http://www.madgoat.com > ================================================================================ Archive-Date: Fri, 28 Jul 2000 09:17:35 -0700 Date: Fri, 28 Jul 2000 18:17:20 +0200 From: Matthias Muth Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: muth@bessy.de Message-ID: <009EDC48.888C0DA3.15@bessy.de> Subject: IMAP4 Server for OpenVMS? Hi all, does anybody know something about an IMAP4 server for OpenVMS? Any hints about sources, companies, prices (for education etc.). -- Matthias Muth - Matthias Muth email: Matthias.Muth@bessy.de BESSY GmbH phone: +49 30 6392 2954 Albert-Einstein-Str. 15 fax: +49 30 6392 2990 D-12489 Berlin GERMANY ================================================================================ Archive-Date: Mon, 31 Jul 2000 08:21:59 -0700 From: "Martin Vorlaender" Reply-To: MX-List@MadGoat.com To: CC: "'Matthias Muth'" Subject: RE: IMAP4 Server for OpenVMS? Date: Mon, 31 Jul 2000 17:22:59 +0200 Message-ID: <13fd418b24979f920771d4ab0c064f9c398599a4@pdv-systeme.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: <009EDC48.888C0DA3.15@bessy.de> > does anybody know something about an IMAP4 server for OpenVMS? > Any hints about sources, companies, prices (for education etc.). Both TCP/IP stacks from Process Software have one, for details see http://www.process.com/tcpip/datasht.html (TCPware) http://www.process.com/tcpip/multinet2.html (Multinet) Sorry, no info about pricing - I'm a tech guy. cu, Martin -- One OS to rule them all | Martin Vorlaender | VMS & WNT programmer One OS to find them | work: mv@pdv-systeme.de One OS to bring them all | http://www.pdv-systeme.de/users/martinv/ And in the Darkness bind them.| home: martin@radiogaga.harz.de