Archive-Date: Tue, 2 Feb 1999 14:36:12 -0800 Date: Tue, 2 Feb 1999 14:36:03 -0800 (PST) From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: Re: moderated lists? In-Reply-To: <541C9C38F3F3D111A3230000F89CCCCC1AC8DA@issmsg1.iss.msfc.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 28 Jan 1999, Porter, Linda wrote: > Any hope of seeing support for moderated lists in a future release? > > I suppose I could fake it with rejman, so that it forwards anything posted > to a particular list to a forwarding address(es)? > > Has anyone tried that? Try something like this. The Rewrite rules must be in the order shown. MCP> DEFINE REWRITE "REAL-listname@hostnmae" "listname@hostname" MCP> DEFINE REWRITE "listname@hostname" "human-moderator@hostname" MCP> DEFINE PATH MODERATE SITE/ROUTE=MODERATE Replace the lowercase "listname" and "hostname" with the name of the mailing list and the name of your host, and "human-moderator" with the username of the person doing the moderating. The moderator can extract the message and resend it to "REAL-listname@hostname" using MX_SITE_IN.EXE - quite a pain but it works. I have set this up on a few systems, but haven't tested this exact solution. -Dan Wing ================================================================================ Archive-Date: Wed, 3 Feb 1999 04:41:34 -0800 From: "Patrick Cox" To: MX-List@MadGoat.com Date: Wed, 3 Feb 1999 08:41:36 AST Subject: Re: moderated lists? Reply-To: MX-List@MadGoat.com References: <541C9C38F3F3D111A3230000F89CCCCC1AC8DA@issmsg1.iss.msfc.nasa.gov> In-Reply-To: On 2 Feb 99, at 14:36, Dan Wing wrote: > On Thu, 28 Jan 1999, Porter, Linda wrote: > > > Any hope of seeing support for moderated lists in a future release? [snip] > Try something like this. The Rewrite rules must be in the order > shown. > > MCP> DEFINE REWRITE "REAL-listname@hostnmae" "listname@hostname" > MCP> DEFINE REWRITE "listname@hostname" "human-moderator@hostname" > MCP> DEFINE PATH MODERATE SITE/ROUTE=MODERATE What is the point of the PATH? > Replace the lowercase "listname" and "hostname" with the name of the > mailing list and the name of your host, and "human-moderator" with > the username of the person doing the moderating. > > The moderator can extract the message and resend it to > "REAL-listname@hostname" using MX_SITE_IN.EXE - quite a pain but it works. Why use MX_SITE_IN? Once the REAL-listname@hostname rewrite has been hit it will go to the list. This should work like: 1) List member sends message to list@host 2) Rewrite rule changes To: to moderator@host 3) Moderator gets message and resends it to REAL-list@host 4) Rewrite rule changes To: to list@host (Rewrite checking stops) 5) Message gets sent to list. All you need is the two rewrite rules. Hmmm... Did I miss something? I don't think so. Dan, i sthis the way it should work? Patrick M. Cox Information Technology Section (Truro) Resources Corporate Services Unit (DAM,DNR,DOF,DOE) ================================================================================ Archive-Date: Wed, 3 Feb 1999 08:26:51 -0800 Date: Wed, 3 Feb 1999 08:26:44 -0800 (PST) From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: Re: moderated lists? In-Reply-To: <199902031250.EAA08944@proxy3.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Wed, 3 Feb 1999, Patrick Cox wrote: > On 2 Feb 99, at 14:36, Dan Wing wrote: > > > On Thu, 28 Jan 1999, Porter, Linda wrote: > > > > > Any hope of seeing support for moderated lists in a future release? > > [snip] > > > Try something like this. The Rewrite rules must be in the order > > shown. > > > > MCP> DEFINE REWRITE "REAL-listname@hostnmae" "listname@hostname" > > MCP> DEFINE REWRITE "listname@hostname" "human-moderator@hostname" > > MCP> DEFINE PATH MODERATE SITE/ROUTE=MODERATE > > What is the point of the PATH? You're right - it isn't needed. My original Rewrite looked like: MCP> DEFINE REWRITE "listname@hostname" "listname-MODERATE@MODERATE" and is then processed by a .COM file to decide if the post is obviously bogus (by doing a simple keyword search). > > Replace the lowercase "listname" and "hostname" with the name of the > > mailing list and the name of your host, and "human-moderator" with > > the username of the person doing the moderating. > > > > The moderator can extract the message and resend it to > > "REAL-listname@hostname" using MX_SITE_IN.EXE - quite a pain but it works. > > Why use MX_SITE_IN? Do avoid generating Remail-* headers for the accepted (moderated) messages. > Once the REAL-listname@hostname rewrite has been > hit it will go to the list. Rewrite rules are processed once. > This should work like: > 1) List member sends message to list@host > 2) Rewrite rule changes To: to moderator@host > 3) Moderator gets message and resends it to REAL-list@host Yes, but step (3), depending on the mailer the moderator is using, could munge headers. That's why I suggest using MX_SITE_IN. > 4) Rewrite rule changes To: to list@host (Rewrite checking stops) It changes the envelope-to -- the rewrite rules won't change the RFC822 To:. > 5) Message gets sent to list. > > All you need is the two rewrite rules. > > Hmmm... Did I miss something? I don't think so. Dan, i sthis the way > it should work? Yes, you can drop the path. Thanks for catching that. -d ================================================================================ Archive-Date: Wed, 3 Feb 1999 12:44:20 -0800 Date: Wed, 3 Feb 1999 15:44:06 -0500 From: "Jonathan E. Hardis" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: hardis@garnet.nist.gov Message-ID: <009D3314.7F102520.3@garnet.nist.gov> Subject: Re: moderated lists? > > > Any hope of seeing support for moderated lists in a future release? > > [snip] > > > Try something like this. The Rewrite rules must be in the order > > shown. [snip] I came up with this some years back -- if you search the archives you can find the details. (Sorry, I don't have the time now.) The messages passed through SITE both inbound and outbound in order to edit the headers and to provide a distribution list to several moderators. There were command files for EDIT to remove traces of the moderating process. DEFINE REWRITE_RULE DEFINE REWRITE_RULE ! DEFINE PATH "password1" SITE/ROUTE="MOD-IN" DEFINE PATH "password2" SITE/ROUTE="MODERATE" SITE_DELIVER.COM: $ SET NOON $ MX_ENTER := $MX_EXE:MX_SITE_IN $ $! Separate processing for different routes $ $ IF P1 .EQS. "MODERATED" THEN GOTO Moderated_Start $ IF P1 .EQS. "MOD-IN" THEN GOTO Mod_In_Start $ EXIT 4 $ $!------------------------------------------------------------------------- $ $ Moderated_Start: $! $! Modify contents of source-file (P2) to remove Resent-To: header $! $ DEFINE/USER_MODE SYS$OUTPUT NL: $ EDIT/EDT/COMMAND=MX_ROOT:[SITE]CHANGE_P2_MODERATED.DAT 'P2' $! $! Modify contents of dest-file (P3) to change from %PASSWORD2 to -PW3 $! $ DEFINE/USER_MODE SYS$OUTPUT NL: $ EDIT/EDT/COMMAND=MX_ROOT:[SITE]CHANGE_P3_MODERATED.DAT 'P3' $ $ NEW_P2 = F$PARSE(";2",P2) $ NEW_P3 = F$PARSE(";2",P3) $! $! Send processed file on its way $! $ MX_ENTER 'NEW_P2' 'NEW_P3' "''P4'" $ $ DELETE 'NEW_P2' $ DELETE 'NEW_P3' $ $ EXIT 1 $ $!------------------------------------------------------------------------- $ $ Mod_In_Start: $ $ MX_ENTER 'P2' MX_SITE_DIR:MOD1.TXT "''P4'" $ MX_ENTER 'P2' MX_SITE_DIR:MOD2.TXT "''P4'" $! MX_ENTER 'P2' MX_SITE_DIR:MOD3.TXT "" $ $ EXIT 1 This ought to give you enough text to search on for the whole solution in the archives. Search on F$PARSE, or something. - Jonathan ================================================================================ Archive-Date: Wed, 3 Feb 1999 12:52:23 -0800 Date: Wed, 3 Feb 1999 14:52:09 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D330D.3CFBEDC9.7@goat.process.com> Subject: Re: moderated lists? "Jonathan E. Hardis" writes: > >I came up with this some years back -- if you search the archives you can >find the details. (Sorry, I don't have the time now.) > Here are a couple of URLs for Jonathan's original posts about moderating lists. http://www2.wku.edu/scripts/mxarchive/archive_search.com?TEXT=R70144-76554-anonymous_root%3A%5Blists.mx-list%5Dmx-list.1995-05 http://www2.wku.edu/scripts/mxarchive/archive_search.com?TEXT=R37548-41202-anonymous_root%3A%5Blists.mx-list%5Dmx-list.1995-12 Or go to the search page and search for "moderated hardis". Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www2.wku.edu/hunter/ ================================================================================ Archive-Date: Thu, 4 Feb 1999 03:06:18 -0800 From: eplan@kapsch.net (Peter LANGSTOEGER) Subject: MX_SMTP_LOCK_EXCLUSIONS Date: 4 Feb 99 11:03:08 GMT Message-ID: <36b97e6c.0@nevada.kapsch.co.at> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU Recently I heard of an (undocumented !?) logical in MX V5.? MX_SMTP_LOCK_EXCLUSIONS 1) Why is it undocumented ? Because the whole LOCK behaviour is undocumented ? 2) How do I use it ? DEFINE/SYSTEM/EXEC MX_SMTP_LOCK_EXCLUSIONS "translation" Is "translation" a) a domain b) a mailserver for a domain c) a list of domains in quotes d) a list of domains each quoted (search list) e) allowed to contain wildcards 3) Is it possible to generally revert the LOCK file behaviour to pre V5 ? TIA ------------------------------------------------------------------------ Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services E-mail eplan@kapsch.net <<< KAPSCH AG Wagenseilgasse 1 PSImail PSI%(0232)281001141::EPLAN A-1121 VIENNA AUSTRIA "I'm not a pessimist, I'm a realist" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Thu, 11 Feb 1999 02:31:23 -0800 Date: Thu, 11 Feb 1999 11:31:47 +0200 From: "Walter F.J. Mueller" Reply-To: MX-List@MadGoat.com To: mx-list@MadGoat.com CC: mueller@axp602.gsi.de Message-ID: <009D393A.92A903A5.42@axp602.gsi.de> Subject: Service Areas for Lists Hallo, we use a couple of open mailing lists and got recently bombed with junk emails, apparently because the list address got somehow on one of the address CD-ROM's. Sure, a simple SET LIST /PROT=(WORLD:R) will fix this and allow only subscribers to send to the list. But these days this solution isn't practical anymore, it's simply too much trouble to match what can all be in the From: field of an email.... So I'd like to limit the write permission to IP domains rather than to individual accounts. That will keep the junk out and is easy to maintain. LISTSERV supports this notion of `service areas' and I wonder how this can be setup with MX. We are running MX V5.0. With best regards, Walter -- Walter F.J. Mueller Mail: W.F.J.Mueller@gsi.de GSI, Abteilung KP3 Phone: +49-6159-71-2766 D-64291 Darmstadt FAX: +49-6159-71-2989 WWW: http://www-kp3.gsi.de/www/kp3/people/mueller.html PGP: http://www-kp3.gsi.de/~mueller/pgp.shtml ================================================================================ Archive-Date: Thu, 11 Feb 1999 04:34:02 -0800 From: eplan@kapsch.net (Peter LANGSTOEGER) Subject: IDENTD support in SMTP_SERVER ? Date: 11 Feb 99 12:28:18 GMT Message-ID: <36c2cce2.0@nevada.kapsch.co.at> Reply-To: MX-List@MadGoat.com To: MX-List@LISTS.WKU.EDU Is the IDENTD already supported by the MX V5.1 SMTP_SERVER ? I doubt. May I suggest adding this functionality to a (near) future version of MX (to the SMTP_SERVER and to REJMAN). TIA ------------------------------------------------------------------------ Peter "EPLAN" LANGSTOEGER Tel. +43 1 81111-2651 Network and OpenVMS system manager Fax. +43 1 81111-888 FBFV/Information Services E-mail eplan@kapsch.net <<< KAPSCH AG Wagenseilgasse 1 PSImail PSI%(0232)281001141::EPLAN A-1121 VIENNA AUSTRIA "I'm not a pessimist, I'm a realist" "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998 ================================================================================ Archive-Date: Thu, 11 Feb 1999 08:11:16 -0800 Date: Thu, 11 Feb 1999 08:11:05 -0800 (PST) From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: mueller@axp602.gsi.de Subject: Re: Service Areas for Lists In-Reply-To: <009D393A.92A903A5.42@axp602.gsi.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 11 Feb 1999 11:31 +0200, Walter F.J. Mueller wrote: > we use a couple of open mailing lists and got recently bombed > with junk emails, apparently because the list address got somehow > on one of the address CD-ROM's. > > Sure, a simple SET LIST /PROT=(WORLD:R) will fix this and allow > only subscribers to send to the list. But these days this solution > isn't practical anymore, it's simply too much trouble to match what > can all be in the From: field of an email.... > > So I'd like to limit the write permission to IP domains rather than > to individual accounts. That will keep the junk out and is easy to > maintain. > > LISTSERV supports this notion of `service areas' and I wonder how > this can be setup with MX. We are running MX V5.0. Using IP addresses is even worse than From: addresses. For example, here at Cisco, my outgoing mail could be processed by any one of our literally 200+ mailers -- depending on which I am connected to which depends on which site I'm located at that day. I typically use the same one, but not always. However, my from address is always dwing@cisco.com. Also, ISPs are free to change their mailer configurations which would cause incoming mail to come from different IP addresses -- but your subscriber's email addresses stay the same. I would recommend either using W:R, as you mentioned, or installing a filter on your mailing lists which was discussed on MX-List a few weeks ago. The filter could forward ALL messages, or filter messages with 'suspect strings' (like "$$$"), or filter messages from non-subscribers -- and send the filtered messages to a human moderator. -Dan Wing ================================================================================ Archive-Date: Thu, 11 Feb 1999 08:13:09 -0800 Date: Thu, 11 Feb 1999 08:13:02 -0800 (PST) From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: Re: IDENTD support in SMTP_SERVER ? In-Reply-To: <36c2cce2.0@nevada.kapsch.co.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 11 Feb 1999 12:28 +0000, Peter LANGSTOEGER wrote: > Is the IDENTD already supported by the MX V5.1 SMTP_SERVER ? I doubt. No, it isn't. > May I suggest adding this functionality to a (near) future version of MX > (to the SMTP_SERVER and to REJMAN). IDENT is easily spoofed and provides untrusted 'authentication' of the sender. With the proliferation of non-privileged machines (Windows) and commonly-available privileged machines where the owner is root (especially Linux), it seems of little value to me. -Dan Wing ================================================================================ Archive-Date: Thu, 11 Feb 1999 09:45:13 -0800 Date: Thu, 11 Feb 1999 18:45:37 +0200 From: "Walter F.J. Mueller" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: mueller@axp602.gsi.de Message-ID: <009D3977.2D8ECB4D.15@axp602.gsi.de> Subject: Re: Service Areas for Lists dwing@cisco.com wrote: >> So I'd like to limit the write permission to IP domains rather than >> to individual accounts. That will keep the junk out and is easy to >> maintain. > Using IP addresses is even worse than From: addresses. > .. Well, my idea was to restrict access at a set of domain names and not to use IP address at all. Allowing for example submissions from "gsi.de" only would allow everybody from our institute to use the list, but keep all external junk out. Adding the domain names of a few collaborating institutes would allow them in, and still keep the junk out. Walter Mueller -- Walter F.J. Mueller Mail: W.F.J.Mueller@gsi.de GSI, Abteilung KP3 Phone: +49-6159-71-2766 D-64291 Darmstadt FAX: +49-6159-71-2989 WWW: http://www-kp3.gsi.de/www/kp3/people/mueller.html PGP: http://www-kp3.gsi.de/~mueller/pgp.shtml ================================================================================ Archive-Date: Thu, 11 Feb 1999 19:20:06 -0800 Date: Thu, 11 Feb 1999 19:16:32 -0800 (PST) From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: Re: Service Areas for Lists In-Reply-To: <009D3977.2D8ECB4D.15@axp602.gsi.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 11 Feb 1999 18:45 +0200, Walter F.J. Mueller wrote: > dwing@cisco.com wrote: > > >> So I'd like to limit the write permission to IP domains rather than > >> to individual accounts. That will keep the junk out and is easy to > >> maintain. > > > Using IP addresses is even worse than From: addresses. > > .. > > Well, my idea was to restrict access at a set of domain names and not > to use IP address at all. Allowing for example submissions from > "gsi.de" only would allow everybody from our institute to use the list, > but keep all external junk out. Adding the domain names of a few > collaborating institutes would allow them in, and still keep the junk out. A filter using the SITE agent would be perfect for the job. I believe I posted some DCL which did some simple filtering like that - in any event the DCL would be triggered by the same REWRITE rules and a special PATH rule -- I believe I posted stuff that would trigger that for a mailing list a month or so ago. The DCL could be something as simple as this (MX_EXE:SITE_DELIVER.COM): $! from our institution? $ IF F$LOCATE("gsi.de",F$EDIT(P4,"LOWERCASE")) THEN GOTO OKAY $ $! subscriber to the mailing list? $ MCR MX_EXE:MCP REVIEW listname/OUTPUT=X.X $ SET NOON $ SEARCH X.X "''P4'" $ S = $STATUS $ SET ON $ IF S THEN GOTO OKAY $ $! someone on the list of special exceptions? $ SET NOON $ SEARCH MX_ROOT:[000000]SPECIAL_EXCEPTIONS.DAT "''P4'" $ S = $STATUS $ SET ON $ IF S THEN GOTO OKAY $ $! no, it is someone we don't know. Bounce it. Something $! descriptive might be more appreciated, but, heck, they lose $ IF F$SEARCH("X.X") THEN DELETE X.X;* $ EXIT %X02C ! %SYSTEM-F-ABORT, not very descriptive, but bounces msg $ $OKAY: $ OPEN/WRITE OUTFILE Y.Y $ WRITE OUTFILE "filtered-LISTNAME@hostname" $ CLOSE OUTFILE $ $ MX_ENTER := $MX_EXE:MX_SITE_IN $ MX_ENTER 'P2' Y.Y "''P4'" $ DELETE Y.Y;,X.X; $ EXIT Obviously you would want to use more dynamically-generated filenames than X.X and Y.Y, but you get the idea. Free code! Public domain! "Embrace and Extend!" -Dan Wing ================================================================================ Archive-Date: Fri, 12 Feb 1999 08:22:09 -0800 Message-ID: <36C4545B.7874073C@ccr.dsi.uanl.mx> Date: Fri, 12 Feb 1999 10:18:37 -0600 From: Roberto Carlos Padilla =?iso-8859-1?Q?Ch=E1vez?= Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@MadGoat.com Subject: Problem... Content-Type: multipart/mixed; boundary="------------0393307563C0F264C6733D1B" This is a multi-part message in MIME format. --------------0393307563C0F264C6733D1B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Everybody!... For weeks ago I have been having a problem with ours MX. The problem already I have commented it to the list, and have followed the suggestions that have commented to me, but the problem follows equal. Of new account them comment the problem. When the users connect themselves by telnet to the VAX and send a mail, the mail does not arrive at its destiny, single the users with all the privileges can send mail and these arrive. The privileges that have the users are TMPMBX, NETMBX. It is possible to clarify that single when the users write the username of the adressee this arrives, but when they put all the dominion does not arrive. ********* Ejample: $ mail mail> send to: username sub: test Test!....... ********* This mail arrives at its destiny. ********** Example 2 $mail mail>send to: username@domain subj: test Test! ********* This mail no arrives at its destiny..... I request to them please that they try to help me... Matt. i make the instuctions that you say me,and i dont found the problem.... somebody speak or understand Spanish???? Thaks! --------------0393307563C0F264C6733D1B Content-Type: text/x-vcard; charset=us-ascii; name="rpadilla.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Roberto Carlos Padilla Chávez Content-Disposition: attachment; filename="rpadilla.vcf" begin:vcard n:Padilla ;Roberto tel;fax:+528 329-40-83 tel;work:+528 329-40-81 x-mozilla-html:TRUE url:http://www.uanl.mx org:U.A.N.L.;Centro de Computo version:2.1 email;internet:rpadilla@ccr.dsi.uanl.mx adr;quoted-printable:;;Pedro de Alba s/n Edif. de Informatica 3er piso=0D=0ACd. Universitaria;San Nicolas de los Garza;Nuevo Leon;66450;Mexico fn:Roberto Carlos Padilla Chavez end:vcard --------------0393307563C0F264C6733D1B-- ================================================================================ Archive-Date: Fri, 12 Feb 1999 10:57:32 -0800 Date: Fri, 12 Feb 1999 12:56:18 -0600 From: hunterl@uwwvax.uww.edu Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D3A0F.8B7BD663.38@uwwvax.uww.edu> Subject: RE: Problem... Should this be M%"username@domain"? => ********** => Example 2 => $mail => mail>send => to: username@domain => subj: test => => Test! => ********* => Lyle Hunter T & IR University Wisconsin-Whitewater 414-472-1967 Fax: 414-472-5733 ================================================================================ Archive-Date: Fri, 12 Feb 1999 11:09:42 -0800 Date: Fri, 12 Feb 1999 12:09:19 MST From: Bill Monday Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D3A08.FB81A520.10@upi.uhcolorado.edu> Subject: RE: Problem... MX%"username@domain" Unless you are using users defines in MXALIAS in which case MX%username can work. -Bill ! From: MX%"MX-List@MadGoat.com" 12-FEB-1999 11:58:02.64 ! To: MX%"MX-List@MadGoat.com" ! CC: ! Subj: RE: Problem... ! ! Should this be M%"username@domain"? ! ! => ********** ! => Example 2 ! => $mail ! => mail>send ! => to: username@domain ! => subj: test ! => ! => Test! ! => ********* ! => ! ! Lyle Hunter ! T & IR ! University Wisconsin-Whitewater ! 414-472-1967 ! Fax: 414-472-5733 ================================================================================ Archive-Date: Fri, 12 Feb 1999 13:39:25 -0800 Message-ID: <36C49D57.FA976769@ccr.dsi.uanl.mx> Date: Fri, 12 Feb 1999 15:29:59 -0600 From: Roberto Carlos Padilla =?iso-8859-1?Q?Ch=E1vez?= Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@MadGoat.com Subject: Re: Problem... References: <009D3A0F.8B7BD663.38@uwwvax.uww.edu> Content-Type: multipart/mixed; boundary="------------25E0A330B36385A03EBE2DA5" This is a multi-part message in MIME format. --------------25E0A330B36385A03EBE2DA5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have already tried to send mail of the form in you say to me, but does not even arrive. when I see the status of mail that was sent this says that is finished, but in fact does not arrive at his destiny. hunterl@uwwvax.uww.edu wrote: > Should this be M%"username@domain"? > > => ********** > => Example 2 > => $mail > => mail>send > => to: username@domain > => subj: test > => > => Test! > => ********* > => > > Lyle Hunter > T & IR > University Wisconsin-Whitewater > 414-472-1967 > Fax: 414-472-5733 --------------25E0A330B36385A03EBE2DA5 Content-Type: text/x-vcard; charset=us-ascii; name="rpadilla.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Roberto Carlos Padilla Chávez Content-Disposition: attachment; filename="rpadilla.vcf" begin:vcard n:Padilla ;Roberto tel;fax:+528 329-40-83 tel;work:+528 329-40-81 x-mozilla-html:TRUE url:http://www.uanl.mx org:U.A.N.L.;Centro de Computo version:2.1 email;internet:rpadilla@ccr.dsi.uanl.mx adr;quoted-printable:;;Pedro de Alba s/n Edif. de Informatica 3er piso=0D=0ACd. Universitaria;San Nicolas de los Garza;Nuevo Leon;66450;Mexico fn:Roberto Carlos Padilla Chavez end:vcard --------------25E0A330B36385A03EBE2DA5-- ================================================================================ Archive-Date: Mon, 15 Feb 1999 00:02:14 -0800 Message-ID: <001701be58ba$128e9c90$ed2300c0@tool201> From: "=?iso-8859-1?Q?Jos=E9_Luis_L=F3pez_Jacob?=" Reply-To: MX-List@MadGoat.com To: Subject: RE: Problem... Date: Mon, 15 Feb 1999 09:06:19 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hola Roberto, No he podido comprender exactamente el problema. Trata de explicarlo en Espanol para ver si te ppodemos ayudar. Un saludo Jose Luis Lopez Jacob Madrid -----Mensaje original----- De: Roberto Carlos Padilla Ch=E1vez Para: MX-List@MadGoat.com Fecha: viernes 12 de febrero de 1999 17:20 Asunto: Problem... >Hi Everybody!... > >For weeks ago I have been having a problem with ours MX. > >The problem already I have commented it to the list, and have followed >the suggestions that have commented to me, but the problem follows >equal. > >Of new account them comment the problem. > >When the users connect themselves by telnet to the VAX and send a mail, >the mail does not arrive at its destiny, single the users with all the >privileges can send mail and these arrive. The privileges that have the >users are TMPMBX, NETMBX. > >It is possible to clarify that single when the users write the username >of the adressee this arrives, but when they put all the dominion does >not arrive. > >********* >Ejample: >$ mail >mail> send >to: username >sub: test > >Test!....... >********* > >This mail arrives at its destiny. > >********** >Example 2 >$mail >mail>send >to: username@domain >subj: test > >Test! >********* > >This mail no arrives at its destiny..... > >I request to them please that they try to help me... > >Matt. i make the instuctions that you say me,and i dont found the >problem.... > >somebody speak or understand Spanish???? > >Thaks! > > > ================================================================================ Archive-Date: Mon, 15 Feb 1999 06:51:00 -0800 Message-ID: <36C82577.17369531@ccr.dsi.uanl.mx> Date: Mon, 15 Feb 1999 07:47:36 -0600 From: Roberto Carlos Padilla =?iso-8859-1?Q?Ch=E1vez?= Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@MadGoat.com Subject: Re: Problem... References: <001701be58ba$128e9c90$ed2300c0@tool201> Content-Type: multipart/mixed; boundary="------------6F0F2041CBB282F6CCC5FAD8" This is a multi-part message in MIME format. --------------6F0F2041CBB282F6CCC5FAD8 Content-Type: multipart/alternative; boundary="------------90AE6E2FC5AD372DC80B2564" --------------90AE6E2FC5AD372DC80B2564 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Gracias Jose Luis. Bueno, tratare de explicarte el problema.. De un tiempo hacia aca he tenido problemas con las cuentas de los usiarios que tenemos en una VAX. Me di cuanta del problema cuando me hablaron varios usuarios diciendome que ellos habian enviado un correo a "x" destino y dicho correo no llegaba. Para esto di de alta una cuenta para hacer pruebas, dicha cuenta tiene los mismos privilegios que los demas usuarios, NETMBX y TMPMBX. , esta cuenta le puse como username ALMA Cuando me mando un correo con la cuenta de ALMA hacia mi cuenta personal, el correo nunca me llega, pero en la cola de correos el status que me indica es de que termino "finished". Deja te muestro como fue. Ok, mira, acabo de mandar un correo con la cuenta de ALMA hacia mi cuenta y este no ha llegado. $ mail MAIL> send To: rpadilla@ccr.dsi.uanlmx Subj: test Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit: test Exit Al ver la cola de correos este es el estatus que me indica: 225 FINISH 4 MAIL Si quiero ver completamente el estatus de este correo me muestra lo siguiente: Rpadilla/:> mcp sh queue/full 225 Entry: 225, Origin: [Local] Status: FINISHED, size: 4 bytes Created: 15-FEB-1999 08:21:40.64, expires 17-MAR-1999 08:21:40.64 Last modified 15-FEB-1999 08:21:46.74 Ni siquiera me muesta hacia donde iba ese correo, es decir, el destinatario... Ahora, he checado los .log que me deja el ROUTER y esto es lo que me muestran: 15-FEB-1999 08:31:53.68 %PROCESS, Processing entry number 225 15-FEB-1999 08:31:53.80 %PROCESS, Status from READ_INFO was 00000001 15-FEB-1999 08:31:53.80 %PROCESS, Message originated in VMS Mail. 15-FEB-1999 08:31:53.80 %PROCESS, will run domain expander on envelope addresses. 15-FEB-1999 08:31:53.80 %PROCESS, will run domain expander on message headers. 15-FEB-1999 08:31:54.34 %PROCESS, Updating the QENT source address. 15-FEB-1999 08:31:54.36 %PROCESS, Finished VMSmail-origin preprocessing. 15-FEB-1999 08:31:54.36 %PROCESS, Marking this entry as finished. Yo tengo todos los privilegios y cuando me conecto por telnet a la VAX y envio correos estos si llegan. Si tienes mas dudas para entender el problema, por favor dime y tratare de explicarte..... Gracias!.. --------------90AE6E2FC5AD372DC80B2564 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Gracias Jose Luis.
Bueno, tratare de explicarte el problema..

De un tiempo hacia aca he tenido problemas con las cuentas de los usiarios que tenemos en una VAX. Me di cuanta del problema cuando me hablaron varios usuarios diciendome que ellos habian enviado un correo a "x" destino y dicho correo no llegaba.

Para esto di de alta una cuenta para hacer pruebas, dicha cuenta tiene los mismos privilegios que los demas usuarios, NETMBX y TMPMBX. , esta cuenta le puse como username ALMA

Cuando me mando un correo con la cuenta de ALMA hacia mi cuenta personal, el correo nunca me llega, pero en la cola de correos el status que me indica es de que termino "finished". Deja te muestro como fue.

Ok, mira, acabo de mandar un correo con la cuenta de ALMA hacia mi cuenta y este no ha llegado.
$ mail

MAIL> send
To:     rpadilla@ccr.dsi.uanlmx
Subj:   test
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
test
Exit

Al ver la cola de correos este es el estatus que me indica:

225 FINISH       4 MAIL   <alma@ccr.dsi.uanl.mx>

Si quiero ver completamente el estatus de este correo me muestra lo siguiente:

Rpadilla/:> mcp sh queue/full 225

Entry: 225, Origin: [Local] <alma@ccr.dsi.uanl.mx>
  Status: FINISHED, size: 4 bytes
  Created: 15-FEB-1999 08:21:40.64, expires 17-MAR-1999 08:21:40.64
  Last modified 15-FEB-1999 08:21:46.74

Ni siquiera me muesta hacia donde iba ese correo, es decir, el destinatario...

Ahora, he checado los .log que me deja el ROUTER y esto es lo que me muestran:

15-FEB-1999 08:31:53.68 %PROCESS, Processing entry number 225
15-FEB-1999 08:31:53.80 %PROCESS, Status from READ_INFO was 00000001
15-FEB-1999 08:31:53.80 %PROCESS, Message originated in VMS Mail.
15-FEB-1999 08:31:53.80 %PROCESS,  will run domain expander on envelope addresses.
15-FEB-1999 08:31:53.80 %PROCESS,  will run domain expander on message headers.
15-FEB-1999 08:31:54.34 %PROCESS, Updating the QENT source address.
15-FEB-1999 08:31:54.36 %PROCESS, Finished VMSmail-origin preprocessing.
15-FEB-1999 08:31:54.36 %PROCESS, Marking this entry as finished.
 

Yo tengo todos los privilegios y cuando me conecto por telnet a la VAX y envio correos estos si llegan.

Si tienes mas dudas para entender el problema, por favor dime y tratare de explicarte.....

Gracias!..
 
 
 
  --------------90AE6E2FC5AD372DC80B2564-- --------------6F0F2041CBB282F6CCC5FAD8 Content-Type: text/x-vcard; charset=us-ascii; name="rpadilla.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Roberto Carlos Padilla Chávez Content-Disposition: attachment; filename="rpadilla.vcf" begin:vcard n:Padilla ;Roberto tel;fax:+528 329-40-83 tel;work:+528 329-40-81 x-mozilla-html:TRUE url:http://www.uanl.mx org:U.A.N.L.;Centro de Computo version:2.1 email;internet:rpadilla@ccr.dsi.uanl.mx adr;quoted-printable:;;Pedro de Alba s/n Edif. de Informatica 3er piso=0D=0ACd. Universitaria;San Nicolas de los Garza;Nuevo Leon;66450;Mexico fn:Roberto Carlos Padilla Chavez end:vcard --------------6F0F2041CBB282F6CCC5FAD8-- ================================================================================ Archive-Date: Mon, 15 Feb 1999 08:27:13 -0800 Message-ID: <002001be5900$94748990$ed2300c0@tool201> From: "=?iso-8859-1?Q?Jos=E9_Luis_L=F3pez_Jacob?=" Reply-To: MX-List@MadGoat.com To: Subject: RE: Problem... Date: Mon, 15 Feb 1999 17:30:59 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001D_01BE5908.F3758BD0" This is a multi-part message in MIME format. ------=_NextPart_000_001D_01BE5908.F3758BD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable En mi instalaci=F3n tenemos MX 5.1 y VMS 6.2. Con este software podemos = enviar y recibir mensajes indistintamente desde OUTLOOK EXPRESS y desde = VMS-Mail con las siguientes diferencias; VMS-MAIL usuario=3D=3D>cen800::jlj = (nodo-decnet::usuario-vms) o bien MX%"jlj@bancoinversion" = (usuario-vms@dominio) OUTLOOK/EXPRESS usuario=3D=3D>jlj@bancoinversion = (usuario-vms@dominio) Lo que nunca he podido hacer es mandar desde VMS un mail con el formato = user@dominio, ya que sin el prefijo MX% el procesador VMS-Mail no sabe = distribuir el mensaje. Para que MX reconozca si el dominio es local o no es necesario = indicarselo en MCP/PATHS de la siguiente manera MCP> show path Domain-to-path mappings: Domain=3D"BANCOINVERSION.COM", Path=3DLocal Domain=3D"BANCOINVERSION.ES", Path=3DLocal Domain=3D"BANCOINVERSION", Path=3DLocal Domain=3D"CEN800", Path=3DLocal Domain=3D"pru101", Path=3DLocal Domain=3D"SEV011", Path=3DLocal Domain=3D"BAR021", Path=3DLocal Domain=3D"VAL031", Path=3DLocal Domain=3D"ZAR051", Path=3DLocal Domain=3D"*", Path=3DSMTP =3D=3D> Por aqui sales = los mensajes no locales MCP> Otro problema es enviar mail desde OUTLOOK a nodos VMS que no tienen MX, = a trav=E9s de uno que s=ED lo tiene. Mediante rewrite_rule en MCP se = pueden rutear los mensajes adecuadamente. Por ejemplo MCP> show rewrite Address-rewriting rules: Rewrite "<{user}@pru101>" =3D> "<""pru101::{user}""@bancoinversion>" Rewrite "<{user}@sev011>" =3D> "<""sev011::{user}""@bancoinversion>" Rewrite "<{user}@BAR021>" =3D> "<""BAR021::{user}""@bancoinversion>" Rewrite "<{user}@VAL031>" =3D> "<""VAL031::{user}""@bancoinversion>" MCP> -----Mensaje original----- =20 De: Roberto Carlos Padilla Ch=E1vez Para: MX-List@MadGoat.com Fecha: lunes 15 de febrero de 1999 15:56 Asunto: Re: Problem... =20 =20 Gracias Jose Luis.=20 Bueno, tratare de explicarte el problema..=20 De un tiempo hacia aca he tenido problemas con las cuentas de los = usiarios que tenemos en una VAX. Me di cuanta del problema cuando me = hablaron varios usuarios diciendome que ellos habian enviado un correo a = "x" destino y dicho correo no llegaba.=20 Para esto di de alta una cuenta para hacer pruebas, dicha cuenta = tiene los mismos privilegios que los demas usuarios, NETMBX y TMPMBX. , = esta cuenta le puse como username ALMA=20 Cuando me mando un correo con la cuenta de ALMA hacia mi cuenta = personal, el correo nunca me llega, pero en la cola de correos el status = que me indica es de que termino "finished". Deja te muestro como fue.=20 Ok, mira, acabo de mandar un correo con la cuenta de ALMA hacia mi = cuenta y este no ha llegado.=20 $ mail=20 MAIL> send=20 To: rpadilla@ccr.dsi.uanlmx=20 Subj: test=20 Enter your message below. Press CTRL/Z when complete, or CTRL/C to = quit:=20 test=20 Exit=20 Al ver la cola de correos este es el estatus que me indica:=20 225 FINISH 4 MAIL =20 Si quiero ver completamente el estatus de este correo me muestra lo = siguiente:=20 Rpadilla/:> mcp sh queue/full 225=20 Entry: 225, Origin: [Local] =20 Status: FINISHED, size: 4 bytes=20 Created: 15-FEB-1999 08:21:40.64, expires 17-MAR-1999 08:21:40.64=20 Last modified 15-FEB-1999 08:21:46.74=20 Ni siquiera me muesta hacia donde iba ese correo, es decir, el = destinatario...=20 Ahora, he checado los .log que me deja el ROUTER y esto es lo que me = muestran:=20 15-FEB-1999 08:31:53.68 %PROCESS, Processing entry number 225=20 15-FEB-1999 08:31:53.80 %PROCESS, Status from READ_INFO was 00000001 = 15-FEB-1999 08:31:53.80 %PROCESS, Message originated in VMS Mail.=20 15-FEB-1999 08:31:53.80 %PROCESS, will run domain expander on = envelope addresses.=20 15-FEB-1999 08:31:53.80 %PROCESS, will run domain expander on = message headers.=20 15-FEB-1999 08:31:54.34 %PROCESS, Updating the QENT source address.=20 15-FEB-1999 08:31:54.36 %PROCESS, Finished VMSmail-origin = preprocessing.=20 15-FEB-1999 08:31:54.36 %PROCESS, Marking this entry as finished.=20 =20 Yo tengo todos los privilegios y cuando me conecto por telnet a la = VAX y envio correos estos si llegan.=20 Si tienes mas dudas para entender el problema, por favor dime y = tratare de explicarte.....=20 Gracias!..=20 =20 =20 =20 =20 ------=_NextPart_000_001D_01BE5908.F3758BD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

En mi instalación tenemos MX = 5.1 y VMS=20 6.2. Con este software podemos enviar y recibir mensajes indistintamente = desde=20 OUTLOOK EXPRESS y desde VMS-Mail con las siguientes = diferencias;
 
VMS-MAIL         &n= bsp;           =20 usuario=3D=3D>cen800::jlj (nodo-decnet::usuario-vms) o bien=20 MX%"jlj@bancoinversion" (usuario-vms@dominio)
OUTLOOK/EXPRESS     =20 usuario=3D=3D>jlj@bancoinversion (usuario-vms@dominio)
 
Lo que nunca he podido hacer es mandar desde VMS un = mail con=20 el formato user@dominio, ya que sin el prefijo MX% el procesador = VMS-Mail no=20 sabe distribuir el mensaje.
 
Para que MX reconozca si el dominio = es local o=20 no es necesario indicarselo en MCP/PATHS de la siguiente = manera
MCP> show=20 path
 
Domain-to-path mappings:
 =20 Domain=3D"BANCOINVERSION.COM", Path=3DLocal
 =20 Domain=3D"BANCOINVERSION.ES", Path=3DLocal
 =20 Domain=3D"BANCOINVERSION", Path=3DLocal
 =20 Domain=3D"CEN800", Path=3DLocal
  = Domain=3D"pru101",=20 Path=3DLocal
  Domain=3D"SEV011", = Path=3DLocal
 =20 Domain=3D"BAR021", Path=3DLocal
  = Domain=3D"VAL031",=20 Path=3DLocal
  Domain=3D"ZAR051", = Path=3DLocal
  = Domain=3D"*",=20 Path=3DSMTP          &n= bsp;        =20 =3D=3D> Por aqui sales los mensajes no locales
MCP>
 
Otro problema es enviar mail desde OUTLOOK a nodos = VMS que no=20 tienen MX, a través de uno que sí lo tiene. Mediante = rewrite_rule=20 en MCP se pueden rutear los mensajes adecuadamente. Por = ejemplo
 
MCP> show rewrite
Address-rewriting rules:
  Rewrite=20 "<{user}@pru101>" =3D>=20 "<""pru101::{user}""@bancoinversion>"=
 =20 Rewrite "<{user}@sev011>" =3D>=20 "<""sev011::{user}""@bancoinversion>"=
 =20 Rewrite "<{user}@BAR021>" =3D>=20 "<""BAR021::{user}""@bancoinversion>"=
 =20 Rewrite "<{user}@VAL031>" =3D>=20 "<""VAL031::{user}""@bancoinversion>"=
MCP>
-----Mensaje = original-----

De: Roberto = Carlos Padilla=20 Chávez <rpadilla@ccr.dsi.uanl.mx>=
Para:=20 MX-List@MadGoat.com = <MX-List@MadGoat.com>
Fec= ha:=20 lunes 15 de febrero de 1999 15:56
Asunto: Re:=20 Problem...

Gracias Jose Luis.
Bueno, tratare = de=20 explicarte el problema..=20

De un tiempo hacia aca he tenido problemas con las cuentas de los = usiarios que tenemos en una VAX. Me di cuanta del problema cuando me = hablaron varios usuarios diciendome que ellos habian enviado un = correo a=20 "x" destino y dicho correo no llegaba.=20

Para esto di de alta una cuenta para hacer pruebas, dicha cuenta = tiene=20 los mismos privilegios que los demas usuarios, NETMBX y TMPMBX. , = esta=20 cuenta le puse como username ALMA=20

Cuando me mando un correo con la cuenta de ALMA hacia mi cuenta = personal,=20 el correo nunca me llega, pero en la cola de correos el status que = me indica=20 es de que termino "finished". Deja te muestro como fue.=20

Ok, mira, acabo de mandar un correo con la cuenta de ALMA hacia = mi cuenta=20 y este no ha llegado.
$=20 mail=20

MAIL>=20 send
To:     = rpadilla@ccr.dsi.uanlmx=20
Subj:  =20 test
Enter=20 your message below. Press CTRL/Z when complete, or CTRL/C to=20 quit:
test
Exit=20

Al ver la cola de correos este es el estatus que me indica:=20

225=20 FINISH       4 MAIL  =20 <alma@ccr.dsi.uanl.mx>=20

Si quiero ver completamente el estatus de este correo me muestra = lo=20 siguiente:=20

Rpadilla/:> = mcp sh=20 queue/full 225=20

Entry: 225, = Origin: [Local]=20 <alma@ccr.dsi.uanl.mx>
  Status: FINISHED, = size: 4=20 bytes
 =20 Created: 15-FEB-1999 08:21:40.64, expires 17-MAR-1999=20 08:21:40.64
  Last modified 15-FEB-1999 = 08:21:46.74=20

Ni siquiera me muesta hacia donde iba ese correo, es decir, el=20 destinatario...=20

Ahora, he checado los .log que me deja el ROUTER y esto es lo que = me=20 muestran:=20

15-FEB-1999 = 08:31:53.68=20 %PROCESS, Processing entry number 225
15-FEB-1999 08:31:53.80 = %PROCESS,=20 Status from READ_INFO was 00000001
15-FEB-1999 08:31:53.80 = %PROCESS,=20 Message originated in VMS Mail.
15-FEB-1999 08:31:53.80=20 %PROCESS,  will run domain expander on envelope=20 addresses.
15-FEB-1999 08:31:53.80 %PROCESS,  will run domain = expander on=20 message headers.
15-FEB-1999 08:31:54.34 %PROCESS, Updating the QENT source = address.
15-FEB-1999 08:31:54.36 %PROCESS, Finished VMSmail-origin=20 preprocessing.
15-FEB-1999 08:31:54.36 %PROCESS, Marking this entry as=20 finished.
 =20

Yo tengo todos los privilegios y cuando me conecto por telnet a = la VAX y=20 envio correos estos si llegan.=20

Si tienes mas dudas para entender el problema, por favor dime y = tratare=20 de explicarte.....=20

Gracias!..
 
 
 
  =

------=_NextPart_000_001D_01BE5908.F3758BD0-- ================================================================================ Archive-Date: Mon, 15 Feb 1999 09:58:18 -0800 Message-ID: <36C85F68.6083FCD3@ccr.dsi.uanl.mx> Date: Mon, 15 Feb 1999 11:54:48 -0600 From: Roberto Carlos Padilla =?iso-8859-1?Q?Ch=E1vez?= Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@MadGoat.com Subject: Re: Problem... References: <002001be5900$94748990$ed2300c0@tool201> Content-Type: multipart/mixed; boundary="------------40861D4F812D052D4DFA412F" This is a multi-part message in MIME format. --------------40861D4F812D052D4DFA412F Content-Type: multipart/alternative; boundary="------------1F25D234A3174A363B09D8D7" --------------1F25D234A3174A363B09D8D7 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Nosotros tenemos la version 042 del MX y la 6.2 de VMS en la VAX Asi es como estan definidos nuestros path en la vax. mcp show path Domain-to-path mappings: Domain="ccr.dsi.uanl.mx", Path=Local Domain="soporte.uanl.mx", Path=Local Domain="alumnos.uanl.mx", Path=Local Domain="gopher.uanl.mx", Path=Local Domain="club.uanl.mx", Path=Local Domain="soporte", Path=Local Domain="uanl.mx", Path=Local Domain="gopher", Path=Local Domain="club", Path=Local Domain="ccr", Path=Local Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP Desde que yo estoy aqui, no se necesita poner el prefijo MX% para enviar correo por VMS mail... José Luis López Jacob wrote: > En mi instalación tenemos MX 5.1 y VMS 6.2. Con este software podemos > enviar y recibir mensajes indistintamente desde OUTLOOK EXPRESS y > desde VMS-Mail con las siguientes > diferencias; VMS-MAIL usuario==>cen800::jlj > (nodo-decnet::usuario-vms) o bien MX%"jlj@bancoinversion" > (usuario-vms@dominio)OUTLOOK/EXPRESS usuario==>jlj@bancoinversion > (usuario-vms@dominio) Lo que nunca he podido hacer es mandar desde VMS > un mail con el formato user@dominio, ya que sin el prefijo MX% el > procesador VMS-Mail no sabe distribuir el mensaje. Para que MX > reconozca si el dominio es local o no es necesario indicarselo en > MCP/PATHS de la siguiente maneraMCP> show path Domain-to-path > mappings: > Domain="BANCOINVERSION.COM", Path=Local > Domain="BANCOINVERSION.ES", Path=Local > Domain="BANCOINVERSION", Path=Local > Domain="CEN800", Path=Local > Domain="pru101", Path=Local > Domain="SEV011", Path=Local > Domain="BAR021", Path=Local > Domain="VAL031", Path=Local > Domain="ZAR051", Path=Local Domain="*", > Path=SMTP ==> Por aqui sales los mensajes no > localesMCP> Otro problema es enviar mail desde OUTLOOK a nodos VMS que > no tienen MX, a través de uno que sí lo tiene. Mediante rewrite_rule > en MCP se pueden rutear los mensajes adecuadamente. Por ejemplo MCP> > show rewriteAddress-rewriting rules: > Rewrite "<{user}@pru101>" => "<""pru101::{user}""@bancoinversion>" > Rewrite "<{user}@sev011>" => "<""sev011::{user}""@bancoinversion>" > Rewrite "<{user}@BAR021>" => "<""BAR021::{user}""@bancoinversion>" > Rewrite "<{user}@VAL031>" => "<""VAL031::{user}""@bancoinversion>" > MCP> --------------1F25D234A3174A363B09D8D7 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Nosotros tenemos la version 042 del MX y la 6.2 de VMS en la VAX

Asi es como estan definidos nuestros path en la vax.

mcp show path

Domain-to-path mappings:
  Domain="ccr.dsi.uanl.mx", Path=Local
  Domain="soporte.uanl.mx", Path=Local
  Domain="alumnos.uanl.mx", Path=Local
  Domain="gopher.uanl.mx", Path=Local
  Domain="club.uanl.mx", Path=Local
  Domain="soporte", Path=Local
  Domain="uanl.mx", Path=Local
  Domain="gopher", Path=Local
  Domain="club", Path=Local
  Domain="ccr", Path=Local
  Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu"
  Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net"
  Domain="*", Path=SMTP

Desde que yo estoy aqui, no se necesita poner el prefijo MX% para enviar correo por VMS mail...
 

José Luis López Jacob wrote:

 En mi instalación tenemos MX 5.1 y VMS 6.2. Con este software podemos enviar y recibir mensajes indistintamente desde OUTLOOK EXPRESS y desde VMS-Mail con las siguientes diferencias; VMS-MAIL                      usuario==>cen800::jlj (nodo-decnet::usuario-vms) o bien MX%"jlj@bancoinversion" (usuario-vms@dominio)OUTLOOK/EXPRESS      usuario==>jlj@bancoinversion (usuario-vms@dominio) Lo que nunca he podido hacer es mandar desde VMS un mail con el formato user@dominio, ya que sin el prefijo MX% el procesador VMS-Mail no sabe distribuir el mensaje. Para que MX reconozca si el dominio es local o no es necesario indicarselo en MCP/PATHS de la siguiente maneraMCP> show path Domain-to-path mappings:
  Domain="BANCOINVERSION.COM", Path=Local
  Domain="BANCOINVERSION.ES", Path=Local
  Domain="BANCOINVERSION", Path=Local
  Domain="CEN800", Path=Local
  Domain="pru101", Path=Local
  Domain="SEV011", Path=Local
  Domain="BAR021", Path=Local
  Domain="VAL031", Path=Local
  Domain="ZAR051", Path=Local  Domain="*", Path=SMTP                    ==> Por aqui sales los mensajes no localesMCP> Otro problema es enviar mail desde OUTLOOK a nodos VMS que no tienen MX, a través de uno que sí lo tiene. Mediante rewrite_rule en MCP se pueden rutear los mensajes adecuadamente. Por ejemplo MCP> show rewriteAddress-rewriting rules:
  Rewrite "<{user}@pru101>" => "<""pru101::{user}""@bancoinversion>"
  Rewrite "<{user}@sev011>" => "<""sev011::{user}""@bancoinversion>"
  Rewrite "<{user}@BAR021>" => "<""BAR021::{user}""@bancoinversion>"
  Rewrite "<{user}@VAL031>" => "<""VAL031::{user}""@bancoinversion>"
MCP>
--------------1F25D234A3174A363B09D8D7-- --------------40861D4F812D052D4DFA412F Content-Type: text/x-vcard; charset=us-ascii; name="rpadilla.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Roberto Carlos Padilla Chávez Content-Disposition: attachment; filename="rpadilla.vcf" begin:vcard n:Padilla ;Roberto tel;fax:+528 329-40-83 tel;work:+528 329-40-81 x-mozilla-html:TRUE url:http://www.uanl.mx org:U.A.N.L.;Centro de Computo version:2.1 email;internet:rpadilla@ccr.dsi.uanl.mx adr;quoted-printable:;;Pedro de Alba s/n Edif. de Informatica 3er piso=0D=0ACd. Universitaria;San Nicolas de los Garza;Nuevo Leon;66450;Mexico fn:Roberto Carlos Padilla Chavez end:vcard --------------40861D4F812D052D4DFA412F-- ================================================================================ Archive-Date: Mon, 15 Feb 1999 12:23:35 -0800 Message-ID: <36C88187.582DC9CC@csubak.edu> Date: Mon, 15 Feb 1999 12:20:23 -0800 From: "Michael W. Fleming" Reply-To: MX-List@MadGoat.com MIME-Version: 1.0 To: MX-List@MadGoat.com Subject: Unusual Mail Redirecting Question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I sent this to the MX newsgroup a couple of weeks ago but didn't get any response so I thought I would try the official mail list. I'm running MX 4.2 on a VAX 4500, VMS 5.5-2, MultiNet v4.1 rev A, academic.csubak.edu. I have created a dns MX record (mxtest) that points to the above system. I want to be able to take any mail message delivered to any user addressed to mxtest and deliver it all to one user. For example: mail addressed to junk@mxtest.csubak.edu delivered to test@csub.edu mail addressed to home@mxtest.csubak.edu delivered to test@csub.edu etc. I created a rewrite rule thusly: define rewrite "<{user}@mxtest.csubak.edu>" "" However, mail addressed to blah@mxtest.csubak.edu gets a Local deliver error Error-for: blah@academic.csubak.edu Error-code: 3 Error-text: No such local user Note the "academic" in the error message. Obviously my mail is getting to the server, but my rewrite is not working. Where did I go wrong, or is MX unable to do what I want? Thanks. Michael -- Michael W. Fleming, Network Analyst, California State University Voice/mail:(805)664-2118 (24hrs) Fax:(805)664-2099 (24hrs) Disclaimer: I directly represent only myself and my family; indirectly, I represent God and all His creation. ================================================================================ Archive-Date: Mon, 15 Feb 1999 23:26:42 -0800 Sender: najman@HADASSAH.org.IL Date: Tue, 16 Feb 1999 09:24:46 -1300 From: "Najman Kahana. Ext:77313" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D3D16.A80F2AD4.37@HADASSAH.org.IL> Subject: RE: Problem... >Subj: RE: Problem... > >Lo que nunca he podido hacer es mandar desde VMS un mail con el formato = >user@dominio, ya que sin el prefijo MX% el procesador VMS-Mail no sabe = >distribuir el mensaje. Para no tener que entrar el prefijo MX%, hay que definir, ANTES de subir el MX, (define/system mail$internet_transport mx ! default for xx% ) Esta definision le dice al VMS que el transporte as MX quando entra la forma aaa@bbb.ccc > >Para que MX reconozca si el dominio es local o no es necesario = >indicarselo en MCP/PATHS de la siguiente manera >MCP> show path > Najman Kahana Hadassah University Hospital Jerusalem. Israel +--------+------------------+------------------------------+---------------+ ! NAJMAN KAHANA ! Hadassah University Hospital ! thanks, ! ! Najman@hadassah.org.il ! Jerusalem, Israel ! we have our ! ! ! (visit our capital soon) ! own viruses ! +--------+------------------+------------------------------+---------------+ ================================================================================ Archive-Date: Tue, 16 Feb 1999 07:31:37 -0800 Sender: madison@MadGoat.Com Date: Tue, 16 Feb 1999 07:31:31 -0800 From: Matt Madison Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: mfleming@csubak.edu Message-ID: <009D3D06.D65AB36C.1@MadGoat.Com> Subject: RE: Unusual Mail Redirecting Question >I have created a dns MX record (mxtest) that points to the above system. > >I want to be able to take any mail message delivered to any user >addressed to mxtest and deliver it all to one user. > >For example: > mail addressed to junk@mxtest.csubak.edu delivered to test@csub.edu > mail addressed to home@mxtest.csubak.edu delivered to test@csub.edu >etc. > >I created a rewrite rule thusly: > >define rewrite "<{user}@mxtest.csubak.edu>" "" > >However, mail addressed to blah@mxtest.csubak.edu gets a Local deliver >error It sounds like you also added a DEFINE PATH for mxtest.csubak.edu. If so, you should probably remove it. Otherwise, try turning on debug logging in the Router process to see what's going on... perhaps there's an earlier rewrite rule that's getting invoked on the address instead of the one you intend. -Matt -- Matthew Madison | MadGoat Software | PO Box 556, Santa Cruz, CA 95061 USA madison@madgoat.com http://www.madgoat.com ================================================================================ Archive-Date: Tue, 16 Feb 1999 11:21:54 -0800 Reply-To: MX-List@MadGoat.com From: "Richard Wolff" To: Subject: MX SMTP Server dies Date: Tue, 16 Feb 1999 11:26:16 -0800 Message-ID: <000d01be59e2$39505700$41933cc7@rbw.selkirk.bc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Lately our MX SMTP Server dies. [I am running MX 4.2 on VMS 6.1] When I start it from the $ prompt with $ RUN SMTP_SERVER the following message appears after several minutes (5-15 commonly): --------- %STR-F-STRTOOLON, string is too long (greater than 65535) %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC 00026547 00026547 SMTP_SERVER PROCESS_CMD 1251 000011D6 000036D0 SMTP_SERVER SMTP_SERVER 386 0000046C 000020CC 16-FEB-1999 09:46:30.09: MX SMTP Server (pid 00001280) exiting, status = 10248074 -------- I have noticed that there is always a message in the queue which reads 87 INPROG 0 SMTP Of course, the etnry-number is different. I cancel the entry with MCP> QUEUE CANCEL 87 The server runs and then dies (again with an entry similar to the above in the queue). What can I do? Richard Wolff Selkirk College ================================================================================ Archive-Date: Tue, 16 Feb 1999 11:25:51 -0800 Date: Tue, 16 Feb 1999 13:25:34 -0600 From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: RWOLFF@SELKIRK.BC.CA Message-ID: <009D3D38.4C0C5CC4.11@goat.process.com> Subject: RE: MX SMTP Server dies "Richard Wolff" writes: > >Lately our MX SMTP Server dies. >[I am running MX 4.2 on VMS 6.1] >When I start it from the $ prompt with >$ RUN SMTP_SERVER >the following message appears after several minutes (5-15 commonly): >--------- >%STR-F-STRTOOLON, string is too long (greater than 65535) >%TRACE-F-TRACEBACK, symbolic stack dump follows Be sure you're running the SMTP_SERVER.EXE found on ftp.wku.edu in [.MX.MX042.PATCHES]. It corrects this problem. >I have noticed that there is always a message in the queue which reads > 87 INPROG 0 SMTP >Of course, the etnry-number is different. It's a spam message that has hundreds of address on a To: or CC: line. Hunter ------ Hunter Goatley, Process Software, http://www.process.com/ http://www2.wku.edu/hunter/ ================================================================================ Archive-Date: Fri, 26 Feb 1999 06:08:48 -0800 Sender: system@mailgate.spotimage.fr Date: Fri, 26 Feb 1999 12:54:53 GMT From: System Manager Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <009D450F.AAAA81A0.23@spotimage.fr> Subject: unnecessary call to DNS server ? hi, I have the following paths (among other): Domain="mailhub.spotimage.int", Path=SMTP, Route="[172.31.254.3]" Domain="*", Path=SMTP, Route="[194.199.150.1]" but email wait with the following error when my DNS is down. why does MX4.1 need the DNS server as I use IP addresses ? TIA, Pierre. Entry: 11, Origin: [Local] <[concealed_username]@mailgate.spotimage.fr> Status: IN-PROGRESS, size: 2259 bytes Created: 26-FEB-1999 12:11:16.78, expires 28-MAR-1999 12:11:16.78 Last modified 26-FEB-1999 12:17:06.25 SMTP entry #12, status: READY, size: 2259 bytes, waiting for retry until 26-FEB-1999 12:49:06.52 Created: 26-FEB-1999 12:11:18.42, expires 28-MAR-1999 12:11:16.78 Last modified 26-FEB-1999 12:19:06.53 Recipient #1: <[concealed_username]@cnes.fr>, Route=[194.199.150.1] DNS errors=1 Last error: %MX-F-NODNSRESPONSE, no response from DNS server Entry: 13, Origin: [SITE] <[concealed_username]@spotimage.fr> Status: IN-PROGRESS, size: 1447 bytes Created: 26-FEB-1999 12:11:19.72, expires 28-MAR-1999 12:11:19.72 Last modified 26-FEB-1999 12:15:05.85 SMTP entry #14, status: READY, size: 1447 bytes, waiting for retry until 26-FEB-1999 12:47:06.15 Created: 26-FEB-1999 12:11:20.30, expires 28-MAR-1999 12:11:19.72 Last modified 26-FEB-1999 12:17:06.15 Recipient #1: <@mailhub.spotimage.int:[concealed_username]@spotimage.fr>, Route=[172.31.254.3] DNS errors=1 Last error: %MX-F-NODNSRESPONSE, no response from DNS server ================================================================================ Archive-Date: Fri, 26 Feb 1999 06:35:33 -0800 Date: Fri, 26 Feb 1999 10:35:21 -0400 From: Rod Regier Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: rr@dymaxion.ca Message-ID: <009D44FC.2CD05A0E.59@dymaxion.ca> Subject: intermittent FLQ-E-NOSUCHENT I have a report from one of my inhouse users that they have twice in the last week received the following condition (intermittently) when completing an edit session to compose an email message to a MX% addressee. %MAIL-E-SENDERR, error sending to user xxxx@yyy.zzz -FLQ-E-NOSUCHENT, entry number does not exist The originator got their CC of the msg. Config info: DIGITAL TCP/IP Services for OpenVMS VAX Version V4.2 - ECO 1 on a VAXstation 4000-90 running OpenVMS V6.2 MX 5.1 w/selected patches Any ideas, or suggestions of what to look at upon the next occurance? Thanks (I tried to post to the MX-SUPPORT list to which I have been subscribed, but the list software validates on "from", not "MX-REPLY-TO"). -- Rod Regier, Software Development bus: (902)422-1973 x108 Dymaxion Research Ltd., 5515 Cogswell St., fax: (902)421-1267 Halifax, Nova Scotia, B3J 1R2 Canada email: RRegier@dymaxion.ca corporate url: http://www.dymaxion.ca ================================================================================ Archive-Date: Fri, 26 Feb 1999 08:43:10 -0800 Date: Fri, 26 Feb 1999 08:43:00 -0800 (PST) From: Dan Wing Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: Re: unnecessary call to DNS server ? In-Reply-To: <009D450F.AAAA81A0.23@spotimage.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 26 Feb 1999 12:54 +0000, System Manager wrote: I dunno. But why not run a caching-only nameserver on your host so your DNS is never "down" ? -Dan Wing > hi, > > I have the following paths (among other): > > > Domain="mailhub.spotimage.int", Path=SMTP, Route="[172.31.254.3]" > Domain="*", Path=SMTP, Route="[194.199.150.1]" > > > but email wait with the following error when my DNS is down. > why does MX4.1 need the DNS server as I use IP addresses ? > > TIA, > Pierre. > > Entry: 11, Origin: [Local] <[concealed_username]@mailgate.spotimage.fr> > Status: IN-PROGRESS, size: 2259 bytes > Created: 26-FEB-1999 12:11:16.78, expires 28-MAR-1999 12:11:16.78 > Last modified 26-FEB-1999 12:17:06.25 > SMTP entry #12, status: READY, size: 2259 bytes, waiting for retry until 26-FEB-1999 12:49:06.52 > Created: 26-FEB-1999 12:11:18.42, expires 28-MAR-1999 12:11:16.78 > Last modified 26-FEB-1999 12:19:06.53 > Recipient #1: <[concealed_username]@cnes.fr>, Route=[194.199.150.1] > DNS errors=1 > Last error: %MX-F-NODNSRESPONSE, no response from DNS server > > Entry: 13, Origin: [SITE] <[concealed_username]@spotimage.fr> > Status: IN-PROGRESS, size: 1447 bytes > Created: 26-FEB-1999 12:11:19.72, expires 28-MAR-1999 12:11:19.72 > Last modified 26-FEB-1999 12:15:05.85 > SMTP entry #14, status: READY, size: 1447 bytes, waiting for retry until 26-FEB-1999 12:47:06.15 > Created: 26-FEB-1999 12:11:20.30, expires 28-MAR-1999 12:11:19.72 > Last modified 26-FEB-1999 12:17:06.15 > Recipient #1: <@mailhub.spotimage.int:[concealed_username]@spotimage.fr>, Route=[172.31.254.3] > DNS errors=1 > Last error: %MX-F-NODNSRESPONSE, no response from DNS server > >