Archive-Date: Mon, 24 Feb 2003 08:56:36 -0800 Date: Mon, 24 Feb 2003 16:58:15 GMT From: System Manager Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <00A1BFAE.6328D43A.91@mailgate.spotimage.fr> Subject: alternate path in MX 4.2 ? Return-Path: system@mailgate.spotimage.fr hi, is it possible to define an alternate path for some routing, in case the primary path fail (for ex. the machine is down) ? TIA, Pierre. ================================================================================ Archive-Date: Mon, 24 Feb 2003 09:56:32 -0800 MIME-Version: 1.0 Date: Mon, 24 Feb 2003 12:54:19 -0500 Message-ID: <00B3F0D8.C22236@smiths-aerospace.com> From: Brian.Tillman@smiths-aerospace.com Reply-To: MX-List@MadGoat.com Subject: Re:alternate path in MX 4.2 ? To: system@mailgate.spotimage.fr, MX-List@MadGoat.com Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Content-Description: cc:Mail note part >is it possible to define an alternate path for some routing, >in case the primary path fail (for ex. the machine is down) ? That's what MX records do, or so I thought. Brian Tillman Internet: Brian.Tillman at smiths-aerospace dot com Smiths Aerospace Addresses modified to prevent SPAM. 3290 Patterson Ave. SE, MS Replace "at" with "@", "dot" with "." Grand Rapids, MI 49512-1991 This opinion doesn't represent that of my company ================================================================================ Archive-Date: Mon, 24 Feb 2003 16:20:03 -0800 Subject: Re:alternate path in MX 4.2 ? From: peter@langstoeger.at (Peter LANGSTOEGER) Message-ID: <8zw6a.79206$Rb4.1140192@news.chello.at> Date: Mon, 24 Feb 2003 21:57:24 GMT Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com In article <00B3F0D8.C22236@smiths-aerospace.com>, Brian.Tillman@smiths-aerospace.com writes: >>is it possible to define an alternate path for some routing, >>in case the primary path fail (for ex. the machine is down) ? > >That's what MX records do, or so I thought. I read it as, the question was, how to do it without MX RR ? And currently I can't answer it, also, because I use MX RR mainly for this reason ;-) -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ================================================================================ Archive-Date: Tue, 25 Feb 2003 04:30:54 -0800 Date: Tue, 25 Feb 2003 12:32:34 GMT From: System Manager Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <00A1C052.6FA344FD.1@mailgate.spotimage.fr> Subject: RE: Re:alternate path in MX 4.2 ? Return-Path: system@mailgate.spotimage.fr >>>is it possible to define an alternate path for some routing, >>>in case the primary path fail (for ex. the machine is down) ? >> >>That's what MX records do, or so I thought. > >I read it as, the question was, how to do it without MX RR ? And currently >I can't answer it, also, because I use MX RR mainly for this reason ;-) yes, I know MX records, but for some reasons of no interest here, some of the nodes of my network do not have (must not have) an IP stack. so I use the folowing path: Domain-to-path mappings: Domain="nodeA.spotimage.fr", Path=Local Domain="nodeA", Path=Local Domain="*", Path=DECnet_SMTP, Route="nodeB" with nodeB acting as a mailhub/relay. but if nodeB is down, I would like to have nodeC as a failover. Pierre. ================================================================================ Archive-Date: Tue, 25 Feb 2003 04:44:24 -0800 Date: Tue, 25 Feb 2003 13:44:08 +0000 From: "Rok Vidmar, NUK Ljubljana" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <00A1C05C.6F48C129.41@NUK.Uni-Lj.Si> Subject: RE: Re:alternate path in MX 4.2 ? MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" > Domain-to-path mappings: > Domain="nodeA.spotimage.fr", Path=Local > Domain="nodeA", Path=Local > Domain="*", Path=DECnet_SMTP, Route="nodeB" > > with nodeB acting as a mailhub/relay. but if nodeB is down, I would like to > have nodeC as a failover. Try to establish a cluster alias node identifier nodeZ and use it on both nodeB and nodeC. If the nodes nodeB and nodeC are not or can not be clustered, make two differnt clusters containing one node each - nodeB and nodeC respectively. Regards, Rok Vidmar Internet: rok.vidmar@nuk.uni-lj.si National and University Library Phone: +386 1 421 5461 Turjaska 1, SI-1000 Ljubljana Fax: +386 1 421 5464 Slovenia ================================================================================ Archive-Date: Fri, 28 Feb 2003 07:57:58 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: MX_REJECTIONS.DAT corruption Date: Fri, 28 Feb 2003 09:59:07 -0600 Message-ID: From: "Larry D. Schuldt" Reply-To: MX-List@MadGoat.com To: All, The MX_REJECTIONS.DAT file is corrupted on our system. As a result, the rule numbers are non-unique. For instance, Rule ID 3743 occurs 6 times in the rule base, each with a different rule.=20 Does anyone know of a way to fix this file? Thanks, Larry Larry Schuldt DLS Internet Services (847) 854-4799 ext. 235=20 ================================================================================ Archive-Date: Fri, 28 Feb 2003 08:01:24 -0800 Message-ID: <3E5F87FB.3070802@SMTP.DeltaTel.RU> Date: Fri, 28 Feb 2003 19:02:03 +0300 From: "Ruslan R. Laishev" Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@MadGoat.com Subject: Re: MX_REJECTIONS.DAT corruption References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi ! $anal /rms /fdl ... $convert/fdl ... Larry D. Schuldt wrote: > All, > > The MX_REJECTIONS.DAT file is corrupted on our system. As a result, the > rule numbers are non-unique. For instance, Rule ID 3743 occurs 6 times > in the rule base, each with a different rule. > > Does anyone know of a way to fix this file? > > Thanks, > Larry > > Larry Schuldt > DLS Internet Services > (847) 854-4799 ext. 235 > > . > -- Cheers, +OpenVMS [Sys|Net] HardWorker .......................................+ Delta Telecom Inc., NMT-450i, IMT-MC-450(CDMA2000) cellular operator Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 116-3222 +http://starlet.deltatel.ru ................. Frying on OpenVMS only + ================================================================================ Archive-Date: Fri, 28 Feb 2003 08:12:22 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: MX_REJECTIONS.DAT corruption Date: Fri, 28 Feb 2003 10:13:29 -0600 Message-ID: From: "Larry D. Schuldt" Reply-To: MX-List@MadGoat.com To: Ruslan, I looked at the RMS structure of the file... It's not really indexed! I can try it, though... $ type mx_rejections.fdl IDENT "28-FEB-2003 09:38:25 OpenVMS ANALYZE/RMS_FILE Utility" SYSTEM SOURCE OpenVMS FILE ALLOCATION 525 BEST_TRY_CONTIGUOUS no CLUSTER_SIZE 3 CONTIGUOUS no EXTENSION 0 FILE_MONITORING no GLOBAL_BUFFER_COUNT 0 NAME "MX_DEVICE:[MX]MX_REJECTIONS.DAT;1" ORGANIZATION sequential OWNER [SYSTEM] PROTECTION (system:RWED, owner:RWED, group:RE, world:) RECORD BLOCK_SPAN yes CARRIAGE_CONTROL none FORMAT variable SIZE 0 -----Original Message----- From: Ruslan R. Laishev [mailto:Laishev@SMTP.DeltaTel.RU]=20 Sent: Friday, February 28, 2003 10:02 AM To: MX-List@MadGoat.com Subject: Re: MX_REJECTIONS.DAT corruption Hi ! $anal /rms /fdl ... $convert/fdl ... Larry D. Schuldt wrote: > All, >=20 > The MX_REJECTIONS.DAT file is corrupted on our system. As a result,=20 > the rule numbers are non-unique. For instance, Rule ID 3743 occurs 6=20 > times in the rule base, each with a different rule. >=20 > Does anyone know of a way to fix this file? >=20 > Thanks, > Larry >=20 > Larry Schuldt > DLS Internet Services > (847) 854-4799 ext. 235 >=20 > . >=20 --=20 Cheers, +OpenVMS [Sys|Net] HardWorker .......................................+ Delta Telecom Inc., NMT-450i, IMT-MC-450(CDMA2000) cellular operator Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 116-3222 +http://starlet.deltatel.ru ................. Frying on OpenVMS only + ================================================================================ Archive-Date: Fri, 28 Feb 2003 08:17:47 -0800 Message-ID: <3E5F8BD4.8020205@SMTP.DeltaTel.RU> Date: Fri, 28 Feb 2003 19:18:28 +0300 From: "Ruslan R. Laishev" Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@MadGoat.com Subject: Re: MX_REJECTIONS.DAT corruption References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hmmm... It' need to ask Matt about file/record structures. Larry D. Schuldt wrote: > Ruslan, > > I looked at the RMS structure of the file... It's not really indexed! I > can try it, though... > > $ type mx_rejections.fdl > IDENT "28-FEB-2003 09:38:25 OpenVMS ANALYZE/RMS_FILE Utility" > > SYSTEM > SOURCE OpenVMS > > FILE > ALLOCATION 525 > BEST_TRY_CONTIGUOUS no > CLUSTER_SIZE 3 > CONTIGUOUS no > EXTENSION 0 > FILE_MONITORING no > GLOBAL_BUFFER_COUNT 0 > NAME "MX_DEVICE:[MX]MX_REJECTIONS.DAT;1" > ORGANIZATION sequential > OWNER [SYSTEM] > PROTECTION (system:RWED, owner:RWED, group:RE, > world:) > > RECORD > BLOCK_SPAN yes > CARRIAGE_CONTROL none > FORMAT variable > SIZE 0 > > > > -----Original Message----- > From: Ruslan R. Laishev [mailto:Laishev@SMTP.DeltaTel.RU] > Sent: Friday, February 28, 2003 10:02 AM > To: MX-List@MadGoat.com > Subject: Re: MX_REJECTIONS.DAT corruption > > > Hi ! > > $anal /rms /fdl ... > $convert/fdl ... > > Larry D. Schuldt wrote: > >>All, >> >>The MX_REJECTIONS.DAT file is corrupted on our system. As a result, >>the rule numbers are non-unique. For instance, Rule ID 3743 occurs 6 >>times in the rule base, each with a different rule. >> >>Does anyone know of a way to fix this file? >> >>Thanks, >>Larry >> >>Larry Schuldt >>DLS Internet Services >>(847) 854-4799 ext. 235 >> >>. >> > > > -- Cheers, +OpenVMS [Sys|Net] HardWorker .......................................+ Delta Telecom Inc., NMT-450i, IMT-MC-450(CDMA2000) cellular operator Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 116-3222 +http://starlet.deltatel.ru ................. Frying on OpenVMS only +