Archive-Date: Fri, 01 Dec 1995 00:10:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Dec 1995 00:09:31 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@MadGoat.com To: mx-list@WKUVX1.WKU.EDU Message-ID: <0099A309.C0788C1C.258@WKUVX1.WKU.EDU> Subject: MX-LIST Administrivia: Monthly Post Posting statistics for list MX-LIST during November 1995 Total number of posts: 135 Total number of posters: 58 Total number of subscribers: 281 Last modified: 28-SEP-1995 13:33 (Updated digest info) Welcome to MX-List@WKUVX1.WKU.EDU, an electronic mailing list established for the discussion of the Message Exchange mail software. This is a routine posting you will see from time to time on MX-List. MX-List postings are also available in a daily digest format. To subscribe to the digest, send the following command in the body of a mail message to MXserver@WKUVX1.WKU.EDU: SUBSCRIBE MX-List-Digest "Your real name here" The MX-List archives are maintained at ARCHIVES@WKUVX1.WKU.EDU. To get a copy of any month's postings, send an e-mail message with the body SEND MX-List.yyyy-mm to ARCHIVES@WKUVX1.WKU.EDU, where "yyyy" is the year and "mm" is the numeric representation of the month. For example, the message SENDME MX-List.1992-04 will send the archives for April 1992. MX itself is available via anonymous ftp from ftp.spc.edu in [.MX.MX041]. You can also get it via e-mail by sending the commands SEND MX and SEND FILESERV_TOOLS on separate lines in the body of a mail message to FILESERV@WKUVX1.WKU.EDU. To remove yourself from the mailing list, send the following command to MXserver@WKUVX1.WKU.EDU: SIGNOFF MX-List MXserver supports a few other commands for your convenience. The following commands can be handled automatically by the list processor: SIGNOFF MX-List - to remove yourself from the list REVIEW MX-List - to get a list of subscribers QUERY MX-List - to get the status of your entry on the list SET MX-List DIGEST - to switch to digest mode SET MX-List NODIGEST - to switch to non-digest mode SET MX-List NOMAIL - to remain on the list but not receive mail SET MX-List MAIL - to resume receiving mail from the list SET MX-List CONCEAL - to not report your address in a REVIEW SET MX-List NOCONCEAL - to report your address in a REVIEW SET MX-List REPRO - to receive posts you make to MX-List SET MX-List NOREPRO - to not receive posts you make to MX-List LIST - to get a list of mailing lists served by WKUVX1 HELP - to receive a help file By default, subscriptions are set to MAIL, REPRO, NOCONCEAL. If you have any questions, comments, or suggestions about MX-List, please contact the list owner at the address below. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Hunter Goatley, Sr. OpenVMS Systems Programmer goathunter@LOKI.COM The LOKI Group, Inc. P.O. Box 9609 Bowling Green, KY 42102-9609 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ================================================================================ Archive-Date: Fri, 01 Dec 1995 03:13:11 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Dec 1995 10:12:53 +0100 From: Pierre Bru <"tlsax5::system"@spotimage.com> Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU Message-ID: <0099A35E.0A49EA80.3@mailgate.spotimage.com> Subject: quoted-printable not decoded Hi, I've just receive a mail that contains the folowing headers MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable but MX 4.1 did not decoded the message embeded quoted-printable characters. this message is delivered thru SITE path. maybe the double-quotes around the iso-8859-1 ? maybe the SITE path ? Pierre Bru System & Network Mgr. system@spotimage.com ================================================================================ Archive-Date: Fri, 01 Dec 1995 10:08:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Dec 1995 10:07:20 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099A35D.43EE876A.20@ALPHA.WKU.EDU> Subject: RE: quoted-printable not decoded Pierre Bru <"tlsax5::system"@spotimage.com> writes: > >I've just receive a mail that contains the folowing headers > >MIME-Version: 1.0 >Content-Type: text/plain; charset="iso-8859-1" >Content-Transfer-Encoding: quoted-printable > >but MX 4.1 did not decoded the message embeded quoted-printable characters. >this message is delivered thru SITE path. > >maybe the double-quotes around the iso-8859-1 ? >maybe the SITE path ? > Only MX Local decodes quoted-printable. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Fri, 01 Dec 1995 10:21:36 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 1 Dec 1995 17:16:42 +0100 From: "GWDGV1::MOELLER" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: RE: quoted-printable not decoded Pierre Bru <"tlsax5::system"@spotimage.com> asks: > I've just receive a mail that contains the folowing headers > > MIME-Version: 1.0 > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > but MX 4.1 did not decoded the message embeded quoted-printable characters. > this message is delivered thru SITE path. Indeed, it's only MX LOCAL that does the MIME decoding; MX SITE passes the received (SMTP) mail without modification. BTW, it's not obvious what exactly MX SITE _could_ do in this respect, since there are many possible uses for that feature, with differing requirements for the (intermediate) data representation. Even MX LOCAL's decoding of quoted-printable can lead to unexpected results, as the resulting "VMS MAIL" might re-enter the SMTP world due to SET FORWARD, and some SMTP packages (most notably MX itself) won't re-encode the non-ASCII-printable characters on their way out. Wolfgang J. Moeller, Tel. +49 551 2011516 or -510, moeller@gwdgv1.dnet.gwdg.de GWDG, D-37077 Goettingen, F.R.Germany PSI%(0262)45050859008::MOELLER Disclaimer: No claim intended! | moeller@decus.decus.de w.moeller@ieee.org ================================================================================ Archive-Date: Fri, 01 Dec 1995 11:33:58 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Dec 1995 12:34:57 EST From: hone@ouvaxa.cats.ohiou.edu Reply-To: MX-List@MadGoat.com To: mx-list@wkuvx1.wku.edu Message-ID: <0099A371.E341694A.192@ouvaxa.cats.ohiou.edu> Subject: insufficient event flags error We're using MX V4.1 on an alpha and vms cluster. When I show the mx queue there are some LOCAL messages that have errors. Here is an example: $ mcp queue show 648 Entry# Status Size Source Agent Entry# Status Size ------ ------ ------- ------ ------- ------ ------ ------- 648 READY 3240 LOCAL $ mcp queue show/full 648 Entry: 648, Origin: [Local] <> Status: READY, size: 3240 bytes Created: 1-DEC-1995 11:11:46.32, expires 31-DEC-1995 11:11:46.32 Last modified 1-DEC-1995 11:11:47.36 Recipient #1: <123456@ucsu.colorado.edu> %MCP-I-QENTRIES, total matching entries: 1 First of all, is it normal for the Origin address to be blank for the /full display? When I type the msg_text file there is an insufficient event flags error. This message is being rejected by our postmaster. Here is the top of the message: Note: this message was generated automatically. An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: "mrgate::\"ouvax::a1::hone\""@ouvaxa.cats.ohiou.edu Error-Code: 2 Error-Text: Error in delivery to user MRGATE::"OUVAX::A1::HONE" insufficient event flags Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ Received: from ucsu.colorado.edu by ouvaxa.cats.ohiou.edu (MX V4.1 AXP) with SMT P; Fri, 01 Dec 1995 11:11:43 EST Has anyone seen an error like this and any suggestions on how to solve or debug the problem? I'm not sure if the error is referring to All-in-1 (v3.1), message router (v3.3), mx, ucx (v3.3) or what. Don Hone Ohio University P.S. By the way when I send mail from vms to MRGATE::"OUVAX::A1::HONE" the message went through OK. The address is a valid address. ================================================================================ Archive-Date: Fri, 01 Dec 1995 12:05:45 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Dec 1995 12:02:10 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: HONE@OUVAXA.CATS.OHIOU.EDU Message-ID: <0099A36D.4EBB7710.3@ALPHA.WKU.EDU> Subject: RE: insufficient event flags error hone@ouvaxa.cats.ohiou.edu writes: > [...] >Entry: 648, Origin: [Local] <> > Status: READY, size: 3240 bytes > Created: 1-DEC-1995 11:11:46.32, expires 31-DEC-1995 11:11:46.32 > Last modified 1-DEC-1995 11:11:47.36 > Recipient #1: <123456@ucsu.colorado.edu> > >%MCP-I-QENTRIES, total matching entries: 1 > > > First of all, is it normal for the Origin address to be blank for the >/full display? Yes, when the message originates from the local Postmaster (MX Local created the bounce message, so the origin address is "<>"). >When I type the msg_text file there is an insufficient >event flags error. This message is being rejected by our postmaster. >Here is the top of the message: > As far as I can tell, that error appears to come from VMS Mail itself, though I'm not sure why. Everytime I've seen it, MRGATE is involved. I have no idea what it means or how to fix it. >P.S. By the way when I send mail from vms to MRGATE::"OUVAX::A1::HONE" >the message went through OK. The address is a valid address. Then MX *ought* to work too; perhaps you should enable MX Local debugging to see if that provides more info. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Fri, 01 Dec 1995 17:51:09 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: Julio Cesar Gonzalez Pedroza Reply-To: MX-List@MadGoat.com Subject: SMTP_SERVER ERROR....!!! please HELP!!! Date: 1 Dec 1995 16:59:39 GMT Message-ID: <49nc9r$90e@rs1.dsi.uanl.mx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: MX-List@WKUVX1.WKU.EDU Hi! I have a problem with the smtp_server process, all week the process is exiting with this error: %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 000268C3 000268C3 SMTP_SERVER PROCESS_CMD 1243 000011D6 00003697 SMTP_SERVER SMTP_SERVER 378 00000433 00002093 And this happen every 3 min , please help!!!!!!! My suspicion is that POP3 of the Microsoft Exchange is doin it, because the automatic wraping, and the line is don`t finish in the 80 columns !! ================================================================================ Archive-Date: Sat, 02 Dec 1995 13:59:08 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 02 Dec 1995 13:58:49 EST From: Julio Gonzalez Pedroza Reply-To: MX-List@MadGoat.com To: MX-LIST@WKUVX1.WKU.EDU CC: jpedroza@ccr.dsi.uanl.mx Message-ID: <0099A446.C50EC26C.3@ccr.dsi.uanl.mx> Hi! I have a problem with the smtp_server process, all week the process is exiting with this error: %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 000268C3 000268C3 SMTP_SERVER PROCESS_CMD 1243 000011D6 00003697 SMTP_SERVER SMTP_SERVER 378 00000433 00002093 And this happen every 3 min , please help!!!!!!! My suspicion is that POP3 of the Microsoft Exchange is doin it, because the automatic wraping, and the line is don`t finish in the 80 columns !! Please help, this is driving me CRAZY!!! Thanx!! ----------------------------------------------------------------------- Universidad Autonoma de Nuevo Leon Direccion de Informatica Julio Cesar Gonzalez Pedroza Jpedroza@uanl.mx Soporte Tecnico 91(8)329-4081 Ext. 5343 ----------------------------------------------------------------------- ================================================================================ Archive-Date: Sun, 03 Dec 1995 03:20:26 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: SMTP_SERVER ERROR....!!! please HELP!!! Date: 3 Dec 1995 03:50:01 GMT Message-ID: <49r6p9$7ih@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <49nc9r$90e@rs1.dsi.uanl.mx>, Julio Cesar Gonzalez Pedroza writes: =I have a problem with the smtp_server process, all week =the process is exiting with this error: = =%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 = 000268C3 =000268C3 =SMTP_SERVER PROCESS_CMD 1243 000011D6 =00003697 =SMTP_SERVER SMTP_SERVER 378 00000433 =00002093 = = =And this happen every 3 min , please help!!!!!!! = = =My suspicion is that POP3 of the Microsoft Exchange is doin it, =because the automatic wraping, and the line is don`t finish in the =80 columns !! Or it could be that there's somebody out there trying to send a message with a humongous To: line in the headers. The way to find out is to enable debugging for the SMTP_SERVER process (DEFINE/SYS/EXEC MX_SMTP_SERVER_DEBUG *), then look at MX_SMTP_DIR:SMTP_SERVER_LOG.LOG after the SMTP SERVER process dies to see what it was working on when it died. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Sun, 03 Dec 1995 19:48:22 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: wiscott@kickit.pgh.net Reply-To: MX-List@MadGoat.com Subject: ATTENTION SYSTEM ADMINISTRATORS : CANCEL ARTICLES LISTED IN THIS LETTER Date: 4 Dec 1995 01:40:20 GMT Message-ID: <49tji4$hjo@dropit.pgh.net> To: VMSnet-Internals@WKUVX1.WKU.EDU Attension System administrators. I request that you erase the articless entitled: "Make Money Easily. Satisfaction Guaranteed....etc... (0/1) "Make Money Easily. .......(1/1) I acted like a moron for posting this and I do sincerely regret offending anyone. Thank You, Scott ================================================================================ Archive-Date: Mon, 04 Dec 1995 03:46:17 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 04 Dec 1995 10:38:41 +0100 From: "Dr. Richard Glasow, IKP, Univ. Muenster" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099A5BD.24641ADD.12@nwz.uni-muenster.de> Subject: Re: insufficient event flags error > --> Error description: > Error-For: "mrgate::\"ouvax::a1::hone\""@ouvaxa.cats.ohiou.edu > Error-Code: 2 > Error-Text: Error in delivery to user MRGATE::"OUVAX::A1::HONE" > insufficient event flags > We observed the same problem after upgrading OVMS VAX to V6.2, not with ALL-IN-1, which is not installed on our plattform, but "normal" local recipient addresses. It turned out that the problem was connected to recipients having a Pathworks forward like PCSA%node$user, which is used for mail notification on PCs and Macs (Shared Image PCSA_MAILSHR.EXE). We made a call to DEC, who send us some Pathworks patches, but no convincing solution yet ... (call is still open). Our workaround ist to shutdown and restart the MX Local Agent every 15 minutes. Someone out with a better solution ? In a small test scenario we could demonstrate that the problem is NOT directly related to MX: Start the normal VMS MAIL and send >32 mails to a recipient with an above mentioned forward from the "MAIL>"-prompt (do not leave the MAIL program !). Watch it from another process with SHOW PROCESS/CONT). After each sent message you will see flip one event flag after another. After some 32 messages (hard work) you will observe that the "MAIL>" - Prompt comes back without sending the mail and notification of the PC. If you try some other commands within MAIL, you sometimes succeed in getting an "insufficient event flag" error message. After restarting the mail all works fine with the next 32 messages. Now imagine what happens with MX Local ! My feeling is that there is a bug in the VMS MAILSHR.EXE, allocating but never freeing an event flag for each message under some circumstances (PCSA%...). I have no idea about All-In-1, but maybe the MRGATE problem is just another manifestation of the same bug ? Best regards, Richard Glasow Universitaet Muenster Germany ================================================================================ Archive-Date: Mon, 04 Dec 1995 06:18:48 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Reply-To: MX-List@WKUVX1.WKU.EDU Date: Tue, 5 Dec 1995 00:53:04 +1000 To: karen@uni.masey.ac.nz From: karen@uni.masey.ac.nz, feldman@rentwes.org.nz, rjames@otego.ac.nz, hharris@earthlite.co.nz, joshua@atc.co.nz, samuels@uni.masey.ac.nz, chen@rentwest.org.nz, chiu@earthlite.co.nz, wind@atc.co.nz, susans@uni.masey.ac.nz, gregor@rentwes.org.nz, ellen@otego.ac.nz, gfos@earthlite.co.nz, trens@atc.co.nz, jimt@uni.masey.ac.nz, fharile@rentwes.org.nz, relson@otego.ac.nz, jnels@earthlite.co.nz, sarap@atc.co.nz, gspelling@earthlite.co.nz (Association of International Students, Executive Board of Directors, New Zealand Chapter) Subject: ===>> FREE 1 yr. Magazine Sub sent worldwide- 295+ Popular USA Titles -----> NOTE: Please first read my note which appears below the "Request for more info Form." Then, to get more info, just fill out the "Request for More Info" form completely and *FAX* or *SMAIL* it back to the company. You will get a quick reply via email within 1 business day of receipt of the info request form below. IMPORTANT NOTICE FOR THOSE FAXING IN THEIR REPLY: Please make sure you return *only* the below form and *no part* of this message other than the actual form below. If you do not know how to cut and paste the below form onto a fresh clean blank page for faxing, then you may re-type the below form, as long as you copy it line for line *exactly.* This is necessary in order for them to be able to process the tremendous number of replies that they get daily. Your fax goes directly onto their 4.2 gigabyte computer hard drive, not paper, and all incoming fax calls are set-up to be *auto-terminated* if your fax: 1. has a cover page; 2. is more than one page 3. does not begin with the "cut here/begin" line from the below form 4. does not end with the "cut here/end" line from the below form. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ NOTE: Their fax line is open 24 hrs. per day, but due to thousands of inquiries coming in per week from potential new members living overseas, the easiest time to get through is Monday-Friday, 9 am - 5 pm EST (New York Time). If you have trouble getting through to their fax, just drop the below form to them via smail (airmail or first class mail). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *------------cut here/begin-------------------------------------------* REQUEST FOR MORE INFO: please return *only* this section (with no cover page) via 1-page fax to: 718-967-1550 in the USA or via smail (airmail) to: Magazine Club Inquiry Center Att. FREE Catalogue-by-email Dept. PO Box 990 Staten Island NY 10312-0990 Sorry, but incomplete forms *will not* be acknowledged. If you do not have an email address, or access to one, they will not be able to help you until you do have one. If you saw this message, then you should have one. :) Name: Internet email address: Smail home address: City-State-Zip: Country: Work Tel. #: Work Fax #: Home Tel. #: Home Fax #: How did you hear about us (name of person who referred you or the area of the internet that you saw us mentioned in): Referral by Karen Stern. 120495-l Name of USA mags you currently get on the newsstand or in the store: Name of USA mags you currently get on the newsstand or in the store: Name of USA mags you currently get on a subscription basis, through the mail: Name of USA mags you would like price quotes on when we call you: Catalogue format desired (list "1," "2," "3" or "4"): *------------cut here/end--------------------------------------------* Catalogue Format Options: 1. 19-Part email- can be read by EVERYONE (~525 K Total). 2. For more advanced computer users: attached text file ~525K - you must know how to download an attached text file and then be able to open it with your word processor. If in doubt, don't ask for this version. This isn't for internet *newbies.* Better to order option 1 and spend a few minutes pasting them into one whole text document with your word processor, than to waste hours trying to figure how to deal with this option. 3. For more advanced Macintosh computer users: compressed attached text file, created with a Stuffit(tm) self-extracting archive (.sea), ~133K. Can be decompressed by any Macintosh computer user; no special expansion software or knowledge of Stuffit (tm) needed. You just double-click on the file icon and it automatically expands (unstuffs). This is for more advanced mac computer users only, as you still have to know how to deal with an attached file. It will cut your download time by 75%. Expands out to the same ~525K file in option #2. See option #2 for more info on what you will need to be able to do. 4. For expert computer users: compressed attached text file, created with Stuffit(tm), ~114K. Can be decompressed by any computer user who has expansion software to decompress (expand) Stuffit(tm) (.sit) files. This is for more advanced computer users only and will cut your download time by 78%. Expands out to the same ~525K file in option #2. See option #2 for more info on what you will need to be able to do. Hi fellow 'netters, My name is Karen Stern and I recently started using a magazine subscription club in the USA that has a FREE 1 yr. magazine subscription deal with your first paid order- and I have been very pleased with them. They have over 1,500 different USA titles that they can ship to any country on a subscription basis. As for computer magazines from the USA, they more of a selection than I ever knew even existed. They have magazines for most every area of interest in their list of 1,500 titles. Within the USA, for their USA members, they are cheaper than all their competitors and even the publishers themselves. This is their price guarantee. Overseas, on the average, they are generally around one-fourth to one-half of what the newsstands overseas charge locally for USA magazines. On some titles they are as little as one-tenth of what the newsstands charge. They feel that mgazines should not be a luxury overseas. In the USA, people buy magazines and then toss them after reading them for just a few minutes or hours. They are so cheap in the USA! Well, this company would like to make it the same way for their overseas members. They are also cheaper than all their competitors in the USA and overseas, including the publishers themselves! This is their price guarantee. Around one-half their business comes from overseas, so they are very patient with new members who only speak limited English as a 2nd language. Their prices are so cheap because they deal direct with each publisher and cut-out all the middlemen. They will send you their DELUXE EMAIL CATALOGUE (around 525K-big and juicey) !)...if you completely fill out the form above. It has lists of all the freebies, lists of all the titles they sell, titles broken down by categories and detailed descriptions on nearly 1,200 of the titles that they sell. Please do not email me as I am just a happy customer and a *busy* student. I don't have time to even complete my thesis in time, let alone run my part-time software business! Please fill out the above form and carefully follow the intructions above to get it to them via fax or smail. They guarantee to beat all their competitors' prices. Sometimes they are less than half of the next best deal I have been able to find and other times, just a little cheaper - but I have never found a lower rate yet. They assured me that if I ever do, they will beat it. They have been very helpful and helped me with all my address changes as I haved moved from one country to another. They have a deal where you can get a free 1 yr. sub to a new magazine from a special list of over 295 popular titles published in the USA. They will give you this free 1 yr. sub when you place your first paid order with them to a renewal or new subscription to any of the over 1,500 different popular USA titles they sell. They can arrange delivery to virtually any country and I think they have clients in around 45 or 46 countries now. Outside the USA there is a charge for FPH (foreign postage and handling) (on both paid and freebie subs) that varies from magazine to magazine. I have found their staff to be very friendly and courteous. They even helped me with an address change when I moved from one country to another. The owner thinks of his service as a "club" and his clients as "members" (even though there is no extra fee to become a member - your first purchase automatically makes you a member) and he is real picky about who he accepts as a new member. When he sets you up as a new member, he himself calls you personally on the phone to explain how he works his deal, or sometimes he has one of his assistants call. He is kind of quirky sometimes - he insists on setting up new members by phone so he can say hi to everyone (I sure wouldn't want to have his phone bills!), but you can place future orders (after your first order) via E-mail. He has some really friendly young ladies working for him, who seem to know just as much as he does about this magazine stuff. If you live overseas, he will even call you there, as long as you are interested, but I think he still makes all his overseas calls on the weekends, I guess cause the long distance rates are cheaper then. He only likes to take new members from referrals from satisfied existing members and he does virtually no advertising. When I got set-up, they had a 2-3 week waiting list for new members to be called back so that they could join up. (Once you are an existing member, they help you immediately when you call. ) I think they are able to get back to prospective new members the same day or within a few days now, as they have increased their staff. I am not sure about this.........but if you email the above form to them, that is the way to get started! They will send you their DELUXE EMAIL CATALOGUE (around 525K-big and juicey) !)...if you completely fill out the form above. It has lists of all the freebies, lists of all the titles they sell, titles broken down by categories and detailed descriptions on nearly 1,200 of the titles that they sell. They then send you email that outlines how his club works and the list of free choices that you can choose from, as well as the entire list of what he sells; and then they will give you a quick (3-5 minute) friendly, no-pressure no-obligation call to explain everything to you personally and answer all your questions. Once you get in, you'll love them. I do. Sincerely, Karen Stern ps. please forward a copy of this message to all your friends on the net who you think might be interested in it! It is a great deal! If you join and then they join after you, you will earn a free 1 yr. subscription for each new person you get to join after you join! If you exceed 25 referrals, they let you use them to give away as gifts, for Christmas, Chanukah or any other occasion. Please be kind enough to mention my name when you join. I will then get a free magazine for a year for referring you. Thank you. ================================================================================ Archive-Date: Tue, 05 Dec 1995 01:03:41 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 5 Dec 1995 08:01:52 +0100 From: reisacher@goethe.de Reply-To: MX-List@MadGoat.com To: Message-ID: <0099A670.669DDCA0.3@GI011L.GOETHE.DE> Subject: is SITE the only solution ? I'm still working on my problem to modify the outgoing messages. (particularly, I want to change the german characters into its 7-bit readable representation). I have no luck with the SITE-Interface, because if I want catch _all_ outgoing messages it goes looping. I've tried all the suggestions. May be I'm wrong. Please read my last postings. Does anybody know any other way instead of SITE for modifying outgoing messages? I'm very clueless. Georg -------------------------------------------------------------------------------- Georg Reisacher ___ System and Network Management /___ Goethe-Institut e.V. //___ Helene-Weber-Allee 1 ///___ _ D 80637 Muenchen ////___ |_| G o e t h e - I n s t i t u t ----------------------------- ///// PHONE +49 89-15921-399 \\\\\ ___ ///// FAX +49 89-15921-435 \\\\\___///// \\\\\_///// http://www.goethe.de reisacher@goethe.de \\\\ //// ================================================================================ Archive-Date: Tue, 05 Dec 1995 07:34:41 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 5 Dec 1995 12:35:01 +0100 From: "GWDGV1::MOELLER" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Subject: RE: is SITE the only solution ? Georg writes: > I'm still working on my problem to modify the outgoing messages. >[...] > Does anybody know any other way instead of SITE for modifying outgoing > messages? I'm very clueless. It surely is possible to dedicate one machine on a DECnet to handle outgoing mail, and have everybody send Internet Mail via node::"user@domain" This gives a lot of flexibility, for the price of some not altogether trivial programming (never seen such a "custom" MAIL object in public). However, I feel that this approach is still a _lot_ easier than writing a custom mail transport ... ------------------------------------- DECnet node here --->vvvvvv Wolfgang J. Moeller, Tel. +49 551 2011516 or -510, moeller@gwdgv1.dnet.gwdg.de GWDG, D-37077 Goettingen, F.R.Germany PSI%(0262)45050859008::MOELLER Disclaimer: No claim intended! | moeller@decus.decus.de w.moeller@ieee.org ================================================================================ Archive-Date: Tue, 05 Dec 1995 08:29:21 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 5 Dec 1995 08:29:30 -0600 From: mbastien@equitable.ca Reply-To: MX-List@MadGoat.com To: Subject: Re: is SITE the only solution ? Message-ID: <95Dec5.100115cst.39681@gateway.equitable.ca> From: NAME: mbastien To: mx%"MX-List@MadGoat.com"@mrgate >Return-Path: <@gateway.equitable.ca:owner-mx-list@WKUVX1.WKU.EDU> >Received: from equitable.ca (NS) by eqvax5.equitable.ca (MX V4.1 VAX) with > SMTP; Tue, 05 Dec 1995 03:04:23 EST >Received: from WKUVX1.WKU.EDU ([161.6.5.2]) by gateway.equitable.ca with SMTP > id <39681>; Tue, 5 Dec 1995 03:35:41 -0600 >X-ListName: Message Exchange Discussion List >Warnings-To: <> >Errors-To: owner-mx-list@WKUVX1.WKU.EDU >Sender: owner-mx-list@WKUVX1.WKU.EDU >Date: Tue, 5 Dec 1995 01:01:52 -0600 >From: reisacher@goethe.de >Reply-To: MX-List@MadGoat.com >To: >X-Vmsmail-To: GI011L::MX%"MX-List@wkuvx1.wku.edu" >Message-ID: <0099A670.669DDCA0.3@GI011L.GOETHE.DE> >Subject: is SITE the only solution ? > >I'm still working on my problem to modify the outgoing messages. >(particularly, I want to change the german characters into its 7-bit >readable representation). I have no luck with the SITE-Interface, because >if I want catch _all_ outgoing messages it goes looping. I've tried all the >suggestions. May be I'm wrong. Please read my last postings. > >Does anybody know any other way instead of SITE for modifying outgoing >messages? I'm very clueless. > >Georg > The best way to modify all outgoing messages is to use the site interface. This is how we have it set up and it works well... Set up your rewrite rules as follow... 1st. rule - {user}@your.host => {user}@your.host 2nd. rule- {user}@{host}.OUT => {user}@{host} 3rd. rule - {user}@{host} => {user}@{host}.INOUT Set up your paths as follow... 1st. path - "your.host" => local 2nd. path - "*.INOUT" => site 3rd. path - "*" => smtp Now when you send a message to an external location (let's assume user@outside.org) the following will happen... - The third rewrite rule will be used and the address will be changed to user@outside.org.INOUT - The path will be searched next and the 2nd. path will be used. - Your message will be delivered to your SITE interface. - Your SITE interface will make whatever modifications you want as well as change the outgoing address to user@outside.org.OUT - The SITE interface will then drop the message on MX_SITE_IN for processing once more. - Now the second rewrite rule will apply and the address of your message will be changed to user@outside.org - The path will be searched and the message will be delivered to your SMTP interface. Try it out...It works. ...Marc ================================================================================ Archive-Date: Tue, 05 Dec 1995 10:19:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 05 Dec 1995 11:14:37 EST From: "Jonathan E. Hardis" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: reisacher@goethe.de, hardis@garnet.nist.gov Message-ID: <0099A68B.53EDF8E0.16@garnet.nist.gov> Subject: RE: is SITE the only solution ? > I'm still working on my problem to modify the outgoing messages. > I have no luck with the SITE-Interface, because > if I want catch _all_ outgoing messages it goes looping. I've tried all the > suggestions. May be I'm wrong. Please read my last postings. I've read *all* your postings, and since (a) I'm busy, and (b) I've posted this information a number of time, I don't want to repeat myself. I suggest that the problem lies in the way that you are using the SITE interface. Beyond the excellent summary by Marc Bastien, here's the way my configuration looks, stripped to show the essential elements. DEFINE REWRITE_RULE DEFINE REWRITE_RULE where: MailList is a mailing list that I run xxx is a secret password DEFINE PATH "yyy" SITE/ROUTE="MODERATED" DEFINE PATH "mod-in" SITE/ROUTE="MOD-IN" where: yyy is a secret password, which only the moderators know. They send mail to MailList%yyy@garnet.nist.gov. MX_DEVICE:[MX.EXE]SITE_DELIVER.COM looks like: $ SET NOON $ MX_ENTER := $MX_EXE:MX_SITE_IN $ $! Separate processing for different routes $ $ IF P1 .EQS. "FAX" THEN GOTO FAX_Start $ 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 %yyy to -xxx $! $ 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'" $ $! Debugging information (Uncomment to see what's happening) $! $! $ open/write ofile mx_exe:showoff.txt $! $ write ofile p1 $! $ write ofile p2 $! $ write ofile p3 $! $ write ofile p4 $! $ write ofile new_p2 $! $ write ofile new_p3 $! $ close ofile $! $ copy 'p2' mx_exe:file2.txt $! $ copy 'p3' mx_exe:file3.txt $! $ copy 'new_p2' mx_exe:filen2.txt $! $ copy 'new_p3' mx_exe:filen3.txt $ $ 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 "" $ $! (MOD1, MOD2, and MOD3 are files containing the addresses of the $! individual moderators.) $ $ EXIT 1 MX_ROOT:[SITE]CHANGE_P2_MODERATED.DAT looks like: FIND "%yyy@" SUBSTITUTE/%yyy// /NOTYPE FIND "%yyy@" DELETE . EXIT MX_ROOT:[SITE]CHANGE_P3_MODERATED.DAT looks like: SUBSTITUTE/@yyy>/-xxx@GARNET.NIST.GOV>/ WHOLE /NOTYPE EXIT ================================================================================ Archive-Date: Tue, 05 Dec 1995 21:57:04 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: trouble sending SMTP messages Date: 6 Dec 1995 03:49:23 GMT Message-ID: <4a33s3$ldu@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <49fdi9$olr@news1.wolfe.net>, davidf@mossadams.com (David Fabritius) writes: =I have just recently installed MX v4.1 and everything was working great, =but now I'm having trouble sending (but not receiving) SMTP messages. =The log file (included at the end of this message) shows two errors, one =an End of File, the other is unknown. Er, no, it's an MX-specific message: $ WRITE SYS$OUTPUT F$MESSAGE(%X870) %SYSTEM-W-ENDOFFILE, end of file $ SET MESSAGE MX_EXE:MX_MSG $ WRITE SYS$OUTPUT F$MESSAGE(%XC278024) %MX-F-NOHOST, no such host So what this is telling you is that MX was unable to find such a host, and the software it was using to try to find the host returned an end-of-file status when the lookup failed. =If anyone has any hints or tips =for me, I would greatly appreciate it. Sorry if my information is =sadly lacking, but I'm no expert at this...yet. TIA. = =-David = =Here are the details of my system: = =MicroVAX 3100-90 =OpenVMS v5.5-2 =CMU-OpenVMS/IP v6.6-5A =Netlib v2.0 The end-of-file message is one given by CMU IP to indicate that the lookup failed for some reason. I don't remember the specific reason (because the NAMRES process died, perhaps?). -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 06 Dec 1995 05:14:41 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: majordomo@singnet.com.sg Reply-To: MX-List@MadGoat.com Subject: * Free Newsletter on Passion & Romance * Date: 5 Dec 1995 23:43:01 GMT Message-ID: <4a2le5$f34@lantana.singnet.com.sg> To: MX-List@WKUVX1.WKU.EDU =================================================================== Introducing * PassionFRUIT * ... ... =================================================================== First Online Newsletter Dedicated to Passion & Romance ... ... Distributed Fortnightly FREE includes:- - how to meet your dream partner - how to get that all important first date - What to do on dates -- how to make your dates sizzle ... - how to keep your dates coming - how to build a deeper & more intimate relationship - how to make YOU an Attractive person & lots of other love tips 1 SIZZLING love tip per fortnightly issue - delivered to Your Mailbox FREE on 1st & 15th monthly! To subscribe, simply e-mail to majordomo@singnet.com.sg -- In the body/content, type SUBSCRIBE PASSIONFRUIT. It's as simple as that! * Serving the Network Community Since 1980 * ------------------------------------------------------------------- ================================================================================ Archive-Date: Wed, 06 Dec 1995 11:53:56 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <9512061654.AA02287@prodpyr2.us.oracle.com> Date: Wed, 6 Dec 95 08:54:36 PST From: "MFRAZIER.US.ORACLE.COM" Reply-To: MX-List@MadGoat.com To: mx-list@madgoat.com Subject: Re: * Free Newsletter on Passion & Romance * Well, I get so much junk mail already, I'm dropping from this list. I really enjoy the information that is passed around, but I can't take the spamming any longer. If this becomes a private list again, I'll reconsider joining it. For now, I'll monitor it whenever I have the time via a newsreader. Goodbye, and thanks to everyone for the helpful info you have shared. Mike ================================================================================ Archive-Date: Wed, 06 Dec 1995 16:48:04 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Dec 1995 16:38:35 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: MFRAZIER@US.ORACLE.COM Message-ID: <0099A781.C0223C28.67@ALPHA.WKU.EDU> Subject: Re: * Free Newsletter on Passion & Romance * "MFRAZIER.US.ORACLE.COM" writes: > >Well, I get so much junk mail already, I'm dropping from this list. I really >enjoy the information that is passed around, but I can't take the spamming any >longer. > >If this becomes a private list again, I'll reconsider joining it. For now, >I'll monitor it whenever I have the time via a newsreader. > And that's exactly why it can't become a private list---if it's private, people using NEWS won't be able to post to the list. The last time I looked into this, there were *lots* of MX users going through the newsgroup.... Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Wed, 06 Dec 1995 19:43:18 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: insufficient event flags error Date: 7 Dec 1995 01:23:31 GMT Message-ID: <4a5fmj$f8t@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0099A5BD.24641ADD.12@nwz.uni-muenster.de>, "Dr. Richard Glasow, IKP, Univ. Muenster" writes: =My feeling is that there is a bug in the VMS MAILSHR.EXE, allocating but =never freeing an event flag for each message under some circumstances =(PCSA%...). Why do you suspect that rather than PCSA_MAILSHR (or whatever the appropriate shareable image is called) allocating an event flag and not releasing it? -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Thu, 07 Dec 1995 05:37:07 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 07 Dec 1995 11:55:17 +0100 From: "Richard Glasow, IKP, Univ. Muenster" Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU Message-ID: <0099A823.5718749D.70@nwz.uni-muenster.de> Subject: Re: insufficient event flags error > In article <0099A5BD.24641ADD.12@nwz.uni-muenster.de>, "Dr. Richard Glasow, IKP, Univ. Muenster" writes: > =My feeling is that there is a bug in the VMS MAILSHR.EXE, allocating but > =never freeing an event flag for each message under some circumstances > =(PCSA%...). > > Why do you suspect that rather than PCSA_MAILSHR (or whatever the appropriate > shareable image is called) allocating an event flag and not releasing it? > -------------------------------------------------------------------------------- > Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL > It is an educated guess only. The reasons: 1. The problems with 'MX Local' started after VMS upgrade from V6.1 to V6.2 . The images of PCSA_MAILSHR (and its companion NETBIOSSHR) as a layered product did not change, but MAILSHR.EXE did. 2. DEC released an ECO of Pathworks (PWRKV50C_E3050) and claimed (at least to me) that the problem should be solved. Though the Image IDs really changed, the problem remained. By the way, I tried a lot of other versions of the Pathworks Shared Images with no effect. No proof, of course, but at least a small hint... Richard Glasow Universitaet Muenster Germany ================================================================================ Archive-Date: Thu, 07 Dec 1995 15:09:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 07 Dec 1995 15:08:38 CDT From: Curtis Williams Reply-To: MX-List@MadGoat.com To: MX-LIST@WKU.EDU Message-ID: <0099A83E.59D31A88.1254@WKUVX1.WKU.EDU> subscribe Curtis Williams ================================================================================ Archive-Date: Sat, 09 Dec 1995 10:41:00 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 9 Dec 1995 10:40:17 -0600 (CST) Message-ID: <199512091640.KAA27051@sound.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: mx-list@wkuvx1.wku.edu From: Doug Ledbetter Reply-To: MX-List@MadGoat.com Subject: SMTP process won't run. Hello, We have been using the MX package for over a year now with absolutely no problems until a few weeks ago. After a system restart, I noticed that the Internet-bound messages were not leaving the campus. After further study, I noticed that the SMTP process was not running. After I re-started the whole MX package, the SMTP process died immediately after it started. The log file shows: 8-DEC-1995 21:45:22.54: MX SMTP (pid 20200189) starting This is the ONLY thing in the STMP log file eventhough the process died right after it was created. I've done a brief check of the MX configuration, and everything looks fine. I can't figure out what the problem is. Any suggestions would be appreciated, as we have over 300 messages waiting in the queue since Dec 5. The system is a MicroVax 3100 running VMS 5.5-2 and DEC TCP/IP (UCX) 3.3, MX version 4.1. Thanks, -dougl Doug Ledbetter -The Mad {Computer} Scientist PC/Mac/Internet Support @ MidAmerica Nazarene College (913) 782-3750 x417 dougl@oz.manc.edu ================================================================================ Archive-Date: Sat, 09 Dec 1995 11:25:29 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 09 Dec 1995 11:25:11 CST From: Dave Miller Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099A9B1.774F27E1.3@BEAVER.Bemidji.MSUS.edu> Subject: RE: SMTP process won't run. > After further study, I noticed that the SMTP process was not > running. After I re-started the whole MX package, the SMTP process died > immediately after it started. The log file shows: > > 8-DEC-1995 21:45:22.54: MX SMTP (pid 20200189) starting If you have disk quota enabled, you might check SYSTEM's quota. //----------\|/------\\ Dave Miller. || /\ -X- || Professor, Computer Science. || / \ /|/\ || || / \ / \ || SYSTEM@BEAVER.Bemidji.MSUS.EDU || / \ \ || || /________\____\ || 1500 Birchmont Dr. NE || || || || Bemidji State University \\------|| -------// Bemidji MN, 56601 ================================================================================ Archive-Date: Sat, 09 Dec 1995 15:19:21 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 09 Dec 1995 16:19:04 EST From: Scott McNeilly Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@MadGoat.com Message-ID: <0099A9DA.8580B620.50@fred.bridgew.edu> Subject: RE: SMTP process won't run. Doug Ledbetter writes: >Hello, > We have been using the MX package for over a year now with >absolutely no problems until a few weeks ago. After a system restart, I >noticed that the Internet-bound messages were not leaving the campus. > > After further study, I noticed that the SMTP process was not >running. After I re-started the whole MX package, the SMTP process died >immediately after it started. The log file shows: > > 8-DEC-1995 21:45:22.54: MX SMTP (pid 20200189) starting > >This is the ONLY thing in the STMP log file eventhough the process died >right after it was created. Try enabling the debug log. $ DEFINE/SYSTEM/EXEC MX_SMTP_DEBUG "TRUE". Start MX again. Then check [MX.SMTP]MX_SMTP_LOG.LOG. This may provide more information. -------------------------------------------------------------------- Scott Mc Neilly email: smcneilly@bridgew.edu Assistant Director Phone: 508-697-1236 Information Services Bridgewater State College Bridgewater, MA 02325 --------------------------------------------------------------------- ================================================================================ Archive-Date: Mon, 11 Dec 1995 11:49:33 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 11 Dec 1995 12:47:01 EST From: Brian Reed Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@MadGoat.com Message-ID: <0099AB4F.3ABB5A9D.3@cbict3.cb.att.com> Subject: Router in loop I got my first rejection message from a fileserv request, and was sent to fileserv-MGR@cbict3.cb.att.com I had set up the fileserv with the manager as fileserv-MGR@cbict3.cb.att.com and found out the router was eating up the CPU. I thought maybe the queue was corrupted, but no. I then changed the fileserv manager to REED, and everything was fine. Then I realized what had happened--the message came in, fileserv says to send it to fileserv-MGR, so it re-routed the message. But that's a special name, so it was intercepted, and then started over. It got stuck in a loop, essentially re-routing the message to itself. That may not be best techincal explanation, but seems to be what happened. Of course I realize what happened now, and the error, so this is more of a note of to the developers, of maybe a situation to check for. I suppose on the grand scale, you'd set it such that the router, or any agent, only handles a message n number of times, then drop it. Not reject the message, as then you could end up in a loop trying to reject it, so marking it as a "dead" message would be safest. Then it could be noticed with the MCP commands. Speaking of which, is there a way to run some MCP command, and only getting info for problems? I've got a program that runs every hour, and if there is a "problem" it writes out the problem, and a window pops up on my screen. Otherwise, no output, no window, so I only see the window when there is something to deal with. I haven't yet figured out how to do an MCP command, so I only get output if messages are stuck, something's not running, etc. Just some comments and feedback. Otherwise working just great. Brian D. Reed AT&T Columbus Works Brian.D.Reed@att.com 614-860-6218 ================================================================================ Archive-Date: Mon, 11 Dec 1995 21:13:11 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: jnb@wiswes Reply-To: MX-List@MadGoat.com Subject: RE: SMTP process won't run. Date: 11 Dec 95 20:36:29 -0600 Message-ID: <1995Dec11.203629@wiswes> To: MX-List@WKUVX1.WKU.EDU In article <0099A9DA.8580B620.50@fred.bridgew.edu>, Scott McNeilly writes: > > Try enabling the debug log. > $ DEFINE/SYSTEM/EXEC MX_SMTP_DEBUG "TRUE". > Start MX again. Then check [MX.SMTP]MX_SMTP_LOG.LOG. > This may provide more information. > We did this for our cluster, with the pleasant but unenlightening result that the SMTP process no longer dies. We set the directory to allow at most 5 files, and waited. After several months everything still looks normal. Our cluster is served by a pair of DSSI-connected VAXen, each running MX, and an Alpha also running MX (referencing the VAX's SYSUAF). The faster of the VAXen is the one where SMTP used to die. James Bellinger jnb@wishep.physics.wisc.edu ================================================================================ Archive-Date: Mon, 11 Dec 1995 21:54:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Dec 1995 14:52:01 +1000 From: Powell HEUER Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@madgoat.com CC: powell@syd.dwt.csiro.au Message-ID: <0099AC29.DB92D4C0.3@syd.dwt.CSIRO.AU> Subject: MX-List-digest I recently returned from some extended sick leave and realised that the Digest form of MX-List no longer seems to exist. Hunter's monthly Administrivia for MX-List still refers to it but MXSERVER@madgoat.com doesn't list it as a known list. Did I miss something? Regards Powell Heuer --------------------------------------------------------------------- Powell Heuer E-Mail: P.Heuer@syd.dwt.csiro.au CSIRO Division of Wool Technology Phone : +61 2 809 9444 PO Box 7 Fax : +61 2 809 9476 Ryde NSW 2112 AUSTRALIA ================================================================================ Archive-Date: Tue, 12 Dec 1995 07:45:26 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Dec 1995 07:44:01 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU CC: POWELL@SYD.DWT.CSIRO.AU Message-ID: <0099ABEE.110E5C46.31@ALPHA.WKU.EDU> Subject: RE: MX-List-digest Powell HEUER writes: > >I recently returned from some extended sick leave and realised that the Digest >form of MX-List no longer seems to exist. Hunter's monthly Administrivia for >MX-List still refers to it but MXSERVER@madgoat.com doesn't list it as a known >list. > Yeah, I need to change that back to MXSERVER@WKUVX1.WKU.EDU. The digest is still there, you just subscribe to it differently now. Send the following commands in the body of a mail message to : SUBSCRIBE MX-List "Your real name here" SET MX-List DIGEST Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Tue, 12 Dec 1995 08:59:23 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: SYSTEM@UHAVAX.HARTFORD.EDU (SYSTEM MANAGER) Reply-To: MX-List@MadGoat.com Subject: Re: SMTP process won't run. Date: 12 Dec 1995 14:21:02 GMT Message-ID: <4ak34e$g4g@ipgate.hartford.edu> To: MX-List@WKUVX1.WKU.EDU In <199512091640.KAA27051@sound.net> dougl@oz.manc.edu writes: > Hello, . . . > After further study, I noticed that the SMTP process was not > running. After I re-started the whole MX package, the SMTP process died > immediately after it started. The log file shows: . . . > The system is a MicroVax 3100 running VMS 5.5-2 and DEC TCP/IP (UCX) > 3.3, MX version 4.1. This type of things happens to me too, although, usually with the inbound SMTP SERVER process. Trying to restart it doesn't work. I usually end up shutting down all IP-dependent software, and then shutting down UCX and restarting it. Then re-starting MX seems to work ok until days, weeks, or months later until I have to do it again. Short term solution: shutdown and restart UCX Long term: ??? Dave Kelley University of Hartford ================================================================================ Archive-Date: Tue, 12 Dec 1995 11:57:15 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: From: Michael Slattery Reply-To: MX-List@MadGoat.com Subject: Re: SMTP process won't run. Date: Tue, 12 Dec 1995 11:56:54 CDT At 12:45 PM 12/12/95, you wrote: > >This type of things happens to me too, although, usually with the inbound SMTP >SERVER process. Trying to restart it doesn't work. I usually end up shutting >down all IP-dependent software, and then shutting down UCX and restarting it. >Then re-starting MX seems to work ok until days, weeks, or months later until >I have to do it again. > > Short term solution: shutdown and restart UCX > Long term: ??? > >Dave Kelley >University of Hartford I also have a ? concering the MX SMTP Server shutting down. It seems that due to our high volume of mail. approx 600 mail accounts.. Actual mail processing ???? Definetly four or more digits.... :) Every couple of months we need to clean out the mail queue files to get rid of the messages that are not vaild or are unsendable for whatever reason. Does anyone have another fix for this .. This is an DEC Alpha AXP 3000 Mod 400 running MX Ver 3.3... P.s - I'm new to this system and to system admin so any suggestions are welcome. Please feel free to email me individually. Michael J. Slattery Computer Technican / Part Time Professional Monroe Community College Rochester, NY ================================================================================ Archive-Date: Thu, 14 Dec 1995 16:44:11 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 14 Dec 1995 13:11:05 EST From: Simeon Broughton Reply-To: MX-List@MadGoat.com To: MX-LIST@WKUVX1.WKU.EDU CC: broughton@NICAD3.NIC.BC.CA Message-ID: <0099ADAE.17320840.362@NICAD3.NIC.BC.CA> Subject: My system_queue.fdl_ctl is broken My MX started behaving very strangely this morning. Users were getting RMS errors with mail. Finally tracked it down to the system_queue.fdl_ctl which ANAL/RMS produced the following error: *** VBN 5734: Index bucket references missing data bucket with VBN 5668. Unrecoverable error encountered in structure of file. I created a new file and restarted MX and everything is working ok, except I have about 100 undelivered mail messages that MCP QUEUE knows nothing about. Is there any way to reinsert these into the queue file so they will get delivered? Sim. Simeon Broughton, Manager, Computer Services. (604)334-5254 North Island College, 2300 Ryan Road, Courtenay, B.C. V9N 8N6. CANADA broughton@nic.bc.ca ================================================================================ Archive-Date: Fri, 15 Dec 1995 07:14:52 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 07:14:42 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099AE45.7818D59D.3@ALPHA.WKU.EDU> Subject: RE: My system_queue.fdl_ctl is broken Simeon Broughton writes: > >My MX started behaving very strangely this morning. Users were >getting RMS errors with mail. Finally tracked it down to the >system_queue.fdl_ctl which ANAL/RMS produced the following error: > >*** VBN 5734: Index bucket references missing data bucket with VBN 5668. >Unrecoverable error encountered in structure of file. > You're running a pretty old version of MX.... >I created a new file and restarted MX and everything is working >ok, except I have about 100 undelivered mail messages that MCP >QUEUE knows nothing about. Is there any way to reinsert these >into the queue file so they will get delivered? > The REFEED package may work with that version, I don't know. You can find it on ftp.wku.edu in [.MX.CONTRIB]MX_REFEED.ZIP. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Fri, 15 Dec 1995 10:16:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 10:15:13 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU CC: MadGoat-Announce@MadGoat.com Message-ID: <0099AE5E.AFD46E20.16@ALPHA.WKU.EDU> Subject: MX V4.2 is now available!! MadGoat Software announces the release of Message Exchange (MX) V4.2. My time for MX has been pretty short since V4.1 was released in June 1994. Still, I was able to make some time in the past few weeks to fix some of the more major problems and add a few enhancements, particularly to the MX MLF server. The enhancement and bug fix sections from the release notes are included below my sig. The major bugs fixed include a bug that caused queue corruption with MCP QUEUE COMPRESS and a bug that would cause various agents to die if you MCP QUEUE CANCELed an entry that was in-progress. For those of you hoping to see a lot more fixed and added in this release, I apologize, but I was surprised that I was able to get as much in as I did. ---------------------------------------- You can get MX V4.2 via: WWW: http://www.wku.edu/www/madgoat/mx.html ftp://ftp.wku.edu/mx/mx042/mx042.zip Anonymous FTP: ftp.wku.edu in [.MX.MX042] ftp.spc.edu in [.MX.MX042] ftp.csus.edu in /pub/mx E-mail: Send the command SEND MX in the body of a mail message to . NOTE: MX will be returned to you in 74 180-block files! Do not order it unless you can't get it via any other method! ---------------------------------------- Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ 3 New Features and Changes in MX V4.2 This chapter notes the new features added to MX V4.2. __________________________________________________________________ 3.1 NETLIB V2.0I MadGoat Software's NETLIB V2.0I is included with MX V4.2. NETLIB V2.0I is a C rewrite of the original NETLIB V1.x routines. Thanks to Matt Madison. __________________________________________________________________ 3.2 MCP Enhancements o The MCP commands SHUTDOWN, RESET, and STATUS now accept a /NODE qualifier to limit the affect of the commands to those agents running on specific nodes. o The DEFINE LIST and MODIFY LIST commands now accept a /DIGEST qualifier. o The MCP commands DEFINE LIST and DEFINE FILE_SERVER now check for the existence of a file server or list, respectively, with the same name as the supplied list or file server name. In previous versions of MX, it was possible to define a file server and a list with the same name, but mail would always be routed to the file server, without warning. __________________________________________________________________ 3.3 MX MLF Enhancements and Changes o MX MLF was modified to support a new DENY flag for subscribers. The DENY flag can be used to add a subscriber to a closed mailing list (one which does not allow WORLD writes) and still prevent that subscriber from posting to the list, thus denying the subscriber access to the list. Subscribers with the DENY flag set cannot post to the list, will not receive posts to the list, cannot change their subscriber entry, and cannot remove themselves from the list. The MX MLF ADD command supports the /DENY and /NODENY qualifiers. o The MX MLF REMOVE command now supports /NOCASE. o The MX MLF processor now adds a Date: header to mailing list posts without one. This was necessary because some SMTP servers reject messages without a Date: header. o A check was added to the MX MLF processor to detect messages from automated mail daemons. Messages from "Postmaster," "Mailer-Daemon," "uucp," "mmdf," "UCX_ SMTP," "LISTSERV," and "MXserver" are no longer processed by the MX MLF processor. This enhancement was added to prevent mail loops created when an automated mailer sends bounce messages to a mailing list or to the list processor itself. o Support for mailing lists digests was added to MX MLF. This involved adding: o /DIGEST qualifier to MCP DEFINE/MODIFY LIST commands. o Recognition of listname-DIGEST addresses. o SET DIGEST commands for MXserver and -request addresses. o /DIGEST qualifier to MX MLF ADD command. o Automatic list forwarding for -digest address. Only a system user or a list owner can post a message to a list-DIGEST address. A message sent to list-DIGEST from any other user is treated as a post to the regular list (which will eventually end up in the daily digest). Note: The MX-DIGEST files are still required. __________________________________________________________________ 3.4 MX SMTP Server Enhancements o By default, the MX SMTP Server listens for incoming connections on port 25. You can now specify a different TCP/IP port by defining the logical MX_ SMTP_PORT. For example, to make the MX SMTP Server listen for connections on port 1025, execute the following command before starting the MX SMTP Server: $ define/system/exec mx_smtp_port 1025 __________________________________________________________________ 3.5 Miscellaneous Enhancements o Error-handling logic in the various MX agents has been enhanced in this version of MX. o The MX Router was modified to perform site-specific header rewrites for all messages, regardless of origin. This was needed to allow site-specific aliases for messages coming from such sources as Eudora (using the ADDRESS_REWRITER feature). o MX now supports the UCX$TZ logical, which was added to Digital TCP/IP Services for OpenVMS V3.2. o The following [CONTRIB] packages have been updated or added: o MX-DIGEST.ZIP-Provides digest support for MX mailing lists. o MX_REFEED.ZIP-Provides a means by which entries can be reentered into the MX queue. o MX_WATCHDOG.COM-A command procedure that will help ensure that all MX processes are running. _______________________________________________________ 4 Bug Fixes MX V4.2 provides the following fixes to bugs in V4.0: o Fixed bug in MX_START.COM that prevented some log file names from including node names. o Fixed a bug in MCP QUEUE COMPRESS that could cause queue corruption. o Modified the behavior of the MCP command QUEUE PURGE so that ROUTER entries are purged after all non- ROUTER entries. Previous versions of MX deleted entries sequentially. If the PURGE process was interrupted for some reason, agent entries that referenced purged router entries could be left behind, causing confusing QUEUE SHOW displays and other problems. (This same modification was also made to the MX Router and MX FLQ Manager images.) o Fixed a couple of bugs introduced in MX V4.1 that occasionally caused the various agents to die with access violations while attempting to update entry information. MX SMTP processes were especially prone to this problem. [End of announcement] ================================================================================ Archive-Date: Fri, 15 Dec 1995 11:17:18 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 18:16:13 +0100 From: Richard Levitte - GNU on VMS hacker Reply-To: MX-List@MadGoat.com To: mx-list@wkuvx1.wku.edu Message-ID: <0099AEA1.E1E2D8B7.14@e.kth.se> Subject: Eudora with MX SMTP-server I know a few people who have some problems sending mail with Eudora (Windows Eudora version 2.1, I think) through MX 4.1 SMTP server. What happens is the following (according to MX_SMTP_SERVER_LOG.LOG): STM[8]: Send "220 sofi.sofi.su.se MX V4.1 VAX SMTP server ready at Thu, 14 Dec 1995 14:40:45 EST" STM[8]: Receive "HELO " STM[8]: Send "501 Syntax is HELO " STM[8]: Receive "QUIT" STM[8]: Send "221 sofi.sofi.su.se Service closing transmission channel." STM[8]: Error: status=20EC Now, I know that the HELO above *is* wrong, but I can't find a way to make Eudora do anything else. I'd like to ask you if there is some kind of workaround, either by making MX more sloopy (I don't like it, but I would prefer MX instead of UCX SMTP by far), or by making Eudora behave. Anyone? TIA -- +--------------------------------------------------------------------+ ! Richard Levitte, GNU on VMS hacker ! tel: +46-8-26 52 47 ! ! Spannvägen 38, I ! fax: none for the moment ! ! S-161 43 Bromma ! Internet: levitte@e.kth.se ! ! SWEDEN ! ! +-GNUish VMS-+ ================================================================================ Archive-Date: Fri, 15 Dec 1995 12:18:40 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 13:18:16 EST From: "Jonathan E. Hardis" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: hardis@garnet.nist.gov Message-ID: <0099AE78.420717C0.8@garnet.nist.gov> Subject: RE: MX V4.2 is now available!! > MadGoat Software announces the release of Message Exchange (MX) V4.2. Wonderful! Thanks a lot! > o MX MLF was modified to support a new DENY flag > for subscribers. The DENY flag can be used to add > a subscriber to a closed mailing list (one which > does not allow WORLD writes) and still prevent that > subscriber from posting to the list, thus denying > the subscriber access to the list. Subscribers with > the DENY flag set cannot post to the list, will > not receive posts to the list, cannot change their > subscriber entry, and cannot remove themselves from > the list. "...will not recieve posts to the list..." ?? I don't understand. If the list is already closed, the /DENYed already can't post to the list, won't receive posts to the list, etc. - Jonathan ================================================================================ Archive-Date: Fri, 15 Dec 1995 12:23:30 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 12:22:48 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099AE70.827AC737.5@ALPHA.WKU.EDU> Subject: RE: MX V4.2 is now available!! "Jonathan E. Hardis" writes: > >> o MX MLF was modified to support a new DENY flag >> for subscribers. The DENY flag can be used to add [...] > >"...will not recieve posts to the list..." ?? I don't understand. > >If the list is already closed, the /DENYed already can't post to the list, >won't receive posts to the list, etc. > "A closed list" wasn't a good choice of words; I'm talking about a list that's open to subscriptions from anyone, but posts are restricted to subscribers (so the protection is (G:W,W:E)). Most of my lists are like this now to cut down on spams. Only subscribers can post, but anyone can subscribe. Most spammers won't bother subscribing to the list just to post to it. This flag is to be used in the case where you have a problem subscriber who refuses to play by the rules---in order to keep him from subscribing to the list, you add him with the /DENY flag and the person is added to the list, but he can't do anything on the list. Does that make sense? Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Fri, 15 Dec 1995 12:27:10 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 12:27:09 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099AE71.1DF08CBA.54@uwwvax.uww.edu> Subject: RE: Eudora with MX SMTP-server => I know a few people who have some problems sending mail with Eudora (Windows => Eudora version 2.1, I think) through MX 4.1 SMTP server. What happens is the => following (according to MX_SMTP_SERVER_LOG.LOG): => => STM[8]: Send "220 sofi.sofi.su.se MX V4.1 VAX SMTP server ready at Thu, 14 Dec 1995 14:40:45 EST" => STM[8]: Receive "HELO " => STM[8]: Send "501 Syntax is HELO " => STM[8]: Receive "QUIT" => STM[8]: Send "221 sofi.sofi.su.se Service closing transmission channel." => STM[8]: Error: status=20EC => => => Now, I know that the HELO above *is* wrong, but I can't find a way to make => Eudora do anything else. => => I'd like to ask you if there is some kind of workaround, either by making => MX more sloopy (I don't like it, but I would prefer MX instead of UCX SMTP => by far), or by making Eudora behave. Have you set the smtp_servers threads greater than the default of 4? This looks like the same problem we solved by doing so. Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Fri, 15 Dec 1995 13:41:09 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 19:38:58 GMT From: Andy Harper - KCL Systems manager Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: A.HARPER@kcl.ac.uk Message-ID: <0099AEAD.71473C97.19@alder.cc.kcl.ac.uk> Subject: RE: Eudora with MX SMTP-server => STM[8]: Send "220 sofi.sofi.su.se MX V4.1 VAX SMTP server ready at Thu, 14 Dec 1995 14:40:45 EST" => STM[8]: Receive "HELO " => STM[8]: Send "501 Syntax is HELO " => STM[8]: Receive "QUIT" => STM[8]: Send "221 sofi.sofi.su.se Service closing transmission channel." => STM[8]: Error: status=20EC => => => Now, I know that the HELO above *is* wrong, but I can't find a way to make => Eudora do anything else. => You dont say what type of system you are on but I've find that this problem occurs when the eudora software cannot determine it's own host name from the underlying TCP stack. For instance, using microsoft TCP, you can configure in the host name to be used. With trumpet winsock you cannot, so it must do a DNS lookup on its own address. it is therefore ESSENTIAL that your IP address be registered in the DNS with a suitable domain name. Do this even if using a TCP stack that allows you to configure the name - the other end of the transaction still needs to look you up. So, if you don't do this, eudora cannot pick up the name and sends a null string down after HELO. MX gets confused by this, as do other SMTP servers (not surprising really - its illegal syntax). Andy Harper Kings College Lodnon ================================================================================ Archive-Date: Fri, 15 Dec 1995 14:15:35 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 20:14:59 GMT From: Tim Llewellyn Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@madgoat.com CC: tjl@siva.bris.ac.uk Message-ID: <0099AEB2.78F22F65.20@siva.bris.ac.uk> Subject: MX Local dies frequently with status=1C08804C Hello MX poeple, Yesterday our MX local process started exiting frequently (several times per hour). In the logfile we see: $ ty mx_local_dir:mx_local_.log;-1 15-DEC-1995 19:22:17.23: MX Local (pid 24000339) starting 15-DEC-1995 19:38:06.14: MX Local (pid 24000339) exiting, status = 1C08804C I turned on debugging for MX local, and from the MX_LOCAL_DIR:MX_LOCAL_LOG.LOG I discovered the exiting of the process is correlated with a logfile containing just one line, for example: 16:35:33.76 Processing queue entry number 21 I tried the usual tricks to get a handle on status=1C08804C (set every message file in SYS$MESSAGE, see what F$MESSAGE reports) but always get noname-f-nomsg. I've written a "daemon" process to check for MX Local every 5 minutes and restart it if not running, so at least incoming mail still works. This is on OpenVMS VAX 6.1, MX 4.1, UCX 3.2. A couple of nodes in our cluster are already running VMS 6.2 and UCX 3.3, we hope to move the rest next week. We have occasionally had problems with MX Local dying, but never as frequently as this. The s/w hasn't changed on the node running MX Local for several months. Has anyone got any ideas about what is happening, or how to investigate further? I'd be most grateful if you have. Also, can I be sure we are not loosing mail when the MX Local process exits? I'm on the digest mode for the list at present so if you could CC any replies to me (tjl@siva.bris.ac.uk) I'd appreciate that too. Thanks Tim Ll. -- "When I play my guitar people they just dance." Soukous Tim Llewellyn, Physicist Programmer, Bristol Uni Particle Physics. Makossa HEPNET/SPAN 19716::TJL Internet tjl@siva.bris.ac.uk Soca Soukous, OpenVMS and cricket addict. Eats NO animal products. Hilife Read at your own risk, standard disclaimer applies. Zouk http://juno.phy.bris.ac.uk/~tjl/ (New pictures too nov 95) Mbalax - ================================================================================ Archive-Date: Fri, 15 Dec 1995 14:21:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Dec 1995 14:20:43 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU CC: TJL@SIVA.BRIS.AC.UK Message-ID: <0099AE80.FBBB9E4A.8@ALPHA.WKU.EDU> Subject: RE: MX Local dies frequently with status=1C08804C Tim Llewellyn writes: > >Yesterday our MX local process started exiting frequently (several times >per hour). In the logfile we see: > >$ ty mx_local_dir:mx_local_.log;-1 >15-DEC-1995 19:22:17.23: MX Local (pid 24000339) starting >15-DEC-1995 19:38:06.14: MX Local (pid 24000339) exiting, status = 1C08804C > That's an FLQ error, but it doesn't match any of the current FLQ statuses, which has me slightly puzzled. >I turned on debugging for MX local, and from the MX_LOCAL_DIR:MX_LOCAL_LOG.LOG >I discovered the exiting of the process is correlated with a logfile containing >just one line, for example: > >16:35:33.76 Processing queue entry number 21 > My guess is that you've either got a corrupted queue, or that you may be missing some of the files for that entry. Be sure you're not having problems creating files on that disk in the MX directories, etc. Oh, and this is the kind of thing that has been enhanced some in MX V4.2. >Has anyone got any ideas about what is happening, or how to investigate >further? I'd be most grateful if you have. Also, can I be sure we are not >loosing mail when the MX Local process exits? > The entries should be left marked INPROGRESS. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Fri, 15 Dec 1995 16:59:20 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: My system_queue.fdl_ctl is broken Date: 15 Dec 1995 22:53:18 GMT Message-ID: <4asu8u$mg5@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0099ADAE.17320840.362@NICAD3.NIC.BC.CA>, Simeon Broughton writes: =My MX started behaving very strangely this morning. Users were =getting RMS errors with mail. Finally tracked it down to the =system_queue.fdl_ctl which ANAL/RMS produced the following error: = =*** VBN 5734: Index bucket references missing data bucket with VBN 5668. =Unrecoverable error encountered in structure of file. = =I created a new file and restarted MX and everything is working =ok, except I have about 100 undelivered mail messages that MCP =QUEUE knows nothing about. Is there any way to reinsert these =into the queue file so they will get delivered? First, may I suggest you upgrade to a more recent version of MX? Meanwhile, you might try using CONVERT to recover as much data as possible from the old queue file. Then shut down MX, reconfigure things so that it uses some other machine that you know is available immediately as a route for all non-local messages, restart MX (butwithout the SMTP_SERVER), and ready all entries. As soon as they've been handed to the router you chose, shut down MX, rename queue files, reconfigure to operate as usual, and restart it. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Fri, 15 Dec 1995 17:41:49 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: RE: Eudora with MX SMTP-server Date: 15 Dec 1995 23:10:39 GMT Message-ID: <4asv9f$mg5@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0099AE71.1DF08CBA.54@uwwvax.uww.edu>, hunterl@uwwvax.uww.edu writes: ==> I know a few people who have some problems sending mail with Eudora (Windows ==> Eudora version 2.1, I think) through MX 4.1 SMTP server. What happens is the ==> following (according to MX_SMTP_SERVER_LOG.LOG): ==> ==> STM[8]: Send "220 sofi.sofi.su.se MX V4.1 VAX SMTP server ready at Thu, 14 Dec 1995 14:40:45 EST" ==> STM[8]: Receive "HELO " ==> STM[8]: Send "501 Syntax is HELO " ==> STM[8]: Receive "QUIT" ==> STM[8]: Send "221 sofi.sofi.su.se Service closing transmission channel." ==> STM[8]: Error: status=20EC ==> ==> ==> Now, I know that the HELO above *is* wrong, but I can't find a way to make ==> Eudora do anything else. ==> ==> I'd like to ask you if there is some kind of workaround, either by making ==> MX more sloopy (I don't like it, but I would prefer MX instead of UCX SMTP ==> by far), or by making Eudora behave. =Have you set the smtp_servers threads greater than the default of 4? =This looks like the same problem we solved by doing so. Oh? How so? MX is accepting the connection without problems. It's sending its initial message properly, then receiving a bogus response from the remote system. MX then informs the remote system that the response was invalid, and the other system is terminating the connection. Now, just whit is it about that that you think has something to do with the number of SMTP server threads? -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Sat, 16 Dec 1995 13:31:48 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 16 Dec 1995 13:59:36 +0100 From: Richard Levitte - GNU on VMS hacker Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099AF47.32CECB74.1@e.kth.se> Subject: RE: Eudora with MX SMTP-server >From: Andy Harper - KCL Systems manager >=> STM[8]: Send "220 sofi.sofi.su.se MX V4.1 VAX SMTP server ready at Thu, 14 Dec 1995 14:40:45 EST" >=> STM[8]: Receive "HELO " >=> STM[8]: Send "501 Syntax is HELO " >=> STM[8]: Receive "QUIT" >=> STM[8]: Send "221 sofi.sofi.su.se Service closing transmission channel." >=> STM[8]: Error: status=20EC >=> >=> >=> Now, I know that the HELO above *is* wrong, but I can't find a way to make >=> Eudora do anything else. >=> I've done some experimenting now, and it seems like the users having this problem use a very old Eudora (it was version 2.1, I'm certain. That's a "commercial" version), because with all tests I've done, Eudora at least doesn't send an empty HELO line. I've done the tests with Eudora for Windows 3.x versions 1.4.4 and 1.5.2. Now, guess what they do when they can't find out their own host name. Send the IP number, you said? No-no, they do better, they send the SMTP server name they have been configured with :-). I guess I still have to send a bug report to Qualcom. Now, to convince those users that they should upgrade... -- +--------------------------------------------------------------------+ ! Richard Levitte, GNU on VMS hacker ! tel: +46-8-26 52 47 ! ! Spannvägen 38, I ! fax: none for the moment ! ! S-161 43 Bromma ! Internet: levitte@e.kth.se ! ! SWEDEN ! ! +-GNUish VMS-+ ================================================================================ Archive-Date: Sat, 16 Dec 1995 13:49:14 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 16 Dec 1995 13:21:44 +0100 From: Richard Levitte - GNU on VMS hacker Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099AF41.E863381B.9@e.kth.se> Subject: RE: Eudora with MX SMTP-server >From: Andy Harper - KCL Systems manager >=> STM[8]: Send "220 sofi.sofi.su.se MX V4.1 VAX SMTP server ready at Thu, 14 Dec 1995 14:40:45 EST" >=> STM[8]: Receive "HELO " >=> STM[8]: Send "501 Syntax is HELO " >=> STM[8]: Receive "QUIT" >=> STM[8]: Send "221 sofi.sofi.su.se Service closing transmission channel." >=> STM[8]: Error: status=20EC >=> >=> >=> Now, I know that the HELO above *is* wrong, but I can't find a way to make >=> Eudora do anything else. >=> > >You dont say what type of system you are on but I've find that this problem >occurs when the eudora software cannot determine it's own host name from the >underlying TCP stack. Woops, sorry. Anyway, you guessed correctly, those users use PCs (hmm, I thought I did mention it being Windows Eudora...) >For instance, using microsoft TCP, you can configure in the host name to be >used. With trumpet winsock you cannot, so it must do a DNS lookup on its own >address. it is therefore ESSENTIAL that your IP address be registered in the That sounds like a very good reason. Thank you. >So, if you don't do this, eudora cannot pick up the name and sends a null >string down after HELO. MX gets confused by this, as do other SMTP servers >(not surprising really - its illegal syntax). You'll be surprised to know that sendmail ("the" sendmail :-)) allows this, if it's configured to be sloopy, at least version 8.6... Anyway, I still think it's a bug in Eudora, because if it can't find resolve its own name, it should send the IP number instead: "HELO 194.25.3.12", and that would still be accepted be all kinds of SMTP servers I know off (yes, I know, MX would still say "250 Verification failed for 194.25.3.12", but that is only a warning, and after that, it does accept MAIL FROM: and so on). I'll send a bug report to Qualcomm about it. -- +--------------------------------------------------------------------+ ! Richard Levitte, GNU on VMS hacker ! tel: +46-8-26 52 47 ! ! Spannvägen 38, I ! fax: none for the moment ! ! S-161 43 Bromma ! Internet: levitte@e.kth.se ! ! SWEDEN ! ! +-GNUish VMS-+ ================================================================================ Archive-Date: Sun, 17 Dec 1995 11:56:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sun, 17 Dec 1995 11:55:53 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-LIST@MADGOAT.COM CC: DAN@TTISMS.COM Message-ID: <0099AFFF.14BF3DF5.5@ALPHA.WKU.EDU> Subject: MX manuals now available via WWW I've just added the MX manuals to the MX WWW home page. To access the manuals, use one of the following links: http://www.wku.edu/www/madgoat/madgoat.html http://www.wku.edu/www/madgoat/mx.html http://www.wku.edu/www/madgoat/mx/mx_docs.html These HTML versions were produced using DECdocument V3.0, using the same SDML sources that were used to produce the text, PostScript, and DECW$BOOK files that are distributed with the MX VMSINSTAL kits. Many thanks to Dan Esbensen, president of Touch Technologies, for his help in my continued use of DECdocument. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Mon, 18 Dec 1995 09:24:16 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: jcring@switch.com (John Charles Ring, Jr.) Reply-To: MX-List@MadGoat.com Subject: RE: Eudora with MX SMTP-server Message-ID: Date: Mon, 18 Dec 1995 14:23:32 GMT To: MX-List@WKUVX1.WKU.EDU In article <0099AF41.E863381B.9@e.kth.se>, Richard Levitte - GNU on VMS hacker wrote: >>From: Andy Harper - KCL Systems manager > >>So, if you don't do this, eudora cannot pick up the name and sends a null >>string down after HELO. MX gets confused by this, as do other SMTP servers >>(not surprising really - its illegal syntax). > >You'll be surprised to know that sendmail ("the" sendmail :-)) allows this, >if it's configured to be sloopy, at least version 8.6... Also, I've seen that it allows you to forget to enclose the to & from addresses in <>, although that's also illegal syntax. Can't say how many Unix "crackers" fail to forge e-mail to a VMS system running Multinet (Anyone know about the other TCP/IP packages on this?) because they don't know that they need the <>'s :) Guess they think Unix = Right... --------- All wars are civil wars. Some just happen to remain within the boundaries of the abstraction known as a "country". John Ring jcring@switch.com ================================================================================ Archive-Date: Mon, 18 Dec 1995 11:11:37 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Dec 1995 11:11:11 -0600 (CST) From: "H.A. Kippenhan Jr." Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: goathunter@LOKI.COM Message-ID: <951218111111.23800db2@fndcd.fnal.gov> Subject: Re: MX manuals now available via WWW Hi All: | | From: SMTP%"MX-List@MadGoat.com" 17-DEC-1995 11:59:04.27 | Subj: MX manuals now available via WWW | | I've just added the MX manuals to the MX WWW home page. To access the | manuals, use one of the following links: | | http://www.wku.edu/www/madgoat/madgoat.html | http://www.wku.edu/www/madgoat/mx.html | http://www.wku.edu/www/madgoat/mx/mx_docs.html | | These HTML versions were produced using DECdocument V3.0, using the | same SDML sources that were used to produce the text, PostScript, and | DECW$BOOK files that are distributed with the MX VMSINSTAL kits. | | Many thanks to Dan Esbensen, president of Touch Technologies, for his | help in my continued use of DECdocument. | | Hunter | ------ | Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. | | While we're thanking people for their help in making the latest version of MX and it's documentation available, I'd like to extend that to Matt Madison (latest version of NetLib) and to Hunter Goatley (latest release of MX). Your time and effort is much appreciated. Best regards - Kipp - \|/ o o +----------------------------------+------------------------+----m--~--m----+ | H.A. Kippenhan Jr. | Internet: Kippenhan@FNAL.GOV | | HEP Network Resource Center | HEPnet/NSI DECnet: FNDCD::KIPPENHAN | | Fermi National Accelerator Lab. | BITnet: Kippenhan@FNDCD.BITNET | | P.O. Box 500 MS: FCC-3E/368 | Telephone: (708) 840-8068 | | Batavia, Illinois 60510 | FAX: (708) 840-8463 | +----------------------------------+----------------------------------------+ | All opinions & ideas expressed are mine alone, and may not necessarily | | reflect those of Fermilab, Univ. Research Assoc., or the Dept. of Energy | +---------------------------------------------------------------------------+ ================================================================================ Archive-Date: Mon, 18 Dec 1995 11:23:42 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Dec 1995 18:23:09 +0100 From: "Rok Vidmar, NUK Ljubljana" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099B0FE.59095E64.6@nuk.uni-lj.si> Subject: RE: MX V4.2 is now available!! > MadGoat Software announces the release of Message Exchange (MX) V4.2. Installs smoothly over V4.1 on both VAX and AXP. But would it be possible for the installation to retain user-defined logicals in MX_DIR:MX_LOGICALS.DAT? One more step towards perfection! Regards, Rok Vidmar Internet: rok.vidmar@uni-lj.si National and University Library Phone: +386 61 125 4218 Turjaska 1, 61000 Ljubljana Fax: +386 61 125 5007 Slovenia ================================================================================ Archive-Date: Mon, 18 Dec 1995 12:06:21 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: wing@tgv.com ("Dan Wing") Subject: RE: Eudora with MX SMTP-server Date: 18 Dec 1995 17:30:13 GMT Message-ID: <4b48fa$klm@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0099AF41.E863381B.9@e.kth.se>, Richard Levitte - GNU on VMS hacker writes: #Anyway, I still think it's a bug in Eudora, because if it can't find resolve #its own name, it should send the IP number instead: "HELO 194.25.3.12", and #that would still be accepted be all kinds of SMTP servers I know off (yes, I #know, MX would still say "250 Verification failed for 194.25.3.12", but that #is only a warning, and after that, it does accept MAIL FROM: and so on). I'll #send a bug report to Qualcomm about it. From RFC1123, Host Requirements: 5.2.5 HELO Command: RFC-821 Section 3.5 The sender-SMTP MUST ensure that the parameter in a HELO command is a valid principal host domain name for the client host. As a result, the receiver-SMTP will not have to perform MX resolution on this name in order to validate the HELO parameter. The HELO receiver MAY verify that the HELO parameter really corresponds to the IP address of the sender. However, the receiver MUST NOT refuse to accept a message, even if the sender's HELO command fails verification. DISCUSSION: [... snipped - see the RFC for the discussion ...] So as long as the sender-SMTP (Eudora) sends *something* after the HELO, MX should accept it (and MX does). However, the sender-SMTP (Eudora) is required to ("MUST") ensure it is, in fact, sending a "valid principal host domain name for the client host", which many versions of Eudora are very lax in doing. -Dan Wing, wing@tgv.com ================================================================================ Archive-Date: Mon, 18 Dec 1995 13:11:58 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Dec 1995 13:11:44 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099B0D2.D7F82D5D.7@ALPHA.WKU.EDU> Subject: RE: MX V4.2 is now available!! "Rok Vidmar, NUK Ljubljana" writes: > >> MadGoat Software announces the release of Message Exchange (MX) V4.2. > > Installs smoothly over V4.1 on both VAX and AXP. But would it be possible for >the installation to retain user-defined logicals in MX_DIR:MX_LOGICALS.DAT? > One more step towards perfection! > V4.2 does, though I forgot to include that in the .RELEASE_NOTES. Look for MX_DIR:*.OLD---you should find MX_LOGICALS.OLD and MX_STARTUP_INFO.OLD. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Mon, 18 Dec 1995 13:13:24 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Dec 1995 13:13:06 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099B0D3.08B3B246.9@ALPHA.WKU.EDU> Subject: RE: MX V4.2 is now available!! Hunter Goatley writes: > >> Installs smoothly over V4.1 on both VAX and AXP. But would it be possible for >>the installation to retain user-defined logicals in MX_DIR:MX_LOGICALS.DAT? >> One more step towards perfection! >> >V4.2 does, though I forgot to include that in the .RELEASE_NOTES. >Look for MX_DIR:*.OLD---you should find MX_LOGICALS.OLD and >MX_STARTUP_INFO.OLD. > Or, rather, it *almost* does. At least they're no longer completely wiped-out. ;-) Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Mon, 18 Dec 1995 15:47:37 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Dec 1995 10:47:06 -0800 From: "Barry.Winter" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@MadGoat.com Subject: SMTP Accounting file Message-ID: <95Dec18.135145pst.39684@ocnet.co.orange.ca.us> My mx_smtp_acc.dat file contains entries similar to the following: 18-DEC-1995 13:39 XMIT: PROTO=SMTP, SOURCE="", HOST="OCNET.CO.ORANGE.CA.US", SENT-TO="OCNET.CO.ORANGE.CA.US", BYTES_SENT=928 The Enties for the Host and Sent-To field contain the name of our filewall, not the address of the actual receipient. The file is practically worthless with this informatin. Is there a way to correct this? The define path command is: Domain="*", Path=SMTP, Route="OCNET.CO.ORANGE.CA.US" ================================================================================ Archive-Date: Mon, 18 Dec 1995 16:08:47 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Dec 1995 16:08:19 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU Message-ID: <0099B0EB.82C55676.7@ALPHA.WKU.EDU> Subject: RE: SMTP Accounting file "Barry.Winter" writes: > >My mx_smtp_acc.dat file contains entries similar to the following: > >18-DEC-1995 13:39 XMIT: PROTO=SMTP, SOURCE="", >HOST="OCNET.CO.ORANGE.CA.US", SENT-TO="OCNET.CO.ORANGE.CA.US", BYTES_SENT=928 > >The Enties for the Host and Sent-To field contain the name of our filewall, >not the address of the actual receipient. The file is practically worthless >with this informatin. Is there a way to correct this? > No. That was something I looked into for V4.2, but the routine that writes the accounting record out does not know the real destination. All it knows at that point is the host the message was sent to. Of course, this is something that can be added, but the change was more involved than I had time for for V4.2. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Mon, 18 Dec 1995 18:52:55 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: RE: SMTP Accounting file Date: 19 Dec 1995 00:35:35 GMT Message-ID: <4b51cn$1p3@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0099B0EB.82C55676.7@ALPHA.WKU.EDU>, Hunter Goatley writes: ="Barry.Winter" writes: => =>My mx_smtp_acc.dat file contains entries similar to the following: => =>18-DEC-1995 13:39 XMIT: PROTO=SMTP, SOURCE="", =>HOST="OCNET.CO.ORANGE.CA.US", SENT-TO="OCNET.CO.ORANGE.CA.US", BYTES_SENT=928 => =>The Enties for the Host and Sent-To field contain the name of our filewall, =>not the address of the actual receipient. The file is practically worthless =>with this informatin. Is there a way to correct this? => =No. That was something I looked into for V4.2, but the routine that =writes the accounting record out does not know the real destination. =All it knows at that point is the host the message was sent to. = =Of course, this is something that can be added, but the change was =more involved than I had time for for V4.2. If you do add something along those lines, please keep the information about the host to which the mail was actually sent by the local machine. There are situations in which that's more important to know than the name of the machine to which the mail was addressed. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Mon, 18 Dec 1995 19:51:37 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Dec 1995 20:51:17 EST From: Brian Reed Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0099B113.0A98BB02.1@cbict3.cb.att.com> Subject: RE: SMTP Accounting file >My mx_smtp_acc.dat file contains entries similar to the following: > >18-DEC-1995 13:39 XMIT: PROTO=SMTP, SOURCE="", >HOST="OCNET.CO.ORANGE.CA.US", SENT-TO="OCNET.CO.ORANGE.CA.US", BYTES_SENT=928 > >The Enties for the Host and Sent-To field contain the name of our filewall, >not the address of the actual receipient. The file is practically worthless >with this informatin. Is there a way to correct this? > >The define path command is: > > Domain="*", Path=SMTP, Route="OCNET.CO.ORANGE.CA.US" I remove the route on mine, thus I just have: Domain="*", Path=SMTP Note I had to remove the above path, and add it--I couldn't modify it. Then I added (well, I already had it) a default router to SMTP: MCP>set smtp/default="OCNET.CO.ORANGE.CA.US" and now my accounting file is "correct". Brian D. Reed AT&T Columbus Works Brian.D.Reed@att.com 614-860-6218 ================================================================================ Archive-Date: Tue, 19 Dec 1995 09:26:09 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: "S.T.Hayes" Subject: VMS 6.2 mail To: MX-List@madgoat.com Reply-To: MX-List@WKUVX1.WKU.EDU Date: Tue, 19 Dec 95 15:23:32 GMT Message-ID: <9512191523.aa15333@uk.ac.ed.festival> Some time ago, I saw a message on this list about problems with VMS 6.2 mail. > From: cooper@utsph.sph.uth.tmc.edu > Date: 21 Sep 1995 00:29:18 GMT > I posted earlier about the MX_LOCAL process dying with the > exceed virtual memory problem after upgradeing to VMS6.2... I had > it fixed after upgrading to 6.1 about a year ago but don't remember if > it was due to a patch or was fixed via the upgrade. In any case I > didn't have the problem during VMS 6.1. However after upgrading to > 6.2, the problem came back. I have called DEC and reported the problem > and asked for a fix. They indicated that there was no patch for VMS 6.2 > and that it was suppose to be fixed in the next release of VMS. Their > suggestion was to either up the virtualpagecnt and reboot or keep > stopping the MX_LOCAL process and restarting it routinely. I tried > the first suggestion and it did not fix the problem. So now I'm running > a process that wakes every 15min to kill the MX_LOCAL process an re-starts > it. Can you tell me please whether this problem has been resolved? One machine here is running alpha VMS 6.2 with UCX 3.3 and MX 4.1. Should we expect problems? ! Stephen Hayes, Edinburgh University Computing Service. ! S.T.Hayes@ed.ac.uk, Tel: +44 (0)131 650 4990. ================================================================================ Archive-Date: Tue, 19 Dec 1995 12:15:19 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Dec 1995 12:14:09 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU CC: MadGoat-Announce@MadGoat.com Message-ID: <0099B193.F6EEAC61.9@ALPHA.WKU.EDU> Subject: MX V4.2 -- modified VMSINSTAL kit A couple of people noticed a bug in the NETLIB installation that would cause an infinite loop during the installation if you wanted to install NETLIB support for more than one TCP/IP product. I've updated the MX kits to fix this problem. There are no other changes from the previous kits, so if you already have MX V4.2, there's no reason to pick this up unless you have experienced the problem above. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. -------------------------------------------------------------------------------- MadGoat Software announces the release of Message Exchange (MX) V4.2. You can get MX V4.2 via: WWW: http://www.wku.edu/www/madgoat/mx.html ftp://ftp.wku.edu/mx/mx042/mx042.zip Anonymous FTP: ftp.wku.edu in [.MX.MX042] ftp.spc.edu in [.MX.MX042] ftp.csus.edu in /pub/mx E-mail: Send the command SEND MX in the body of a mail message to . NOTE: MX will be returned to you in 74 180-block files! Do not order it unless you can't get it via any other method! -------------------------------------------------------------------------------- ================================================================================ Archive-Date: Thu, 21 Dec 1995 04:32:13 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: pdb@pds2.compd.com (Peter Burnett) Subject: Netlib 2.0 Date: Thu, 21 Dec 1995 08:36:13 GMT Message-ID: <4bb6ad$4d9@linux.compd.com> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU I have grabbed a copy of the MX 4.2 distribution and its all installed fine over the 4.1 I had previously been using. MX also installed Netlib 2.0(i?) as well as previously I had been using v1.7 of Netlib from the MGFTP 2.1-? distribution. MGFTP with Netlib 2.0 seems to ok on the basic tests I have done but MX does not wnat to play ball. When the Netlib 2.0 series were first released, I played with the a,b,c & d varients and none of them seemed to be happy on my system. I thought I would give the (i) varient a go but it seems not to be a happy-chappie. MX (SMTP) seems not to want to hand off eMail and generates a selection of errors like :- 'Network partner disconnected logical link" and " bad parameter....etc etc...." as the error messages from the MX 'Show Queue Full" command. If I go back to Netlib 1.7, these all seem to disappear. So, what I am after is any advice, guidence or whatever on getting Netlib to perform on my system. I have upped the MAXBUF setting as recomended in the Netlib documentation. I have also checked the CMU-TEK 6.6-5a installation and that seems all ok as best as I can judge. This is the setup as is at present:- MV 3100/10e, 16MB Ram, VMS 5.5-2 MGFTP 2.1-?, MX 4.2, CMU-TEK 6.6-5a One thing I have noticed is that the MGFTP Server is more responsive using Netlib 2.0 as opposed to v1.7, but then MX seems to work with v1.7 and not with v2.0i of Netlib. I know an answer is to go back to v1.7 of Netlib but I would prefer to get Netlib 2.0 to operate on this h/w combination as if I have any future problems, a level of support for a current version can be sought. Regards, Peter. -- Peter Burnett Tel: 44-1424-853481 x2266 DDDDDDDDDDDDD Computing Devices Co. Ltd Fax: 44-1424-851520 DCCCCC D Castleham Road Email: pdb@pds2.compd.com DCCCCC II D St. Leonards On Sea Home Tel: 44-1424-853168 DC II D East Sussex Home Fax: 44-1424-853364 DCCCCC II D UK TN38 9NJ Home Data: 44-1424-853361 DCCCCC D Home Email: pdb@neverlnd.demon.co.uk DDDDDDDDDDDDD ================================================================================ Archive-Date: Thu, 21 Dec 1995 09:31:47 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 21 Dec 1995 09:20:08 EST From: "Brian Tillman, x8425" Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU CC: pdb@pds2.compd.com Message-ID: <0099B30D.FC5E0FE0.1@swdev.si.com> Subject: RE: Netlib 2.0 Peter Burnett (pdb@pds2.compd.com) writes: > >So, what I am after is any advice, guidence or whatever on getting >Netlib to perform on my system. I have upped the MAXBUF setting as >recomended in the Netlib documentation. I have also checked the >CMU-TEK 6.6-5a installation and that seems all ok as best as I can >judge. > >This is the setup as is at present:- > >MV 3100/10e, 16MB Ram, VMS 5.5-2 >MGFTP 2.1-?, MX 4.2, CMU-TEK 6.6-5a This is exactly one of the combinations I use, with one exception, and it works perfectly. I have NETLIB V2.0I, MGFTP V2.1-2, CMUIP V6.6-5A, and VMS V5.5-2, but I'm still using MX V4.1. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS239 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Fri, 22 Dec 1995 03:23:38 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Netlib 2.0 Date: 22 Dec 1995 09:10:51 GMT Message-ID: <4bdsmr$arb@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <4bb6ad$4d9@linux.compd.com>, pdb@pds2.compd.com (Peter Burnett) writes: =I have grabbed a copy of the MX 4.2 distribution and its all installed =fine over the 4.1 I had previously been using. MX also installed =Netlib 2.0(i?) as well as previously I had been using v1.7 of Netlib =from the MGFTP 2.1-? distribution. MGFTP with Netlib 2.0 seems to ok =on the basic tests I have done but MX does not wnat to play ball. When =the Netlib 2.0 series were first released, I played with the a,b,c & d =varients and none of them seemed to be happy on my system. I thought I =would give the (i) varient a go but it seems not to be a =happy-chappie. = =MX (SMTP) seems not to want to hand off eMail and generates a =selection of errors like :- = = 'Network partner disconnected logical link" Y'know, it would be useful if you'd actually take the time to THINK about what you're talking about. The above error message means that THE REMOTE HOST terminated the connection prematurely. Don't blame that on NETLIB. =and = = " bad parameter....etc etc...." = =as the error messages from the MX 'Show Queue Full" command. Guess what, shit-for-brains? There *IS* no such command. And you SHOULD get the message: %CLI-W-NUMBER, invalid numeric value - supply an integer \FULL\ if you try it. Try using the ACTUAL command (SHOW QUEUE/FULL) instead. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Fri, 22 Dec 1995 09:16:46 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Dec 1995 09:16:27 CST From: Hunter Goatley Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU Message-ID: <0099B3D6.A2D87905.1@ALPHA.WKU.EDU> Subject: MX V4.2 sources are now available The MX V4.2 sources are now available in MX042_SRC.ZIP via anonymous ftp from ftp.wku.edu in [.MX.MX042]. The file is also available on ftp.spc.edu in [.MX.MX042] and on ftp.csus.edu in pub/mx. Hunter ------ Hunter Goatley, Sr. OpenVMS Systems Programmer, The LOKI Group, Inc. ================================================================================ Archive-Date: Fri, 22 Dec 1995 09:43:31 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Dec 1995 16:42:44 +0100 From: Richard Levitte - GNU on VMS hacker Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU Message-ID: <0099B414.FB65DC34.20@e.kth.se> Subject: Re: Netlib 2.0 >From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) >=and >= >= " bad parameter....etc etc...." >= >=as the error messages from the MX 'Show Queue Full" command. > >Guess what, shit-for-brains? There *IS* no such command. And you SHOULD get >the message: > %CLI-W-NUMBER, invalid numeric value - supply an integer > \FULL\ >if you try it. Try using the ACTUAL command (SHOW QUEUE/FULL) instead. Y'know, it would be useful if you'd actually take the time to THINK about what you answer to ;-). Since Peter talked about "the MX 'Show Queue Full'", he probably meant the MCP command QUEUE SHOW/FULL. -- +--------------------------------------------------------------------+ ! Richard Levitte, GNU on VMS hacker ! tel: +46-8-26 52 47 ! ! Spannvägen 38, I ! fax: none for the moment ! ! S-161 43 Bromma ! Internet: levitte@e.kth.se ! ! SWEDEN ! ! +-GNUish VMS-+ You may not add me to a commercial mailing list or send me commercial advertising without my consent! See http://www.e.kth.se/~levitte/anti.html for further reference. ================================================================================ Archive-Date: Fri, 22 Dec 1995 14:11:19 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Dec 1995 15:07:33 EST From: "Jonathan E. Hardis" Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com CC: hardis@garnet.nist.gov Message-ID: <0099B407.AF36B820.6@garnet.nist.gov> Subject: Re: Netlib 2.0 > Since Peter talked about "the MX 'Show Queue Full'", he probably meant > the MCP command QUEUE SHOW/FULL. Oh, it's the holiday season ... the winter solstice. Days are short. Tempers are short. Serotonin is low. Testosterone is high. And now we're going to have an escalating food fight on our hands, since: $ MCP SHOW QUEUE/FULL - does exactly the same thing as - $ MCP QUEUE SHOW/FULL Hey guys. Knock it off! Now. Please. *No* more messages in this thread. *No* replies to this post. Thank you. ================================================================================ Archive-Date: Fri, 22 Dec 1995 18:59:03 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Dec 1995 18:56:33 EST From: "Bryan, 296-9371" Reply-To: MX-List@MadGoat.com To: mx-list@vc.pca.state.mn.us Message-ID: <0099B427.ACDFC240.1@spock.pca.state.mn.us> Subject: DECUS UUCP question Does anyone know where I might find a resonably up-to-date copy of DECUS UUCP that I could get via FTP? Thanks. ********************************************************************** * Bryan Fredrick Minnesota Pollution Control Agency * * Computer Services Office 520 Lafayette Road N. * * +1 612 296 9371 Voice St. Paul, MN 55155 * * +1 612 282 5446 Fax bryan.fredrick@pca.state.mn.us * ********************************************************************** ================================================================================ Archive-Date: Mon, 25 Dec 1995 03:08:20 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: Peter Burnett Reply-To: MX-List@MadGoat.com Subject: Netlib 2.0 Date: 25 Dec 95 00:17:01 Message-ID: <49e_9512250024@neverlnd.demon.co.uk> To: MX-List@WKUVX1.WKU.EDU Hello Richard! >> Guess what, shit-for-brains? There *IS* no such command. And you >> SHOULD get the message: %CLI-W-NUMBER, invalid numeric value - >> supply an integer \FULL\ if you try it. Try using the ACTUAL >> command (SHOW QUEUE/FULL) instead. l> Y'know, it would be useful if you'd actually take the time to THINK l> about what you answer to ;-). l> Since Peter talked about "the MX 'Show Queue Full'", he probably meant l> the MCP command QUEUE SHOW/FULL. Well, something like that... What I should have said was :- MCP> SHOW QUEUE/FULL but Richard understood where I was coming from... -- Peter Burnett Internet: pdb@neverlnd.demon.co.uk 10 Parsons Close system.VAX2@neverlnd.demon.co.uk St. Leonards On Sea Fidonet: Peter Burnett 2:441/80 East Sussex, UK, TN38 9QT Fax: 44-1424-853364 ================================================================================ Archive-Date: Mon, 25 Dec 1995 03:08:32 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: Peter Burnett Reply-To: MX-List@MadGoat.com Subject: Netlib 2.0 Date: 25 Dec 95 00:08:14 Message-ID: <49d_9512250023@neverlnd.demon.co.uk> To: MX-List@WKUVX1.WKU.EDU Hello carl! .....shit for brains here.... Friday December 22 1995, carl@SOL1.GPS.CALTECH.EDU writes to All: c> Y'know, it would be useful if you'd actually take the time to THINK c> about what you're talking about. The above error message means that THE c> REMOTE HOST terminated the connection prematurely. Don't blame that on c> NETLIB. Carl, I do not profess to know 1% of what you know about VAXen and VMS, I amke no apoligy that I need a lot of help at times, that is why I use the newsgroups in the mistaken hope that individuals like yourself might help such "shit for brains" types like myself. I am not saying Netlib is _the_ fault here, I would not be surprised if its a tuning problem, I was looking for advice / suggestions / pointers towards a conclusion that could be drawn against the reports I am receiving. c> =and c> = c> = " bad parameter....etc etc...." c> = c> =as the error messages from the MX 'Show Queue Full" command. c> Guess what, shit-for-brains? There *IS* no such command. And you c> SHOULD get the message: %CLI-W-NUMBER, invalid numeric value - supply c> an integer \FULL\ if you try it. Try using the ACTUAL command (SHOW c> QUEUE/FULL) instead. Thank you for your input Carl, I shall try and reproduce the problem and post the full report here. -- Peter Burnett Internet: pdb@neverlnd.demon.co.uk 10 Parsons Close system.VAX2@neverlnd.demon.co.uk St. Leonards On Sea Fidonet: Peter Burnett 2:441/80 East Sussex, UK, TN38 9QT Fax: 44-1424-853364 ================================================================================ Archive-Date: Mon, 25 Dec 1995 19:17:35 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Netlib 2.0 Date: 26 Dec 1995 01:13:09 GMT Message-ID: <4bni75$4f0@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <49d_9512250023@neverlnd.demon.co.uk>, Peter Burnett writes: = c> Y'know, it would be useful if you'd actually take the time to THINK = c> about what you're talking about. The above error message means that THE = c> REMOTE HOST terminated the connection prematurely. Don't blame that on = c> NETLIB. = =Carl, I do not profess to know 1% of what you know about VAXen and VMS, I amke =no apoligy that I need a lot of help at times, that is why I use the newsgroups =in the mistaken hope that individuals like yourself might help such "shit for =brains" types like myself. Oh, I'll gladly help. But you've got to do SOME of the work yourself. Just because the computer you're using has a CPU is no excuse to shut down the one between your ears. =I am not saying Netlib is _the_ fault here, I would not be surprised if its =a tuning problem, Even after being enjoined to think, you refuse to do so, eh? Tell me, just how do you figure that THE REMOTE HOST closing a connection is a tuning problem? Make your guesses before reading the next paragraph. If you can't come up with an idea for how it could be a tuning problem, then what makes you think it's a tuning problem? OK, the only situation in which I can think of a tuning problem causing the remote system to close the connection is if the local process, somehow, manages to get enough CPU time to initiate the connection, then for some reason is denied the resources necessary to continue the session for long enough that something on the reomte host times out. =I was looking for advice / suggestions / pointers towards =a conclusion that could be drawn against the reports I am receiving. Well, if what you're looking for are pointers, then you should start by reading the _Message Exchange Management Guide_. Chapter 8 is "Troubleshooting MX." You obviously haven't bothered reading it. Otherwise, you'd've enabled debugging for outgoing SMTP deliveries: $ DEFINE/SYS/EXEC MX_SMTP_DEBUG * and mailed us the contents of the debug log (MX_SMTP_DIR:MX_SMTP_LOG.LOG). So I have no choice but to conclude that you don't want pointers, what you want is for someone else to manage MX for you. = c> =and = c> = = c> = " bad parameter....etc etc...." = c> = = c> =as the error messages from the MX 'Show Queue Full" command. = = c> Guess what, shit-for-brains? There *IS* no such command. And you = c> SHOULD get the message: %CLI-W-NUMBER, invalid numeric value - supply = c> an integer \FULL\ if you try it. Try using the ACTUAL command (SHOW = c> QUEUE/FULL) instead. = =Thank you for your input Carl, I shall try and reproduce the problem and post =the full report here. That'd be a start. The DCL command "SET HOST 0/LOG" may be of interest to you for this. It will allow you to get an actual transcript of a session in which you get such an error, and will make it easy for you to post the actual command you used and the full text of any error message you got, instead of posting at best vague descriptions of them. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Mon, 25 Dec 1995 21:01:15 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Dec 1995 20:00:37 MST From: Mark Tarka Reply-To: MX-List@MadGoat.com To: MX-List@WKUVX1.WKU.EDU Message-ID: <0099B68C.1F9BA0E0.9@earth.oscs.montana.edu> Subject: Re: Netlib 2.0 In article <4bni75$4f0@gap.cco.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: [NB Quote symbol is "| " for the current message.] | In article <49d_9512250023@neverlnd.demon.co.uk>, Peter Burnett | writes: | = c> Y'know, it would be useful if you'd actually take the time to THINK Jeez...now who said _that_? [Snip...] | = c> Guess what, shit-for-brains? There *IS* no such command. And you | = c> SHOULD get the message: %CLI-W-NUMBER, invalid numeric value - supply | = c> an integer \FULL\ if you try it. Try using the ACTUAL command (SHOW | = c> QUEUE/FULL) instead. | = | =Thank you for your input Carl, I shall try and reproduce the problem and post | =the full report here. | | That'd be a start. The DCL command "SET HOST 0/LOG" may be of interest to you | for this. It will allow you to get an actual transcript of a session in which | you get such an error, and will make it easy for you to post the actual | command | you used and the full text of any error message you got, instead of posting at | best vague descriptions of them. SET HOST 0/LOG=file.ext is a great tool, but it comes with extraneous information, as in: [Snip...] Z [62"p F = [Snip...] $ [Snip...] $ lo Now I know a DCL script (is that the correct term?) can strip unwanted characters from a file; but can it clean-up a SET HOST log file? I need a clear pointer on how to handle those NL's, CR's, and reversed ?'s (either a line or two of code, or a reference to the manuals -- I've got access to VMS 4.x documentation at home, 5.5 at school). To recapitulate, I'd like to create a DCL .COM file to clean-up any SET HOST log file I might happen to come across in the course my daily activity on the VAX. We're working with VMS 5.5-2. I'm a chemist, not a computer guy. How do I get rid of the NL, CR, reverse ? terms (ESC codes?)? Mark ichjsmt@earth.oscs.montana.edu ================================================================================ Archive-Date: Mon, 25 Dec 1995 22:15:22 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Dec 1995 21:14:57 MST From: Mark Tarka Reply-To: MX-List@MadGoat.com To: MX-List@MadGoat.com Message-ID: <0099B696.817E0640.1@earth.oscs.montana.edu> Subject: Re: Netlib 2.0 In article <0099B68C.1F9BA0E0.9@earth.oscs.montana.edu>, Mark Tarka writes: [NB Quote symbol is "!" for the current message.] [Snip...] !SET HOST 0/LOG=file.ext is a great tool, but it comes with !extraneous information, as in: ! ![Snip...] !Z ![62"p F != ![Snip...] !$ ! ![Snip...] !$ lo Gee...in MAIL this doesn't look at all like what I had on my screen when I was editing (TPU) the message prior to posting. Mark [Snip...] ================================================================================ Archive-Date: Tue, 26 Dec 1995 14:12:17 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Netlib 2.0 Date: 26 Dec 1995 20:09:11 GMT Message-ID: <4bpkp7$n38@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0099B414.FB65DC34.20@e.kth.se>, Richard Levitte - GNU on VMS hacker writes: =>From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) = =>=and =>= =>= " bad parameter....etc etc...." =>= =>=as the error messages from the MX 'Show Queue Full" command. => =>Guess what, shit-for-brains? There *IS* no such command. And you SHOULD get =>the message: => %CLI-W-NUMBER, invalid numeric value - supply an integer => \FULL\ =>if you try it. Try using the ACTUAL command (SHOW QUEUE/FULL) instead. = =Y'know, it would be useful if you'd actually take the time to THINK about =what you answer to ;-). = =Since Peter talked about "the MX 'Show Queue Full'", he probably meant the =MCP command QUEUE SHOW/FULL. Don't you just love it when one moron decides to come to the defense of another? Since you were obviously too damned stupid to understand it first time around: 1) The MCP command "SHOW QUEUE FULL" returns an error message consistent with the first idiot's vague description; 2) The MCP command "SHOW QUEUE/FULL" does not normally return such a status. 3) The MCP command "SHOW QUEUE/FULL" is equivalent to the MCP command "QUEUE SHOW/FULL" (though it's not documented in the on-line help, at least for MX v4.1). So the reasonable conclusion is that the first idiot actually used the command he told us he did, and therefore got an error message which he was too stupid to bother quoting exactly. However, Levitte, himself apparently also a moron, concludes that the first moron actually typed a valid command and exercised a heretofore unknown bug in MX. SHEESH! -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Thu, 28 Dec 1995 16:48:01 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: pacific@decus.org.au Reply-To: MX-List@MadGoat.com Subject: MX and All-in-1 Message-ID: <1995Dec28.101559.15639@decus.org.au> Date: 28 Dec 95 10:15:59 AEST To: MX-List@WKUVX1.WKU.EDU I am looking for something to get my SMTP mail neatly into an All-in-1 system. UCX is installed on the All-in-1 system, so the box itself will send and receive SMTP mail quite happily, but getting SMTP mail directly to the A1 subscriber is proving a problem. Can MX do this for me ? ================================================================================ Archive-Date: Sat, 30 Dec 1995 09:15:55 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: Peter Burnett Reply-To: MX-List@MadGoat.com Subject: Netlib 2.0 Date: 27 Dec 95 22:14:42 Message-ID: <4a4_9512301452@neverlnd.demon.co.uk> To: MX-List@WKUVX1.WKU.EDU Tuesday December 26 1995, carl@SOL1.GPS.CALTECH.EDU writes to All: c> Oh, I'll gladly help. But you've got to do SOME of the work yourself. c> Just because the computer you're using has a CPU is no excuse to shut c> down the one between your ears. Oh... you are wit Carl..... Yes, I realise I am gonna have to do some work here myself, well, lets admit it, unless you have some sort of ESP, you will never know whats happing on my system here, so its dependant on what I post here and how accurately I do that to boot as well. c> =I am not saying Netlib is _the_ fault here, I would not be surprised if c> its =a tuning problem, c> Even after being enjoined to think, you refuse to do so, eh? Tell me, c> just how do you figure that THE REMOTE HOST closing a connection is a c> tuning problem? Make your guesses before reading the next paragraph. If c> you can't come up with an idea for how it could be a tuning problem, c> then what makes you think it's a tuning problem? OK, the only c> situation in which I can think of a tuning problem causing the remote c> system to close the connection is if the local process, somehow, manages c> to get enough CPU time to initiate the connection, then for some reason c> is denied the resources necessary to continue the session for long c> enough that something on the reomte host times out. Carl, I have allready admitted that when it comes to VMS and Vaxen in general, I am a nuthead..... I am at home on 8080/8085/80x86 systems employing MS-Dos and Isis-II, but they are not what I have a problem with. I have a pair of 3100/10e's that I eventually want to use for my internet conectivity but as you can see, I am having a few problems, not least in my in-experience to do with VMS and Vaxen but I am prepared to learn. c> =I was looking for advice / suggestions / pointers towards c> =a conclusion that could be drawn against the reports I am receiving. c> Well, if what you're looking for are pointers, then you should start by c> reading the _Message Exchange Management Guide_. Chapter 8 is c> "Troubleshooting MX." You obviously haven't bothered reading it. c> Otherwise, you'd've enabled debugging for outgoing SMTP deliveries: $ c> DEFINE/SYS/EXEC MX_SMTP_DEBUG * and mailed us the contents of the debug c> log (MX_SMTP_DIR:MX_SMTP_LOG.LOG). So I have no choice but to conclude c> that you don't want pointers, what you want is for someone else to c> manage MX for you. I am going to try and do this... I have got to get the system back to the state it was in when I get this problem however, I have been reading up on Netlib and tried an alternative suggested in the dox and that seems to cause problems not related to MX. What I will do expalin my system set up here. Two 3100/10e's with 16MB each running CMU 6.6-5a, MX 4.2 and Netlib 2.0i. VAX1 runs Don Orchards DNS suite as a primary and VAX2 runs the same but as a secondary from VAX1. VAX2's MX is configured to hand all its mail off to VAX1 and then VAX1 deals with it as neccesary according to the PATHS I have defined in MX. What I had configured on VAX2 was that Netlib did not use the NAMRES of CMU but use the actual DNS resolvers as per the dox of Netlib. After a reboot of VAX2 and then performing a :- PING VAX1 I would get 100% result, leave the system overnight and try it some 12 or so hours later, I would then get 100% failure. Even PING vax1.neverlnd.demon.co.uk would fail as would PING 194.70.122.1. (Note; PING is a symbol I have set up as "IPNCP PING"). I have now reset netlib back to using the NAMRES for hostname lookup and the above command seems to be stable after 24 hours plus. = c>> =and = c>> = = c>> = " bad parameter....etc etc...." = c>> = = c>> =as the error messages from the MX 'Show Queue Full" command. c> = = c>> Guess what, shit-for-brains? There *IS* no such command. And you = c>> SHOULD get the message: %CLI-W-NUMBER, invalid numeric value - = c>> supply an integer \FULL\ if you try it. Try using the ACTUAL = c>> command (SHOW QUEUE/FULL) instead. c> = c> =Thank you for your input Carl, I shall try and reproduce the problem c> and post =the full report here. c> That'd be a start. The DCL command "SET HOST 0/LOG" may be of interest c> to you for this. It will allow you to get an actual transcript of a c> session in which you get such an error, and will make it easy for you to c> post the actual command you used and the full text of any error message c> you got, instead of posting at best vague descriptions of them. Yes, a good reminder of the use of the command, but what I shall do is Telnet from my PC here and capture is that way as I have better editors on the PC to manage the resulting output file. Having just send a load of test messages from VAX2 to VAX1, all seems to have worked 100%.... I am going to have to play some more. One of the problems is that I would be reluctant to go back to the exact system build I did have as since the problem did arise, I have done a few things to the system, ie; increased the PAGE and SWAP file sizes and trying to get the the QUEUE_MANAGER to work ( but thats another story for another day :-) I note in a nother message that you refer to me as a moron(1) as well as Richard L, in my case, you are more than likely correct and I make no excuses for it but there agin, we can not all be perfect can we. Lets just drop the moron(ic) bit and I will try and be more accurate in my postings. -- Peter Burnett Internet: pdb@neverlnd.demon.co.uk 10 Parsons Close system.VAX2@neverlnd.demon.co.uk St. Leonards On Sea Fidonet: Peter Burnett 2:441/80 East Sussex, UK, TN38 9QT Fax: 44-1424-853364 ================================================================================ Archive-Date: Sat, 30 Dec 1995 18:28:47 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 30 Dec 1995 18:27:37 CST From: Dave Miller Reply-To: MX-List@MadGoat.com To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0099BA6C.F593A719.1@BEAVER.Bemidji.MSUS.edu> Subject: SMTP_SERVER.LOG problem Folks .. I've noticed that the SMTP_SERVER.LOG files didn't include node name. This was curious because SMTP_xx.LOG file do. Furthermore, since I limited my .LOG file to 5 versions, when the 6th node was started it was unable to open a SMTP_SERVER.LOG file (because the 5 were open and none could be deleted.) Well, it didn't seem to affect operations, so I just pushed it down the stack of outstanding problems. Aren't holiday's wonderful? I got time to check it out. Apparently, in MX_START.COM, since SMTP_SERVER isn't a MULTI_THING, FILEID isn't defined (I didn't bother to find out why.) So I changed all occurances of FILEID to NODE in the SMTP_SERVER startup code. Problem fixed. BTW, this is MX 4.1. //----------\|/------\\ Dave Miller. || /\ -X- || Professor, Computer Science. || / \ /|/\ || || / \ / \ || SYSTEM@BEAVER.Bemidji.MSUS.EDU || / \ \ || || /________\____\ || 1500 Birchmont Dr. NE || || || || Bemidji State University \\------|| -------// Bemidji MN, 56601 ================================================================================ Archive-Date: Sun, 31 Dec 1995 02:31:54 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Netlib 2.0 Date: 31 Dec 1995 00:38:59 GMT Message-ID: <4c4m33$6f1@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <4a4_9512301452@neverlnd.demon.co.uk>, Peter Burnett writes: =Oh... you are wit Carl..... Yes, I realise I am gonna have to do some =work here myself, well, lets admit it, unless you have some sort of ESP, you =will never know whats happing on my system here, so its dependant on what I =post here and how accurately I do that to boot as well. Correct. = c> =I am not saying Netlib is _the_ fault here, I would not be surprised if = c> its =a tuning problem, = = c> Even after being enjoined to think, you refuse to do so, eh? Tell me, = c> just how do you figure that THE REMOTE HOST closing a connection is a = c> tuning problem? Make your guesses before reading the next paragraph. If = c> you can't come up with an idea for how it could be a tuning problem, = c> then what makes you think it's a tuning problem? OK, the only = c> situation in which I can think of a tuning problem causing the remote = c> system to close the connection is if the local process, somehow, manages = c> to get enough CPU time to initiate the connection, then for some reason = c> is denied the resources necessary to continue the session for long = c> enough that something on the reomte host times out. = =Carl, I have allready admitted that when it comes to VMS and Vaxen in general, =I am a nuthead..... Sorry, but that doesn't cut it. Unless you're claiming that anybody who's unfamiliar with VMS is an utter moron. At no point in this thread has there been ANYTHING which requires a familiarity with VMS on your part. All that's required is that you actually read English and THINK about what you're talking about. =I am at home on 8080/8085/80x86 systems employing MS-Dos =and Isis-II, but they are not what I have a problem with. I have a pair of =3100/10e's that I eventually want to use for my internet conectivity but as =you can see, I am having a few problems, not least in my in-experience to do =with VMS and Vaxen but I am prepared to learn. No, your fundamental problem is that you think that because you're not familiar with VMS, there's no reason for you to THINK about what's going on. Now, I'll admit, if the operating system in question were Unix, where the error messages are pretty much meaningless, you'd have a point. But why the fuck are you unwilling even to TRY to think about what's going on? =I am going to try and do this... I have got to get the system back to the =state it was in when I get this problem however, I have been reading up on =Netlib and tried an alternative suggested in the dox and that seems to cause =problems not related to MX. = =What I will do expalin my system set up here. Two 3100/10e's with 16MB each =running CMU 6.6-5a, MX 4.2 and Netlib 2.0i. VAX1 runs Don Orchards DNS suite =as a primary and VAX2 runs the same but as a secondary from VAX1. VAX2's =MX is configured to hand all its mail off to VAX1 and then VAX1 deals with =it as neccesary according to the PATHS I have defined in MX. = =What I had configured on VAX2 was that Netlib did not use the NAMRES of CMU =but use the actual DNS resolvers as per the dox of Netlib. After a reboot of =VAX2 and then performing a :- = = PING VAX1 = =I would get 100% result, leave the system overnight and try it some 12 or so =hours later, I would then get 100% failure. Even PING vax1.neverlnd.demon.co.uk =would fail as would PING 194.70.122.1. (Note; PING is a symbol I have set =up as "IPNCP PING"). OK, now try THINKING about what you just told us instead of engaging in your penchant for logorrhea: PING *DOES NOT* use NETLIB. Therefore, what's broken is NOT NETLIB (unless you're somehow that NETLIB is somehow corrupting the memory used by CMUIP by directly overwriting it; if you think about the problem enough to realize that NETLIB simply calls documented interfaces to CMUIP, then there's no way you can argue that the problem is in NETLIB). What's broken is CMUIP. Perhaps NETLIB has allowed you to run across a CMUIP bug. But that doesn't change the fact that you're talking about a bug in CMUIP, if there's a bug at all (rather than a network connectivity failure that just happened to coincide with your installation of NETLIB). -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it.