Archive-Date: Sat, 01 Jan 1994 00:04:57 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Sat, 01 Jan 1994 00:04:23 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <00977DC2.39D4FE0C.117@WKUVX1.WKU.EDU> Subject: MX-LIST Administrivia: Monthly Post Posting statistics for list MX-LIST during December 1993 Total number of posts: 56 Total number of posters: 29 Total number of subscribers: 213 Total number of digest subscribers: 22 Last modified: 31-MAY-1993 23:55 (Added digest info.) Welcome to MX-List@WKUVX1.BITNET, an electronic mailing list established for the discussion of the Message Exchange mail software. This is a routine posting you will see from time to time on MX-List. 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.BITNET: SUBSCRIBE MX-List-Digest "Your real name here" The MX-List archives are maintained at ARCHIVES@WKUVX1.BITNET. To get a copy of any month's postings, send an e-mail message with the body SEND MX-List.yyyy-mm to ARCHIVES@WKUVX1.BITNET, where "yyyy" is the year and "mm" is the numeric representation of the month. For example, the message SENDME MX-List.1992-04 will send the archives for April 1992. To remove yourself from the mailing list, send the following command to MXserver@WKUVX1.BITNET: 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 NOMAIL - to remain on the list but not receive mail SET MX-List MAIL - to resume receiving mail from the list SET MX-List CONCEAL - to not report your address in a REVIEW SET MX-List NOCONCEAL - to report your address in a REVIEW SET MX-List REPRO - to receive posts you make to MX-List SET MX-List NOREPRO - to not receive posts you make to MX-List LIST - to get a list of mailing lists served by WKUVX1 HELP - to receive a help file By default, subscriptions are set to MAIL, REPRO, NOCONCEAL. If you have any questions, comments, or suggestions about MX-List, please contact the list owner at the address below. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Hunter Goatley, VAX Systems Programmer goathunter@WKUVX1.BITNET Western Kentucky University Academic Computing, STH 226 (502) 745-5251 Bowling Green, KY 42101 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ================================================================================ Archive-Date: Mon, 03 Jan 1994 17:29:32 CST Sender: list-mgr@WKUVX1.WKU.EDU From: z999012@UTSCC.MDA.UTH.TMC.EDU Subject: Addressing Multiple Cluster Nodes Date: 3 Jan 1994 22:48:33 GMT Message-ID: <2ga7c1$ds4@oac4.hsc.uth.tmc.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU I have a 4 node CI cluster where all nodes mount all disks. It has VMS A5.5-2, CMUIP 6.6-5A and MX 3.3. All of the MX components run on one node, MDACC, and the logicals are defined and images installed on all nodes. Outgoing mail works great. Incoming mail works only with @mdacc.mda.uth.tmc.edu in the address. Mail addresses to any other node name as in @utscc.mda.uth.tmc.edu does not work and the message just disappears. The sending node does not complain, and nothing ever reaches the MX queue. The sending node is an AXP with VMS and UCX. This has been a long standing problem, but enough occurances lately have convinced me I should fix it. I see my options as: Run SMTP_SERVER on all nodes or set MX records in the DNS tables to point the other node's mail to MDACC. Is there another way and which is the recommended way? MX_STARTUP_INFO.DAT: 002ROUTER:MDACC 003LOCAL:MDACC 004SMTP:MDACC 004SMTP_SERVER:MDACC The config file is: (blanks in col 1 only in this message.) ! Configuration file: MX_DEVICE:[MX33]MX_CONFIG.MXCFG;1 ! Created: 30-DEC-1993 17:36:12.15 by MXCONFIG ! MX version id: MX V3.3 VAX DEFINE REWRITE_RULE - "<{user}@memo>" - "<""MDA85::MRGATE::\""MEMO::MDACC.{user}\""""@mdacc.mda.uth.tmc.edu>" ! DEFINE PATH "mdacc.mda.uth.tmc.edu" LOCAL DEFINE PATH "mdaprs.mda.uth.tmc.edu" LOCAL DEFINE PATH "mda85.mda.uth.tmc.edu" LOCAL DEFINE PATH "utscc.mda.uth.tmc.edu" LOCAL DEFINE PATH "[129.106.60.3]" LOCAL DEFINE PATH "[129.106.60.4]" LOCAL DEFINE PATH "[129.106.60.5]" LOCAL DEFINE PATH "[129.106.60.7]" LOCAL DEFINE PATH *.UUCP SMTP/ROUTE="uunet.uu.net" DEFINE PATH *.BITNET SMTP/ROUTE="cunyvm.cuny.edu" ! NOTE: The next path definition should always be LAST. DEFINE PATH * SMTP ! ! Done with routing information. ! SET SMTP/NOACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 /DNS_RETRIES=12- /NODEFAULT_ROUTER SET LOCAL/NOACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96/MULTIPLE_FROM/HEADERS=(TOP=(- FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID,- RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT,- ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM,- RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER), BOTTOM=(- NOALL)) SET ROUTER/PERCENT_HACK SET JNET/PERCENT_HACK/NOBSMTP_REPLY/NOACCOUNTING/NOLENIENT/NOUSERNAME SET DECNET_SMTP/NOACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 SET SITE/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 SET X25_SMTP/NOACCOUNTING/RETRY_INTERVAL=" 0 00:30:00.00" - /MAXIMUM_RETRIES=96 Any help in solving this will be most appreciated. _________________________________________________________________________ Lawrence Newton Mail Box 167 | Z999012@mdacc.mda.uth.tmc.edu University of Texas | lnewt@mdacc.mda.uth.tmc.edu M.D. Anderson Cancer Center | THENET MDACC::Z999012 1515 Holcombe Houston, Texas 77030 | Voice (713) 792-6344 ------------------------------------------------------------------------- ================================================================================ Archive-Date: Mon, 03 Jan 1994 18:54:37 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 03 Jan 1994 16:50:28 EST From: Virtual Bill Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00977FE1.1B4847C0.2073@gtewd> Subject: RE: Addressing Multiple Cluster Nodes Larry, I'm far from and expert on MX, but you might try using a wild card in your MX_STARTUP_INFO.DAT instead of the MDACC. ================================================================================ Archive-Date: Mon, 03 Jan 1994 19:24:09 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Addressing Multiple Cluster Nodes Message-ID: <1994Jan3.174337.641@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 3 Jan 94 17:43:37 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <2ga7c1$ds4@oac4.hsc.uth.tmc.edu>, z999012@UTSCC.MDA.UTH.TMC.EDU writes: > I have a 4 node CI cluster where all nodes mount all disks. It has > VMS A5.5-2, CMUIP 6.6-5A and MX 3.3. All of the MX components run on one > node, MDACC, and the logicals are defined and images installed on all nodes. > Outgoing mail works great. Incoming mail works only with > @mdacc.mda.uth.tmc.edu in the address. Okay. >Mail addresses to any other node > name as in @utscc.mda.uth.tmc.edu does not work and the message just > disappears. The sending node does not complain, and nothing ever reaches the > MX queue. The sending node is an AXP with VMS and UCX. utscc.mda.uth.tmc.edu only has an A record, which points to 129.106.60.3, and when I try to TELNET to the SMTP port, I get a "connection refused" error. You need to create an MX record for utscc.mda.uth.tmc.edu pointing to mdacc.mda.uth.tmc.edu, or allow incoming SMTP to utscc.mda.uth.tmc.edu. > This has been a long standing problem, but enough occurances lately have > convinced me I should fix it. > > I see my options as: > Run SMTP_SERVER on all nodes or > set MX records in the DNS tables to point the other node's mail to MDACC. > > Is there another way and which is the recommended way? If you want to have one node handle all incoming mail, the "best" method is to create MX records like this: node_a MX 10 mail_gateway node_a MX 20 node_a node_b MX 10 mail_gateway node_b MX 20 node_b node_c MX 10 mail_gateway node_c MX 20 node_c mail_gateway MX 10 mail_gateway and then run incoming SMTP processes on all your nodes -- this way, if your mail gateway goes down, your other nodes can take over and you can still receive incoming Email. If you really don't want ot run incoming SMTP processes on the other nodes, just don't setup the preference 20 MX records, and don't have MX startup the processes on the other nodes. Another solution is to just have all your outgoing mail addressed with a single return address, like mdacc.mda.uth.tmc.edu -- this way all replies will come back to that node. For example, in a VAXcluster you could setup all nodes to have the same "From:" host address, even though there are several machines you can send outgoing mail from (you could be logged into node_a, above, and your hostname could be @mail_gateway.site.edu, and node_a and mail_gateway could be two different VAXes). -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Mon, 03 Jan 1994 20:14:51 CST Sender: list-mgr@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Addressing Multiple Cluster Nodes Date: 4 Jan 1994 01:39:40 GMT Message-ID: <2gahcs$crd@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <2ga7c1$ds4@oac4.hsc.uth.tmc.edu>, z999012@UTSCC.MDA.UTH.TMC.EDU writes: = I have a 4 node CI cluster where all nodes mount all disks. It has = VMS A5.5-2, CMUIP 6.6-5A and MX 3.3. All of the MX components run on one = node, MDACC, and the logicals are defined and images installed on all nodes. = Outgoing mail works great. Incoming mail works only with = @mdacc.mda.uth.tmc.edu in the address. Mail addresses to any other node = name as in @utscc.mda.uth.tmc.edu does not work and the message just = disappears. The sending node does not complain, and nothing ever reaches the = MX queue. The sending node is an AXP with VMS and UCX. = = This has been a long standing problem, but enough occurances lately have = convinced me I should fix it. = = I see my options as: = Run SMTP_SERVER on all nodes or = set MX records in the DNS tables to point the other node's mail to MDACC. = = Is there another way and which is the recommended way? There's no other way: One way or another, the messages have to be directed to a machine with the SMTP_SERVER running. It *IS* rather strange that, if you don't have MX records for the other nodes, and you don't have SMTP_SERVER running on them, that the sending machine doesn't complain: Since there are no MX records, it must be connecting to port 25 on the other machines; since you're not running the SMTP_SERVER on those nodes, it's not getting the SMTP_SERVER when it connects. So what *IS* it getting? Either a rejection of the connect request or, presumably, something left over from the installation of CMUIP. It turns out that what it's getting is a rejection of the connect request (I just tried TELNETing to port 25 of each of your machines). So, apparently, the AXP running UCX is misconfigured: It should be bouncing the mail back to the sender. As to which technique is better, since you've got a CI cluster, I'd recommend that you run the SMTP_SERVER process on all nodes. Why? Well, presumably you're booting off a disk that's available even if MDACC is down. If that's the case, then by running SMTP_SERVER on all nodes, you'll allow your systems to receive SMTP mail even when MDACC is down (note: The mail won't actually be delivered to the users until MDACC comes back up unless you've also got the ROUTER and the LOCAL agents running on the other nodes, but it will be put in the MX queue). You might also want to set up MX records for all of your systems anyway: If there are MX records for each of the machines pointing to all four machines, and you're running the SMTP_SERVER on each of the machines, then mail can be sent to your cluster as long as any one of the machines is up and running. If you also run the ROUTER and LOCAL agents on each machine, then mail addressed to any of the machines can be delivered to the user as long as any machine in the cluster is up. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 05 Jan 1994 11:48:44 CST Sender: list-mgr@WKUVX1.WKU.EDU From: desroches@woods.uml.edu Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Can MX send to MAILworks directly? Date: 5 Jan 94 11:51:15 -0500 Message-ID: <1994Jan5.115115.1@woods.uml.edu> To: MX-List@WKUVX1.WKU.EDU We are using MX 3.2 along with DEC's MailWorks and Message Router software. My question is about receiving incoming email over the internet. Currently when MX receives a message it is first sent to the user's VMSmail mailbox. Each user has a forwarding address of the format "mrgate::am::username" to get it from VMSmail over to the users MailWorks mailbox. Probably a very ineffecient use of resources. If you are wondering why the system was set up this way it is because we needed to preserve our users former address: "username@node.domain". I know that if we changed the address to "username%am.mrgate@node.domain" it would go directly into MailWorks without passing through VMSmail but I couldn't ask 13,000 users to change their busines cards and letterhead - we had to use the old address format - hence the forwarding form VMSmail to MailWorks. Now I am wondering if there is a way around this problem. Is there any way that MX would allow us to maintain the current address format and send messages directly to MailWorks without using the VMSmail forwarding address? I was wondering in the MX "rewrite rules" would make this possible. I'd appreciate any ideas you may have. Thanks, Dick Desroches ================================================================================ Archive-Date: Wed, 05 Jan 1994 13:41:06 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 05 Jan 1994 15:36:20 ADT From: Greg Bishop Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00978169.14957F40.27626@ac.nsac.ns.ca> Subject: file not found error using MX_BULL I was going to install MX_BULL on two VAXes today. The first one is working fine but the second one was not to be conquered. They are both running VMS 5.5, Multinet V3.2B, MX 3.3 and MX_BULL 01-002. The only error message I get is in the MX_SITE_LOG.LOG shown below. Any assistance would be greatly appreciated. Greg Bishop ----------------------------------------------------- 5-JAN-1994 15:17:44.16 Processing queue entry number 13398. 5-JAN-1994 15:17:45.64 DELIVER: Delivering... 5-JAN-1994 15:17:45.69 DELIVER_FILE: Command: @MX_EXE:SITE_DELIVER - 5-JAN-1994 15:17:45.70 DELIVER_FILE: "BULLETIN" - 5-JAN-1994 15:17:45.70 DELIVER_FILE: MX_ROOT:[SITE]SITE_MSG_7BAD20A0_00978166_00002C49.TMP;1 - 5-JAN-1994 15:17:45.71 DELIVER_FILE: MX_ROOT:[SITE]SITE_ADR_7BAD20A0_00978166_00002C49.TMP;1 - 5-JAN-1994 15:17:45.74 DELIVER_FILE: "" 5-JAN-1994 15:17:46.94 DELIVER_FILE: Subprocess says: MX_BULL: Opening message file.... 5-JAN-1994 15:17:46.97 DELIVER_FILE: Subprocess says: MX_BULL: Error status %X00018292 5-JAN-1994 15:17:47.05 DELIVER_FILE: Subprocess says: %RMS-E-FNF, file not found 5-JAN-1994 15:17:47.28 DELIVER_FILE: Subprocess says: EXIT:00000001 Greg Bishop Internet: GBISHOP@AC.NSAC.NS.CA System Manager Voice: (902) 893-6693 Nova Scotia Agricultural College Fax: (902) 895-4547 Truro, Nova Scotia CANADA B2N 5E3 ================================================================================ Archive-Date: Wed, 05 Jan 1994 14:08:06 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 05 Jan 1994 18:41:12 +0100 From: "GWDGV1::MOELLER" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: question re SITE interface (maybe internals) This is not in the documentation, so maybe one of the developers can help out: Is it 'legal' to RENAME the message file passed to the SITE interface instead of processing it immediately (in my case, that's essentially via COPY)? This would save me a few disk I/Os - but it all depends on the way that the message file is deleted (by "MX Site") after the subprocess has done its work. Wolfgang J. Moeller, Tel. +49 551 201516 or -510, GWDG, D-37077 Goettingen, F.R.Germany PSI%(0262)45050352008::MOELLER Disclaimer: No claim intended! | ================================================================================ Archive-Date: Wed, 05 Jan 1994 14:08:34 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 05 Jan 1994 18:45:58 +0100 From: "GWDGV1::MOELLER" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: MIME decoder anyone? Are there any tools to decode MIME-coded mails once they have been received by a traditional UA? In particular, our received mail all passes thru the MX SITE interface, so I don't even have the benefit of MX's "MAIL/FORWARD" capability. Could the MX-specific decoding code be 'lifted' from the sources? Has anyone tried to do this yet? Wolfgang J. Moeller, Tel. +49 551 201516 or -510, GWDG, D-37077 Goettingen, F.R.Germany PSI%(0262)45050352008::MOELLER Disclaimer: No claim intended! | ================================================================================ Archive-Date: Wed, 05 Jan 1994 14:15:45 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 05 Jan 1994 14:15:31 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097815D.CAE6C2EC.11@ALPHA.WKU.EDU> Subject: RE: question re SITE interface (maybe internals) "GWDGV1::MOELLER" writes: > >This is not in the documentation, so maybe one of the developers >can help out: > >Is it 'legal' to RENAME the message file passed to the SITE interface >instead of processing it immediately (in my case, that's essentially via COPY)? > >This would save me a few disk I/Os - but it all depends on the way >that the message file is deleted (by "MX Site") after the subprocess >has done its work. > Yes, that's OK---MX will still try to delete it, but the failure to find the file will not cause any problems. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 05 Jan 1994 14:18:33 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 05 Jan 1994 14:17:33 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097815E.13433F70.13@ALPHA.WKU.EDU> Subject: RE: MIME decoder anyone? "GWDGV1::MOELLER" writes: > >Are there any tools to decode MIME-coded mails once they have been >received by a traditional UA? > MultiNet includes a DECODE command to decode APPLICATION/RMS files (the type generated by MX with SEND/FOREIGN). >In particular, our received mail all passes thru the MX SITE interface, >so I don't even have the benefit of MX's "MAIL/FORWARD" capability. >Could the MX-specific decoding code be 'lifted' from the sources? >Has anyone tried to do this yet? > I hope to either provide a standalone utility or add the ability to decode to the SITE interface for the next version of MX. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 05 Jan 1994 15:16:06 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: file not found error using MX_BULL Message-ID: <1994Jan5.131134.651@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 5 Jan 94 13:11:33 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <18997537@MVB.SAIC.COM>, Greg Bishop writes: > 5-JAN-1994 15:17:44.16 Processing queue entry number 13398. > 5-JAN-1994 15:17:45.64 DELIVER: Delivering... > 5-JAN-1994 15:17:45.69 DELIVER_FILE: Command: @MX_EXE:SITE_DELIVER - > 5-JAN-1994 15:17:45.70 DELIVER_FILE: "BULLETIN" - > 5-JAN-1994 15:17:45.70 DELIVER_FILE: MX_ROOT:[SITE]SITE_MSG_7BAD20A0_00978166_00002C49.TMP;1 - > 5-JAN-1994 15:17:45.71 DELIVER_FILE: MX_ROOT:[SITE]SITE_ADR_7BAD20A0_00978166_00002C49.TMP;1 - > 5-JAN-1994 15:17:45.74 DELIVER_FILE: "" > 5-JAN-1994 15:17:46.94 DELIVER_FILE: Subprocess says: MX_BULL: Opening message file.... > 5-JAN-1994 15:17:46.97 DELIVER_FILE: Subprocess says: MX_BULL: Error status %X00018292 > 5-JAN-1994 15:17:47.05 DELIVER_FILE: Subprocess says: %RMS-E-FNF, file not found > 5-JAN-1994 15:17:47.28 DELIVER_FILE: Subprocess says: EXIT:00000001 Add a "$ SET VERIFY" command as the first ine in your SITE_DELIVER.COM, and then re-do whatever you were doing, and examine your MX_SITE_LOG.LOG file again. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Wed, 05 Jan 1994 15:16:18 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Can MX send to MAILworks directly? Message-ID: <1994Jan5.133041.652@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 5 Jan 94 13:30:41 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <1994Jan5.115115.1@woods.uml.edu>, desroches@woods.uml.edu writes: >My question is about receiving incoming email over the internet. Currently >when MX receives a message it is first sent to the user's VMSmail mailbox. >Each user has a forwarding address of the format "mrgate::am::username" to >get it from VMSmail over to the users MailWorks mailbox. Probably a very >ineffecient use of resources. >If you are wondering why the system was set up this way it is because we >needed to preserve our users former address: "username@node.domain". I know >that if we changed the address to "username%am.mrgate@node.domain" it would >go directly into MailWorks without passing through VMSmail but I couldn't ask >13,000 users to change their busines cards and letterhead - we had to use the >old address format - hence the forwarding form VMSmail to MailWorks. > >Now I am wondering if there is a way around this problem. Is there any way >that MX would allow us to maintain the current address format and send messages >directly to MailWorks without using the VMSmail forwarding address? I was >wondering in the MX "rewrite rules" would make this possible. A rewrite rule something like: DEFINE REWRITE_RULE - "<{user}@node.domain>" - "<""mrgate::am::{user}""@node.domain>" you should be able to retain your existing Email addresses without requiring changing business cards, and without maintaining per-user forwarding, and without activating the local delivery agent. Of course, the users within Mail-doesn't-Works may or may not have replyable addresses, and *everyone's* mail will be sent to Mail-doesn't- Works, which may or may not be what you want (I'll wager you don't want it to happen to *everyone* on the system). -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Wed, 05 Jan 1994 16:22:44 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 05 Jan 1994 16:51:50 EST From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: WKUVX1.WKU.EDU!MX-list@esseye.si.com Message-ID: <00978173.A0FD8360.9085@swdev.si.com> Subject: RE: MIME decoder anyone? >I hope to either provide a standalone utility or add the ability to >decode to the SITE interface for the next version of MX. > >Hunter While adding it to SITE is exemplary, please supply the stand-alone utility as well. Thanks heaps. -- Brian tillman_brian@si.com ================================================================================ Archive-Date: Thu, 06 Jan 1994 07:01:30 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Thu, 06 Jan 1994 05:52:48 GMT From: "Jamie Jones, HICOM Operations" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <009781E0.BA6D6D20.16838@hicom.lut.ac.uk> Subject: Rewrite for Span Sorry this isn't really MX related, but I want to know if there is any *official* internet --> span relay, so that I can add the following rewrite rule: define rewrite "<{user}@{node}.span>" "<""{node}::{user}""@the.relay.name>" The bitnet one was included in the MX distribution, so here's hoping someone can provided one for span. Jamie. ================================================================================ Archive-Date: Thu, 06 Jan 1994 09:27:26 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: 6 Jan 94 09:17:00 CST From: "John Clement-Rice U. (713)527-8101x2037" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: Addressing Multiple Cluster Nodes To: "MX-List" > > I have a 4 node CI cluster where all nodes mount all disks. It has > VMS A5.5-2, CMUIP 6.6-5A and MX 3.3. All of the MX components run on one > node, MDACC, and the logicals are defined and images installed on all nodes. > Outgoing mail works great. Incoming mail works only with > @mdacc.mda.uth.tmc.edu in the address. Mail addresses to any other node > name as in @utscc.mda.uth.tmc.edu does not work and the message just >> disappears. The sending node does not complain, and nothing ever reaches the > MX queue. The sending node is an AXP with VMS and UCX. > > This has been a long standing problem, but enough occurances lately have > convinced me I should fix it. > > I see my options as: > Run SMTP_SERVER on all nodes or > set MX records in the DNS tables to point the other node's mail to MDACC. > > Is there another way and which is the recommended way? > Essentially your solution is that you probably need to run the smtp server on all nodes. Without the server no other host can even contact the target host. It should be possible by modifying MX records to get your name server to tell remote hosts that all mail to the other nodes should be rerouted to MDACC. If your name server may be managed by someone else, you may not be able to do this yourself. Enabling the SMTP server on each node is trivial, and easy. If you do enable the server on the other nodes and the problem persists, then your name server may already be telling other hosts to send the mail to some other destination. The one puzzling thing is that the mail does not get bounced!!! I have tried to send you mail at UTSCC and I see that in the mail queue I have Entry: 19831, Origin: [Local] Status: IN-PROGRESS SMTP entry #19832, status: READY Waiting for retry until: 6-JAN-1994 09:44:27.51 Recipient #1: , Route=UTSCC.MDA.UTH.TMC.EDU Error count=1 Last error: %SYSTEM-F-REJECT, connect to network object rejected Eventually the mail will bounce back to me. I do not know of any other way to fix your problem. > MX_STARTUP_INFO.DAT: > >002ROUTER:MDACC >003LOCAL:MDACC >004SMTP:MDACC >004SMTP_SERVER:MDACC This should be 004SMTP_SERVER:MDACC,node2,node3,node4 Also looking at this I would recommend running the other components on at least one other node, to prevent problems if MX goes down om MDACC. > > Any help in solving this will be most appreciated. > > _________________________________________________________________________ > Lawrence Newton Mail Box 167 | Z999012@mdacc.mda.uth.tmc.edu > University of Texas | lnewt@mdacc.mda.uth.tmc.edu > M.D. Anderson Cancer Center | THENET MDACC::Z999012 > 1515 Holcombe Houston, Texas 77030 | Voice (713) 792-6344 > ------------------------------------------------------------------------- > John Clement Rice University ================================================================================ Archive-Date: Thu, 06 Jan 1994 10:29:21 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Rewrite for Span Message-ID: <1994Jan6.083726.659@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 6 Jan 94 08:37:26 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19022128@MVB.SAIC.COM>, "Jamie Jones, HICOM Operations" writes: >Sorry this isn't really MX related, but I want to know if there is >any *official* internet --> span relay, so that I can add the following >rewrite rule: > >define rewrite "<{user}@{node}.span>" "<""{node}::{user}""@the.relay.name>" > >The bitnet one was included in the MX distribution, so here's hoping someone >can provided one for span. The best bet would be to contact the Administrator of any node that is on both SPAN and the Internet, and ask if you can use them. The closer they are to your site, the better -- then the message can get into SPAN and go through the internal DECnet routing within SPAN (HEPnet, or whatever it is really called now). cunyvm.cuny.edu is in the middle of the BITNET 'world', but it isn't strictly the 'official' gateway -- if you have access to, and permission of, an InterBIT gateway closer to your site, you should use it. I'm sure Hunter has better information about this, though -- I'm only repeating what I was told by a local InterBIT gateway's administrator. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Thu, 06 Jan 1994 12:28:59 CST Sender: list-mgr@WKUVX1.WKU.EDU From: kmm@cc.colorado.edu Subject: More cluster questions. Message-ID: Reply-To: MX-List@WKUVX1.WKU.EDU Date: Thu, 6 Jan 1994 17:37:43 GMT To: MX-List@WKUVX1.WKU.EDU I have two VMS systems in a cluster (microvax 3400, vms 5.5-2; Alpha 3000/300l, OpenVMS 1.5) each running MX3.3 and Multinet 3.2c. The MX software is running independently on both machines, and I am now (finally) ready to set up MX to run "clustered" from the same directory. The alpha is RIKKI, the microvax TOOMAI and the DECNET Cluster Alias is CCNODE. I have not set up a cluster alias with multinet, since we don't have the same layered software on both machines. MAIL$SYSTEM_FLAGS is 7 on both machines, they share the sysuaf.dat, rightslist.dat, and vmsmail_profiles.data files. I have been following the "clustering MX" thread, but have a few questions relating to moving from two independent systems to a clustered system. 1. Do I need to reinstall the software or can I unify the config.mcp, mx_logicals.dat, and mx_startup_info.dat, point sys$startup:mx_startup.com to the common directory and restart MX on both systems? 2. When looking at mx_logicals.dat, I became confused by the first two logical definitions MX_FLQ_NODE_NAME and MX_NODE_NAME. From comparing the two files, I assume MX_FLQ_NODE_NAME should be the DECNET Cluster Alias (CCNODE). What should MX_NODE_NAME be if I am using the same MX directory structure on both machines - also CCNODE? I was unable to find anything in the manuals that identify what each of these logicals is used for, and the paragraph on page 1-3 of the install manual implies that this is overridden by the MX_VMSMAIL_FROM_FORMAT. Is this interpretation correct? I really don't want CCNODE.colorado.edu going out as the return address. 3. Can I safely set MX_VMSMAIL_LOCALHOST to @cc.colorado.edu ? Is this what determines the Sender: or Return-path field? (Various listservs seem to pick up various fields for subscriptions and I need to make sure I know what I'm messing with here.) Thanks for your help (and/or reassurance), Karen Michels Files in question follow: ======================================================================== MX_logicals.dat on rikki (done before system was clustered) --------------------------------------------------------- MX_FLQ_NODE_NAME\/SYSTEM/EXEC\RIKKI MX_NODE_NAME\/SYSTEM/EXEC\rikki.cc.colorado.edu MX_VMSMAIL_LOCALHOST\/SYSTEM/EXEC\@rikki.cc.colorado.edu MX_VMSMAIL_FROM_FORMAT\/SYSTEM/EXEC\ MX_FLQ_DIR\/SYSTEM/EXEC\SITELIB:[MX.QUEUE] !$ will change to $disk2:[mx033] $! MX_FLQ_RECLAIM_WAIT\/SYSTEM/EXEC\0 02:00:00 MX_ROUTER_DIR\/SYSTEM/EXEC\MX_ROOT:[ROUTER] MX_LOCAL_DIR\/SYSTEM/EXEC\MX_ROOT:[LOCAL] MX_MCP_HELPLIB\/SYSTEM\MX_DIR:MX_MCP_HELPLIB MX_ALIAS_HELPLIB\/SYSTEM\MX_DIR:MX_ALIAS_HELPLIB mx_logicals.dat on TOOMAI (done after system was clustered) ------------------------------------------------------------ MX_FLQ_NODE_NAME\/SYSTEM/EXEC\CCNODE MX_NODE_NAME\/SYSTEM/EXEC\toomai.cc.colorado.edu MX_VMSMAIL_LOCALHOST\/SYSTEM/EXEC\@toomai.cc.colorado.edu MX_VMSMAIL_FROM_FORMAT\/SYSTEM/EXEC\ MX_FLQ_DIR\/SYSTEM/EXEC\$DISK2:[MX033] MX_FLQ_RECLAIM_WAIT\/SYSTEM/EXEC\0 02:00:00 MX_ROUTER_DIR\/SYSTEM/EXEC\MX_ROOT:[ROUTER] MX_LOCAL_DIR\/SYSTEM/EXEC\MX_ROOT:[LOCAL] MX_MCP_HELPLIB\/SYSTEM\MX_DIR:MX_MCP_HELPLIB MX_ALIAS_HELPLIB\/SYSTEM\MX_DIR:MX_ALIAS_HELPLIB Unified MX_startup_info.dat (no questions, just added for completeness). ---------------------------------------------------------- 001NETLIB:* 002ROUTER:* 003LOCAL:RIKKI=2,TOOMAI=2 004SMTP:RIKKI=2,TOOMAI=1 004SMTP_SERVER:* 005MLF:RIKKI=1 ================================================================================ Archive-Date: Thu, 06 Jan 1994 15:18:05 CST Sender: list-mgr@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Rewrite for Span Date: 6 Jan 1994 20:21:18 GMT Message-ID: <2ghrru$rjg@gap.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19022128@MVB.SAIC.COM>, "Jamie Jones, HICOM Operations" writes: =Sorry this isn't really MX related, but I want to know if there is =any *official* internet --> span relay, There used to be, and I'm sure there still is, but I don't know what it is. By the say, SPAN is now the NASA Science Internet (NSI). I suggest you contact someone at the NSI network information center (NISNIC.GSFC.NASA.GOV) for help. I don't know specifically whom you should contact, but mail sent to postmaster@NISNIC.GSFC.NASA.GOV should, eventually, be forwarded to someone who can help you. =so that I can add the following rewrite rule: = =define rewrite "<{user}@{node}.span>" "<""{node}::{user}""@the.relay.name>" That might not be the rewrite rule you want. Depends on the form of address the gateway is looking for. For example, instead of a rewrite rule, you'd be better off defining a path: define path *.SPAN SMTP/Route=the.relay.name if the mail gateway knows how to deal with a pseudo-domain of .SPAN. -------------------------------------------------------------------------------- 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, 06 Jan 1994 15:18:12 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: More cluster questions. Message-ID: <1994Jan6.134500.665@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 6 Jan 94 13:45:00 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article , kmm@cc.colorado.edu writes: >I have two VMS systems in a cluster (microvax 3400, vms 5.5-2; Alpha 3000/300l, >OpenVMS 1.5) each running MX3.3 and Multinet 3.2c. The MX software is running >independently on both machines, and I am now (finally) ready to set up >MX to run "clustered" from the same directory. The alpha is RIKKI, the >microvax TOOMAI and the DECNET Cluster Alias is CCNODE. I have >not set up a cluster alias with multinet, since we don't have the same >layered software on both machines. MAIL$SYSTEM_FLAGS is 7 on both machines, >they share the sysuaf.dat, rightslist.dat, and vmsmail_profiles.data files. > >I have been following the "clustering MX" thread, but have a few questions >relating to moving from two independent systems to a clustered system. > >1. Do I need to reinstall the software or can I unify the config.mcp, > mx_logicals.dat, and mx_startup_info.dat, point sys$startup:mx_startup.com > to the common directory and restart MX on both systems? Make sure the [.EXE] and [.ALPHA_EXE] directories have the appropriate files in them. Also be sure to shutdown MX and make it so no incoming mail will happen, and no local users will try to send mail. >2. When looking at mx_logicals.dat, I became confused by the first two > logical definitions MX_FLQ_NODE_NAME and MX_NODE_NAME. From comparing > the two files, I assume MX_FLQ_NODE_NAME should be the DECNET Cluster > Alias (CCNODE). Doesn't matter what it MX_FLQ_NODE_NAME is at all (Hunter, plz correct me if I'm wrong), as it is only used to generate a cluster-wide lock name for communications between processes. MX_NODE_NAME should contain the nodename you want in your "From:" fields for mail you're sending out. For example, with: "MX_NODE_NAME" = "node.name" "MX_VMSMAIL_LOCALHOST" = "@vmsmail_localhost" and MX_VMSMAIL_FROM_FORMAT un-defined, if I send mail to myself I get headers like: Return-Path: Received: by uh01.Colorado.EDU (MX V3.3 VAX) id 6353; Thu, 06 Jan 1994 13:38:51 MST Sender: sysmgr@vmsmail_localhost Date: Thu, 06 Jan 1994 13:38:50 MST From: Dan Wing Reply-To: sysmgr@vmsmail_localhost To: sysmgr@uh01.colorado.edu Message-ID: <00978221.D5140620.6353@node.name> Subject: ejfk I'm guessing the "Received:" line's value is because I didn't reset the Router.... >What should MX_NODE_NAME be if I am using the same > MX directory structure on both machines - also CCNODE? I was unable to > find anything in the manuals that identify what each of these logicals is > used for, and the paragraph on page 1-3 of the install manual implies > that this is overridden by the MX_VMSMAIL_FROM_FORMAT. Is this > interpretation correct? I really don't want CCNODE.colorado.edu going > out as the return address. If I recall correctly, MX_VMSMAIL_FROM_FORMAT overrides MX_NODE_NAME. >3. Can I safely set MX_VMSMAIL_LOCALHOST to @cc.colorado.edu ? Yes. This is also used if you specify just MX%username. >Is this > what determines the Sender: or Return-path field? (Various listservs > seem to pick up various fields for subscriptions and I need to make sure > I know what I'm messing with here.) See example above. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Thu, 06 Jan 1994 20:45:25 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Gateway to FaxJr fax processor Message-ID: <1994Jan6.130014.3374@dymaxion.ns.ca> From: bg@dymaxion.ns.ca (Ben Armstrong) Reply-To: MX-List@WKUVX1.WKU.EDU Date: 6 Jan 94 13:00:14 AST To: MX-List@WKUVX1.WKU.EDU How do I gateway mail messages to my local fax processor, FaxJr? FaxJr expects addresses of the form: FAXJR!6095551212 This works locally because the comment gets preserved so that FaxJr can use it. But if I try to send such an address through MX, the comment gets lost, or it gets validated as part of the username depending on where I put it. None of the following work: No such user: MX%"FAXJR!6095551212" MX%"FAXJR!6095551212@DYMAXION.NS.CA" Invalid host name: MX%"FAXJR@DYMAXION.NS.CA!6095551212" The message gets through, but the comment gets lost: MX%"FAXJR@DYMAXION.NS.CA"!6095551212 MX%"FAXJR"!6095551212 Suggestions, anyone? Ben. -- Ben Armstrong (INTP), Software Development, bus: (902)422-1973 Dymaxion Research Ltd., fax: (902)421-1267 Halifax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca ================================================================================ Archive-Date: Thu, 06 Jan 1994 21:22:50 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Gateway to FaxJr fax processor Message-ID: <1994Jan6.192830.669@buckie.uh.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 6 Jan 94 19:28:29 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <1994Jan6.130014.3374@dymaxion.ns.ca>, bg@dymaxion.ns.ca (Ben Armstrong) writes: >How do I gateway mail messages to my local fax processor, FaxJr? > >FaxJr expects addresses of the form: > >FAXJR!6095551212 > >This works locally because the comment gets preserved so that FaxJr >can use it. But if I try to send such an address through MX, the >comment gets lost, or it gets validated as part of the username >depending on where I put it. None of the following work: Could you give us a background on FaxJr? You type: $ MAIL MAIL> SEND To: FAXJR!3035551212 ... and it faxes the message? Is that right? -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Thu, 06 Jan 1994 22:22:48 CST Sender: list-mgr@WKUVX1.WKU.EDU From: dciem!priort!system@uunet.UU.NET Reply-To: MX-List@WKUVX1.WKU.EDU Date: Thu, 6 Jan 1994 11:15:33 -0500 Message-ID: <0097821632918CC0.00000786@priort.UUCP> Subject: UUCP Interface To: mx-list@wkuvx1.wku.edu Content-Type: text Hi there. I've been trying to download the UU20BOOT file from ftp.spc.edu, but to no avail. I tried several different ways, but once I got it, I couldn't unzip it. What I specifically need is version 1.3-2 (or higher) of UUCP_MAILSHR.EXE. I was hoping that someone could either mail this file to me UUENCODED, or at least give me an alternate site to retrieve this file. Thanx in advance. ================================================================================ Archive-Date: Fri, 07 Jan 1994 02:49:48 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 07 Jan 1994 09:45:10 EST From: Matthias Clausen DESY -MKV2/KRYK- Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: claus@heracc.desy.de Message-ID: <009782CA.5ACE8E40.21945@heracc.desy.de> Subject: RE: Gateway to FaxJr fax processor >How do I gateway mail messages to my local fax processor, FaxJr? > >FaxJr expects addresses of the form: > >FAXJR!6095551212 > >This works locally because the comment gets preserved so that FaxJr >can use it. But if I try to send such an address through MX, the >comment gets lost, or it gets validated as part of the username >depending on where I put it. None of the following work: I wonder how mail to FAXJR!6095551212 works since -I thought- you would need something like FAXJR%6095551212 to do it. Nevertheless here are some hints: Try: MX%"'FAXJR!6095551212'@DYMAXION.NS.CA" or: MX%"'DECNET_NODE::FAXJR!6095551212'@DYMAXION.NS.CA" This will cause MX to NOT parse through FAXJR!6095551212 or: \'FAXJR!6095551212\'@DYMAXION.NS.CA" from unix type machines Matthias Clausen Deutsches Elektronen Synchrotron DESY Gruppe: MKV2/KRYK Notkestrasse 85 VXHERA::CLAUS 22603 Hamburg Bahrenfeld CLAUS@DESYVAX.BITNET Tel: -49 40 8998-3256 claus@vxhera.desy.de Fax: -49 40 8998-4388 PSI%(0262)45050958002::CLAUS ---------------------------------------------------------------- Matthias Clausen Deutsches Elektronen Synchrotron Gruppe: KRYK DESY/Hamburg, Germany ================================================================================ Archive-Date: Fri, 07 Jan 1994 19:46:44 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 07 Jan 1994 20:40:25 -0400 (EDT) From: "G. Del Merritt" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Gateway to FaxJr fax processor To: MX-List@WKUVX1.WKU.EDU Message-ID: <00978325E4A8B7C0.26A046DB@giant.IntraNet.com> Content-Transfer-Encoding: 7BIT >How do I gateway mail messages to my local fax processor, FaxJr? > >FaxJr expects addresses of the form: > >FAXJR!6095551212 > >This works locally because the comment gets preserved so that FaxJr >can use it. But if I try to send such an address through MX, the >comment gets lost, or it gets validated as part of the username >depending on where I put it. None of the following work: This "feature" of FAX Jr. (and of it's big brother, FAX Sr., which I have) is a clever hack, but I think you would be better off buying the "real" foreign mail interface that Omtool will happily sell you. The other suggestions are all interesting, but continue to work with the fact that you are using the "fact" that VMS MAIL is preserving the "comment" you made in your original message in the text it sends to the recipient, in this case the user "FAXJR". If you want to avoid the expense (which I do believe is actually pretty small unless you are using FAX Jr. on the uVAX II you bought for $10 o0r your home ;-), then you can look at how FAXJR_MAIL.COM does it's job. I modified mine to make use of parameter files, for example. You could, for instance, have the command file parse the message text to pull out the destination fax numbers and addressees. For grins, I would have attached a copy of my modified version of the file FAXSR_MAIL.COM, which works with FAXSR version 3.0, after my signature. Unfortunately, it is copyrighted by Omtool, so if you are interested, contact me directly via mail and we'll work something out. Del Merritt del@IntraNet.com ccavax!giant!del IntraNet, Inc., One Gateway Center, Newton, MA 02158 Voice: 617-527-7020; FAX: 617-527-6779 ================================================================================ Archive-Date: Fri, 07 Jan 1994 20:50:41 CST Sender: list-mgr@WKUVX1.WKU.EDU From: bg@dymaxion.ns.ca (Ben Armstrong) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Gateway to FaxJr fax processor Message-ID: <1994Jan7.112821.3376@dymaxion.ns.ca> Date: 7 Jan 94 15:28:21 GMT To: MX-List@WKUVX1.WKU.EDU In article <1994Jan6.192830.669@buckie.uh.colorado.edu>, dwing@uh01.Colorado.EDU (Dan Wing) writes: > In article <1994Jan6.130014.3374@dymaxion.ns.ca>, bg@dymaxion.ns.ca (Ben Armstrong) writes: >>How do I gateway mail messages to my local fax processor, FaxJr? >> >>FaxJr expects addresses of the form: >> >>FAXJR!6095551212 >> >>This works locally because the comment gets preserved so that FaxJr >>can use it. But if I try to send such an address through MX, the >>comment gets lost, or it gets validated as part of the username >>depending on where I put it. None of the following work: > > Could you give us a background on FaxJr? > > You type: > > $ MAIL > MAIL> SEND > To: FAXJR!3035551212 > ... > > and it faxes the message? Is that right? That's right. That's about all I know about how it works. Ben. ================================================================================ Archive-Date: Sun, 09 Jan 1994 22:19:04 CST Sender: list-mgr@WKUVX1.WKU.EDU From: bg@dymaxion.ns.ca (Ben Armstrong) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Gateway to FaxJr fax processor Message-ID: <1994Jan9.093523.3377@dymaxion.ns.ca> Date: 9 Jan 94 13:35:23 GMT To: MX-List@WKUVX1.WKU.EDU In article <19079886@MVB.SAIC.COM>, "G. Del Merritt" writes: >>How do I gateway mail messages to my local fax processor, FaxJr? >> >>FaxJr expects addresses of the form: >> >>FAXJR!6095551212 >> >>This works locally because the comment gets preserved so that FaxJr >>can use it. But if I try to send such an address through MX, the >>comment gets lost, or it gets validated as part of the username >>depending on where I put it. None of the following work: > > This "feature" of FAX Jr. (and of it's big brother, FAX Sr., which I have) is > a clever hack, but I think you would be better off buying the "real" foreign > mail interface that Omtool will happily sell you. The other suggestions are > all interesting, but continue to work with the fact that you are using the > "fact" that VMS MAIL is preserving the "comment" you made in your original > message in the text it sends to the recipient, in this case the user "FAXJR". > > If you want to avoid the expense (which I do believe is actually pretty small > unless you are using FAX Jr. on the uVAX II you bought for $10 o0r your home > ;-), then you can look at how FAXJR_MAIL.COM does it's job. I modified mine > to make use of parameter files, for example. You could, for instance, have > the command file parse the message text to pull out the destination fax > numbers and addressees. > > For grins, I would have attached a copy of my modified version of the file > FAXSR_MAIL.COM, which works with FAXSR version 3.0, after my signature. > Unfortunately, it is copyrighted by Omtool, so if you are interested, contact > me directly via mail and we'll work something out. > > Del Merritt del@IntraNet.com ccavax!giant!del > IntraNet, Inc., One Gateway Center, Newton, MA 02158 > Voice: 617-527-7020; FAX: 617-527-6779 Thanks very much. I'll be in touch. And thanks to all who gave their suggestions. Ben. -- Ben Armstrong (INTP), Software Development, bus: (902)422-1973 Dymaxion Research Ltd., fax: (902)421-1267 Halifax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca ================================================================================ Archive-Date: Mon, 10 Jan 1994 19:46:33 CST Sender: list-mgr@WKUVX1.WKU.EDU From: cooper@utsph.sph.uth.tmc.edu Subject: MX on AXP "local" process keeps dying Date: 11 Jan 1994 00:36:34 GMT Message-ID: <2gssai$np9@oac4.hsc.uth.tmc.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Hello, I'm running MX version 3.3 on our ALPHA 7610 using DEC's UCX as our TCP/IP transport. For some reason, the MX_LOCAL process keeps dying and thus we get a lot of mail jam-ups. Has anyone else experenced this problem and if so were you able to fix it? Thanks for your help in advance Charlie cooper@utsph.sph.uth.tmc.edu ================================================================================ Archive-Date: Mon, 10 Jan 1994 19:58:41 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 10 Jan 1994 20:54:18 EST From: koenig@CVAX.IPFW.INDIANA.EDU Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00978583.547C2730.12480@CVAX.IPFW.INDIANA.EDU> Subject: RE: MX on AXP "local" process keeps dying > From: cooper@utsph.sph.uth.tmc.edu > > Hello, > I'm running MX version 3.3 on our ALPHA 7610 using DEC's UCX as our > TCP/IP transport. For some reason, the MX_LOCAL process keeps dying > and thus we get a lot of mail jam-ups. Has anyone else experenced > this problem and if so were you able to fix it? > > Thanks for your help in advance > > Charlie > > cooper@utsph.sph.uth.tmc.edu While I'm not running an AXP system, perhaps I can still help. Have you considered turning on the Local process debug mode? Just define the logical MX_LOCAL_DEBUG in the system logical table and the Local process will create a log file for each message it handles. These will be created in the Local process's directory in the MX directory structure. For example, $ define/system/exec MX_LOCAL_DEBUG "TRUE" Then look in the Local directory. The log files may help you find a corrupted message entry in the index file or some other oddity. Good luck! ---Greg --------------------------------------------------------------------------- Greg Koenig koenig@cvax.ipfw.indiana.edu Systems Programmer koenig@ipfwcvax.bitnet Indiana University - Purdue University koenig@smtplink.ipfw.indiana.edu Fort Wayne, Indiana (219) 481-6031 --------------------------------------------------------------------------- ================================================================================ Archive-Date: Tue, 11 Jan 1994 05:51:18 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 11 Jan 1994 05:49:31 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009785CE.1924D560.22@ALPHA.WKU.EDU> Subject: RE: MX on AXP "local" process keeps dying cooper@utsph.sph.uth.tmc.edu writes: > >Hello, >I'm running MX version 3.3 on our ALPHA 7610 using DEC's UCX as our >TCP/IP transport. For some reason, the MX_LOCAL process keeps dying >and thus we get a lot of mail jam-ups. Has anyone else experenced >this problem and if so were you able to fix it? > Have you installed the second Mandatory OpenVMS AXP Update? (I think that's the one.) Another site was having problems and discovered that the second MUP replaced MAILSHR, etc., and those apparently have problems. He replaced those with the original OpenVMS AXP V1.5 images and all is fine again. I've had no such problems here, and no one else has reported them. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 11 Jan 1994 07:35:01 CST Sender: list-mgr@WKUVX1.WKU.EDU From: (Martin Egger) Subject: Re: MX on AXP "local" process keeps dying Message-ID: <1994Jan11.080542.20176@aragorn.unibe.ch> Reply-To: MX-List@WKUVX1.WKU.EDU Date: Tue, 11 Jan 1994 08:05:42 GMT To: MX-List@WKUVX1.WKU.EDU In article <2gssai$np9@oac4.hsc.uth.tmc.edu>, cooper@utsph.sph.uth.tmc.edu writes: >I'm running MX version 3.3 on our ALPHA 7610 using DEC's UCX as our >TCP/IP transport. For some reason, the MX_LOCAL process keeps dying >and thus we get a lot of mail jam-ups. Has anyone else experenced >this problem and if so were you able to fix it? Have you installed the AXPMUP02 (security patches)? If yes, then replace the new MAIL.EXE, MAIL_SERVER.EXE, MAILSHR.EXE and MAILSHRP.EXE with the ones from the standard 1.5 release (6-MAY-1993). My MX_LOCAL (and my POP3 Server) started using up memory and then dying about once to twice a day after I installed the MUP. After I replaced the new versions of the MAIL*.EXE with the old ones last week, everything seems to work fine again. Martin ******************************************************************************* Martin Egger, Ph.D., Computing Services - Head of System/User Support Group University of Bern, Gesellschaftsstrasse 6, CH-3012 Bern, Switzerland Phone: ++41 (0)31 631 38 45, Fax: ++41 (0)31 631 38 65, Telex: 912643 pibe ch RFC: egger@id.unibe.ch, X.400: S=egger;OU=id;O=unibe;P=switch;A=arcom;C=ch; HEPNET/SPAN: 20579::49202::egger, DECnet (Switzerland): 49202::egger ******************************************************************************* ================================================================================ Archive-Date: Tue, 11 Jan 1994 07:35:06 CST Sender: list-mgr@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: MX on AXP "local" process keeps dying Date: 11 Jan 1994 11:31:07 GMT Message-ID: <2gu2lr$h0r@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <2gssai$np9@oac4.hsc.uth.tmc.edu>, cooper@utsph.sph.uth.tmc.edu writes: =Hello, =I'm running MX version 3.3 on our ALPHA 7610 using DEC's UCX as our =TCP/IP transport. For some reason, the MX_LOCAL process keeps dying =and thus we get a lot of mail jam-ups. Has anyone else experenced =this problem and if so were you able to fix it? Well, that's very difficult to say, since you're apparently too stupid to RTFM. Had you done so, you would undoubtedly at least posted the contents of the MX Local process' log file, and more than likely have enabled debugging for that process, and posted the corresponding output. However, since you apparently think that that information's irrelevent, it's unlikely that anybody can be of much help to you. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Tue, 11 Jan 1994 07:35:34 CST Sender: list-mgr@WKUVX1.WKU.EDU From: (Martin Egger) Subject: Re: MX on AXP "local" process keeps dying Message-ID: <1994Jan11.121843.1157@aragorn.unibe.ch> Reply-To: MX-List@WKUVX1.WKU.EDU Date: Tue, 11 Jan 1994 12:18:43 GMT To: MX-List@WKUVX1.WKU.EDU In article <2gu2lr$h0r@gap.cco.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: >In article <2gssai$np9@oac4.hsc.uth.tmc.edu>, cooper@utsph.sph.uth.tmc.edu writes: >=I'm running MX version 3.3 on our ALPHA 7610 using DEC's UCX as our >=TCP/IP transport. For some reason, the MX_LOCAL process keeps dying >=and thus we get a lot of mail jam-ups. Has anyone else experenced >=this problem and if so were you able to fix it? > >Well, that's very difficult to say, since you're apparently too stupid to RTFM. >Had you done so, you would undoubtedly at least posted the contents of the MX >Local process' log file, and more than likely have enabled debugging for that >process, and posted the corresponding output. However, since you apparently >think that that information's irrelevent, it's unlikely that anybody can be of >much help to you. If it's really the same problem as we had here, then there is no relevant information in the Local process log. We had to extract the exit code of the Local process from the accounting, which was an ACCVIO. Martin ******************************************************************************* Martin Egger, Ph.D., Computing Services - Head of System/User Support Group University of Bern, Gesellschaftsstrasse 6, CH-3012 Bern, Switzerland Phone: ++41 (0)31 631 38 45, Fax: ++41 (0)31 631 38 65, Telex: 912643 pibe ch RFC: egger@id.unibe.ch, X.400: S=egger;OU=id;O=unibe;P=switch;A=arcom;C=ch; HEPNET/SPAN: 20579::49202::egger, DECnet (Switzerland): 49202::egger ******************************************************************************* ================================================================================ Archive-Date: Tue, 11 Jan 1994 07:53:01 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 11 Jan 1994 04:45:19 PST From: Pat Murphy - (415)329-4044 Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: pmurphy@isdmnl.wr.usgs.gov Message-ID: <009785C5.20F78EE4.32528@isdmnl.wr.usgs.gov> Subject: RE: addresses with no domain name MX list readers: Sorry to have failed to reply on your informative mail on the following bullet: >Having just converted from Multinet's SMTP to MX, it was reported by >some of our POP3 clients, which were accustomed to using the MX host >for the SMTP server, that they were having problems with RCPT TO >addresses with no domain name. Users have become accustomed to doing >this for the convenience. I was surprised to learn than POP3 clients >such as Eudora did not fully qualify the address before sending it. >Testing showed that MX refused these addresses with a nuisance 501 >address syntax error, while Multinet's SMTP was more forgiving of >the the syntax. I acknowledge that this is invalid syntax. As a >patch, I tried to DEFINE PATH "" LOCAL, hoping that this would solve >the problem, but it did not, most likely because the syntax >processing happens before the PATH routing occurs. Any ideas? I took on a horrible case of influenza, and haven't been out of bed for two weeks. To answer a few questions, the POP3 client, has nothing at all to do with this problem. It is the SMTP server side of the Eudora application which is failing. When the user configures the application, his POP3 server and SMTP server are normally one and the same and injects the confusion into his usage of the application, namely the idea of using usernames when sending mail to his fellow Eudora users of that SMTP server. With Multinet's SMTP server, there was never a problem. Modifying the Eudora application to fully qualify the addresses is the ideal solution. Modifying the MX SMTP server code to allow for a painless migration from Multinet's SMTP server would eliminate the need to worry about possible conflicts with other POP3 clients. Eudora is the only one reported to me so far. This is what I would like to see. The suggestion to configure the Bind server, which is also the same as the POP3 server, to provide default domain information, sounds promising as a quick fix, and I will look into it. Thanks again. Hope you all got your flu shots. Patrick W. Murphy, Ph.D. Computer Scientist US Geological Survey IP - pmurphy@isdmnl.usgs.gov. NSINET - isdmnl::pmurphy BITNET - pmurphy@usgsresv Ph: (415)329-4044 ================================================================================ Archive-Date: Wed, 12 Jan 1994 16:58:40 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 12 Jan 1994 23:51:37 +0100 From: "GWDGV1::MOELLER" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: elementary BASE64 decoder For the curious, here's the basic C code to decode a file coded in "MIME"s BASE64 format (RFC1341). Applying MX's FDL-description to the output file is left as an exercise for the reader ... Wolfgang J. Moeller, Tel. +49 551 201516 or -510, GWDG, D-37077 Goettingen, F.R.Germany PSI%(0262)45050352008::MOELLER Disclaimer: No claim intended! | ----- D-B64.C ----------------------------------------------------------------- /* decode BASE64 stdin => stdout */ #include static unsigned char b64_bin[256]; /* => 0..63, pad=64, inv=65, else ign */ /***/ /* setup B64 (ascii) => binary table */ static void init_b64bin(void) { int i,j; for(i = 0; i <= 32; i++) b64_bin[i] = 66; /* ignore controls */ for(i = 33; i < 127; i++) b64_bin[i] = 65; /* printable => inv */ for(i = 127; i <= 160; i++) b64_bin[i] = 66; /* ignore controls */ for(i = 161; i < 256; i++) b64_bin[i] = 65; /* printable => inv */ j = 0; for(i = 'A'; i <= 'Z'; i++, j++) b64_bin[i] = j; for(i = 'a'; i <= 'z'; i++, j++) b64_bin[i] = j; for(i = '0'; i <= '9'; i++, j++) b64_bin[i] = j; b64_bin['+'] = j++; b64_bin['/'] = j++; b64_bin['='] = 64; } /* get next 6-bit group, or pad */ static int GNC_b64bin(unsigned int *ip) { int c; do { c = getchar(); if(c == EOF) return EOF; *ip = b64_bin[c & 0xFF]; } while(*ip > 65); return 0; } /* decode => stdout */ static void do_decode(void) { int/*logical*/ done; unsigned int v6; unsigned int v24; /* room for >= 24 bits */ #define ERROR exit(2) done = 0; while(GNC_b64bin(&v6) != EOF) { if(done) ERROR; /* bytes following pad */ if(v6 > 63) ERROR; v24 = v6; if(GNC_b64bin(&v6) == EOF) ERROR; if(v6 > 63) ERROR; v24 = (v24 << 6) | v6; putchar((v24 >> (2*6-8)) & 0xFF); if(GNC_b64bin(&v6) == EOF) ERROR; if(v6 > 64) ERROR; /* invalid */ if(v6 == 64) { /* pad after 1 char */ done = 1; if(GNC_b64bin(&v6) == EOF) ERROR; if(v6 != 64) ERROR; } else { v24 = (v24 << 6) | v6; putchar((v24 >> (3*6-16)) & 0xFF); if(GNC_b64bin(&v6) == EOF) ERROR; if(v6 > 64) ERROR; /* invalid */ if(v6 == 64) { /* pad after 2 char */ done = 1; } else { putchar(((v24 << 6) | v6) & 0xFF); } } } exit(0); } main(int argc, char **argv) { #ifdef VAXC redirect(&argc,&argv); #endif init_b64bin(); do_decode(); } ----- cut here ---------------------------------------------------------------- Wolfgang J. Moeller, Tel. +49 551 201516 or -510, GWDG, D-37077 Goettingen, F.R.Germany PSI%(0262)45050352008::MOELLER Disclaimer: No claim intended! | ================================================================================ Archive-Date: Thu, 13 Jan 1994 21:33:24 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Can MX keep fileserv requests? Message-ID: <1994Jan13.151049.328@ondec.lonestar.org> From: d_north@ondec.lonestar.org (David G. North, CCP) Reply-To: MX-List@WKUVX1.WKU.EDU Date: 13 Jan 94 15:10:49 CDT To: MX-List@WKUVX1.WKU.EDU In article <1994Jan13.120356.327@ondec.lonestar.org>, d_north@ondec.lonestar.org (David G. North, CCP) wrote: > Is is possible to get MX to keep the mail messages that are sent > to a fileserver for future perusal by the fileserv-mgr? > > 'twould be nice. I was looking for a log of what had been transmitted. Stoopid me. I missed the fileserv_log.log file in mx_mlf_dir:. Wayne Sewell (wayne@tachyon.com), was kind enough to point out my oversight. Thank you Wayne. -- David G. North, CCP, D_North@Ondec.Lonestar.Org {...!letni!tachyon!ondec...} "It's a shame ignorance isn't painful." ================================================================================ Archive-Date: Fri, 14 Jan 1994 00:17:08 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Thu, 13 Jan 1994 22:07:51 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <009787E9.1A00D160.25729@Data.Basix.COM> Subject: Re: Can MX keep fileserv requests? d_north@ondec.lonestar.org (David G. North, CCP) wrote: > > Is it possible to get MX to keep the mail messages that are sent > > to a fileserver for future perusal by the fileserv-mgr? > Stoopid me. I missed the fileserv_log.log file in mx_mlf_dir:. Wayne > Sewell (wayne@tachyon.com), was kind enough to point out my oversight. I too had wondered the same thing for a long time, I "discovered" this wonderful item myself a week or two ago. I'm using MX to service requests for additional information in my DEC Professional "Internet Resource Guide" column, which, coincidentally, starts this month by highlighting: MX! I got to wondering how many people were requesting the additional information on a daily basis, so I wrote a relatively short .COM file which will summarize the contents of the log file. For example, to find out how many people requested the Internet Resource Guide info for January, 1994, I type: $ @FILESERV_SUM IRG.1994-01 since the users are (eventually) instructed to use SEND IRG.1994-01 I get an output like this: Requests for string: IRG.1994-01 Date: Tue 4-JAN-1994 Requests: 5 Date: Wed 5-JAN-1994 Requests: 3 Date: Thu 6-JAN-1994 Requests: 9 Date: Fri 7-JAN-1994 Requests: 6 Date: Mon 10-JAN-1994 Requests: 4 Date: Tue 11-JAN-1994 Requests: 7 Date: Wed 12-JAN-1994 Requests: 4 Date: Thu 13-JAN-1994 Requests: 3 Total Requests: 41 Notes: it creates a temporary file SYS$LOGIN:DP.TMP, and it runs at the speed of DCL... ;)} Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ============================================= FILESERV_SUM.COM - 29 lines $ on control_y then goto control_y $ search mx_mlf_dir:fileserv_log.log /out=sys$login:dp.tmp - "''p1'" $ lastdate = "" $ count = 0 $ grand = 0 $ write sys$output " Requests for string: ",p1 $ open/read dp sys$login:dp.tmp $next: $ read/end=nomore dp rec $ date = f$extract(0,11,rec) $ if date .eqs. lastdate then goto same $ if lastdate .eqs. "" then goto first_rec $ day = f$cvt(lastdate,,"Weekday") $ write sys$output f$fao("Date: !3AS !AS Requests: !4UL",day,lastdate,count) $ count = 0 $first_rec: $ lastdate = date $same: $ count = count + 1 $ grand = grand + 1 $ goto next $control_y: $ write sys$output "Control-Y detected... count will be incomplete..." $nomore: $ day = f$cvt(lastdate,,"Weekday") $ write sys$output f$fao("Date: !3AS !AS Requests: !4UL",day,lastdate,count) $ write sys$output f$fao(" Total Requests: !4UL",grand) $ close dp ================================================================================ Archive-Date: Fri, 14 Jan 1994 06:22:24 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 14 Jan 1994 06:16:43 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: FSUPDATE@WKUVX1.WKU.EDU CC: BARBE@EPS.SINET.SLB.COM, MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097882D.651052F4.16@ALPHA.WKU.EDU> Subject: VMS Mail "@" patch for OpenVMS AXP V1.5!!! He's done the impossible!! Claude Barbe, original author of the popular "@" patch for VMS Mail, which lets you omit the MX%"", SMTP%"", etc., when sending mail to Internet addresses, has now done the impossible. Claude has just released a version of his patch for OpenVMS AXP V1.5!!! I'm amazed. Thanks, Claude!!!! The patch is specific to OpenVMS AXP V1.5---this version will not work under V1.0 or T2.0-FT3. The DEC C compiler is required for the installation to work---I have not included binaries for this package. Claude's patch is available via e-mail and anonymous ftp. You can get it via anonymous ftp from ftp.spc.edu; you'll need: [.MACRO32]UNZIP.EXE or UNZIP.ALPHA_EXE [.MACRO32.SAVESETS]PATCH_MAILSHR_ON_VMS_N_AXP_1_5.ZIP To get it via e-mail, send the following commands in the body of a mail message to FILESERV@WKUVX1.WKU.EDU: SEND PATCH_MAILSHR_ON_VMS_N_AXP_1_5 !Comes as 2 60-block files SEND FILESERV_TOOLS !Needed if you don't have MFTU and UNZIP Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 14 Jan 1994 07:44:18 CST Sender: list-mgr@WKUVX1.WKU.EDU From: cschua@iss.nus.sg (Chua Choon Seng - pzwang) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: reroute Date: 14 Jan 1994 13:02:09 GMT Message-ID: <2h654h$o7@holodeck.iss.nus.sg> To: MX-List@WKUVX1.WKU.EDU Is it possible to auto route all my mails from vax account to unix one.? If so , how ? ================================================================================ Archive-Date: Fri, 14 Jan 1994 08:30:35 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 14 Jan 1994 15:15:32 CET From: Hans-Joachim Koch Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU CC: sys_hjk@LISSY1.lif.de Message-ID: <00978878.AAA06340.10885@LISSY1.LIF.DE> Subject: Reason for X-MX-Warning? Hello all, below is a complete mail header. We checked already the appropriate RFC, but could not find any reason for the "X-MX-Warning". Could someone please give us an idea? Thanks. Hans. > Return-Path: > Received: from lif.de (sunny.lif.de) by lissy1.lif.de (MX V3.3 VAX) with SMTP; > Wed, 12 Jan 1994 17:06:19 CET > Received: from zd001.lif.de by lif.de (4.1/SMI-4.1) id AA02204; Wed, 12 Jan 94 > 17:12:22 +0100 > From: zdtwa@sunny (Theo Wawers / ZD) > Message-ID: <9401121612.AA02204@lif.de> > Subject: Root Passwort auf den Unix Maschinen > X-MX-Warning: Warning -- Invalid "To" header. > To: zdhjk (Hans-Joachim Koch), zdukr (Uta Karle-Rades) > Date: Wed, 12 Jan 1994 17:02:36 +0100 (MET) > X-Mailer: ELM [version 2.4 PL2] > MIME-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Length: 459 -- Hans-Joachim Koch, Computer department of Lahmeyer International Lyoner Strasse 22, D-60528 Frankfurt, Germany Phone: +49 (69) 6677-642, Fax: +49 (69) 6677-388, Tx: 413478 li d ================================================================================ Archive-Date: Fri, 14 Jan 1994 09:00:02 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 14 Jan 1994 08:59:35 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00978844.25B053C2.4@ALPHA.WKU.EDU> Subject: RE: Reason for X-MX-Warning? Hans-Joachim Koch writes: > >Hello all, > >below is a complete mail header. We checked already the appropriate RFC, >but could not find any reason for the "X-MX-Warning". > >Could someone please give us an idea? > Because it's an invalid "To:" header. 8-) >> X-MX-Warning: Warning -- Invalid "To" header. >> To: zdhjk (Hans-Joachim Koch), zdukr (Uta Karle-Rades) RFC822 says that addresses must be in the form user@domain and these aren't. Therefore, MX flags it as being an invalid header. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 14 Jan 1994 09:30:50 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 14 Jan 1994 07:25:25 PST From: Mike Johnson (415) 594-3530 Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: mcjohnson@wizard.farinon.harris.com Message-ID: <00978836.FE010400.3322@wizard.farinon.harris.com> Subject: RE: reroute > Is it possible to auto route all my mails from vax account to unix > one.? If so , how ? If I understand your question correctly, this is what you would do in VMS Mail: $ MAIL MAIL> SET FORWARD MX%"""@""" MAIL> SHO ALL Check the output of the SHO ALL and make sure the forward line appears to be correct. It will now appear with only one (1) set of quotes. MAIL> SEND Do this to test it. Hope this is what you were looking for. Mike ------------------------------------------------------------------------------- Michael Johnson Harris Corp./Farinon Div. 1691 Bayport Ave., San Carlos, CA 94070-5307 (Voice) 415 594-3530 (FAX) 415 594-3777 (Internet) mcjohnson@wizard.farinon.harris.com ------------------------------------------------------------------------------ ================================================================================ Archive-Date: Fri, 14 Jan 1994 09:41:41 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 14 Jan 1994 08:35:57 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <00978840.D8AE5FE0.25867@Data.Basix.COM> Subject: RE: Reason for X-MX-Warning? > below is a complete mail header. We checked already the appropriate RFC, > but could not find any reason for the "X-MX-Warning". > > X-MX-Warning: Warning -- Invalid "To" header. > > To: zdhjk (Hans-Joachim Koch), zdukr (Uta Karle-Rades) It's because the header doesn't conform to the Internet-standard RFC-822 mail address format. The sender's software needs some tweaking if it's going to operate well on the Internet! The generated return and from addresses are bad too: > > Return-Path: > > From: zdtwa@sunny (Theo Wawers / ZD) Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Fri, 14 Jan 1994 13:14:00 CST Sender: list-mgr@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Reason for X-MX-Warning? Date: 14 Jan 1994 18:34:25 GMT Message-ID: <2h6ojh$rrn@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19279321@MVB.SAIC.COM>, Hans-Joachim Koch writes: =Hello all, = =below is a complete mail header. We checked already the appropriate RFC, =but could not find any reason for the "X-MX-Warning". = =Could someone please give us an idea? Check RFC822. In particular, check out section 6, ADDRESS SPECIFICATION: address = mailbox ; one addressee / group ; named list ... mailbox = addr-spec ; simple address / phrase route-addr ; name & addr-spec ... addr-spec = local-part "@" domain ; global address Now look at the To: line in your header: => X-MX-Warning: Warning -- Invalid "To" header. => To: zdhjk (Hans-Joachim Koch), zdukr (Uta Karle-Rades) Neither address contains the "@domain" part, which is required for a valid address. -------------------------------------------------------------------------------- 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, 14 Jan 1994 14:20:22 CST Sender: list-mgr@WKUVX1.WKU.EDU From: wayne@tachyon.com (Wayne Sewell) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Can MX keep fileserv requests? Message-ID: <1994Jan14.103848.957@tachyon.com> Date: 14 Jan 94 10:38:48 CST To: MX-List@WKUVX1.WKU.EDU In article <19271283@MVB.SAIC.COM>, "Ray Harwood -- Data Basix: (602)721-1988" writes: > d_north@ondec.lonestar.org (David G. North, CCP) wrote: > >> > Is it possible to get MX to keep the mail messages that are sent >> > to a fileserver for future perusal by the fileserv-mgr? >> Stoopid me. I missed the fileserv_log.log file in mx_mlf_dir:. Wayne >> Sewell (wayne@tachyon.com), was kind enough to point out my oversight. > > I too had wondered the same thing for a long time, I "discovered" this > wonderful item myself a week or two ago. I'm using MX to service requests for > additional information in my DEC Professional "Internet Resource Guide" column, > which, coincidentally, starts this month by highlighting: MX! > > I got to wondering how many people were requesting the additional information > on a daily basis, so I wrote a relatively short .COM file which will summarize > the contents of the log file. For example, to find out how many people > requested the Internet Resource Guide info for January, 1994, I type: > $ @FILESERV_SUM IRG.1994-01 > since the users are (eventually) instructed to use SEND IRG.1994-01 > I get an output like this: [output deleted] > Ray [command procedure deleted] I did something similar. I maintain a file server for Del Rey Books (a science fiction publisher), containing current and back issues of the Del Rey Internet Newsletter. Every month, I send statistics to the Del Rey editor who writes the newsletter, informing her of how many people asked for each particular issue. It looks like this (the counts are low because this is normally done at the end of the month, not the middle): Transactions: 22 Help requests: 6 List requests: 1 Requests for current newsletter (January): 8 Requests for April 93 newsletter: 1 Requests for December 93 newsletter: 5 Requests for February 93 newsletter: 1 Requests for June 93 newsletter: 1 Requests for March 93 newsletter: 1 Requests for May 93 newsletter: 1 Requests for November 93 newsletter: 1 Requests for October 93 newsletter: 1 -------------------------------------------------------------------------- In order to do this, I have to keep the logs for a whole month. To save disk space, I zip the current log whenever I reset MX (the only time the log file is closed), then delete it. I use the time stamp to give the log file a unique name. I think that zip can store multiple version of the same file name if you tell it to, but I didn't know that when I wrote this. ----------- file mx_mlf_dir:getlog.com ----------------------------- $ set ver $ set noon $ datetime := 'f$time()' $ date := 'f$extract(0,6,datetime)'x $ bl_pos = 'f$locate(" ",datetime)' $ time := 'f$extract(bl_pos,20,datetime)' $ hour = 'f$extract(0,2,time)' $ min = 'f$extract(3,2,time)' $ sec = 'f$extract(6,2,time)' $ hund = 'f$extract(9,2,time)' $ stamp := 'date'_'hour'_'min'_'sec'_'hund $ ren dka300:[mx.mlf]fileserv_log.log *.'stamp' $ zip = "$dka200:[utilities]zip.exe" $ zip dka300:[mx.mlf]delrey_server_log dka300:[mx.mlf]fileserv_log.'stamp' $ del dka300:[mx.mlf]fileserv_log.'stamp'; ---------------------------------------------------------------------- Then I use the following two command procedures to create the monthly report: ----------- file util:scan_log.com ----------------------------- $ set nover $ set def [hold_area] $ unzip -j mx_mlf_dir:delrey_server_log $ @util:do_search/out=aaatrans.stat "File server DELREY" "Transactions" $ @util:do_search/out=bbbhelp.stat "FILESERV_HELP.TXT" "Help requests" $ @util:do_search/out=ccclist.stat "LIST result" "List requests" $ @util:do_search/out=dddcurrent.stat newsletter.curr "Requests for current newsletter (''p1')" $ @util:do_search/out=eeejan93.stat newsletter_93.january "Requests for January 93 newsletter" $ @util:do_search/out=eeefeb93.stat newsletter_93.february "Requests for February 93 newsletter" $ @util:do_search/out=eeemar93.stat newsletter_93.march "Requests for March 93 newsletter" $ @util:do_search/out=eeeapr93.stat newsletter_93.april "Requests for April 93 newsletter" $ @util:do_search/out=eeemay93.stat newsletter_93.may "Requests for May 93 newsletter" $ @util:do_search/out=eeejun93.stat newsletter_93.june "Requests for June 93 newsletter" $ @util:do_search/out=eeejul93.stat newsletter_93.july "Requests for July 93 newsletter" $ @util:do_search/out=eeeaug93.stat newsletter_93.august "Requests for August 93 newsletter" $ @util:do_search/out=eeesep93.stat newsletter_93.september "Requests for September 93 newsletter" $ @util:do_search/out=eeeoct93.stat newsletter_93.october "Requests for October 93 newsletter" $ @util:do_search/out=eeenov93.stat newsletter_93.november "Requests for November 93 newsletter" $ @util:do_search/out=eeedec93.stat newsletter_93.december "Requests for December 93 newsletter" $ @util:do_search/out=eeeaaaback93.stat newsletter_93.description "Requests for all 93 issues" $ @util:do_search/out=eeeaaaback93z.stat newsletter_93_zipped.description "Requests for all 93 issues (zipped)" $ @util:do_search/out=eeejan94.stat newsletter_94.january "Requests for January 94 newsletter" $ @util:do_search/out=eeefeb94.stat newsletter_94.february "Requests for February 94 newsletter" $ @util:do_search/out=eeemar94.stat newsletter_94.march "Requests for March 94 newsletter" $ @util:do_search/out=eeeapr94.stat newsletter_94.april "Requests for April 94 newsletter" $ @util:do_search/out=eeemay94.stat newsletter_94.may "Requests for May 94 newsletter" $ @util:do_search/out=eeejun94.stat newsletter_94.june "Requests for June 94 newsletter" $ @util:do_search/out=eeejul94.stat newsletter_94.july "Requests for July 94 newsletter" $ @util:do_search/out=eeeaug94.stat newsletter_94.august "Requests for August 94 newsletter" $ @util:do_search/out=eeesep94.stat newsletter_94.september "Requests for September 94 newsletter" $ @util:do_search/out=eeeoct94.stat newsletter_94.october "Requests for October 94 newsletter" $ @util:do_search/out=eeenov94.stat newsletter_94.november "Requests for November 94 newsletter" $ @util:do_search/out=eeedec94.stat newsletter_94.december "Requests for December 94 newsletter" $ @util:do_search/out=eeeaaaback94.stat newsletter_94.description "Requests for all 94 issues" $ @util:do_search/out=eeeaaaback94z.stat newsletter_94_zipped.description "Requests for all 94 issues (zipped)" $ copy *.stat x.x $ open/read infile x.x $ open/write outfile stats.lis $ write outfile "" $ write outfile "Monthly statistics for Del Rey file server" $ write outfile "" $ write outfile "Compiled ''f$time()'" $ write outfile "" $ write outfile "This mail message was automatically generated by software. $ write outfile "" $ write outfile "Note: When someone requests all newsletters for a given year," $ write outfile "the request-for-all count is incremented, and so is the" $ write outfile "count for each individual issue. Therefore, such issues are" $ write outfile "counted twice. Conversely, subtracting the indiviual issue count" $ write outfile "from the request-for-all count will give you the number of times that" $ write outfile "issue was explicitly requested." $ write outfile "" $ write outfile "Note #2: There are no longer two separate counts for the current issue," $ write outfile "newsletter_yy.mmm and newsletter.current. The current issue is no longer" $ write outfile "available in the newsletter_yy.mmm form." $ write outfile "" $ loop: $ read/end=thats_all infile curr_line $ linelen = 'f$length(curr_line)' $ if linelen .eq. 0 then goto loop $ short_line := "''f$extract(0,40,curr_line)'" $ count = 0 $ xxx_pos = 'f$locate("xxx",curr_line)' $ match_pos = 'f$locate("Records matched:",curr_line)' ne)'" $ if match_pos .eq. 0 then count = 'f$extract(20,80,short_line)' $ if count .eq. 0 then goto loop $ write sys$output curr_ident,": ",count $ write outfile curr_ident,": ",count $ goto loop $ thats_all: $ close infile $ close outfile $ type stats $ del *.stat;* $ del fileserv_log.*;* $ del x.x;* ---------------------------------------------------------------------- ----------- file util:do_search.com ----------------------------- $ write sys$output "xxx",p2 $ search/stat/match=and/wind=0/nooutput fileserv*.* "DELREY","''p1'" ---------------------------------------------------------------------- They aren't pretty, but they do work. I delete the zip file manually, instead of in the procedure, in case something screws up. -- ============================================================================== Wayne Sewell |INET: wayne@tachyon.com Tachyon Software Consulting |UUCP: uupsi!uupsi6!tachyon!wayne P. O. Box 550937, Dallas TX 75355-0937 |Voice: (214)-553-9760, Fax: -553-0077 ============================================================================= Curly: "I keep tryin' to think, but nuthin' happens!" ================================================================================ Archive-Date: Fri, 14 Jan 1994 14:20:35 CST Sender: list-mgr@WKUVX1.WKU.EDU From: tcomeau@teela.stsci.edu Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX mail incorrectly delivered via MM Message-ID: <1994Jan14.134606.1@teela.stsci.edu> Date: 14 Jan 94 18:46:06 GMT To: MX-List@WKUVX1.WKU.EDU Yesterday I upgraded from MX V3.1 to V3.3, and immediately ran into a problem with delivery of SMTP mail. We use TGV's Multinet, and are currently running V3.2 Rev C. Multinet hasn't been upgraded for some time. One of my users had a MAIL.TXT file in his SYS$LOGIN directory. He did _not_ have a SYS$LOGIN:$HDRS$MAIL.TXT, yet MX delivered his mail to MAIL.TXT using MM. However, since he lacked a header file, the messages were badly scrambled, and couldn't be read using MM. Renaming the MAIL.TXT file to MAIL.SAVED restored the pre-upgrade (correct) behavior. It's not immediately obvious whether this is an MX or MM bug, but since MX changed and Multinet didn't, I'm more suspicious of MX. It's easy to reproduce this behavior: Create a mail.txt in your default directory, and send yourself mail. Has anybody else seen this? (Does anybody know for sure if it's MX or MM?) tc> ----------------------------------------------------------------------------- Tom Comeau | "Good logistics is Combat Power" tcomeau@stsci.edu | -- Lt. Gen. Gus Pagonis, USA Space Telescope Science Institute | 3700 San Martin Drive | Baltimore, MD 21218 | ----------------------------------------------------------------------------- ================================================================================ Archive-Date: Fri, 14 Jan 1994 14:28:20 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 14 Jan 1994 14:26:54 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00978871.DF5C199B.9@ALPHA.WKU.EDU> Subject: RE: MX mail incorrectly delivered via MM tcomeau@teela.stsci.edu writes: > >Yesterday I upgraded from MX V3.1 to V3.3, and immediately ran into a >problem with delivery of SMTP mail. We use TGV's Multinet, and are currently >running V3.2 Rev C. Multinet hasn't been upgraded for some time. > And it comes up again, Dan.... >One of my users had a MAIL.TXT file in his SYS$LOGIN directory. He did _not_ >have a SYS$LOGIN:$HDRS$MAIL.TXT, yet MX delivered his mail to MAIL.TXT using >MM. However, since he lacked a header file, the messages were badly >scrambled, and couldn't be read using MM. Renaming the MAIL.TXT file to >MAIL.SAVED restored the pre-upgrade (correct) behavior. > >It's not immediately obvious whether this is an MX or MM bug, but since MX >changed and Multinet didn't, I'm more suspicious of MX. It's easy to >reproduce this behavior: Create a mail.txt in your default directory, and >send yourself mail. > Old versions of MultiNet did not expect a $HDRS$MAIL.TXT. Since who knows what people will be running, MX had to support the oldest stuff too, hence the problem. V3.4 of MX will allow you to disable all delivery via MM. You can get that now by grabbing the proper .ZIP file in [.MX.BETA] on ftp.spc.edu. Those .EXEs disable delivery via MM. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 14 Jan 1994 15:40:04 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: RE: MX mail incorrectly delivered via MM Message-ID: <1994Jan14.140044.744@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 14 Jan 94 14:00:44 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19290987@MVB.SAIC.COM>, "Hunter Goatley, WKU" writes: >V3.4 of MX will allow you to disable all delivery via MM. You can get >that now by grabbing the proper .ZIP file in [.MX.BETA] on >ftp.spc.edu. Those .EXEs disable delivery via MM. (The docs aren't completed yet, so don't try to have MX V3.4-beta install the docs, like I did. :-)) -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Fri, 14 Jan 1994 21:06:42 CST Sender: list-mgr@WKUVX1.WKU.EDU From: cooper@utsph.sph.uth.tmc.edu Subject: Thanks>>>Mx Local process dying... Date: 15 Jan 1994 02:10:30 GMT Message-ID: <2h7jam$mpt@oac4.hsc.uth.tmc.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Thanks for those of you who were kind enough to respond to by query as to why MX_local process was dying. Thanks also to you Carl for you in-direct way of trying to help. In any case, I have been running the DEBUG which has not given any information as to what is the cause may be as to why the process dies ..randomly (yes Carl, we are all "stupid" at times...but in this case I had run the debug without results and so count give you an information as to the cause) In any case, those of you who responded to possible a mail share violation...I haven't done the latest upgrade...so this does not seem to be the problem. I just keep plugging and hope I can discover what is happening. I have a possible clue that I following...but have to wait till the process dies again to see if I'm right...I'll let you folks know if I find out anything. Again, thanks to those of you who were kind enough to respond. Charles Cooper Director of Research Computing University of Texas School of Public Health cooper@utsph.sph.uth.tmc.edu ================================================================================ Archive-Date: Sat, 15 Jan 1994 11:27:43 CST Sender: list-mgr@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Thanks>>>Mx Local process dying... Date: 15 Jan 1994 07:25:48 GMT Message-ID: <2h85ps$h4t@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <2h7jam$mpt@oac4.hsc.uth.tmc.edu>, cooper@utsph.sph.uth.tmc.edu writes: =Thanks for those of you who were kind enough to respond to by query =as to why MX_local process was dying. Thanks also to you Carl for =you in-direct way of trying to help. In any case, I have been running =the DEBUG which has not given any information as to what is the cause =may be as to why the process dies ..randomly (yes Carl, we are all ="stupid" at times...but in this case I had run the debug without results =and so count give you an information as to the cause) Yes, but only a few are so stupid as to fail to provide the log file (MX_LOCAL_DIR:MX_LOCAL_node.LOG, if I recall correctly) even after they're prompted for it (Note: This log file is generated whether or not you've got debugging enabled; it's the LOCAL agent's SYS$OUTPUT. It will normally contain the error message generated as the process dies). -------------------------------------------------------------------------------- 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, 17 Jan 1994 11:13:48 CST Sender: list-mgr@WKUVX1.WKU.EDU From: williscc@vax.sbu.ac.uk (Christopher C Willis) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: FileServers - how to set up? Message-ID: <1994Jan17.160713.4525@vax.sbu.ac.uk> Date: 17 Jan 94 16:07:13 GMT To: MX-List@WKUVX1.WKU.EDU I know this may be the wrong place to ask or whatever but comments and suggestions are appreciated if they're constructive...but how does one set up a file server? What I mean to ask is can a user do this? I'm not a systems admin person or anything like that so don't hassle me if you need extra priveleges. It's just that working in international affairs, much information which I have to email manually could be done automatically if this were possible. Thanks in advance for the help. Chris Willis International Officer South Bank University, London -- \\|// (o o) __________oOO____(_)____OOo____________________________________________ E-Mail: williscc@vax.sbu.ac.uk Christopher C Willis Home: chris@fire.demon.co.uk ...censored space... _______________________________________________________________________ ================================================================================ Archive-Date: Mon, 17 Jan 1994 11:40:20 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: FileServers - how to set up? Message-ID: <1994Jan17.101310.754@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 17 Jan 94 10:13:09 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <1994Jan17.160713.4525@vax.sbu.ac.uk>, williscc@vax.sbu.ac.uk (Christopher C Willis) writes: >I know this may be the wrong place to ask or whatever but comments and >suggestions are appreciated if they're constructive...but how does one set up a >file server? What I mean to ask is can a user do this? I'm not a systems admin >person or anything like that so don't hassle me if you need extra priveleges. >It's just that working in international affairs, much information which I have >to email manually could be done automatically if this were possible. Hassle Hassle. After the initial setup (which does require privileges), file protections can be set to allow any non-privileged user to manage the file server; it can also be setup to allow certain non-privileged users to manage the file server (instead of everyone on the system!). If your system manager would like information on how to set this up on your system, have him/her post to this newsgroup, or Email me directly, if that is preferred. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Tue, 18 Jan 1994 11:57:20 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 18 Jan 1994 11:55:46 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.BITNET Message-ID: <00978B81.6C61F9B1.17@ALPHA.WKU.EDU> Subject: RE: Receipt confirmation requests Hi, Per. A few months ago, you wrote: >Appreciated. Thinking of how unpredictable the X-header info tends to be, >and the fact that any software producer can use it for whatever purposes, >it would be nice if this filter could be configured locally, like a >KILL_THESE_HEADERS.DAT file. That way we could cope with situations like >this without the need for updates of MX. (You can probably find at least >ten good reasons why not... :-)) > I just thought I'd let you know that MX V3.4, entering beta test today or tomorrow, includes /REMOVE=OTHER for DEFINE/MODIFY list so that all headers not recognized by MX will not be passed on to the list. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 19 Jan 1994 15:35:32 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: MX verses PMDF Message-ID: <1994Jan19.121922.539@earlham.edu> From: michaelb@earlham.edu Reply-To: MX-List@WKUVX1.WKU.EDU Date: Wed, 19 Jan 94 12:19:17 -500 To: MX-List@WKUVX1.WKU.EDU I was wondering if anyone had compared MX 3.3 to PMDF 4.2? I am running MX 3.3 on my vaxstation. I am a member of a vax cluster. The other 3 machines in the cluster are running PMDF 4.2. Our postmaster for the cluster wants to know whether or not to install PMDF on my machine or MX on the cluster? Any thoughts? Michael ---_________________________________________________________________________--- Michael L. Bowden | Voice: (317) 983-1355 Technology/Reference Librarian | Fax: (317) 983-1304 Drawer 198 | Internet: MichaelB@Earlham.Edu Earlham College | Internet: MichaelB@Tian.Earlham.Edu Richmond, Indiana 47374-4095 | ListOwner: LIBMASTR@UOTTAWA ---_________________________________________________________________________--- ================================================================================ Archive-Date: Wed, 19 Jan 1994 16:16:35 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 19 Jan 1994 23:06:31 +0100 From: "GWDGV1::MOELLER" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: memory leak in SMTP_SERVER (3.3) I'm seeing SMTP_SERVER's virtual address space growing without bound ... It died a few times with ACCVIO due to page file quota exhaustion (PGFLQUO is around 32k pages). Particulars: VMS 5.1-1, UCX 1.3A (sorry for the old versions :-) Our Internet connection is pretty flaky lately, so I suspect that the behaviour (not a 'reproducible' growth) has to do with aborted SMTP connections, which at times occur extremely often (as MX_SMTP_SERVER_DEBUG showed me). From SHOW PROCESS/CONTINUOUS it appears that the virtual address space grows in steps of around 200 pages, but I can't correlate those events to SMTP_SERVER's operation (the 200 might also be an artefact caused by LIB$GET_VM always fetching memory in large chunks - not sure about that). I scanned the source (just for LIB${GET,FREE}_VM) and now I think that the FLQ structure is not freed on 'cleanup' after connection abort. Seems unlikely that it alone (1 page) could account for the large steps I've seen, though ... Wolfgang J. Moeller, Tel. +49 551 201516 or -510, GWDG, D-37077 Goettingen, F.R.Germany PSI%(0262)45050352008::MOELLER Disclaimer: No claim intended! | ================================================================================ Archive-Date: Wed, 19 Jan 1994 17:39:46 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 19 Jan 1994 15:33:04 EST From: "vaxst2::nagy_l"@tik.matav.hu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@RPIECSVX.BITNET Message-ID: <00978C68.F21EC7E0.10889@tik.matav.hu> Subject: help help ================================================================================ Archive-Date: Thu, 20 Jan 1994 09:52:08 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Thu, 20 Jan 94 10:36:24 EST From: intrepid!tb@uunet.UU.NET (Tom Barkanic X7264) Reply-To: MX-List@WKUVX1.WKU.EDU Message-ID: <9401201536.AA06765@intrepid.shuttles> To: MX-List@WKUVX1.WKU.EDU Subject: Help! I just installed MX V3.3 and have a few problems and questions. Our setup is that we have a dialup connection to the internet with UUNET through a SUN on our net. We have UCX V2.0 installed on all the VAX's. to send mail out from a VAX we have to address our messages MX-List@WKUVX1.WKU.EDU@intrepid. Were intrepid is the SUN. MX does not like this address. When mail comes in the SUN forwards it to the user on a VAX. When this happens I get the following error sent to the Postmaser on the SUN (aquila is the VAX running MX). ----- Transcript of session follows ----- Connected to aquila: >>> MAIL From: <<< 501 Invalid address: 554 barkanic@aquila... Remote protocol error I also have a question about the "MX network node name" that is asked when installing the software. Only the SUN, intrepid, is registered on the Internet as intrepid.shuttles (shuttles being the domain I believe). Another question is the release notes for MX it states that if you are using UCX you should use your Fully Qualified Domain Name as your primary local host name. What is the FQDN? Do I have one since our VAXs our not on the Internet? When I do a 'show host' within UCX the localhost address is 127.0.0.1 but my node, aquila, is 192.8.200.172 and the SUN's is 192.8.200.7. The bind database is on the SUN so all other VAXs on the net are given the name 'node.shuttles'. I didn't install the original UCX software on the VAXs our SUN administrator did. Thanks for any help. =-=-=-=-=-=-=-=-=-=-=-=-=-=- ! Tom Barkanic ! ! E-Systems, ECI Division ! ! St. Petersburg, FL ! ! intrepid!tb@uunet.uu.net ! =-=-=-=-=-=-=-=-=-=-=-=-=-=- ================================================================================ Archive-Date: Thu, 20 Jan 1994 11:02:12 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Help! Message-ID: <1994Jan20.092055.792@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 20 Jan 94 09:20:54 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19463226@MVB.SAIC.COM>, intrepid!tb@uunet.UU.NET (Tom Barkanic X7264) writes: >I just installed MX V3.3 and have a few problems and questions. Our setup is >that we have a dialup connection to the internet with UUNET through a SUN on >our net. We have UCX V2.0 installed on all the VAX's. to send mail out from >a VAX we have to address our messages MX-List@WKUVX1.WKU.EDU@intrepid. Were >intrepid is the SUN. MX does not like this address. It shouldn't -- that is an invalid address. Try MX-LIST%WKUVX1.WKU.EDU@INTREPID.SHUTTLES.COM (You are only allowed one "@" in an Internet address; you should also fully qualify your addresses). A much, much better solution, though, would be to simply setup your MX PATHs like: DEFINE * SMTP/ROUTE=INTREPID.SHUTTLES.COM and then you can simply address your mail normally -- MX will automatically send all SMTP mail to INTREPID.COM (or whatever the fully-qualified domain name is for your Sun system), and your users will never have to worry about that -- you can address things just like: MX-LIST@WKUVX1.WKU.EDU >I also have a question about the "MX network node name" that is asked when >installing the software. Only the SUN, intrepid, is registered on the Internet >as intrepid.shuttles (shuttles being the domain I believe). If your VAXes aren't known to the Internet, how are you going to get replies back to your VAXes? You at least need MX records pointing to the same host that is handling your Sun's mail (which is on the Internet). As your Sun isn't on the Internet itself (you have a dialup link, I suppose via UUCP?), you don't want MX records pointing to the Sun itself. >Another question is >the release notes for MX it states that if you are using UCX you should use >your Fully Qualified Domain Name as your primary local host name. What is the >FQDN? Your registered domain name. >Do I have one since our VAXs our not on the Internet? When I do a >'show host' within UCX the localhost address is 127.0.0.1 but my node, aquila, >is 192.8.200.172 and the SUN's is 192.8.200.7. The bind database is on the SUN >so all other VAXs on the net are given the name 'node.shuttles'. I didn't >install the original UCX software on the VAXs our SUN administrator did. I assume you got the 192.8.200.0 addresses from the NIC? Actually, it looks like you didn't: $ WHOIS NET 192.8.200 Spartacus Computers Inc. (NETBLK-SPARTACUS) 5 Oak Park Drive Bedford, MA 01730 Netname: SPARTACUS Netblock: 192.8.3.0 - 192.8.255.0 Coordinator: Kodinsky, Edward (EK48) edk@conextions.com (508) 475-5411 If your company ever decides to get a full connection to the Internet, be sure to have your resume updated. If you do get a full connection, you will need to change the IP addresses (and, apparently based on your internal naming standard) and host names of all your systems running IP. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Sat, 22 Jan 1994 08:23:38 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Sat, 22 Jan 1994 15:14:51 CET From: Hans-Joachim Koch Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU CC: sys_hjk@LISSY1.lif.de Message-ID: <00978EC1.E54BEE20.12014@LISSY1.LIF.DE> Subject: Mail2News Gateway with NEWSRDR? We are feeding incoming mailing lists to BULLETIN. Because we are changing our pc server systems from VMS to UNIX, I need an other place to store these mails. Anybody changed bulletin to use it under SUN-OS??? I don't think so, therefore I want to address these mails to local newsgroups. Better ideas? Now I'm looking for a gateway mail to news. All examples in the .contrib subdirectory of mx are using ANU-NEWS. Has anybody done this with the NEWSRDR? It's not that difficult to add a news message via the site path. The only problem is to preserve the original senders address for the news article. Bulletin has a nice subroutine to do this - is there a simple way for NEWSRDR to do the same? Thanks a lot. Hans. -- Hans-Joachim Koch, Computer department of Lahmeyer International Lyoner Strasse 22, D-60528 Frankfurt, Germany Phone: +49 (69) 6677-642, Fax: +49 (69) 6677-388, Tx: 413478 li d ================================================================================ Archive-Date: Sat, 22 Jan 1994 10:41:06 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Mail2News Gateway with NEWSRDR? Message-ID: <1994Jan22.092104.805@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 22 Jan 94 09:21:03 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19535291@MVB.SAIC.COM>, Hans-Joachim Koch writes: >Now I'm looking for a gateway mail to news. All examples in the .contrib >subdirectory of mx are using ANU-NEWS. Has anybody done this with the >NEWSRDR? It's not that difficult to add a news message via the site >path. The only problem is to preserve the original senders address for >the news article. Bulletin has a nice subroutine to do this - is there a >simple way for NEWSRDR to do the same? NEWSRDR is a news reader; ANU-NEWS is a news server. I don't believe it would be possible to get NEWSRDR to perform gateway functions between a mailing list and a newsgroup -- you'd have to implement such a thing on the system running your news server. If that is a Unix machine, you need a Unix solution. BULLETIN hasn't, and I'll bet won't, be ported to Unix. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Sat, 22 Jan 1994 15:29:58 CST Sender: list-mgr@WKUVX1.WKU.EDU From: jspinnow@netcom.com (John Stewart Pinnow) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: How do you multiple forward using MX%,SMTP%, or standard vms Message-ID: Date: Sat, 22 Jan 1994 20:40:10 GMT To: MX-List@WKUVX1.WKU.EDU I would like to send a copy of my mail from a vms machine to a unix machine. I would like it to keep a local copy on the vms machine. What I am after is like this: set forward mx%"jspinnow@myunixmachine",myaccountonthisvmsmachine How do I do this for 1 without creating an infinite loop, and/or bypassing the error message when I typing the above in. -- ____________________________________________________________________________ Tmoh Research Internet: jspinnow@netcom.com Phone: (414) 761-1537 John S. Pinnow jspinnow@world.std.com Disclaim: Opinions==Mine ================================================================================ Archive-Date: Sat, 22 Jan 1994 17:55:15 CST Sender: list-mgr@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: How do you multiple forward using MX%,SMTP%, or standard vms Date: 22 Jan 1994 22:50:36 GMT Message-ID: <2hsajt$5b9@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article , jspinnow@netcom.com (John Stewart Pinnow) writes: = =I would like to send a copy of my mail from a vms machine to a unix =machine. I would like it to keep a local copy on the vms machine. = =What I am after is like this: = =set forward mx%"jspinnow@myunixmachine",myaccountonthisvmsmachine = =How do I do this for 1 without creating an infinite loop, and/or =bypassing the error message when I typing the above in. VMS MAIL doesn't allow lists as forwarding addresses. This is because of a limitation of the MAIL-11 protocol which makes mail delivery to remote mailing lists unreliable. If you can set up forwarding on your unix machine to forward back to the VMS machine as well as keeping a copy there, then, on the VMS machine: MAIL> SET FORWARD mx%"""jspinnow@myunixmachine""" and on the unix machine, set up your mail to keep a copy for itself, and to forward to your account on the VMS machine, but with the username prefixed by an underscore. The underscore tells VMS MAIL to ignore any forwarding for the account. -------------------------------------------------------------------------------- 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, 23 Jan 1994 03:25:36 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Sun, 23 Jan 94 09:34 JST From: "Najman Kahana. Ext:7313" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: WEBSTER To: MX-List@WKUVX1.WKU.EDU Message-ID: <70A47128633F2002A9@HADASSAH.BITNET> Hi. Does anyone know what is a WEBSTER server ? If yes, can you point me to some information or address. Thanks Najman Kahana Najman@hadassah.bitnet ================================================================================ Archive-Date: Sun, 23 Jan 1994 06:14:37 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 21 Jan 1994 01:15:08 EST From: acpwvw!wvwc!wvwc.!programmer@ms.uky.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00978D83.6CACB880.25161@aca.wvwc.edu> Subject: archiving mailing lists & resetting message queue This is 2 questions rolled into one: 1) We have a local discussion list and would like to have the list automagically archive these into a file. The MX033 describes this and I thought I set it up correctly, but nothing seems to get into it. The setup looks like: Mailing lists: Name: COMP-DISC Owner: "PROGRAMMER@ACA.WVWC.EDU" Reply-to: List, NOSender Archive: STU$DISK:[ANONYMOUS.ARCHIVES.COMP-DISC]COMP-DISC.ARCHIVE Add message: MX_MLF_ROOT:[MAILING_LISTS] Remove message: MX_MLF_ROOT:[MAILING_LISTS] Forwarded-to-owner message: MX_MLF_ROOT:[MAILING_LISTS] Description: WVWC General Computer Discussion List Errors-to: PROGRAMMER@ACA.WVWC.EDU Strip header: NOReceived Private list: No Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) Any suggestions? 2) This is not critical but would be helpful. Is there anyway to reset the mail message number of the mx messages? I am getting sick of typing a number in the 10 and hundred thousand (soon to be millions) range. I would also like to have it reset to keep statistics monthly or yearly on the number being processed. TIA! ,`````````````````````````````````````.``````````````````````````````````````, , William G. Howard (O.T.O.) . , , West Virginia Wesleyan College . What we need is a , , acpwvw!wvwc!howard_w@ms.uky.edu . long-term quick fix! , , nroth@wvnvaxa.wvnet.edu . , , (304)473-8318 . -The Wall Street Journal , ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ================================================================================ Archive-Date: Sun, 23 Jan 1994 13:10:20 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Sun, 23 Jan 1994 19:05:07 GMT From: "Jamie Jones, HICOM Operations" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00978FAB.3B163600.1@hicom.lut.ac.uk> Subject: Some Comments on MX V3.4-BETA-1 Hi. Well, I installed V3.4-BETA-1 on friday (as a 'new' installation - i.e. I renamed the V3.3 tree to something else, instead of 'upgrading' it). Here are a few initial comments : 1) MX_SITE_IN now requires SYSLCK to work, but didn't in V3.3. I didn't notice this mentioned in V3.4 installation notes (but forgive me if I missed it) 2) After an hour or so of initial installation, something hung. This made calls to port 25 get accepted, but no output was given by smtp_server. Also, mcp shutdown and reset didn't work. Also, on entering a To: mx% address in MAIL caused MAIL to hang... This was mended by stop/id'ing the processes, and rebooting. Unfortunatly I didn't have debug logs on at this stage, and the process logs only contained the "..... starting " line. Things have been fine since - this was probably just some coincidental fluke, but I thought I'd better mention it. 3) I personally don't like the format of the VMS To: & CC: lines (for those that haven't installed it, they are basically copies of the rfc822 header lines, but in MX% syntax, and on a single line (up to 255 characters maximum length, as usual) It just seems like duplication to me. It can also be messy. Here is a typical message to a list of people (usernames changed to protect the innocent) : | | From: MX%"jamie@hicom.lut.ac.uk" 23-JAN-1994 05:10:35.47 | To: MX%"jamie@dorothy.ibmpcug.co.uk",MX%"jamie@hicom.lut.ac.uk",MX%"xxxxxx@nrd.cf.ac.uk",MX%"xxx@robobar.co.uk",MX%"xxxxxxxxx@hicom.lut.ac.uk",MX%"xxx@hecate.astro.cf.ac.uk",MX%"xxxxxx@nrd.cf.ac.uk",MX%"xxxxxxx@pyr.swan.ac.uk",MX%"xxxxxx@thor.cf.ac.uk" | CC: | Subj: | | Return-Path: | Received: by hicom.lut.ac.uk (MX V3.4-Beta-1 VAX) id 2; Sun, 23 Jan 1994 | 05:09:30 GMT | Sender: jamie@hicom.lut.ac.uk | Date: Sun, 23 Jan 1994 05:09:24 GMT | From: "Jamie Jones, HICOM Operations" | Reply-To: "Jamie Jones" | To: jamie@dorothy.ibmpcug.co.uk, jamie@hicom.lut.ac.uk, | xxxxxx@nrd.cf.ac.uk, xxx@robobar.co.uk, xxxxxxxxx@hicom.lut.ac.uk, | xxx@hecate.astro.cf.ac.uk, xxxxxx@nrd.cf.ac.uk, xxxxxxx@pyr.swan.ac.uk, | xxxxxx@thor.cf.ac.uk, xxx@leicester.ac.uk, xxxxxxxxxx@hicom.lut.ac.uk, | xxxxxxx@deep-thought.ericsson.se, xxxxx@vax-b.physics.liverpool.ac.uk, | xxxxxx@softage.demon.co.uk, xxx@cs.nott.ac.uk, xxxxxxx@hicom.lut.ac.uk, | "xxx::xxxxxxx"@hermes.mod.uk, xxxxxx@tartarus.uwa.edu.au, | xxxxx@westminister.ac.uk, xxxxxxx@brunel.ac.uk, | xxxxxxx@sugalaxy.swan.ac.uk, xxxxxxxx@hicom.lut.ac.uk, | xxx@dcs.edinburgh.ac.uk, xxx@cm.cf.ac.uk, xxxxxxxxxxxx@hicom.lut.ac.uk, | xxxxxxxx@american.edu, xxxxx@ibmpcug.co.uk, xxxxxxxx@hicom.lut.ac.uk, | xxx@dvorak.amd.com, xxxxxx@pyr.swan.ac.uk, | xxx%condor.csd.aberdeen.ac.uk@aberdeen.ac.uk | Message-ID: <00978F36.7CAB0DE0.2@hicom.lut.ac.uk> | X-MX-Warning: VMS Mail To: line does not include all To: addresses | | As can be seen, the VMSMAIL To: line has been truncated at 255 characters anyway. I really think the To: line should contain the username part of all local users specified in the envelope "RCPT TO:" line. E.g. (we are registered as hicom.lut.ac.uk & hicom.org) If the following lines were in one transaction : RCTP TO: RCPT TO: RCPT TO: RCPT TO: I'd expect to see VMSMAIL TO: as "To: jamie_jones, user" Note that "jamie_jones" just does a vmsmail forward to "jamie" but this isn't translated in the "To:" line. (This is so that, for example, I can do "select mail/to=system" - as system mail is forwarded to my 'jamie' account) This is basically how the JANET CBS X29 mail system treats the To: line, with the envelope "To:" data. With both V3.3 & V3.4, there isn't actually a way of definitely telling what the envelope To: line contains (think of a user with many local mail forwards [e.g. "system", "postmaster","xyzlist-owner"] who gets mail from a mailing list [rfc822 "To: " just says To: list-recipients@some.site]) It *would* be handy to be able to do "MAIL> select/to=postmaster" ; "MAIL> delete/all" again ! ;-) 4) The new queue format. The change to this structure is great, on the low level. It's great to be able to do "MCP> queue show/all" and get a continuous output without long delays between entry numbers. (This "continuous output" previously only happened just after Andy Harper's MX_SHRINK program had been run) However, would it be possible to keep an incremental message counter outside the queue structure, so as to give a similar operational effect as in V3.3 ? Maybe with an extra 16bit field in the structure for each queue entry... (Again, for the benefit of those who haven't installed the new version, when a previous queue-number has finished, and been purged, the next queue entry will USE the same number, so you often get mesage 1 queued etc...) With V3.4 reusing entry-numbers, you get a "MCP>queue show/all" output that isn't chronological, which I find a pain, when trying to trace a recently occured bounce (for example) In addiion, we have MX_VMSMAIL_SHOW_INFO defined true,and it seems less logical 'reusing' queue positions. Would it be relatively easy to give an incremental queue entry numbering system, with the same internal queue file format as in 3.4-beta-1 ? + I hope these comments aren't taken as criticism. I am extremely grateful for the MX package, and the fact you are dedicating your own time to user support, and software improvements. Thanks for listening, and thanks for MX, Jamie. Jamie Jones, Operations ================================================================================ Archive-Date: Sun, 23 Jan 1994 18:18:36 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: RE: How do you multiple forward using MX%,SMTP%, or s Message-ID: <1994Jan23.175043.613@earlham.edu> From: michaelb@earlham.edu Reply-To: MX-List@WKUVX1.WKU.EDU Date: Sun, 23 Jan 94 17:50:32 -500 To: MX-List@WKUVX1.WKU.EDU >What I am after is like this: > >set forward mx%"jspinnow@myunixmachine",myaccountonthisvmsmachine > >How do I do this for 1 without creating an infinite loop, and/or >bypassing the error message when I typing the above in. John: Check out a program called DELIVER. It allows you to customize what is actually delivered and what is forwarded or dumped. ================================================================================ Archive-Date: Mon, 24 Jan 1994 00:01:55 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 94 07:57 JST From: "Najman Kahana. Ext:7313" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: POP server To: MX-List@WKUVX1.WKU.EDU Message-ID: <6FE8E49D733F2002B3@HADASSAH.BITNET> Hi. I am running MX under CMU. Is there a POPn (2,3) server to interface with the MX ?. I know there is under Multinet, but I need one that either interfaces directly with the MX or with the CMU. Thanks Najman Kahana Najman@hadassah.bitnet ================================================================================ Archive-Date: Mon, 24 Jan 1994 00:52:15 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Sun, 23 Jan 1994 23:46:06 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <00978FD2.7BF3FA00.29066@Data.Basix.COM> Subject: RE: POP server "Najman Kahana. Ext:7313" writes: > I am running MX under CMU. > Is there a POPn (2,3) server to interface with the MX ?. > I know there is under Multinet, but I need one that either interfaces > directly with the MX or with the CMU. A POP server is simply a program that listens on the appropriate TCP/IP port for a client connection request. This isn't something you'll find bundled with bare-bones TCP/IP packages like CMU or UCX, but, as you mentioned, *is* bundled in with MultiNet. Your best bet would be to try and locate a Public Domain POPn program that is properly configured to run under CMU, but I have no idea if one is actually available for it or not. IMHO, it's not a function appropriate to MX, because all the POPn server really does is look in your mailbox on the server's host when you are only logged into the client's machine. Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Mon, 24 Jan 1994 05:26:45 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 05:26:57 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00979002.19B53879.11@ALPHA.WKU.EDU> Subject: RE: archiving mailing lists & resetting message queue acpwvw!wvwc!wvwc.!programmer@ms.uky.edu writes: > >This is 2 questions rolled into one: > >1) We have a local discussion list and would like to have the list >automagically archive these into a file. The MX033 describes this and I >thought I set it up correctly, but nothing seems to get into it. > [...] > Archive: STU$DISK:[ANONYMOUS.ARCHIVES.COMP-DISC]COMP-DISC.ARCHIVE I assume you've created this directory. Try turning on debug for MX MLF and see what that tells you: $ define/system/exec mx_mlf_debug true That'll create log files in MX_ROOT:[MLF]. >2) This is not critical but would be helpful. Is there anyway to reset the >mail message number of the mx messages? I am getting sick of typing a number >in the 10 and hundred thousand (soon to be millions) range. I would also like >to have it reset to keep statistics monthly or yearly on the number being >processed. > What mail message number? In what context? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 24 Jan 1994 06:01:32 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 06:01:49 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00979006.F825C188.19@ALPHA.WKU.EDU> Subject: Re: Mail2News Gateway with NEWSRDR? dwing@uh01.Colorado.EDU (Dan Wing) writes: > >In article <19535291@MVB.SAIC.COM>, Hans-Joachim Koch writes: >>Now I'm looking for a gateway mail to news. All examples in the .contrib >>subdirectory of mx are using ANU-NEWS. Has anybody done this with the >>NEWSRDR? It's not that difficult to add a news message via the site >>path. The only problem is to preserve the original senders address for >>the news article. Bulletin has a nice subroutine to do this - is there a >>simple way for NEWSRDR to do the same? > >NEWSRDR is a news reader; ANU-NEWS is a news server. I don't believe it >would be possible to get NEWSRDR to perform gateway functions between a >mailing list and a newsgroup -- you'd have to implement such a thing on the >system running your news server. If that is a Unix machine, you need a >Unix solution. > You can use Brian McKeever's MX_POST, which works with NNTP servers to post messages. Sounds like it'd do exactly what Hans wants to do. This software is included in MX V3.4, due out soon. You can also get it now from ftp.spc.edu in [.MX.CONTRIB]MX_POST.ZIP. >BULLETIN hasn't, and I'll bet won't, be ported to Unix. > Several hundred blocks for VMS-specific FORTRAN code?? Not likely. 8-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 24 Jan 1994 06:23:50 CST Sender: list-mgr@WKUVX1.WKU.EDU From: john@vax.sbu.ac.uk Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX Line length limit. Is there one? Message-ID: <1994Jan24.112207.4589@vax.sbu.ac.uk> Date: 24 Jan 94 11:22:06 GMT To: MX-List@WKUVX1.WKU.EDU Hello there, My question is: Does MX impose a line length limit on lines within a message body? If it does what is this limit? And can it be changed? My reason for asking is that attempts to send RTF files using MX result in parts of paragraphs being lost. This does not happen with VMS MAIL or mail on our UNIX based workstations. Thanks for any suggestions John Murphy. -- -------------------------------------------------------------------------------- John Murphy, Computer Services, South Bank University, London, U.K. john@vax.sbu.ac.uk ================================================================================ Archive-Date: Mon, 24 Jan 1994 07:28:48 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 14:07:18 +0100 From: Herve Gilibert -CRITeR- Universite de St Etienne Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <0097904A.CA5F3ACE.8049@stroph.univ-st-etienne.fr> Hello there ! I'm running MX in an mixed Vax alpha environment, all MX components are running on a VAX node, no component on the alpha node. All is OK when I send mail from the VAX node (as you can see),but From: header is incorrect when I send mails from the alpha node ( instead of ) and the vms personnal name is not listed. MX_VMSMAIL_FROM_FORMAT is DEFINED as on the VAX node. Defining it on the alpha node does not change anything. Debbuging the local agent does not help (There is no debug code for MX_mailshr). MX_MAILSHR seems unable to construct the From header. Could someone tell me what I am doing wrong ? Thanks in advance. ================================================================================ Archive-Date: Mon, 24 Jan 1994 07:43:14 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 07:43:02 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00979015.1C371A05.4@ALPHA.WKU.EDU> Subject: MX and node names Herve Gilibert -CRITeR- Universite de St Etienne writes: > >Hello there ! > >I'm running MX in an mixed Vax alpha environment, all MX components are running >on a VAX node, no component on the alpha node. >All is OK when I send mail from the VAX node (as you can see),but From: header >is incorrect when I send mails from the alpha node ( instead of >) and the vms personnal name is not listed. >MX_VMSMAIL_FROM_FORMAT is DEFINED as on the VAX node. >Defining it on the alpha node does not change anything. >Debbuging the local agent does not help (There is no debug code for MX_mailshr). >MX_MAILSHR seems unable to construct the From header. >Could someone tell me what I am doing wrong ? Even if you are running no MX agents on the AXP, you must still execute the MX_STARTUP.COM in your VAX SYS$STARTUP. That'll INSTALL the images and DEFINE all the appropriate logicals. Without all the right logicals, MX_MAILSHR on the AXP won't be able to notify the MX Router of ready mail, etc. To be specific, in the problem above, you also need to define MX_VMSMAIL_LOCALHOST and MX_NODE_NAME. But defining *all* of the logicals is the right way to go. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 24 Jan 1994 08:51:29 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 08:46:40 CST From: Howard Meadows Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097901E.002D5AA0.32502@cslvax.weeg.uiowa.edu> Subject: RE: POP server "Najman Kahana. Ext:7313" writes: > >Hi. > I am running MX under CMU. > Is there a POPn (2,3) server to interface with the MX ?. > I know there is under Multinet, but I need one that either interfaces >directly with the MX or with the CMU. >Thanks > >Najman Kahana >Najman@hadassah.bitnet > I'm testing a POP3 server with MX 3.3 and UCX 2.0 and it seems to work OK. It's from Indiana University (named IUPOP3), and I think you can get it via anonymous ftp to ftp.indiana.edu in directory pub/vms/iupop3. Attached is the README file that I have... -Howard *************************************************************************** * Howard Meadows Sr. Systems Programmer Weeg Computing Center * * University Of Iowa Iowa City, Iowa 52242 Phone: 319-335-5519 * * email: howard-meadows@uiowa.edu FAX : 319-335-5505 * *************************************************************************** ============================== Attachment =================================== ------------ Contents ------------ Copyright Authors History Synopsis Files Notes Extensions Making IUPOP3 Configuring IUPOP3 Comments ------------ Copyright ------------ (C) Copyright 1991 The Trustees of Indiana University Permission to use, copy, modify, and distribute this program for non-commercial use and without fee is hereby granted, provided that this copyright and permission notice appear on all copies and supporting documentation, the name of Indiana University not be used in advertising or publicity pertaining to distribution of the program without specific prior permission, and notice be given in supporting documentation that copying and distribution is by permission of Indiana University. Indiana University makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. ------------ Authors ------------ Indiana University University Computing Services Network Applications Group Jacob Levanon - Manager, Network Applications Larry Hughes - Lead Software Engineer ------------ History ------------ Current Version : 1.7 Release Date : March 16, 1992 Comments : Replaced several unnecessary malloc()'s with static data areas in the POP data structure. Determine list of cluster nodes dynamically at startup, if PATCH_FROM_LINE is defined at compile time. If you are unfamiliar with this source code option, see the "Notes" section below. Added 3 new headers to the header list: X-From, X-ID, X-Server. X-From is the unpatched "From:" line, X-ID is a unique message identifier, and X-Server is the name of the host that served the message. These are particularly helpful when tracking down suspected problems in a clustered environment. Fixed an octet count bug. The count wasn't being correctly initialized until a STAT command was issued. The count is still not perfect, especially with the new X- headers. Since most clients do not rely on it, we feel it is safe to simply add 150 octets to what VMS Mail reports, which usually errs on the safe side. Double buffered the network data for character mode clients (most notably POPMAIL). This is also nice for telnet'ing to the server in character mode for testing, and for issuing the optional "XTND SHUTDOWN" command to stop IUPOP3 gracefully. Retrieved messages are now not marked as retrieved until the next CR/LF terminated command is fully received. This should fix the problem that caused partially-downloaded messages to be moved to the old mail folder, when the connection abnormally terminated. (This could occasionally cause a user to receive two copies of the same message, if the message was successfully retrieved before the abnormal termination but before a new command was sent to the server. We feel this is better than the alternative.) Modify socket buffer sizes from the default 4K to 8K to accomodate large messages. If you feel this is excessive, you can modify it before building IUPOP3: change the SOCK_BUFSIZE constant in IUPOP3_GENERAL.H. IUPOP3 automatically compensates for this large buffer size; if the socket buffers become full, a 2-second rest is taken so the buffers can emtpy, and to service other threads. Fixed the bug where the server gets blocked in the network write() with ASTs disabled. This was causing the server to hang when there was unsent data queued in the socket buffers, which was possible with very large mail messages. Modified the optional "XTND STATS" report to add a few new fields. See the example later in this file. New fields are Version Number, Retrieved Octets, Average Octets, Minimum Octets, Maximum Octets, and Blocked Socket Count. The Blocked Socket Count value represents the number of times IUPOP3 was "blocked" from perform a network write() to a client, due to its sockets buffers being full. (As mentioned above, IUPOP3 then gives that client thread a 2-second rest so the buffers can empty). Support for the optional "XTND CLIENT" command, purely for information logging and problem tracking. If the POP3 client issues this command, it is simply written verbatim to the IUPOP3 log, and the client is acknowledged. If you have client sources, we recommend that the client report its program name and version number, i.e. "XTND CLIENT IUMAIL 1.3". (Note that IUPOP3 commands are limited to 10 tokens on a line, each a maximum of 10 characters.) Version : 1.6a Release Date : June 6, 1991 Comments : Fix client_read_ast() so any IOSB error assumes a client disconnect, especially for UCX. Added support for the optional "XTND SHUTDOWN" command. Version : 1.6 Release Date : May 16, 1991 Comments : Support for UCX and Multinet, in addition to WIN/TCP. Version : 1.5 Release Date : April 2, 1991 Comments : Initial release to public. ------------ Synopsis ------------ The IUPOP3 server is a VMS implementation of the Post Office Protocol Version 3, based on RFC 1225 (which supersedes RFC 1081). There are many differences between IUPOP3 and the BSD UNIX popper, partly due to the differences between VMS and UNIX as operating systems. Probably the most notable difference is that IUPOP3 is a permanent, multithreaded server. The server always listens on the network port for new connections, and can handle up to 31 simultaneous POP3 client connections. In this way, expensive VMS process creation overhead can be avoided. Note that this does not mean that IUPOP3 can serve only 31 clients; indeed, at IU it serves hundreds. The limitation is 31 concurrent connections from POP3 clients at any given moment in time. IUPOP3 was developed and tested on VMS 5.3 and 5.4 systems, using the VMS callable mail (MAIL$) interface. The current release is believed to be compatible with current versions of these TCP/IP network implementations: Wollongong's WIN/TCP for VMS, DEC's UCX, and TGV's Multinet. ------------ Files ------------ README.TXT - This file COPYRIGHT.TXT - IUPOP3 copyright RFC1225.TXT - RFC 1225 describing POP3 protocol RFC1082.TXT - RFC 1082 describing POP3 extentions IUPOP3.COM - Runs the IUPOP3 server (must be configured!) START_IUPOP3.COM - Starts IUPOP3.COM as a detached job (must be configured!) MAKE.COM - The required mechanism for building IUPOP3 IUPOP3.MMS - The MMS makefile invoked by MAKE.COM, if MMS is installed UCX.MACRO - MMS macro for UCX UCX.OPT - Linker options file for UCX WINS.MACRO - MMS macro for WIN/TCP WINS.OPT - Linker options file for WIN/TCP MULTINET.MACRO - MMS macro for Multinet MULTINET.OPT - Linker options file for Multinet IUPOP3.C - Main source file IUPOP3_COMMANDS.C - Routines which process the POP3 server commands IUPOP3_VMS.C - MAIL$ and SYS$ routines IUPOP3_UTILITY.C - Various utility and support routines PASSWD_V54.C - VMS 5.4 password hashing and validation PASSWD_V53.C - Pre VMS 5.4 password hashing and validation UCX_IOCTL.C - A somewhat functional ioctl() function for UCX CHANGE_CASE.MAR - A few very fast string routines IUPOP3_GENERAL.H - Includes files... IUPOP3_GLOBAL.H IUPOP3_VMS.H DESCR.H INETIODEF.H ITMLST.H VERSION.H MAILMISCDEF.H MAILMSGDEF.H POP_XTND.DAT - An example authorization file for XTND commands ------------ Notes ------------ IUPOP3 has been tested with three POP3 clients: Eudora for the Macintosh, FTP Software's POP3 for DOS and IU's home grown POP3 client for DOS. It seems to work well with these clients. If you test it with other clients, we would appreciate knowing the results. True to the POP3 protocol, IUPOP3 does not perform any mail delivery functions (notably, the optional "XTND XMIT" command). At IU, we rely on a UNIX host to act as an SMTP mail relay for POP3 clients. As many VMS sites will appreciate, at IU we have several foreign mailers that interface with VMS Mail. These mailers provide mail transport to (and from) BITNET and the Internet. Mail arriving into the VMS system from these networks has "From:" lines of the form TRANSPORT%"user@node". This can obviously create problems for POP3 clients that wish to reply to mail delivered by IUPOP3, since most POP3 clients will attempt to establish a direct SMTP connection to a relay or the originating host. To avoid this problem, IUPOP3 has an IU-specific routine that reformats "From:" lines. If you wish to adopt this mechanism for your site, make the necessary changes to the function "patch_from_line()" in IUPOP3_UTILITY.C, then add "/DEFINE=PATCH_FROM_LINE" in the appropriate MMS .MACRO file. If you do not have MMS, you will have to modify the CC command in the MAKE.COM to define this constant. Due to a change in the password hashing algorithm in VMS 5.4 (and the introduction of the SYS$HASH_PASSWORD system service call), IUPOP3 includes both VMS 5.4 and pre VMS 5.4 algorithms and password verification routines. The MAKE.COM procedure should automatically sense your VMS version and use the right algorithm when building IUPOP3. Finally, the current version of IUPOP3 logs just about everything that it does, with date and time stamps, to SYS$OUTPUT. We are careful to avoid logging passwords of course, but most other activites are logged profusely. This is partly because we have a very heterogeneous and complicated electronic mail environment at IU, and we sometimes need to verify the path of mail messages. Also, this profuse logging has simply helped us to debug IUPOP3 on many occasions. For security purposes, however, you should be as paranoid as we are, and jealously protect the IUPOP3 log! ------------ Extensions ------------ IUPOP3 implements none of the XTND extensions recommended in RFC 1082. However, it does implement three custom extensions for our own purposes. If a client supplies an "XTND CLIENT" command, to identify the client program name and version number, it will appear in the log file for tracking purposes. This can be helpful for trouble shooting, if you use IUPOP3 with a variety of POP3 clients. If a specially validated user issues an "XTND STATS" command to the server, a statistical report like this will be returned to the client: +OK Statistics follow Version Number : 1.7 Current Time : 1992-02-13 17:44:11 Start Time : 1992-02-13 07:32:53 CPU Seconds : 113.80 (1 mins, 53 secs) Current Threads : 2 Total Threads : 218 Max Threads : 8 Too Many Threads : 0 'From' Parse Errors : 0 Normal Disconnects : 215 Abnormal Disconnects : 2 Client Timeouts : 1 Blocked Socket Count : 3 Retrieved Messages : 127 Retrieved Octets : 52451 Average Octets : 413 Minimum Octets : 265 Maximum Octets : 1029 Current Users : 0. hughes 1. levanon . If a specially validated user issues an "XTND SHUTDOWN" command to the server, the server will perform a clean shutdown after all clients have disconnected. Administrators of the IUPOP3 server can validate users for the "XTND STATS" and "XTND SHUTDOWN" commands by modifying the example POP_XTND.DAT file that comes with the IUPOP3 distribution. (The "XTND CLIENT" command requires no special validation.) An example: # # Format: # xtnd_command [valid_user ...] # stats system levanon hughes shtudown system levanon hughes Then, define the logical name "POP_XTND_LIST" for the server, equivalenced to the file's full file specification, in IUPOP3.COM Note that this is a generic mechanism for validating other XTND commands we (or you) might wish to implement in the future. ------------- Making IUPOP3 ------------- To build IUPOP3, simply type this command in the IUPOP3 distribution directory: $ @MAKE The MAKE.COM accepts two optional paramters: $ @MAKE [UCX | MULTINET | WINS] [MMS | NOMMS] Although MAKE.COM should be able to automatically detect your TCP/IP implementation and whether or not you have MMS, you may override the automatic detection by supplying either or both parameters. ------------------ Configuring IUPOP3 ------------------ After you execute the MAKE.COM procedure, you'll have to edit the IUPOP3.COM (which actually runs IUPOP3), and START_IUPOP3.COM (which starts IUPOP3.COM as a detached process). The only changes you'll need to make to these procedures are to correct the directory specifications like "SYS$NOWHERE:[NOBODY]". These unusual and probably invalid directory references are used to encourage you to correctly configure IUPOP3 for your individual site. You might also wish to change START_IUPOP3.COM to submit IUPOP3.COM to a batch queue, instead of running it as a detached process. We prefer the latter approach, and also choose to run it at priority 5. ------------ Comments ------------ IUPOP3 is an unsupported program. If you decide to use it, do so only in strict adherence to the copyright/disclaimer shown at the top of this file, in COPYRIGHT.TXT, and throughout the source code. You may send comments and bug reports via Internet mail to iupop3@indiana.edu, or BITNET mail to IUPOP3@IUGATE. We will respond on a time-available basis. We do appreciate hearing from you! Also, if you wish to be notified of future updates and/or bug reports, please send email to one of the addresses listed above, and ask to be placed on the list. Enjoy! ================================================================================ Archive-Date: Mon, 24 Jan 1994 10:08:45 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: MX Line length limit. Is there one? Message-ID: <1994Jan24.085355.807@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 24 Jan 94 08:53:54 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <1994Jan24.112207.4589@vax.sbu.ac.uk>, john@vax.sbu.ac.uk writes: > My question is: Does MX impose a line length limit on lines within a message >body? If it does what is this limit? And can it be changed? > >My reason for asking is that attempts to send RTF files using MX result in >parts of paragraphs being lost. This does not happen with VMS MAIL or mail on >our UNIX based workstations. I just did some testing, and it appears MX's line-length limit is 255 characters; if the line contains 256 or 257 characters, the extra characters are discarded. However, if the line contains 1024 characters, the entire line is discarded; I'm not sure where this problem would be. Note, my testing involved sending mail to myself, so I don't know if the problem is in the local delivery, or if the lines are stripped immediately when you send the file with long record lengths. Can you use MX's SEND/FOREIGN facility if you're communicating to other VMS machines, or are you exchanging mail between a VMS machine and a Unix machine? -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Mon, 24 Jan 1994 10:30:35 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 17:26:23 +0100 From: Herve Gilibert -CRITeR- Universite de St Etienne Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00979066.9A6D4CAE.8101@stroph.univ-st-etienne.fr> Subject: RE: MX and node names > > Even if you are running no MX agents on the AXP, you must still > execute the MX_STARTUP.COM in your VAX SYS$STARTUP. That'll INSTALL > the images and DEFINE all the appropriate logicals. Without all the > right logicals, MX_MAILSHR on the AXP won't be able to notify the MX > Router of ready mail, etc. > > To be specific, in the problem above, you also need to define > MX_VMSMAIL_LOCALHOST and MX_NODE_NAME. But defining *all* of the > logicals is the right way to go. > On the vax Node I execute : @sys$startup:mx_startup logicals and submit .................... sys$startup:mx_startup on the AXP node : @sys$startup:mx_startup I noticed that the logical mx_site_dom_expansion was not defined on the AXP, but defining it does not help (after stoping and restarting MX on both nodes). domain_expansion.exe is not in alpha_exe directory is it right ? Here the AXP logicals : MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "$1$DKB700:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_EXE" = "MX_ROOT:[ALPHA_EXE]" "MX_FLQ_DIR" = "DISK$VAXVMS:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "RINETA" "MX_FLQ_RECLAIM_WAIT" = "0 02:00:00" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "stroph.univ-st-etienne.fr" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SITE_NAME_CONVERSION" = "MX_EXE:NAME_CONVERSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_VMSMAIL_FROM_FORMAT" = "" "MX_VMSMAIL_LOCALHOST" = "@univ-st-etienne.fr" Here the VAX logicals: "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_FLQ_DIR" = "DISK$VAXVMS:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "RINETA" "MX_FLQ_RECLAIM_WAIT" = "0 02:00:00" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "stroph.univ-st-etienne.fr" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_ALIASES" = "$1$dkb700:[mx]ALIASES.TXT" "MX_SITE_AUTHORIZED_DOMAIN" = "univ-st-etienne.fr" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SITE_NAME_CONVERSION" = "MX_EXE:NAME_CONVERSION" "MX_SITE_NOT_AUTHORIZED_DOMAIN" = "univ-st-etienne.fr" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_VMSMAIL_FROM_FORMAT" = "" "MX_VMSMAIL_LOCALHOST" = "@univ-st-etienne.fr" Here mx_logicals.dat : MX_FLQ_NODE_NAME\/SYSTEM/EXEC\RINETA MX_NODE_NAME\/SYSTEM/EXEC\stroph.univ-st-etienne.fr MX_VMSMAIL_LOCALHOST\/SYSTEM/EXEC\@univ-st-etienne.fr MX_FLQ_DIR\/SYSTEM/EXEC\DISK$VAXVMS:[MX.QUEUE] MX_FLQ_RECLAIM_WAIT\/SYSTEM/EXEC\0 02:00:00 MX_ROUTER_DIR\/SYSTEM/EXEC\MX_ROOT:[ROUTER] MX_LOCAL_DIR\/SYSTEM/EXEC\MX_ROOT:[LOCAL] MX_MCP_HELPLIB\/SYSTEM\MX_DIR:MX_MCP_HELPLIB MX_ALIAS_HELPLIB\/SYSTEM\MX_DIR:MX_ALIAS_HELPLIB Thanks in advance. -- Herve GILIBERT UUUU UUUU CRITeR UUUU UUUU Universite Jean Monnet St-Etienne UUUU UUUU 23, Rue du Dr. P. Michelon UUUU UUUU 42023 ST ETIENNE Cedex 2 UUUU UUUU Tel : 33 77 42 15 79 UUUU UUUU Fax : 33 77 42 15 75 UUUUUUUUUUU RFC822: gilibert@univ-st-etienne.fr UUUUUUUUU ================================================================================ Archive-Date: Mon, 24 Jan 1994 12:16:02 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 94 13:10:43 EST From: Tim Biddle Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Invalid media address I am running MX v.3.3 on a Microvax II LAVC, both machines in the cluster are UVax IIs, which is acting as a mail router. However, whenever I try to send a message, I look at the mail queue with mailq, the message has failed, and has the following as the last error message: %SYSTEM-F-IVADDR, invalid media address I suspected it was the disk drive that was giving the error, since the VMS error manual says that that error is associated with disk read and writes, so I moved the MX directory to another disk, and I am still getting this error. The two machines in the LAVC are sharing the MX directory area. I am running CMUIP on this cluster. If more info is needed, I will provide it, but PLEASE help! Tim Biddle biddlet@indy.navy.mil ================================================================================ Archive-Date: Mon, 24 Jan 1994 12:26:33 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 10:21:11 PST From: Ed Bates Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: ebates@uop.edu Message-ID: <0097902B.341114EE.15252@vms1.cc.uop.edu> Subject: RE: MX Line length limit. Is there one? On 24 Jan 94 at 11:22:06 GMT, john@vax.sbu.ac.uk wrote: >Hello there, > My question is: Does MX impose a line length limit on lines within a message >body? If it does what is this limit? And can it be changed? > >My reason for asking is that attempts to send RTF files using MX result in >parts of paragraphs being lost. This does not happen with VMS MAIL or mail on >our UNIX based workstations. I have noticed that either MX or VMS Mail (I haven't taken the time to research it) truncates lines longer than 255 characters. If I wish to send a file that may have lines longer than 255 bytes or contains non-printable characters, I uuencode the file before sending. (UUEncode and UUDecode are common programs for all computer platforms.) True, it is extra steps, but I have no problems with data integrity. -- Ed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Edwin J. (Ed) Bates VAX Admin/Internet Mgr/ Senior Academic Consultant Macintosh Consultant . . _ _ Office of Computing Services Internet: ebates@uop.edu |#| / \ | \ University of the Pacific AppleLink: U1441 |#| | | |_/ 877 W. Stadium Dr. Telephone: (209) 946-2251 |#| | | | Stockton, CA 95211 Fax: (209) 946-2898 \_/ \_/ | ================================================================================ Archive-Date: Mon, 24 Jan 1994 14:27:22 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Invalid media address Message-ID: <1994Jan24.131128.814@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 24 Jan 94 13:11:28 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19589847@MVB.SAIC.COM>, Tim Biddle writes: >I am running MX v.3.3 on a Microvax II LAVC, both machines in the cluster are >UVax IIs, which is acting as a mail router. >However, whenever I try to send a message, I look at the mail queue with mailq, >the message has failed, and has the following as the last error message: > > %SYSTEM-F-IVADDR, invalid media address > >I suspected it was the disk drive that was giving the error, since the VMS >error manual says that that error is associated with disk read and writes, so I >moved the MX directory to another disk, and I am still getting this error. The >two machines in the LAVC are sharing the MX directory area. I am running CMUIP >on this cluster. If more info is needed, I will provide it, but PLEASE help! From your VAX running CMU/IP, try to TELNET to port 25 of the system that MX was trying to connect to. I'm guessing that CMU/IP on your system is confused. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Mon, 24 Jan 1994 14:37:20 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 13:52:31 CST From: George Franklin Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <00979048.BA28F340.1762@oehl.brooks.af.mil> Subject: Subscribe to Mailing List SUBSCRIBE spectator@oehl.brooks.af.mil ================================================================================ Archive-Date: Mon, 24 Jan 1994 14:39:32 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 13:51:16 CST From: George Franklin Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <00979048.8D14BA60.1760@oehl.brooks.af.mil> Subject: Please Help I am having trouble creating a MX mailing list. Included is a list of how I have my mailing list setup. Please help. George Franklin =============================================================================== Mailing lists: Name: OEMI Owner: "HOLLENBECK@OEHL.BROOKS.AF.MIL" "SCHILLINGS@OEHL.BROOKS.AF.MIL" Reply-to: NOList, Sender Archive: MX_ROOT:[MLF.MAILING_LISTS]OEMI Description: OEMI, Brooks AFB Errors-to: HOLLENBECK@OEHL.BROOKS.AF.MIL Strip header: NOReceived Private list: No Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) ============================================================================== From: MX%"Postmaster@OEHL.brooks.af.mil" 24-JAN-1994 12:48:11.55 To: FRANKLIN CC: Subj: LOCAL delivery error Return-Path: <> Date: Mon, 24 Jan 1994 12:48:02 CST From: Local delivery agent To: Subject: LOCAL delivery error X-Report-Type: Nondelivery; boundary="> Error description:" Note: this message was generated automatically. An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: oemi-request@OEHL.brooks.af.mil Error-Code: 3 Error-Text: No such local user Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ Received: by oehl.brooks.af.mil (MX V3.3 VAX) id 1753; Mon, 24 Jan 1994 12:47:55 CST Date: Mon, 24 Jan 1994 12:47:54 CST From: franklin@OEHL.brooks.af.mil To: oemi-request@oehl.brooks.af.mil Message-ID: <0097903F.B32E3B80.1753@oehl.brooks.af.mil> Subject: Subscribe to Mailing List SUBSCRIBE franklin@OEHL.BROOKS.AF.MIL ================================================================================ Archive-Date: Mon, 24 Jan 1994 16:24:27 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 23:16:17 +0100 From: "GWDGV1::MOELLER" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: re: memory leak in SMTP_SERVER (3.3) - Problem solved (most probably) On 19-JAN-1994 23:06:21.48, I wrote: > I'm seeing SMTP_SERVER's virtual address space growing without bound ... > > It died a few times with ACCVIO due to page file quota exhaustion > (PGFLQUO is around 32k pages). > > Particulars: VMS 5.1-1, UCX 1.3A (sorry for the old versions :-) >[...] As it turns out, my SYSTEM_QUEUE.FDL had the line global buffers 32 in it, which somehow made RMS use up the address space, because the queue file gets opened very often by SMTP_SERVER (Yes, I had deliberately set that once out of curiosity, but was "pretty sure" that the global buffers were long gone). Seems that RMS global buffers must be handled with great care (is that behaviour a bug?). I apologize for having some readers of this list, and in particular Hunter Goatley, caused some headaches. Sorry, Wolfgang J. Moeller, Tel. +49 551 201516 or -510, GWDG, D-37077 Goettingen, F.R.Germany PSI%(0262)45050352008::MOELLER Disclaimer: No claim intended! | ================================================================================ Archive-Date: Mon, 24 Jan 1994 17:03:05 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 17:01:50 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00979063.2C55A28C.15@ALPHA.WKU.EDU> Subject: RE: Please Help George Franklin writes: > >I am having trouble creating a MX mailing list. Included is a list of >how I have my mailing list setup. Please help. > Did you do an MCP RESET to reset the MX Router and MX MLF? It sounds like you didn't. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 24 Jan 1994 17:12:26 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 17:03:08 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: spectator@oehl.brooks.af.mil Message-ID: <00979063.5AC91A40.26220@SHSU.edu> Subject: RE: Please Help On Mon, 24 Jan 1994 13:51:16 CST, George Franklin posted: > I am having trouble creating a MX mailing list. Included is a list of how > I have my mailing list setup. Please help. First guess is that following the MCP DEFINE LIST you didn't follow with a MCP RESET to get the definition in place. One thing (at least) in the configuration also needs to be looked at: >Mailing lists: > Name: OEMI > Owner: "HOLLENBECK@OEHL.BROOKS.AF.MIL" > "SCHILLINGS@OEHL.BROOKS.AF.MIL" What you very likely want to do is something along the lines of: MCP MOD LIST OEMI/own=("hollenbeck@OEHL.brooks.af.mil",- "schilling@OEHL.brooks.af.mil") to get the casings properly defined. MX will lowercase usernames (so thay must be quoted to get in place properly) and it appears from your From: address that you have a casing element in the FQDN (although this really doesn't matter since MX views these as all uppercase -- even to the point of converting them to uppercase following the command above). Nevertheless, you want to ensure that the username is properly cased to provide the owners' commands (ADD and REMOVE) to be used by the owners. --George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Mon, 24 Jan 1994 17:28:32 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 16:23:00 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <0097905D.BFEDCCA0.29402@Data.Basix.COM> Subject: RE: Please Help George Franklin writes: > I am having trouble creating a MX mailing list. Included is a list of > how I have my mailing list setup. Please help. > > Mailing lists: > Name: OEMI > Owner: "HOLLENBECK@OEHL.BROOKS.AF.MIL" > "SCHILLINGS@OEHL.BROOKS.AF.MIL" > Reply-to: NOList, Sender > Archive: MX_ROOT:[MLF.MAILING_LISTS]OEMI > Description: OEMI, Brooks AFB > Errors-to: HOLLENBECK@OEHL.BROOKS.AF.MIL > Strip header: NOReceived > Private list: No > Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) > ============================================================================== > --> Error description: > Error-For: oemi-request@OEHL.brooks.af.mil > Error-Code: 3 > Error-Text: No such local user After actually creating the list, you need to do an MCP RESET. Note: On occasion, I've had to do this two or three times, or maybe I'm just not waiting long enough for everything to actually BE reset. (Hunter: How long does it take?) Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Mon, 24 Jan 1994 18:54:06 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: re: memory leak in SMTP_SERVER (3.3) - Problem solved (most probably) Message-ID: <1994Jan24.171144.823@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 24 Jan 94 17:11:44 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19599509@MVB.SAIC.COM>, "GWDGV1::MOELLER" writes: >On 19-JAN-1994 23:06:21.48, I wrote: >> I'm seeing SMTP_SERVER's virtual address space growing without bound ... >> >> It died a few times with ACCVIO due to page file quota exhaustion >> (PGFLQUO is around 32k pages). >> >> Particulars: VMS 5.1-1, UCX 1.3A (sorry for the old versions :-) >>[...] > >As it turns out, my SYSTEM_QUEUE.FDL had the line > global buffers 32 >in it, which somehow made RMS use up the address space, >because the queue file gets opened very often by SMTP_SERVER >(Yes, I had deliberately set that once out of curiosity, >but was "pretty sure" that the global buffers were long gone). > >Seems that RMS global buffers must be handled with great care >(is that behaviour a bug?). > >I apologize for having some readers of this list, >and in particular Hunter Goatley, caused some headaches. Sounds like a nasty RMS bug; you might want to log a call with DEC, or ask on comp.os.vms, to see if anyone else has seen it. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Mon, 24 Jan 1994 21:21:52 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Invalid media address Message-ID: <2i1rd5$k9g@gap.cco.caltech.edu> From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Date: 25 Jan 1994 01:07:49 GMT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19589847@MVB.SAIC.COM>, Tim Biddle writes: =I am running MX v.3.3 on a Microvax II LAVC, both machines in the cluster are =UVax IIs, which is acting as a mail router. =However, whenever I try to send a message, I look at the mail queue with mailq, =the message has failed, and has the following as the last error message: = = %SYSTEM-F-IVADDR, invalid media address = =I suspected it was the disk drive that was giving the error, since the VMS =error manual says that that error is associated with disk read and writes, so I =moved the MX directory to another disk, and I am still getting this error. The =two machines in the LAVC are sharing the MX directory area. I am running CMUIP =on this cluster. If more info is needed, I will provide it, but PLEASE help! This message means that CMUIP has failed. If you try to telnet to port 25 of the machine in quesion, you'll get that message from CMUIP. -------------------------------------------------------------------------------- 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, 24 Jan 1994 23:32:48 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 07:54:01 +0300 From: syseng@BHUOB00.BITNET Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009790DF.CF81B500.23601@bhuob00> Subject: RE: Please Help Hi there, Regarding the mailing list problem, "NO such local user" is related to oemi-request, try to use oemi-Request, "R not r", and I hope it works. Nader Nasry ================================================================================ Archive-Date: Tue, 25 Jan 1994 02:26:48 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 24 Jan 1994 22:09:28 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <0097908E.26401A00.29519@Data.Basix.COM> Subject: Easy way to troubleshoot bad subscriber addresses? I know this isn't EXACTLY an MX thing, but I'm wondering if there's anything easy/simple I can do -- short of leaving MLF debugging on all the time -- to help troubleshoot bounced messages like this (it's a "welcome to the XYZ-List" response to a SUBSCRIBE message): > Note: this message was generated automatically. > A problem occurred during SMTP delivery of your message. > Error occurred sending to the following user(s): > (via SEATTLE): > %MX-F-RETRYEXCD, retry count exceeded > -MX-F-NOHOST, no such host At this point, the SUBSCRIBE message is history (unless I catch it before the message is purged!). My guess, of course, is that some UCX site has not put the FQDN name in the SMTP configuration. ;)} For the poor sucker who is on such a system, I'd like to be able to manually subscribe them AND send a "nice note" to the system manager on how to fix it... A similar question: Is there a slick way to find all the (for example) SEATTLE.* and SEATTLE.*.* (etc.!)? (Maybe using Multinet's NSLOOKUP?) At least if there is only one (or maybe two, if I'm energetic!), I can try to find the original subscriber... Thanks folks! Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Tue, 25 Jan 1994 05:54:02 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 05:49:28 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009790CE.68DCECE5.9@ALPHA.WKU.EDU> Subject: RE: Please Help "Ray Harwood -- Data Basix: (602)721-1988" writes: > >After actually creating the list, you need to do an MCP RESET. Note: On >occasion, I've had to do this two or three times, or maybe I'm just not waiting >long enough for everything to actually BE reset. (Hunter: How long does it >take?) > It all depends on what the agent is doing at the time. If it's busy processing a message, then the RESET doesn't happen until the message processing is complete. For mailing lists and stuff, this could take a while. But all the agents should eventually do the RESET. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 25 Jan 1994 06:39:59 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 94 07:33:20 EST From: Tim Biddle Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: re: invalid media address Thnaks for all the help with my invalid media address. A couple of people suggested looking at the CMU/IP. That turned out to be the culprit. I had defined the RECURSE variable in my namres$config file, but had taken out REFMAX. The result was that the name resolver could not resolve mx records correctly from any nameservers. Once I added that variable definition back into my namres$config, everything started working normally again. Thanks for the help. BTW, the RECURSE variable is not documented anywhere in the manual. You might as well give up looking for it, it aint there! Tim Biddle biddlet@indy.navy.mil ================================================================================ Archive-Date: Tue, 25 Jan 1994 07:17:33 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 94 07:14:19 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: need to find a MAIL logical name To: mx-list@wkuvx1.wku.edu Message-ID: <009790DA43AEABA0.2020117A@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT MXers, I know this is more of a MAIL question than a MX question, but I remember seeing a note (which I filed and can't find) about a MAIL (maybe MX) logical that controls the interpretation of aliases ... e.g. assign "mx%""mx-list@wkuvx1.wku.edu""" mxlist when 'mxlist' is used in the TO: field it is interpreted to its definition when mailed. Thanks in advance for any help on this. --Rick +---------- A bad day fishing is better than a good day at work -------------+ | Rick Stacks, Sr. Programmer Analyst | voice: 501-570-2174 | | Ark Dept Pollution Control & Ecology | fax: 501-562-4632 | | 8001 National Dr. / POB 8913 | email: rick_sys@adpce.lrk.ar.us | | Little Rock, AR 72219 USA | DCS: stacks DECUServe: stacks | +----------------------------------------------------------------------------+ ================================================================================ Archive-Date: Tue, 25 Jan 1994 07:41:13 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 94 07:37:45 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: in search of a Fortran version of NAME_CONVERSION.C To: mx-list@wkuvx1.wku.edu Message-ID: <009790DD89E0EAE0.2020117A@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Help! I have tried to no avail to understand the "C" version of the NAME_CONVERSION routine that accompanies MX 3.3. I do not have a C compiler, cannot (it seems) read C code, and can't seem to get a grip on what I need to do to write a Fortran version from scratch. Please, does anyone have a WORKING Fortran version of the NAME_CONVERSION.C program that they would be willing to share? I need to rewrite the program to work with VMS Mail and WordPerfect Mail (WPGATE) as well as work with a mixed VAX and AXP cluster. Thanks MUCH for any help... --Rick +---------- A bad day fishing is better than a good day at work -------------+ | Rick Stacks, Sr. Programmer Analyst | voice: 501-570-2174 | | Ark Dept Pollution Control & Ecology | fax: 501-562-4632 | | 8001 National Dr. / POB 8913 | email: rick_sys@adpce.lrk.ar.us | | Little Rock, AR 72219 USA | DCS: stacks DECUServe: stacks | +---- Share time - Hunt with your kids today and not for them tomorrow -----+ ================================================================================ Archive-Date: Tue, 25 Jan 1994 08:15:37 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 08:59:15 EST From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: rharwood@Data.Basix.COM CC: mx-list@wku.edu Message-ID: <009790E8.EC796460.20742@swdev.si.com> Subject: RE: Easy way to troubleshoot bad subscriber addresses? One way to find out is to use Multinet's WHOIS command, as below. My guess is that the message is from the City of Seattle. $ whois seattle City of Seattle (NET-SEATTLE) SEATTLE 156.74.0.0 Seattle Community Network (SCN-DOM) SCN.ORG Seattle FilmWorks (NET-SFW) SFW 192.112.65.0 Seattle Macintosh Business Users' Group (DBUG-DOM) DBUG.ORG Seattle Online (ONLINE-DOM) ONLINE.COM Seattle Pacific University (NET-SEA-PAC-UNIV) SEA-PAC-UNIV 192.190.33.0 Seattle Pacific University (SPU-DOM) SPU.EDU Seattle People's Internet Cooperative (NETBLK-SPI-NET) NETBLK-SPI-NET 198.252.219.0 - 198.252.220.0 Seattle People's Internet Cooperative (SPI2-DOM) SPI.NET Seattle Public Library (NET-SPL-NET) SPL-NET 198.137.188.0 Seattle Times INC (SEATIMES-DOM) SEATIMES.COM Seattle University (NET-SEATTLEU-NET) SEATTLEU-NET 192.48.211.0 Seattle University (NET-SEATTLEU1) SEATTLEU1 192.222.32.0 Seattle University (NET-SEATTLEU10) SEATTLEU10 192.222.41.0 Seattle University (NET-SEATTLEU11) SEATTLEU11 192.222.42.0 Seattle University (NET-SEATTLEU12) SEATTLEU12 192.222.43.0 Seattle University (NET-SEATTLEU13) SEATTLEU13 192.222.44.0 Seattle University (NET-SEATTLEU14) SEATTLEU14 192.222.45.0 Seattle University (NET-SEATTLEU15) SEATTLEU15 192.222.46.0 Seattle University (NET-SEATTLEU16) SEATTLEU16 192.222.47.0 Seattle University (NET-SEATTLEU17) SEATTLEU17 192.222.48.0 Seattle University (NET-SEATTLEU18) SEATTLEU18 192.222.49.0 Seattle University (NET-SEATTLEU19) SEATTLEU19 192.222.50.0 Seattle University (NET-SEATTLEU2) SEATTLEU2 192.222.33.0 Seattle University (NET-SEATTLEU20) SEATTLEU20 192.222.51.0 Seattle University (NET-SEATTLEU21) SEATTLEU21 192.222.52.0 Seattle University (NET-SEATTLEU22) SEATTLEU22 192.222.53.0 Seattle University (NET-SEATTLEU23) SEATTLEU23 192.222.54.0 Seattle University (NET-SEATTLEU24) SEATTLEU24 192.222.55.0 Seattle University (NET-SEATTLEU25) SEATTLEU25 192.222.56.0 Seattle University (NET-SEATTLEU26) SEATTLEU26 192.222.57.0 Seattle University (NET-SEATTLEU28) SEATTLEU28 192.222.59.0 Seattle University (NET-SEATTLEU29) SEATTLEU29 192.222.60.0 Seattle University (NET-SEATTLEU3) SEATTLEU3 192.222.34.0 Seattle University (NET-SEATTLEU30) SEATTLEU30 192.222.61.0 Seattle University (NET-SEATTLEU31) SEATTLEU31 192.222.62.0 Seattle University (NET-SEATTLEU32) SEATTLEU32 192.222.63.0 Seattle University (NET-SEATTLEU4) SEATTLEU4 192.222.35.0 Seattle University (NET-SEATTLEU5) SEATTLEU5 192.222.36.0 Seattle University (NET-SEATTLEU6) SEATTLEU6 192.222.37.0 Seattle University (NET-SEATTLEU7) SEATTLEU7 192.222.38.0 Seattle University (NET-SEATTLEU8) SEATTLEU8 192.222.39.0 Seattle University (NET-SEATTLEU9) SEATTLEU9 192.222.40.0 Seattle University (NETBLK-SEATTLEU-NET) NETBLK-SEATTLEU-NET 192.222.32.0 - 192.222.63.0 Seattle University (SEATTLEU-DOM) SEATTLEU.EDU Seattle University (BACH3-HST) BACH.SEATTLEU.EDU 192.48.211.11 Seattle University (SPIFF-HST) SPIFF.SEATTLEU.EDU 192.222.35.190 Seattle Unix Group (SEASLUG-DOM) SEASLUG.ORG Seattle VA Hospital General Medical Research (NET-SVAGMR1) SVAGMR1 198.137.0.0 Seattle VA Hospital General Medical Research (NET-SVAGMR2) SVAGMR2 198.137.1.0 Seattle VA Hospital General Medical Research (NET-SVAGMR3) SVAGMR3 198.137.2.0 Seattle VA Hospital General Medical Research (NET-SVAGMR4) SVAGMR4 198.137.3.0 Seattle VA Hospital General Medical Research (NET-SVAGMR5) SVAGMR5 198.137.4.0 Seattle VA Hospital General Medical Research (NET-SVAGMR6) SVAGMR6 198.137.5.0 Seattle VA Hospital General Medical Research (NET-SVAGMR7) SVAGMR7 198.137.6.0 Seattle VA Hospital General Medical Research (NET-SVAGMR8) SVAGMR8 198.137.7.0 Seattle VA Hospital General Medical Research (NETBLK-SVAGMR198) NETBLK-SVAGMR198 198.137.0.0 - 198.137.7.0 The InterNIC Registration Services Host ONLY contains Internet Information (Networks, ASN's, Domains, and POC's). Please use the whois server at nic.ddn.mil for MILNET Information. $ whois "City of Seattle" City of Seattle (NET-SEATTLE) 710 2nd Ave. Suite 880 Seattle, WA 98104 Netname: SEATTLE Netnumber: 156.74.0.0 Coordinator: Tranberg, Peter (PT100) [No mailbox] (206) 684-0955 Record last updated on 19-Dec-91. The InterNIC Registration Services Host ONLY contains Internet Information (Networks, ASN's, Domains, and POC's). Please use the whois server at nic.ddn.mil for MILNET Information. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Tue, 25 Jan 1994 08:19:53 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 08:04:11 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009790E1.3AB830A0.30325@SHSU.edu> Subject: RE: Please Help On Tue, 25 Jan 1994 05:49:28 CST, "Hunter Goatley, WKU" followed up further: > "Ray Harwood -- Data Basix: (602)721-1988" writes: > > > >After actually creating the list, you need to do an MCP RESET. Note: On > >occasion, I've had to do this two or three times, or maybe I'm just not waiting > >long enough for everything to actually BE reset. (Hunter: How long does it > >take?) > > > It all depends on what the agent is doing at the time. If it's busy > processing a message, then the RESET doesn't happen until the message > processing is complete. For mailing lists and stuff, this could take > a while. But all the agents should eventually do the RESET. Or, if running MX on multiple nodes of a VAXcluster, RESET/CLUSTER to reset the specified agent(s) cluster-wide. --George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Tue, 25 Jan 1994 09:12:41 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 09:12:34 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009790EA.C8887337.10@ALPHA.WKU.EDU> Subject: RE: need to find a MAIL logical name Rick Stacks writes: > >MXers, > >I know this is more of a MAIL question than a MX question, but I remember >seeing a note (which I filed and can't find) about a MAIL (maybe MX) >logical that controls the interpretation of aliases ... e.g. > >assign "mx%""mx-list@wkuvx1.wku.edu""" mxlist > >when 'mxlist' is used in the TO: field it is interpreted to its definition >when mailed. > Yes, if you do the ASSIGN above, VMS Mail will translate MXLIST to the MX% string. I'm not sure what you're asking about---you can also use MXALIAS to define aliases instead of using logicals. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 25 Jan 1994 09:16:59 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 10:09:22 EST From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: WKUVX1.WKU.EDU!MX-list@esseye.si.com CC: rick_sys@adpce.lrk.ar.us Message-ID: <009790F2.B81CF560.20805@swdev.si.com> Subject: RE: need to find a MAIL logical name Rick Stacks (rick_sys@adpce.lrk.ar.us) writes: >I know this is more of a MAIL question than a MX question, but I remember >seeing a note (which I filed and can't find) about a MAIL (maybe MX) >logical that controls the interpretation of aliases ... e.g. > >assign "mx%""mx-list@wkuvx1.wku.edu""" mxlist > >when 'mxlist' is used in the TO: field it is interpreted to its definition >when mailed. Um... what's the question? There is no question in the above. If you are asking if one can define a logical as in your example to take the place of a mail address, the answer is "yes". If my guess is wrong, please actually _ask_ your question. -- Brian ================================================================================ Archive-Date: Tue, 25 Jan 1994 11:18:23 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 11:12:19 CST From: George Franklin Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@wkuvx1.wku.edu Message-ID: <009790FB.8345F4A0.1916@oehl.brooks.af.mil> Subject: Signoff User SIGNOFF spectator@OEHL.brooks.af.mil ================================================================================ Archive-Date: Tue, 25 Jan 1994 12:03:19 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 94 11:57:32 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: RE: need to find a MAIL logical name To: mx-list@wkuvx1.wku.edu Message-ID: <00979101D49A8400.20201349@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > >Rick Stacks (rick_sys@adpce.lrk.ar.us) writes: > >>I know this is more of a MAIL question than a MX question, but I remember >>seeing a note (which I filed and can't find) about a MAIL (maybe MX) >>logical that controls the interpretation of aliases ... e.g. >> >>assign "mx%""mx-list@wkuvx1.wku.edu""" mxlist >> >>when 'mxlist' is used in the TO: field it is interpreted to its definition >>when mailed. > >Um... what's the question? There is no question in the above. If you are >asking if one can define a logical as in your example to take the place of a >mail address, the answer is "yes". If my guess is wrong, please actually _ask_ >your question. >-- >Brian Sorry... What is the name of the logical used to have MAIL replace alias (logical) names with the definition of the logical? TIA, Rick ================================================================================ Archive-Date: Tue, 25 Jan 1994 12:31:17 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 13:26:56 EST From: Mighty Firebreather Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rick_sys@adpce.lrk.ar.us Message-ID: <0097910E.51D9B1A0.28945@nscvax.princeton.edu> Subject: Re: RE: need to find a MAIL logical name Rick Stacks writes: >> >>Rick Stacks (rick_sys@adpce.lrk.ar.us) writes: >> >>>I know this is more of a MAIL question than a MX question, but I remember >>>seeing a note (which I filed and can't find) about a MAIL (maybe MX) >>>logical that controls the interpretation of aliases ... e.g. >>> >>>assign "mx%""mx-list@wkuvx1.wku.edu""" mxlist >>> >>>when 'mxlist' is used in the TO: field it is interpreted to its definition >>>when mailed. >> >>Um... what's the question? There is no question in the above. If you are >>asking if one can define a logical as in your example to take the place of a >>mail address, the answer is "yes". If my guess is wrong, please actually _ask_ >>your question. >>-- >>Brian > >Sorry... > >What is the name of the logical used to have MAIL replace alias (logical) >names with the definition of the logical? > >TIA, >Rick Rick, There is no logical to turn it on or off (as far as I know). The reason why so many people had trouble with your question is that your message appeared to contain what they thought was the answer! $ assign "mx%""mx-list@wkuvx1.wku.edu""" mxlist will let you send mail to MX-List without spelling out the address in full. $ assign "MX%""dragon@nscvax.princeton.edu""" dragon will let you address mail to me as simply "dragon". You need one logical name per addressee. I never thought it was worth the trouble to define a bunch of logicals as most of my outgoing mail consists of replies to other messages. ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Tue, 25 Jan 1994 13:05:08 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 94 13:01:25 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: need to find a MAIL logical name To: mx-list@wkuvx1.wku.edu Message-ID: <0097910AC11E54C0.202014A3@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Richard B. Gilbert -- writes in reply: > Rick, > > There is no logical to turn it on or off (as far as I know). The >reason why so many people had trouble with your question is that your >message appeared to contain what they thought was the answer! > I realized that after I saw the message come back to me... Teach me to not read before sending! :-) >$ assign "mx%""mx-list@wkuvx1.wku.edu""" mxlist > >will let you send mail to MX-List without spelling out the address in full. > >$ assign "MX%""dragon@nscvax.princeton.edu""" dragon > >will let you address mail to me as simply "dragon". You need one logical >name per addressee. > I was thinking (uh-oh) that there was a logical to control turning on/off the display of the full interpretation of the logical while within MAIL. Oh, well... ;-) maybe next time. Many thanks for the help on this one. --Rick +---------- A bad day fishing is better than a good day at work -------------+ | Rick Stacks, Sr. Programmer Analyst | voice: 501-570-2174 | | Ark Dept Pollution Control & Ecology | fax: 501-562-4632 | | 8001 National Dr. / POB 8913 | email: rick_sys@adpce.lrk.ar.us | | Little Rock, AR 72219 USA | DCS: stacks DECUServe: stacks | +---- Share time - Hunt with your kids today and not for them tomorrow -----+ ================================================================================ Archive-Date: Tue, 25 Jan 1994 13:17:52 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 12:16:12 MST From: "Louis B. Moore" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00979104.6FD5FA60.110@tchden.org> Subject: RE: in search of a Fortran version of NAME_CONVERSION.C >I have tried to no avail to understand the "C" version of the >NAME_CONVERSION routine that accompanies MX 3.3. I do not have a C >compiler, cannot (it seems) read C code, and can't seem to get a grip on >what I need to do to write a Fortran version from scratch. You can try unpacking nickname.zip in mx_root:[contrib] and looking at the mx_name_conversion.mar. It may give you another view to consider. Louis B. Moore Internet: MOORE.LOUIS@tchden.org Systems Programmer Phone: +1.303.837.2513 The Children's Hospital of Denver Denver, Colorado USA 80218 ================================================================================ Archive-Date: Tue, 25 Jan 1994 14:13:15 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 94 15:09:00 EST From: Tim Biddle Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Subject: Adding subscribers to a list I own. I own the following list: $ mcp show list sysadmin Mailing lists: Name: SYSADMIN Owner: "tim@TBIDDLE.NAWC-AD-INDY.NAVY.MIL" Reply-to: List, NOSender Description: System Administrators @ NAWC AD Indy Errors-to: biddlet@mr1.nawc-ad-indy.navy.mil Strip header: NOReceived Private list: No Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWED) And these are the people who are subscribed to the list: $ mcp review sysadmin Tim Biddle Scott Redmon thomas@SIM3.NAWC-AD-INDY.NAVY.MIL I want to add another person to this list, so I send a message as follows: To: mx%"mxserver@mr1.nawc-ad-indy.navy.mil" Subj: add "johnnie.goodman@oa-mail.nawc-ad-indy.navy.mil" I get no feedback from this message. So, then when I look at the mx_mlf_log.log file, I see: $ type mx_mlf_log.log 25-JAN-1994 14:49:22.74 Processing queue entry number 1951 25-JAN-1994 14:49:23.52 Checking local name: sysadmin-Request 25-JAN-1994 14:49:23.53 This is a list control address. 25-JAN-1994 14:49:23.86 LIST_CTRL_REQ: Message is from:biddlet@mr1.nawc-ad-i ndy.navy.mil 25-JAN-1994 14:49:24.34 LIST_CTRL_REQ: command is: add "johnnie.goodman@oa-mail.nawc-ad-indy.navy.mil" 25-JAN-1994 14:49:24.35 CHECK_ACCESS: checking biddlet@mr1.nawc-ad-indy.navy. mil for access mask=00000010 25-JAN-1994 14:49:24.39 CHECK_ACCESS: Found address on system_users list. 25-JAN-1994 14:49:24.40 CHECK_ACCESS: -- access granted under SYSTEM class. 25-JAN-1994 14:49:24.58 All done with this entry. Then another mcp review sysadmin gives the following: $ mcp review sysadmin Tim Biddle Scott Redmon thomas@SIM3.NAWC-AD-INDY.NAVY.MIL Why isn't that user being added to the list? What am I not doing right? Other users can subscribe by sending a message to the -request address, and that is how the I subscribed myself, and the other two users subscribed. I can't do anything as the owner, though. Tim Biddle biddlet@indy.navy.mil ================================================================================ Archive-Date: Tue, 25 Jan 1994 15:49:11 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 14:55:35 EST From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: WKUVX1.WKU.EDU!MX-list@esseye.si.com Message-ID: <0097911A.B387AEA0.21066@swdev.si.com> Subject: Re: need to find a MAIL logical name Rick Stacks (rick_sys@adpce.lrk.ar.us) writes: >Sorry... > >What is the name of the logical used to have MAIL replace alias (logical) >names with the definition of the logical? Are you discussing aliases or logicals? There is a difference. A logical name is, of course, a VMS construct. If I define a name, as in the following: $ define mx-list "mx%""MX-List@wku.edu""" then I can send mail like this: MAIL> send To: mx-list and it will be sent through MX. No magic necessary and no further logicals need to be defined. If you are talking about aliases, those are MX constructs anmd you define them with the command MXALIAS, like this: MXalias> add mx-list "MX-List@wku.edu" You then use it like this: MAIL> send To: mx%mx-list No logical names at all are needed in this case. -- Brian tillman_brian@si.com ================================================================================ Archive-Date: Tue, 25 Jan 1994 15:50:36 CST Sender: list-mgr@WKUVX1.WKU.EDU From: mark@infocomm.com (Mark Pizzolato 510-837-5600) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: need to find a MAIL logical name Message-ID: <1994Jan25.125219.25767@infopiz> Date: 25 Jan 94 12:52:19 PST To: MX-List@WKUVX1.WKU.EDU In article <009790EA.C8887337.10@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: > Rick Stacks writes: >> >>MXers, >> >>I know this is more of a MAIL question than a MX question, but I remember >>seeing a note (which I filed and can't find) about a MAIL (maybe MX) >>logical that controls the interpretation of aliases ... e.g. >> >>assign "mx%""mx-list@wkuvx1.wku.edu""" mxlist >> >>when 'mxlist' is used in the TO: field it is interpreted to its definition >>when mailed. >> > Yes, if you do the ASSIGN above, VMS Mail will translate MXLIST to the > MX% string. > > I'm not sure what you're asking about---you can also use MXALIAS to > define aliases instead of using logicals. Yes, but then you still have to type MX%mxlist to get the expansion. :-( This is even true if the infamous patch that lets you NOT type the MX% before domain addressed mail. I asked at the MX bof in San Francisco if anyone was less lazy than I and had modified the patch to pass addresses without an "@" through the MX mailshr processing also. Since I've been too lazy to dig into this, I can't really complain, but pointing it out, might inspire someone else to look into it. :-) -- Mark Pizzolato - INFO COMM Computer Consulting, Danville, Ca PHONE: (510)837-5600 UUCP: decwrl!infopiz!mark or uunet!lupine!infopiz!mark DOMAIN: mark@infocomm.com ================================================================================ Archive-Date: Tue, 25 Jan 1994 15:50:46 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Adding subscribers to a list I own. Message-ID: <1994Jan25.143252.836@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 25 Jan 94 14:32:51 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19627873@MVB.SAIC.COM>, Tim Biddle writes: >I own the following list: > >$ mcp show list sysadmin > >Mailing lists: > Name: SYSADMIN > Owner: "tim@TBIDDLE.NAWC-AD-INDY.NAVY.MIL" > Reply-to: List, NOSender > Description: System Administrators @ NAWC AD Indy > Errors-to: biddlet@mr1.nawc-ad-indy.navy.mil > Strip header: NOReceived > Private list: No > Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWED) You probably don't want W:RWED on that list, but that is your decision, I 'spose. :-) >I want to add another person to this list, so I send a message as follows: > >To: mx%"mxserver@mr1.nawc-ad-indy.navy.mil" >Subj: >add "johnnie.goodman@oa-mail.nawc-ad-indy.navy.mil" The above commands don't tell MX's MLF agent which address you'd like Johnnie Goodman added to. It can't guess for you. I believe it should complain and send you an error message, though. However, per the MX_DOC:MLF_GUIDE.TXT documentation, for MX V3.4-beta (the V3.3 docs should be very similar in this regard, as there is no change in this area): 3.6.1 ADD The ADD command adds other users to a mailing list. The syntax for this command for the -Request interface is: ADD [/NONOTIFY] [/NOMAIL] [/NOCASE] [/CONCEAL] - [/NOREPRO] [/ACCESS] address [,...] The syntax for the MXSERVER interface is: ADD [/NONOTIFY] list-name address [,...] So, being that you decided to send the message to the MXSERVER interface, you should have sent a message like: MAIL> SEND To: MX%"MXSERVER@mr1.nawc-ad-indy.navy.mil" Subj: ADD SYSADMIN johnnie.goodman@oa-mail.nawc-ad-indy.navy.mil Note that the address is not enclosed in quotes -- that isn't necessary, and, in fact, if MX tried to use it would result in an invalid address -- I'm sure this is why MX didn't add the user (Hunter, I'm not getting any complaints when trying to add an invalid address like that, either?). Using greater-than/less-than (the "<" and ">" characters) is the proper way to delimite an Email address, if you want to do that: MAIL> SEND To: MX%"MXSERVER@mr1.nawc-ad-indy.navy.mil" Subj: ADD SYSADMIN Additionally, if you use the listname-REQUEST address, you can include the user's personal name, so it shows up in the REVIEW commands (it looks like this is what you did previously to add the other users), using something like: MAIL> SEND To: MX%"SYSADMIN-REQUEST@mr1.nawc-ad-indy.navy.mil" Subj: ADD "Johnnie Goodman" Also, if the user has a VMSmail personal name set, and the user subscribes themselves (by using the SUBSCRIBE command -- see below), then their personal name is automatically stuck into the datafile used by REVIEW. No big deal, but easier to read than a long username.... >I get no feedback from this message. So, then when I look at the mx_mlf_log.log >file, I see: > >$ type mx_mlf_log.log >25-JAN-1994 14:49:22.74 Processing queue entry number 1951 >25-JAN-1994 14:49:23.52 Checking local name: sysadmin-Request >25-JAN-1994 14:49:23.53 This is a list control address. >25-JAN-1994 14:49:23.86 LIST_CTRL_REQ: Message is from:biddlet@mr1.nawc-ad-i >ndy.navy.mil >25-JAN-1994 14:49:24.34 LIST_CTRL_REQ: command is: add >"johnnie.goodman@oa-mail.nawc-ad-indy.navy.mil" >25-JAN-1994 14:49:24.35 CHECK_ACCESS: checking biddlet@mr1.nawc-ad-indy.navy. >mil for access mask=00000010 >25-JAN-1994 14:49:24.39 CHECK_ACCESS: Found address on system_users list. >25-JAN-1994 14:49:24.40 CHECK_ACCESS: -- access granted under SYSTEM >class. >25-JAN-1994 14:49:24.58 All done with this entry. Well, the above log isn't for the sample you gave at the top of your message. In the sample at the top of your message, you show mailing a message to MXSERVER, and the output of this log indicates it is processing an entry sent to sysadmin-request. The MXSERVER and listname-REQUEST addresses have different "interfaces", and accept their ADD and REMOVE commands in a different order. Note, too, with your protection set to W:RWED, the user could simply subscribe themselves by sending a message to user MXSERVER on your node with the single line: SUBSCRIBE SYSADMIN in the body of their mail message. Note, too, that anyone on the Internet could also subscribe to that list. I would imagine you want to fix that. Later, -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Tue, 25 Jan 1994 16:58:15 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 16:58:27 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097912B.DE054645.9@ALPHA.WKU.EDU> Subject: RE: need to find a MAIL logical name mark@infocomm.com (Mark Pizzolato 510-837-5600) writes: > >Yes, but then you still have to type MX%mxlist to get the expansion. :-( > Unless you use SET TRANSPORT MX%. Note that *all* messages sent will then go through MX. >This is even true if the infamous patch that lets you NOT type the MX% before >domain addressed mail. I asked at the MX bof in San Francisco if anyone was >less lazy than I and had modified the patch to pass addresses without an "@" >through the MX mailshr processing also. Since I've been too lazy to dig into >this, I can't really complain, but pointing it out, might inspire someone else >to look into it. :-) > While this is true for the VAX patch, the recently announced AXP patch actually works correctly with SET TRANSPORT MX%. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 25 Jan 1994 17:00:56 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 16:57:49 EST From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: WKUVX1.WKU.EDU!MX-list@esseye.si.com Message-ID: <0097912B.C761B680.21305@swdev.si.com> Subject: RE: need to find a MAIL logical name Rick Stacks (rick_sys@adpce.lrk.ar.us) writes: >I was thinking (uh-oh) that there was a logical to control turning on/off >the display of the full interpretation of the logical while within MAIL. >Oh, well... ;-) maybe next time. Many thanks for the help on this one. Ah! Now that's a different matter. If one examines the MX docuemntation, one finds that the logical name MX_VMSMAIL_SHOW_ADDR controls MX's display of its rewrite process. Here is an exerpt from MXALIAS' help file: MXalias> help using display Using_Aliases Displaying_Translations To see the resulting addresses used by MX for all MX% addresses, define the logical MX_VMSMAIL_SHOW_ADDR as TRUE: $ define mx_vmsmail_show_addr true $ mail MAIL> SEND To: MX%JOE, MX%"MX-List@WKUVX1.BITNET", SYSTEM MX rewrote alias JOE as MX rewrote MX-List@WKUVX1.BITNET as Subj: .... The MX_VMSMAIL_SHOW_ADDR works regardless of whether or not MX aliases are specified. Perhaps this is what you want. -- Brian ================================================================================ Archive-Date: Tue, 25 Jan 1994 17:09:24 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: MX <-> MHS Message-ID: <1994Jan25.172432.1@nebula> From: itsmgjd@nebula.syscon.hii.com (Gregory J. Donaldson) Reply-To: MX-List@WKUVX1.WKU.EDU Date: 25 Jan 94 17:24:32 -0700 To: MX-List@WKUVX1.WKU.EDU Folks, Several months ago I posted a request for help connecting MX with MHS. After some work I have hacked something together. While it is not something I am ready to distribute I would be interested in sharing my experiences with anyone who is interested. At my site the MX to MHS link was easy. We have an MHS server and a FTP server on our Novell File Server. Therefore all I had to do was format the files, extract some information and transfer them. +------------------------------------------------------------------------------+ | Greg Donaldson, Senior Systems Analyst SYSCON Corporation | | GDonaldson@SYSCON.HII.COM 1000 Thomas Jefferson St. NW | | (202) 342-4123 Washington, DC 20007 | +------------------------------------------------------------------------------+ ================================================================================ Archive-Date: Tue, 25 Jan 1994 17:12:33 CST Sender: list-mgr@WKUVX1.WKU.EDU Message-ID: <0097912D.CFBEEA62.27@ALPHA.WKU.EDU> Return-Path: Date: Tue, 25 Jan 1994 16:57:17 EST From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: WKUVX1.WKU.EDU!list-mgr@esseye.si.com CC: rick_sys@adpce.lrk.ar.us Subject: RE: need to find a MAIL logical name Rick Stacks (rick_sys@adpce.lrk.ar.us) writes: >I was thinking (uh-oh) that there was a logical to control turning on/off >the display of the full interpretation of the logical while within MAIL. >Oh, well... ;-) maybe next time. Many thanks for the help on this one. Ah! Now that's a different matter. If one examines the MX docuemntation, one finds that the logical name MX_VMSMAIL_SHOW_ADDR controls MX's display of its rewrite process. Here is an exerpt from MXALIAS' help file: MXalias> help using display Using_Aliases Displaying_Translations To see the resulting addresses used by MX for all MX% addresses, define the logical MX_VMSMAIL_SHOW_ADDR as TRUE: $ define mx_vmsmail_show_addr true $ mail MAIL> SEND To: MX%JOE, MX%"MX-List@WKUVX1.BITNET", SYSTEM MX rewrote alias JOE as MX rewrote MX-List@WKUVX1.BITNET as Subj: .... The MX_VMSMAIL_SHOW_ADDR works regardless of whether or not MX aliases are specified. Perhaps this is what you want. -- Brian ================================================================================ Archive-Date: Tue, 25 Jan 1994 18:05:34 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Tue, 25 Jan 1994 17:57:43 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: biddlet@indy.navy.mil Message-ID: <00979134.252DE240.1591@SHSU.edu> Subject: RE: Adding subscribers to a list I own. On Tue, 25 Jan 94 15:09:00 EST, Tim Biddle posted: > I own the following list: > > $ mcp show list sysadmin > > Mailing lists: > Name: SYSADMIN > Owner: "tim@TBIDDLE.NAWC-AD-INDY.NAVY.MIL" > And these are the people who are subscribed to the list: > > $ mcp review sysadmin > Tim Biddle > I want to add another person to this list, so I send a message as follows: >... > I get no feedback from this message. So, then when I look at the > mx_mlf_log.log file, I see: > > $ type mx_mlf_log.log > 25-JAN-1994 14:49:22.74 Processing queue entry number 1951 > 25-JAN-1994 14:49:23.52 Checking local name: sysadmin-Request > 25-JAN-1994 14:49:23.53 This is a list control address. > 25-JAN-1994 14:49:23.86 LIST_CTRL_REQ: > Message is from:biddlet@mr1.nawc-ad-indy.navy.mil > 25-JAN-1994 14:49:24.34 LIST_CTRL_REQ: command is: add > Why isn't that user being added to the list? What am I not doing right? > Other users can subscribe by sending a message to the -request address, and > that is how the I subscribed myself, and the other two users subscribed. I > can't do anything as the owner, though. > > Tim Biddle > biddlet@indy.navy.mil The primary reason you don't have access to privileged commands (ADD/REMOVE) is because you are *not* the list owner. The list owner's address is listed as: > Owner: "tim@TBIDDLE.NAWC-AD-INDY.NAVY.MIL" and you are generating: > Tim Biddle (at least on this post). Also, the MLF log indicates that you are: > Message is from:biddlet@mr1.nawc-ad-indy.navy.mil Modify the owner entry via: $ MCP MOD LIST SYSADMIN- /owner=("tim@TBIDDLE.NAWC-AD-INDY.NAVY.MIL","BIDDLET@INDY.NAVY.MIL"- "biddlet@mr1.nawc-ad-indy.navy.mil") and everything should work fine from all of these addresses. Otherwise, get a single address and keep it somehow. I'd also look at considering: $ MCP MOD LIST SYSADMIN /PROT=(S:RWED,O:RWED,G:RWED,W:RWE) but that's not as important for what you're after at the moment. Regards, George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Tue, 25 Jan 1994 22:45:45 CST Sender: list-mgr@WKUVX1.WKU.EDU From: teague@acavax.lynchburg.edu (Kipp) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: How is newsgroup gatewayed to list? Message-ID: <1994Jan25.191507.547@acavax.lynchburg.edu> Date: 25 Jan 94 19:15:07 -0500 To: MX-List@WKUVX1.WKU.EDU Can the maintainer of the MX mailing list advise me as to how the associated USENET newsgroup is gatewayed to the mailing list? I am considering interfacing a mailing list with a newsgroup and I need assistance. Thanks. -------------------------------------------------------------------------------- Kipp Teague E-Mail: teague@acavax.lynchburg.edu Lynchburg College, Lynchburg, Virginia Phone: (804) 522-8358 ================================================================================ Archive-Date: Tue, 25 Jan 1994 23:30:54 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: How is newsgroup gatewayed to list? Message-ID: <1994Jan25.215451.841@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 25 Jan 94 21:54:51 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <1994Jan25.191507.547@acavax.lynchburg.edu>, teague@acavax.lynchburg.edu (Kipp) writes: >Can the maintainer of the MX mailing list advise me as to how the associated >USENET newsgroup is gatewayed to the mailing list? I am considering >interfacing a mailing list with a newsgroup and I need assistance. Hunter Goatley, goathunter@alpha.wku.edu, maintains the mailing list. Mark Berryman, Mark.Berryman@mvb.saic.com, runs the MX-LIST <-> vmsnet.mail.mx gateway on his news server at mvb.saic.com. The news server running on that system (a VMS system) is not ANU-NEWS, but is a (really sharp) news server written in DSM. If you don't know what DSM is, you don't have it. However, there is code in MX_ROOT:[CONTRIB] which is used to run a few mailing lists; I know that DMC.COM runs a few newsgroup <-> mailing list gateways, and that site runs both MX and ANU-NEWS, I believe. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Wed, 26 Jan 1994 05:54:06 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 94 06:48:51 EST From: Tim Biddle Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: RE: Adding subscribers to a list I own. >The primary reason you don't have access to privileged commands >(ADD/REMOVE) is because you are *not* the list owner. The list owner's >address is listed as: >> Owner: "tim@TBIDDLE.NAWC-AD-INDY.NAVY.MIL" >>and you are generating: >> Tim Biddle >(at least on this post). I am the owner of the list. I generate messages from both tim@tbiddle.nawc-ad-indy.navy.mil (my mac) AND biddlet@mr1.nawc-ad-indy.navy.mil (a uVAXII) and neither one works. biddlet@mr1.nawc-ad-indy.navy.mil is registered as a system user. > Also, the MLF log indicates that you are: >> Message is from:biddlet@mr1.nawc-ad-indy.navy.mil Sending a message from biddlet@mr1... should work, because that address is registered as a system user. Sending a message from tim@tbiddle... should also work, because that is the owner address. >Regards, George Thanks, George! BTW, in response to the post Dan Wing made, it doesn't matter whether I send a message to the -Request address, or to mxserver, both of which I have done, being very careful to include all the right commands for both addresses, and neither works. I think I messed up on the post I made, but I have been over and over this, pouring over the manual to try to find something I missed. For example: I send a message to mxserver that says: add sysadmin johnnie.goodman@oa-mail... and that does not succeed. I send a message to sysadmin-request that says: add johnnie.goodman@oa-mail... and that does not succeed either. I am about to pull my hair out. And I don't have that much. TIm Biddle biddle@indy.navy.mil (my primary internet connection!) ================================================================================ Archive-Date: Wed, 26 Jan 1994 06:55:03 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 94 06:51:38 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: need to find a MAIL logical name To: mx-list@wkuvx1.wku.edu Message-ID: <009791A0433D6140.20201B2C@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > >Rick Stacks (rick_sys@adpce.lrk.ar.us) writes: > >>I was thinking (uh-oh) that there was a logical to control turning on/off >>the display of the full interpretation of the logical while within MAIL. >>Oh, well... ;-) maybe next time. Many thanks for the help on this one. > Brian Tillman writes in reply: >Ah! Now that's a different matter. If one examines the MX docuemntation, one ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Ooopps, missed it! :-( But this is *exactly* what I was looking for :-) >finds that the logical name MX_VMSMAIL_SHOW_ADDR controls MX's display of its >rewrite process. Here is an exerpt from MXALIAS' help file: > >MXalias> help using display >Using_Aliases > > Displaying_Translations > > To see the resulting addresses used by MX for all MX% addresses, > define the logical MX_VMSMAIL_SHOW_ADDR as TRUE: > > $ define mx_vmsmail_show_addr true > $ mail > > MAIL> SEND > To: MX%JOE, MX%"MX-List@WKUVX1.BITNET", SYSTEM > MX rewrote alias JOE as > MX rewrote MX-List@WKUVX1.BITNET as > Subj: .... > > The MX_VMSMAIL_SHOW_ADDR works regardless of whether or not MX > aliases are specified. > >Perhaps this is what you want. >-- >Brian Thanks so much to all for the help on this one. Next time I'll need to use another program obtained from DECUS friends -- VTBOOK to read the documentation a little closer -- Thanks, --Rick ================================================================================ Archive-Date: Wed, 26 Jan 1994 07:52:40 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 07:48:18 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: biddle@indy.navy.mil CC: MX-List@WKUVX1.WKU.EDU Message-ID: <009791A8.2D2F0AE0.5238@SHSU.edu> Subject: RE: Adding subscribers to a list I own. On Wed, 26 Jan 94 06:48:51 EST, Tim Biddle replied: > >The primary reason you don't have access to privileged commands > >(ADD/REMOVE) is because you are *not* the list owner. The list owner's > >address is listed as: > >> Owner: "tim@TBIDDLE.NAWC-AD-INDY.NAVY.MIL" > >>and you are generating: > >> Tim Biddle > >(at least on this post). >... > Sending a message from biddlet@mr1... should work, because that address is > registered as a system user. Sending a message from tim@tbiddle... should > also work, because that is the owner address. >... > BTW, in response to the post Dan Wing made, it doesn't matter whether I > send a message to the -Request address, or to mxserver, both of which I > have done, being very careful to include all the right commands for both > addresses, and neither works. I think I messed up on the post I made, but > I have been over and over this, pouring over the manual to try to find > something I missed. This sounds similar to a bug back in an earlier version of MX (pre-3.x if I recall right) which was fixed by Matt back when he was running the show (I know it was pre-Hunter because this series of exchanges and the testing on it allowed me to get to learn more about Matt and MX -- and probably make Matt wish that SHSU wasn't using MX). The bug was such that only list owners had list owner command access and system protections on lists were effectively meaningless for ADD and REMOVE. Insofar as the problems and applications the bug impacted on our operation, everything was graciously, effectively, and efficiently fixed (thanks again, Matt!). However, maybe this event is something hidden that is related if not parallel. I don't mean to even infer that your report is in error -- please don't take this next sentence that way. Can you verify that mail from the address fails -- have you seen the debug log with this exactly-cased username on that exactly named host fail? Regards, George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Wed, 26 Jan 1994 08:09:33 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 94 09:01:32 EST From: Tim Biddle Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Subject: Adding users to the list. Thanks to Dan Wing for pointing out that the address with the quotes around it was an invalid address. For example: This address IS NOT valid: "Timothy.Biddle@oa-mail.nawc-ad-indy.navy.mil" But, change the quotes to angle brackets and This address IS valid: It sure would be nice if the mxserver would send an error message to let the list owner know he is sending addresses in an invalid format. As it is, it doesn't complain at all. Those addresses just never get added. Maybve something for 3.4 when it goes production. Tim Biddle biddlet@indy.navy.mil ================================================================================ Archive-Date: Wed, 26 Jan 1994 10:05:23 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 08:00:30 PDT From: Jim Wheeler # 916-978-5089 Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: teague@acavax.lynchburg.edu, jimww@sacto.mp.usbr.gov Message-ID: <009791A9.E204DCB4.30494@sacto.mp.usbr.gov> Subject: RE: How is newsgroup gatewayed to list? >From: MX%"MX-List@WKUVX1.WKU.EDU" 25-JAN-1994 21:12:46.70 > >Can the maintainer of the MX mailing list advise me as to how the associated >USENET newsgroup is gatewayed to the mailing list? I am considering >interfacing a mailing list with a newsgroup and I need assistance. > >Thanks. >-------------------------------------------------------------------------------- >Kipp Teague E-Mail: teague@acavax.lynchburg.edu >Lynchburg College, Lynchburg, Virginia Phone: (804) 522-8358 Please, answer to the list, I have the same desire. Kipp, If you get info not from the list would you share?? TIA - jimww ================================================================================ # James W. Wheeler # # # Regional Systems & WAN Manager # voice: 916 978-5089 fax: 916-978-5284 # # Mid Pacific Region # # # U.S. Bureau of Reclamation # inet: jimww@sacto.mp.usbr.gov # # 2800 Cottage Way MP1130 # # # Sacramento, CA 95825 # # ================================================================================ ================================================================================ Archive-Date: Wed, 26 Jan 1994 10:17:06 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 11:12:00 EST From: Mighty Firebreather Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009791C4.A25E0FC0.28985@nscvax.princeton.edu> Subject: MX Startup I just had to restart MX V3.1 by hand (don't ask) and got about dozen messages in reply saying that I needed CMKRNL privilege. It would be a nice convenience if the startup file were jacketed with something like the following: $ REQUIRED_PRIVILEGES :=(CMKRNL, ...) ! Insert all required privs $ PREV_PRIVS = F$SETPRV(REQUIRED_PRIVILEGES) $ IF .NOT. F$PRIVILEGE(REQUIRED_PRIVILEGES) THEN GOTO NO_PRIVILEGES $... $... $EXIT: $ PREV_PRIVS = F$SETPRV(PREV_PRIVS) $ EXIT $ $NO_PRIVILEGES: $ WRITE SYS$OUTPUT "Insufficient privileges to start the MX Mailer" $ WRITE SYS$OUTPUT "Requires ",REQUIRED_PRIVILEGES," privileges." $ GOTO EXIT If the user has SETPRV or if he has AUTHORIZED privileges which are not turned on, the startup goes ahead and does the right thing. If the user does not have the necessary privileges, the startup simply exits with an informative message and no loss of time or half complete startups. ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Wed, 26 Jan 1994 10:29:12 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 11:24:49 EST From: kamrul@ycvax.york.cuny.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@wkuvx1.wku.edu Message-ID: <009791C6.6CDA3160.4482@ycvax.york.cuny.edu> Subject: Documents on Fileserver of MX Hi: I am trying to understand how MX Fileserver works. Does anyone know where I can find some info on it ? I looked into the document MLF_GUIDE.SDML which has only a few lines. I would like to know how to manage the file server and how to retrieve information from it. Thanks in advance. Kamrul Ahsan York College, CUNY New York. 718-262-2754 ================================================================================ Archive-Date: Wed, 26 Jan 1994 11:44:42 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 12:40:17 EST From: kam@ycvax.york.cuny.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: Mx-List@wkuvx1.wku.edu Message-ID: <009791D0.F7893AE0.4542@ycvax.york.cuny.edu> Subject: Doc for Mx Fileserver Could anyone please tell me where to find documentations for MX Fileserver only . I need some info on how to manage and maintain Mx fileserver. Willing to read the manual. Thanks in advance. Kamrul Ahsan York College CUNY, New York ================================================================================ Archive-Date: Wed, 26 Jan 1994 11:48:31 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Adding users to the list. Message-ID: <1994Jan26.094025.842@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 26 Jan 94 09:40:24 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19664685@MVB.SAIC.COM>, Tim Biddle writes: >Thanks to Dan Wing for pointing out that the address with the quotes around it >was an invalid address. > >For example: > > This address IS NOT valid: "Timothy.Biddle@oa-mail.nawc-ad-indy.navy.mil" > >But, change the quotes to angle brackets and > > This address IS valid: > > It sure would be nice if the mxserver would send an error message to let the >list owner know he is sending addresses in an invalid format. As it is, it >doesn't complain at all. Those addresses just never get added. Maybve >something for 3.4 when it goes production. Does this mean you got the address added to your mailing list? -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Wed, 26 Jan 1994 12:03:17 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 10:04:49 EST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: biddlet@indy.navy.mil Message-ID: <009791BB.3FC695C0.5901@SHSU.edu> Subject: RE: Adding users to the list. On Wed, 26 Jan 94 09:01:32 EST, Tim Biddle posted: > Thanks to Dan Wing for pointing out that the address with the quotes around > it was an invalid address. > > For example: > > This address IS NOT valid: "Timothy.Biddle@oa-mail.nawc-ad-indy.navy.mil" > > But, change the quotes to angle brackets and > > This address IS valid: > > It sure would be nice if the mxserver would send an error message to let > the list owner know he is sending addresses in an invalid format. As it > is, it doesn't complain at all. Those addresses just never get added. > Maybve something for 3.4 when it goes production. Hmmmmm. It's not that the address is in an invalid format -- the address is missing! > For address, you should enter the RFC822-type address > for the user to be added. It should generally appear > exactly as it does on the From line of a message, > since the mailing list processor is case sensitive in > the username part of addresses. You may include the > personal name, if desired. [MX_DOC:MLF_GUIDE.*; V3.3, May 1993, p. 3-9] I agree that notification that it was unable to process a request would be a nice feature eventually. A valid "RFC822-type address" specifically would mean that the quoted string is essentially ignored in processing intentionally to provide support for things such as personal names; however, a quoted string is required when the string includes a special character in its token (such as a period or other symbols). I don't have the RFC handy at the moment, but if I recall correctly, addresses are intended to have angle brackets around them. MLF trashes them in the *.MAILING_LIST files if there is no personal name, though. Possibly a specific example of ADD is needed in the MLF guide in addition to the generalized format of the command. Might be a good beginning for inclusion in the 3.4 docs, Hunter. --George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Wed, 26 Jan 1994 12:40:42 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 12:12:11 CST From: George Franklin Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <009791CD.0A988540.2055@oehl.brooks.af.mil> Subject: Subscribe to Mailing List SUBSCRIBE spectator@OEHL.brooks.af.mil ================================================================================ Archive-Date: Wed, 26 Jan 1994 13:14:52 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 13:14:16 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009791D5.B7176CD4.17@ALPHA.WKU.EDU> Subject: RE: Adding users to the list. "George D. Greenwade" writes: > >I agree that notification that it was unable to process a request would be >a nice feature eventually. Yep. On the wish list. >A valid "RFC822-type address" specifically >would mean that the quoted string is essentially ignored in processing >intentionally to provide support for things such as personal names; >however, a quoted string is required when the string includes a special >character in its token (such as a period or other symbols). I don't have >the RFC handy at the moment, but if I recall correctly, addresses are >intended to have angle brackets around them. MLF trashes them in the >*.MAILING_LIST files if there is no personal name, though. > Correct. >Possibly a specific example of ADD is needed in the MLF guide in addition >to the generalized format of the command. Might be a good beginning for >inclusion in the 3.4 docs, Hunter. > Already in there. A little example goes a long way. 8-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 26 Jan 1994 13:38:24 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 07:44:44 CST From: George Franklin Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <009791A7.ADB51200.2013@oehl.brooks.af.mil> Subject: Please Help The following are error messages that I get when trying to send mail to Germany over the internet. I did talk to someone there and the person logged into her computer to give me the information concerning her mailing address. Can someone advise me on what might be causing this problem? Thanks, George Franklin System Administrator (210)536-2484 Brooks AFB, TX FAX: (210)536-3945 ******************************************************************************* I could not ping it, either. %FINGER-F-CONNECT, Can't open a connection to 192.138.41.1 -IPACP-E-URC, Destination Unreachable Entry: 2009, Origin: [Local] Status: IN-PROGRESS, size: 650 bytes Created: 26-JAN-1994 07:25:27.44, expires 25-FEB-1994 07:25:27.44 Last modified 26-JAN-1994 07:25:35.18 SMTP entry #2010, status: READY, size: 650 bytes, waiting for retry until 26-JAN-1994 07:55:41.21 Created: 26-JAN-1994 07:25:32.52, expires 25-FEB-1994 07:25:27.44 Last modified 26-JAN-1994 07:25:41.21 Recipient #1: , Route=larmc-amedd.army.mil Error count=1 Last error: %SYSTEM-F-UNREACHABLE, remote node is not currently reachable Entry: 2011, Origin: [Local] Status: IN-PROGRESS, size: 86 bytes Created: 26-JAN-1994 07:28:34.18, expires 25-FEB-1994 07:28:34.18 Last modified 26-JAN-1994 07:29:10.02 SMTP entry #2012, status: READY, size: 86 bytes, waiting for retry until 26-JAN-1994 07:59:11.26 Created: 26-JAN-1994 07:29:07.42, expires 25-FEB-1994 07:28:34.18 Last modified 26-JAN-1994 07:29:11.29 Recipient #1: , Route=larmc-amedd.army.mil Error count=1 Last error: %SYSTEM-F-UNREACHABLE, remote node is not currently reachable ================================================================================ Archive-Date: Wed, 26 Jan 1994 15:20:12 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 14:42:33 CST From: George Franklin Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <009791E2.0C3BEF80.2079@oehl.brooks.af.mil> Subject: MCP Errors The following are error messages that I get when trying to send mail to Germany over the internet. I did talk to someone there and the person logged into her computer to give me the information concerning her mailing address. Can someone advise me on what might be causing this problem and how I might recover from this? Thanks, George Franklin System Administrator (210)536-2484 Brooks AFB, TX FAX: (210)536-3945 ******************************************************************************* I could not ping it, either. %FINGER-F-CONNECT, Can't open a connection to 192.138.41.1 -IPACP-E-URC, Destination Unreachable Entry: 2009, Origin: [Local] Status: IN-PROGRESS, size: 650 bytes Created: 26-JAN-1994 07:25:27.44, expires 25-FEB-1994 07:25:27.44 Last modified 26-JAN-1994 07:25:35.18 SMTP entry #2010, status: READY, size: 650 bytes, waiting for retry until 26-JAN-1994 07:55:41.21 Created: 26-JAN-1994 07:25:32.52, expires 25-FEB-1994 07:25:27.44 Last modified 26-JAN-1994 07:25:41.21 Recipient #1: , Route=larmc-amedd.army.mil Error count=1 Last error: %SYSTEM-F-UNREACHABLE, remote node is not currently reachable Entry: 2011, Origin: [Local] Status: IN-PROGRESS, size: 86 bytes Created: 26-JAN-1994 07:28:34.18, expires 25-FEB-1994 07:28:34.18 Last modified 26-JAN-1994 07:29:10.02 SMTP entry #2012, status: READY, size: 86 bytes, waiting for retry until 26-JAN-1994 07:59:11.26 Created: 26-JAN-1994 07:29:07.42, expires 25-FEB-1994 07:28:34.18 Last modified 26-JAN-1994 07:29:11.29 Recipient #1: , Route=larmc-amedd.army.mil Error count=1 Last error: %SYSTEM-F-UNREACHABLE, remote node is not currently reachable ================================================================================ Archive-Date: Wed, 26 Jan 1994 15:30:40 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 13:22:05 EST From: "Brian R. Kuhn" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009791D6.CE51B840.6285@SD68.NANAIMO.BC.CA> Subject: Re: Please Help George Franklin says: > The following are error messages that I get when trying to send > mail to Germany over the internet. > > I did talk to someone there and the person logged into her computer to > give me the information concerning her mailing address. > > ******************************************************************************* > > I could not ping it, either. > > > %FINGER-F-CONNECT, Can't open a connection to 192.138.41.1 > -IPACP-E-URC, Destination Unreachable > > > Entry: 2009, Origin: [Local] > Status: IN-PROGRESS, size: 650 bytes > Created: 26-JAN-1994 07:25:27.44, expires 25-FEB-1994 07:25:27.44 > Last modified 26-JAN-1994 07:25:35.18 > SMTP entry #2010, status: READY, size: 650 bytes, waiting for retry until > 26-JAN-1994 07:55:41.21 > Created: 26-JAN-1994 07:25:32.52, expires 25-FEB-1994 07:25:27.44 > Last modified 26-JAN-1994 07:25:41.21 > Recipient #1: , Route=larmc-amedd.army.mil > Error count=1 > Last error: %SYSTEM-F-UNREACHABLE, remote node is not currently reachable > > Entry: 2011, Origin: [Local] > Status: IN-PROGRESS, size: 86 bytes > Created: 26-JAN-1994 07:28:34.18, expires 25-FEB-1994 07:28:34.18 > Last modified 26-JAN-1994 07:29:10.02 > SMTP entry #2012, status: READY, size: 86 bytes, waiting for retry until > 26-JAN-1994 07:59:11.26 > Created: 26-JAN-1994 07:29:07.42, expires 25-FEB-1994 07:28:34.18 > Last modified 26-JAN-1994 07:29:11.29 > Recipient #1: , Route=larmc-amedd.army.mil > Error count=1 > Last error: %SYSTEM-F-UNREACHABLE, remote node is not currently reachable As the message says, the remote node is not currently reachable which indicates either they are off-line at that point *or* there is a routing problem there - I tried a UCX PING and got imcp_type(3) back which I think indicates a routing or subnet masking problem??? Brian ----------------------------------------------------------------------- Brian R. Kuhn, Co-ordinator of Information Systems VOICE: 604 741 5289 School District No. 68 (Nanaimo), FAX: 604 754 6511 British Columbia, Canada DATA: 604 754 3630 TELNET: crc.sd68.nanaimo.bc.ca (guest) *(bbs --> guest)* EMAIL: bkuhn@sd68.nanaimo.bc.ca Compuserve: 75430,3250 ------------------------------------------------------------------------ ================================================================================ Archive-Date: Wed, 26 Jan 1994 18:08:55 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Wed, 26 Jan 1994 19:04:23 EST From: kam@ycvax.york.cuny.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@wkuvx1.wku.edu CC: kamyc@cunyvm.cuny.edu Message-ID: <00979206.9FC5ABA0.4878@ycvax.york.cuny.edu> Subject: Local delivery error for fileserv I went through the document mlf_guide.txt as directed by Ray Harwood ( Thank you) and now came up with real problem. Whenever I send a mail to fileserv it bounces back with "Local delivery error". I tried to capture mx_mlf_dir:mx_mlf_log.log by turning on the logical mx_mlf_debug true.But it does not even create a log file. Whereas, if I send mail to listserv it creates a new mx_mlf_log.log file. I am including the return mail for your perusal. Do I need to activate fileserver seperately? Thank you for any help. Here is the returned mail ***************************************************************************** From: MX%"Postmaster@ycvax.york.cuny.edu" 26-JAN-1994 18:26:31.53 To: ARAM CC: Subj: LOCAL delivery error Return-Path: <> Date: Wed, 26 Jan 1994 18:26:24 EST From: Local delivery agent To: Subject: LOCAL delivery error X-Report-Type: Nondelivery; boundary="> Error description:" Note: this message was generated automatically. An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: fileserv@ycvax.york.cuny.edu Error-Code: 3 Error-Text: No such local user Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ Received: by ycvax.york.cuny.edu (MX V3.3 VAX) id 4838; Wed, 26 Jan 1994 18:26:21 EST Date: Wed, 26 Jan 1994 18:26:19 EST From: aram@ycvax.york.cuny.edu To: fileserv@ycvax.york.cuny.edu Message-ID: <00979201.4EB338E0.4838@ycvax.york.cuny.edu> Help ================================================================================ Archive-Date: Wed, 26 Jan 1994 20:48:42 CST Sender: list-mgr@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Please Help Date: 27 Jan 1994 02:05:27 GMT Message-ID: <2i77h8$aj1@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <009791A7.ADB51200.2013@oehl.brooks.af.mil>, George Franklin writes: =The following are error messages that I get when trying to send =mail to Germany over the internet. = =I did talk to someone there and the person logged into her computer to =give me the information concerning her mailing address. = =Can someone advise me on what might be causing this problem? The machine's not reachable. The machine might be down, or some network link between you and the machine you're trying to reach might be down. -------------------------------------------------------------------------------- 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, 27 Jan 1994 02:24:01 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Thu, 27 Jan 1994 08:20:28 EST From: Mike Davies Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00979275.D5F45EA0.11300@hectic.harwell.aea.orgn.uk> Subject: RE: Please Help > %FINGER-F-CONNECT, Can't open a connection to 192.138.41.1 > -IPACP-E-URC, Destination Unreachable > Last modified 26-JAN-1994 07:25:35.18 > SMTP entry #2010, status: READY, size: 650 bytes, waiting for retry until > 26-JAN-1994 07:55:41.21 > Created: 26-JAN-1994 07:25:32.52, expires 25-FEB-1994 07:25:27.44 > Last modified 26-JAN-1994 07:25:41.21 > Recipient #1: , Route=larmc-amedd.army.mil > Error count=1 > Last error: %SYSTEM-F-UNREACHABLE, remote node is not currently reachable When trying to ping this destination, I get : % ping larmc-amedd.army.mil ICMP Host Unreachable from gateway en-0.ENSS136.t3.ANS.NET (192.41.177.253) for icmp from gw (151.182.136.1) to 192.138.41.1 -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Davies Internet: Mike.Davies@AEA.orgn.uk AEA Technology, 364 Harwell, Didcot Local: hectic::davies Oxfordshire, OX11 0RA, U.K. Phone: +44 235 434079 FAX: +44 235 436318 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Please note that any views expressed here do not necessarily reflect the views or policies of AEA Technology. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ================================================================================ Archive-Date: Thu, 27 Jan 1994 09:10:46 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Doc for Mx Fileserver Message-ID: <1994Jan27.072613.845@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 27 Jan 94 07:26:13 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <009791D0.F7893AE0.4542@ycvax.york.cuny.edu>, kam@ycvax.york.cuny.edu writes: >Could anyone please tell me where to find documentations for MX Fileserver only >.. I need some info on how to manage and maintain Mx fileserver. Willing to read >the manual. MX_DOC:MLF_GUIDE.TXT, .PS, and .DECW$BOOK. If you didn't install documentation when you installed MX, you can pull them out of the .K saveset manually. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Thu, 27 Jan 1994 09:11:08 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Re: Local delivery error for fileserv Message-ID: <1994Jan27.072938.846@buckie.hsc.colorado.edu> From: dwing@uh01.Colorado.EDU (Dan Wing) Date: 27 Jan 94 07:29:38 MDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <00979206.9FC5ABA0.4878@ycvax.york.cuny.edu>, kam@ycvax.york.cuny.edu writes: >I went through the document mlf_guide.txt as directed by Ray Harwood ( >Thank you) and now came up with real problem. Whenever I send a mail to >fileserv it bounces back with "Local delivery error". I tried to capture >mx_mlf_dir:mx_mlf_log.log by turning on the logical mx_mlf_debug true.But it >does not even create a log file. Whereas, if I send mail to listserv it creates >a new mx_mlf_log.log file. > >I am including the return mail for your perusal. Do I need to activate >fileserver seperately? Did you do a "MCP RESET/CLUSTER ROUTER"? -d -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing@eisner.decus.org ================================================================================ Archive-Date: Thu, 27 Jan 1994 11:11:18 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Thu, 27 Jan 1994 09:04:22 PDT From: Jim Wheeler # 916-978-5089 Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: jimww@sacto.mp.usbr.gov Message-ID: <0097927B.F80B41C4.31302@sacto.mp.usbr.gov> Subject: RE: Please Help =From: MX%"MX-List@WKUVX1.WKU.EDU" 27-JAN-1994 01:07:59.66 =Subject: RE: Please Help = = => %FINGER-F-CONNECT, Can't open a connection to 192.138.41.1 => -IPACP-E-URC, Destination Unreachable = = => Last modified 26-JAN-1994 07:25:35.18 => SMTP entry #2010, status: READY, size: 650 bytes, waiting for retry until => 26-JAN-1994 07:55:41.21 => Created: 26-JAN-1994 07:25:32.52, expires 25-FEB-1994 07:25:27.44 => Last modified 26-JAN-1994 07:25:41.21 => Recipient #1: , Route=larmc-amedd.army.mil => Error count=1 => Last error: %SYSTEM-F-UNREACHABLE, remote node is not currently reachable = =When trying to ping this destination, I get : = =% ping larmc-amedd.army.mil = =ICMP Host Unreachable from gateway en-0.ENSS136.t3.ANS.NET (192.41.177.253) = for icmp from gw (151.182.136.1) to 192.138.41.1 = =-- =- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =Mike Davies Internet: Mike.Davies@AEA.orgn.uk =AEA Technology, 364 Harwell, Didcot Local: hectic::davies =Oxfordshire, OX11 0RA, U.K. Phone: +44 235 434079 = FAX: +44 235 436318 =- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - = Please note that any views expressed here do not = necessarily reflect the views or policies of AEA Technology. =- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - traceroute to 192.138.41.1 (192.138.41.1), 30 hops max, 38 byte packets 1 mp-recnet (140.214.12.253) 30 ms 10 ms 20 ms 2 USBR.BARRNET.NET (192.31.51.1) 30 ms 20 ms 20 ms 3 UCD.BARRNET.NET (131.119.12.1) 20 ms 20 ms 30 ms 4 CR2.BARRNET.NET (131.119.9.1) 30 ms 30 ms 20 ms 5 fd-0.enss128.t3.ans.net (192.31.48.244) 30 ms !H 30 ms !H 30 ms !H Please, note the ping and traceroute stop at ans.net. My guess is there is a firewall blocking your efforts. This is not unusual for protected nets in MIL (or anywhere else). jimww ================================================================================ # James W. Wheeler # # # Regional Systems & WAN Manager # voice: 916 978-5089 fax: 916-978-5284 # # Mid Pacific Region # # # U.S. Bureau of Reclamation # inet: jimww@sacto.mp.usbr.gov # # 2800 Cottage Way MP1130 # # # Sacramento, CA 95825 # # ================================================================================ ================================================================================ Archive-Date: Thu, 27 Jan 1994 11:59:40 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Thu, 27 Jan 1994 12:55:27 EST From: kamrul@ycvax.york.cuny.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097929C.4056E8A0.5451@ycvax.york.cuny.edu> Subject: Re: Local delivery error for fileserv > In article <00979206.9FC5ABA0.4878@ycvax.york.cuny.edu>, kam@ycvax.york.cuny.edu writes: > >I went through the document mlf_guide.txt as directed by Ray Harwood ( > >Thank you) and now came up with real problem. Whenever I send a mail to > >fileserv it bounces back with "Local delivery error". I tried to capture > >mx_mlf_dir:mx_mlf_log.log by turning on the logical mx_mlf_debug true.But it > >does not even create a log file. Whereas, if I send mail to listserv it creates > >a new mx_mlf_log.log file. > > > >I am including the return mail for your perusal. Do I need to activate > >fileserver seperately? > > Did you do a "MCP RESET/CLUSTER ROUTER"? > > -d Yes I did. Only thing I did differently is to redefine the directory for a list's fileservice directory ( first time I defined a file service for a list). Thank you. Kamrul Ahsan CUNY ================================================================================ Archive-Date: Thu, 27 Jan 1994 13:38:24 CST Sender: list-mgr@WKUVX1.WKU.EDU From: sys_hjk@lissy1.lif.de (Hans-Joachim Koch) Subject: Re: Mail2News Gateway with NEWSRDR? Message-ID: <4090@sunny.lif.de> Date: 27 Jan 94 08:43:03 GMT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <19578437@MVB.SAIC.COM>, goathunter@ALPHA.WKU.EDU (Hunter Goatley, WKU) writes: >You can use Brian McKeever's MX_POST, which works with NNTP servers to >post messages. Sounds like it'd do exactly what Hans wants to do. >This software is included in MX V3.4, due out soon. You can also get >it now from ftp.spc.edu in [.MX.CONTRIB]MX_POST.ZIP. Hello Hunter, thanks a lot for this _great_ hint. I got the program (already modified it, my very first change in a c program :-) and it works very well. >>BULLETIN hasn't, and I'll bet won't, be ported to Unix. >Several hundred blocks for VMS-specific FORTRAN code?? Not likely. 8-) I never really thought of it... Hans. -- Hans-Joachim Koch, Computer department of Lahmeyer International Lyoner Strasse 22, D-60528 Frankfurt, Germany Phone: +49 (69) 6677-642, Fax: +49 (69) 6677-388, Tx: 413478 li d ================================================================================ Archive-Date: Thu, 27 Jan 1994 18:38:00 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Thu, 27 Jan 1994 18:33:44 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <009792CB.8232E920.3695@uwwvax.uww.edu> Subject: RE: Please Help Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Fri, 28 Jan 1994 07:08:59 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 28 Jan 1994 07:02:28 CST From: Roger Courtney Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00979334.1AF42760.3593@ringo.birdville.k12.tx.us> Subject: Remove subscriber problem I am trying to remove a user from a local mailing list. I keep getting "REMOVE failed: insufficient privilege" errors. I am the OWNER of the list! Any ideas? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Roger Courtney Birdville Independent School District - Supervisor of Systems, 3126 Carson St Programming and operations Fort Worth, TX 76117 Voice: (817) 831-5892 E-Mail: courtney@birdville.k12.tx.us Fax: (817) 831-5896 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ MESSAGE FOLLOWS > From: MX%"Postmaster@birdville.k12.tx.us" > Subject: > Message-ID: > > Return-Path: <> > Date: Fri, 28 Jan 1994 06:56:21 CST > From: Mailing list & file server > > Note: this message was generated automatically. > > The following error(s) occurred during local delivery of your message. > > Error in delivery to mailing list SIS: > REMOVE failed: insufficient privilege > > ------------------------------ Rejected message ------------------------------ > From: COURTNEY@BIRDVILLE.K12.TX.US > To: SIS-request@BIRDVILLE.K12.TX.US > Date: Fri, 28 Jan 1994 06:56:19 CST > Subject: remove phelps@ringo.birdville.k12.tx.us > > remove phelps@ringo.birdville.k12.tx.us > ================================================================================ Archive-Date: Fri, 28 Jan 1994 07:47:21 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 28 Jan 1994 07:42:55 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <00979339.C1EA8460.5965@uwwvax.uww.edu> Subject: RE: Remove subscriber problem => I am trying to remove a user from a local mailing list. I keep getting => "REMOVE failed: insufficient privilege" errors. I am the OWNER of the list! => => Any ideas? I found that so matter what I did it failed with listserv however it works with request. Also watch the case that your owner= indicates and the case send. It is a nasty problem. Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Fri, 28 Jan 1994 08:49:13 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Fri, 28 Jan 1994 09:45:23 -0500 (EST) From: NROTH@WVNVAXA.WVNET.EDU Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX033 --> UUCP 2.0 problems To: mx-list@wkuvx1.wku.edu Message-ID: <01H87MP6TCOYFBVR2T@WVNVMS.WVNET.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT We are trying to get MX033 working correctly with UUCP 2.0 and are having problems with MX putting information into the FROM: line incorrectly (maybe we are doing it wrong). Our mail goes like this: VAX 3900 <----> UNIX machine <----> Univ. KY (internet) Internally we call our machine aca.wvwc.edu (VAX) the Unix machine is acpwvw Univ. of KY is ms.uky.edu The problem seems to come from MX when it hands it over to UUCP. MX is insisting upon putting its own wvwc.! in front of the user. We have yet to figure where the "." is coming from. Can some on shed some light on this and how to correct it? The from line should look like: acpwvw!wvwc!user@ms.uky.edu Here are the logicals (some of them) that are defined: MX_NODE_NAME = "aca.wvwc.edu" MX_UUCP_REWRITE = "TRUE" MX_VMSMAIL_LOCAL_HOST = "@aca.wvwc.edu" UUCP_HOST_NAME = "wvwc" UUCP_UUXQT_DCL_RMAIL_MX = "TRUE" This is the message received from MX From: IN%"acpwvw!wvwc!wvwc.!programmer@ms.uky.edu" 26-JAN-1994 11:18:38.68 To: IN%"nroth@WVNVMS.WVNET.EDU" CC: Subj: mx ---> wvu Return-path: <@s.ms.uky.edu:acpwvw!wvwc!wvwc.!programmer@ms.uky.edu> Received: from mozart.ms.uky.edu by WVNVMS.WVNET.EDU (PMDF V4.2-14 #5406) id <01H84XCMY2PSF9KNQZ@WVNVMS.WVNET.EDU>; Wed, 26 Jan 1994 11:18:12 EST Received: from s.ms.uky.edu by mozart.ms.uky.edu id ak05550; 26 Jan 94 10:45 EST Received: by wvwc.UUCP (DECUS UUCP /2.0/2.0/2.0/); Tue, 25 Jan 94 22:22:54 EST Received: by aca.wvwc.edu (MX V3.3 VAX) id 28183; Tue, 25 Jan 1994 22:21:12 EST Date: Tue, 25 Jan 1994 22:16:10 -0500 (EST) From: acpwvw!wvwc!wvwc.!programmer@ms.uky.edu Subject: mx ---> wvu Sender: acpwvw!wvwc!wvwc.!programmer@ms.uky.edu To: nroth@WVNVMS.WVNET.EDU Message-id: <00979158.408C5FC0.28183@aca.wvwc.edu> Content-transfer-encoding: 7BIT I have checked the rewrite rules as well as just about anything else I could think of to see if there was a typo, but nothing. Thanks in advance. William G. Howard West Virginia Wesleyan College acpwvw!wvwc!programmer@ms.uky.edu (slow) nroth@wvnsvc.wvnet.edu (Please use this until we clear it up) (304) 473-8318 ================================================================================ Archive-Date: Fri, 28 Jan 1994 20:02:25 CST Sender: list-mgr@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Remove subscriber problem Date: 29 Jan 1994 01:06:02 GMT Message-ID: <2iccpq$sbi@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <00979334.1AF42760.3593@ringo.birdville.k12.tx.us>, Roger Courtney writes: = =I am trying to remove a user from a local mailing list. I keep getting ="REMOVE failed: insufficient privilege" errors. I am the OWNER of the list! = =MESSAGE FOLLOWS = => From: MX%"Postmaster@birdville.k12.tx.us" => Subject: => Message-ID: => => Return-Path: <> => Date: Fri, 28 Jan 1994 06:56:21 CST => From: Mailing list & file server => => Note: this message was generated automatically. => => The following error(s) occurred during local delivery of your message. => => Error in delivery to mailing list SIS: => REMOVE failed: insufficient privilege => => ------------------------------ Rejected message ------------------------------ => From: COURTNEY@BIRDVILLE.K12.TX.US => To: SIS-request@BIRDVILLE.K12.TX.US => Date: Fri, 28 Jan 1994 06:56:19 CST => Subject: remove phelps@ringo.birdville.k12.tx.us => => remove phelps@ringo.birdville.k12.tx.us => You didn't bother to send the output of the MCP SHOW LIST command. Are you *REALLY* the owner of the list? We can't tell since you haven't given us that information. Remember: In usernames, case counts. -------------------------------------------------------------------------------- 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, 30 Jan 1994 22:52:20 CST Sender: list-mgr@WKUVX1.WKU.EDU Subject: Q:Linking mailing lists to file servers. Message-ID: <1994Jan30.210309.766@earlham.edu> From: michaelb@earlham.edu Reply-To: MX-List@WKUVX1.WKU.EDU Date: Sun, 30 Jan 94 21:02:33 -500 To: MX-List@WKUVX1.WKU.EDU I am setting up a mailing list and want to have an associated file server for the list. My question is do I need to have a file server for each mailing list or can I set up one file server? If I can set up one file server, can I still link it to a list? I have a list called palnitrn-l and a file server called palnitrn-f. I sent the message HELP to palnitrn-f and I got a message back that said there was an error processing my request. I am not sure what to do. I created the list properly and set all the protections to REWD. But I still get this message. Is this suppose to happen? Lastly, is there a way to setup individual MLIST_ADD_MESSAGE.TXT for each list? Michael ================================================================================ Archive-Date: Mon, 31 Jan 1994 06:46:01 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 31 Jan 1994 06:45:51 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097958D.47CD0EE0.19@ALPHA.WKU.EDU> Subject: RE: Q:Linking mailing lists to file servers. michaelb@earlham.edu writes: > >I am setting up a mailing list and want to have an associated file server >for the list. My question is do I need to have a file server for each >mailing list or can I set up one file server? If I can set up one file >server, can I still link it to a list? > No, the relationship is one mailing list per file server. >I have a list called palnitrn-l and a file server called palnitrn-f. I >sent the message HELP to palnitrn-f and I got a message back that said >there was an error processing my request. I am not sure what to do. I >created the list properly and set all the protections to REWD. But I still >get this message. Is this suppose to happen? > Does your address match your subscriber entry, which, given the address above, should be "michaelb@EARLHAM.EDU"? You can enabled debug logs for the MX MLF by defining the logical MX_MLF_DEBUG as: $ DEFINE/SYSTEM/EXEC MX_MLF_DEBUG TRUE >Lastly, is there a way to setup individual MLIST_ADD_MESSAGE.TXT for each >list? > The /ADD_MESSAGE qualifier on DEFINE LIST lets you specify a list-specific file. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 31 Jan 1994 13:43:01 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Mon, 31 Jan 1994 11:41 PST From: MENDI@ARVAX.SYNTEX.COM (GREG MENDIZABAL, IAR, 415-855-5407) Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU QUERY MX-LIST LIST