Archive-Date: Wed, 01 Apr 1992 14:54:37 EST Sender: Date: Wed, 01 Apr 1992 11:55:17 PST From: "W. Todd Wipke" Reply-To: "W. Todd Wipke" To: mx-list@vms.ecs.rpi.edu Message-ID: <0095873B.817F1FA0.6080@SECS.UCSC.EDU> Subject: EXQUOTA priv required in MX031 I changed from 2.3 to 3.1 and wondered why MX wasn't firing up on system startup. The reason was that 3.1 requires EXQUOTA on the MAILER account (2.3 did not require that priv). I don't recall seeing that in the install, but then I skipped 3.0 which might have had it pointed out. Maybe this will save someone a moment or two. W. Todd Wipke wipke@secs.ucsc.edu Molecular Engineering Laboratory wipke@chemistry.ucsc.edu Department of Chemistry wipke@cats.bitnet University of California tel 408 459-2397 Santa Cruz, CA 95064 FAX 408 459-4716 ============= where innovation is a tradition =================== ================================================================================ Archive-Date: Wed, 01 Apr 1992 22:03:16 EST To: mx-list@vms.ecs.rpi.edu Date: 1 Apr 92 20:17:28 GMT From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr1.151728.4259@dmc.com> Subject: How about remove xxx /all? It would sure be handy if all of the remove commands took a /all qualifier (and/or wild cards for the ones not needing quoted strings). -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Thu, 02 Apr 1992 11:17:58 EST Message-ID: Date: 2 Apr 92 08:46:00 EST From: "OCEANA::TILLMAN" Reply-To: "OCEANA::TILLMAN" Subject: RE: EXQUOTA priv required in MX031 To: "mx-list" CC: "wipke" Why would EXQUOTA be needed for V3.1? ================================================================================ Archive-Date: Thu, 02 Apr 1992 13:32:01 EST To: mx-list@vms.ecs.rpi.edu Date: Thu, 2 Apr 1992 18:30:14 GMT From: madison@mdmvs.ecs.rpi.edu (Matt Madison) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: References: Reply-To: madison@vms.ecs.rpi.edu Subject: RE: EXQUOTA priv required in MX031 In article , TILLMAN%OCEANA.decnet@benzie.si.com (OCEANA::TILLMAN) writes: >Why would EXQUOTA be needed for V3.1? Mainly because there were more than a few cases where a problem arose because someone put their message queue on a disk with diskquotas enabled and then forgot to grant sufficient diskquota to [1,4] for all the messages that were getting processed. The MX startup procedure does perform a privilege check before trying to start each of the agent processes. EXQUOTA is on the list to be checked for all of them. If your message queue (wherever logical FLQ_DIR points) is on a disk with quotas disabled then you don't really need EXQUOTA and you could, if you really wanted to, modify MX_EXE:MX_START.COM to remove the EXQUOTA check. -Matt -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Thu, 02 Apr 1992 18:45:42 EST Date: Thu, 2 Apr 92 15:44:54 PST From: rick@dfwdsr.SINet.SLB.COM Reply-To: rick@dfwdsr.SINet.SLB.COM Message-ID: <9204022344.AA20505@sjosu1.sinet.slb.com> To: mx-list@vms.ecs.rpi.edu Subject: mrgate problem From: RICK@DFWDSR@PSI%HUBVX6@MRGATE@SNDRTR To: "MX-List@vms.ecs.rpi.edu"@M_INTERNET@MRGATE@SNDRTR Hello, I'm having a problem sending to a user on a IBM system on our network. If I just use regular mail I can send to address such as: hubvx6::m_namfld::hambyl and this goes thru ok. But if I add this to a mail list in the form "hubvx6::m_namfld::hambyl"@dfwdsr I get an error back from the router. (hubvx6 is a routing vax with psi software and Dec's Message router MRGATE software. The m_namfld goes via psi to a SUN machine somewhere and some other software to get to an IBM system). I believe the 2 problems are that MRGATE doesn't like the address after MX processes them, and 2nd the SUN machine sees the %MX as a call to another protocol which isn't present on the SUN so it fails with a protocol error. What I need is some way to convert mx's outgoing address to look like they never went thru mx - ie leave all references to mx% and the double quotes off. Looking at the name_conversion package in the contrib directory it looks like the name_conversion software might be able to do what I want, but being a beginning C programmer I'm not sure. I assume what is stored in the user struct has a 1:1 correspondence to what is in the nick structure, but it isn't clear to me if the mx% and the double quotes can be replaced by blanks. Has someone else come up with a fix they could explain on how to make it thru the MRGATE software? I currently have a decnet only connection to our WAN. Would it help to add the SMTP over DECNET option? I'm not sure what this would do / buy me. In about a month I will have a 2nd network connection to our WAN over x.25, would turning on SMTP over psi help)? The install notes for SMTP over Decnet says I need the same object number in all my Vaxes for the SMTP object. Is this company wide on the WAN (I assume to only the routing Vaxes) or just on my local LAN network? Any help would be appreciated. rick caldwell rick@dfwdsr.sinet.slb.com Sample failed messages follow - one with protocol error, the other with route too complex. From: HUB::PSI%SNDRTR::PSI%SJOSU1::Mailer-Daemon "Mail Delivery Subsystem" 31-MAR-1992 16:03:47.91 To: DFWDSR::RICK CC: Subj: Returned mail: Remote protocol error ----- Transcript of session follows ----- Connected to sjosn4: >>> MAIL From:<@DFWDSR.SINet.SLB.COM,@rick@dfwdsr,@sndrtr.psi,@hubvx6.PSI, @dfwdsr:RICK@mx> <<< 501 Syntax error. The : delimiter expected in path name. >>> QUIT <<< 501 Syntax error in username or hostname. 554 sjosn4.psi::meyers... Remote protocol error ----- Unsent message follows ----- Received: from sndrtr.psi by sjosu1.sinet.slb.com id AA27877; Tue, 31 Mar 92 14:00:14 PST Errors-To: RICK@DFWDSR.SINet.SLB.COM Apparently-To: "sjosn4.psi::meyers" X-Vms-From: PSI%HUBVX6::DFWDSR::MX%"rick@DFWDSR" X-Vms-To: hubvx6::m_mailnow::m_sjosn4::meyers Return-Path: Errors-To: RICK@DFWDSR.SINet.SLB.COM X-Listname: TESTLIST@DFWDSR Received: by DFWDSR (MX V3.1) id 16465; Tue, 31 Mar 1992 16:02:57 CST Sender: Date: Tue, 31 Mar 1992 16:03:26 CST From: "Rick Caldwell, Data Services Division, 214-980-7924" Reply-To: "Rick Caldwell, Data Services Division, 214-980-7924" To: testlist@DFWDSR.SINet.SLB.COM Message-Id: <00958695.01F3ED20.16465@DFWDSR> Subject: test 7 sent via mailing list as follows: "hubvx6::m_mailnow::m_sjosn4::meyers"@dfwdsr RICK@DFWDSR --------------------------------- end ---------------------------------------- I also get bounces with a route to complex - these happen when I go to a Vax account. From: MX%"'hub::psi%sndrtr::sndrtr::mrgate::\'MRGATE\''@DFWDSR" 1-APR-1992 07:22:56.70 To: RICK CC: Subj: Message Router VMSmail Gateway nondelivery notification Return-Path: <"hub::psi%sndrtr::sndrtr::mrgate::\"MRGATE\""@DFWDSR> Received: by DFWDSR (MX V3.1) id 16576; Wed, 01 Apr 1992 07:22:51 CST Sender: <"hub::psi%sndrtr::sndrtr::mrgate::\"MRGATE\""@DFWDSR> Date: Wed, 01 Apr 1992 07:22:51 CST From: "hub::psi%sndrtr::sndrtr::mrgate::\"MRGATE\""@DFWDSR To: X-VMSmail-To: PSI%HUBVX6::DFWDSR::MX%"rick@DFWDSR" X-VMSmail-CC: Message-ID: <00958715.72A27480.16576@DFWDSR> Subject: Message Router VMSmail Gateway nondelivery notification Delivery of this message through the Gateway had the following results: Invalid reply path generated - Route too complex Unable to deliver to : M_SINET::MEYERS The original message follows: From: MX%"rick@DFWDSR"@DFWDSR@PSI%HUBVX6@MRGATE@SNDRTR Subject: 4th test To: MEYERS@M_SINET@MRGATE@SNDRTR Return-Path: Errors-To: RICK@DFWDSR X-ListName: TESTLIST@DFWDSR Received: by DFWDSR (MX V3.1) id 16453; Tue, 31 Mar 1992 15:43:39 CST Sender: Date: Tue, 31 Mar 1992 15:44:09 CST From: "Rick Caldwell, Data Services Division, 214-980-7924" Reply-To: "Rick Caldwell, Data Services Division, 214-980-7924" To: testlist@DFWDSR Message-ID: <00958692.4FF82F20.16453@DFWDSR> Subject: 4th test xxxx list test send to: "hubvx6::m_namfld::hambyl"@dfwdsr "hubvx6::m_sinet::meyers"@dfwdsr "hubvx6::m_sjosn4::meyers"@dfwdsr RICK@DFWDSR rick@dfwdsr.sinet.slb.com ================================================================================ Archive-Date: Thu, 02 Apr 1992 22:12:29 EST Date: Fri, 3 Apr 92 03:10:04 GMT From: rick@dfwdsr.SINet.SLB.COM Reply-To: rick@dfwdsr.SINet.SLB.COM Message-ID: <9204030310.AA04987@sndsu1.sinet.slb.com> To: mx-list@vms.ecs.rpi.edu Subject: problem with site_deliver.com From: RICK@DFWDSR@PSI%SDRVX2@MRGATE@PRSRTR To: "mx-list@vms.ecs.rpi.edu"@M_INTERNET@MRGATE@PRSRTR Hello, I'm having a problem with the site_deliver.com file's exit status causing the site process to crash. If I exit site_deliver.com with a status of 1 everything works fine. But if there is a problem in the com file and I exit with an error status the site agent crashes. The following short site_deliver.com file will show the problem: $ set ver $! site_deliver.com $! $ stat = %x107e803a ! force an error $ set message sys$message:cliutlmsg $ write sys$output f$mess(stat) ! report the error $ exit stat ! exit with status This exit status corresponds to: %MAIL-E-LOGLINK, error creating network link to node !AS The example on page 1-3 of the programmer's guide shows a similar exit with status, and the text on page 1-2 indicates that the message will either be bounced on severe errors, or requeued on non-severe errors. For some reason it is crashing the server instead on errors. Looking in the mx_site_node.log file we get the following crash: $!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! $! ! $! SYSTEM-WIDE LOGIN FOR DALLAS 9000 CLUSTER ! $! ! $!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! $ SET noVER 2-APR-1992 17:08:16.36: MX Site Agent (pid 2020418D) starting %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=7FE21400, PC=0002C78D, PSL=03C00000 %TRACE-F-TRACEBACK, symbolic stack dump follows module name routine name line rel PC abs PC 0002C78D 0002C78D DELIVER DELIVER_FILE 309 000000E4 00001DB1 DELIVER DELIVER 226 000004AB 00001C57 PROCESS PROCESS 179 00000166 00001673 MX_SITE MX_SITE 31 00000212 00001012 2-APR-1992 17:09:04.92: MX Site Agent (pid 2020418D) exiting SYSTEM job terminated at 2-APR-1992 17:09:05.39 Accounting information: Buffered I/O count: 126 Peak working set size: 938 Direct I/O count: 163 Peak page file size: 4836 Page faults: 671 Mounted volumes: 0 Charged CPU time: 0 00:00:00.51 Elapsed time: 0 00:00:52.24 And in the mx_site_log.log 2-APR-1992 17:08:57.09 Processing queue entry number 16918. 2-APR-1992 17:09:01.47 DELIVER: Delivering... 2-APR-1992 17:09:01.59 DELIVER_FILE: Status=00000001 spawning subprocess. 2-APR-1992 17:09:01.59 DELIVER_FILE: Command: @MX_EXE:SITE_DELIVER "dfwdsr.dnet" MX_ROOT:[SITE]SITE_MSG_7E0740A0_00958830_2020418D.TMP;1 MX_ROOT:[SITE]SITE_ADR_7E0740A0_00958830_2020418D.TMP;1 "" 2-APR-1992 17:09:01.93 DELIVER_FILE: Subprocess says: $! site_deliver.com 2-APR-1992 17:09:01.97 DELIVER_FILE: Subprocess says: $! 2-APR-1992 17:09:01.99 DELIVER_FILE: Subprocess says: $ stat = %x107e803a 2-APR-1992 17:09:02.08 DELIVER_FILE: Subprocess says: $ set message sys$message:cliutlmsg 2-APR-1992 17:09:02.51 DELIVER_FILE: Subprocess says: $ write sys$output f$mess(stat) 2-APR-1992 17:09:02.54 DELIVER_FILE: Subprocess says: %MAIL-E-LOGLINK, error creating network link to node !AS 2-APR-1992 17:09:02.54 DELIVER_FILE: Subprocess says: $ exit stat 2-APR-1992 17:09:02.61 DELIVER_FILE: Subprocess says: WRITE SYS$OUTPUT F$FAO("EXIT:!XL",F$INTEGER($STATUS)) 2-APR-1992 17:09:02.61 DELIVER_FILE: Subprocess says: EXIT:107E803A 2-APR-1992 17:09:04.02 DELIVER: Delivering... ------------------------------------------------------------------------------- Any clue to the problem would be appreciated. Running version mx 3.1. rick@dfwdsr.sinet.slb.com ================================================================================ Archive-Date: Sun, 05 Apr 1992 18:52:52 EDT To: mx-list@vms.ecs.rpi.edu Date: 4 Apr 92 23:08:44 EDT From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr4.230844.4263@dmc.com> Subject: Bug in LOCAL delivery timeout? There seems to be a bug in the requeueing logic for LOCAL delivery. With the local path set as follows: LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. Top headers: 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 headers: (none) I sent a message and it bounced almost immediately, as shown below: Return-Path: <> Date: Sat, 04 Apr 1992 22:45:27 EST From: Local delivery agent To: Subject: LOCAL delivery error Note: this message was generated automatically. The following error(s) occurred during local delivery of your message. Error in delivery to user BATROC::MUNROE: retry count exceeded Message follows. Received: by DMC.COM (MX V3.1) id 9402; Sat, 04 Apr 1992 22:38:10 EST Sender: Date: Sat, 04 Apr 1992 22:38:00 EST From: "Don't take life so serious--it ain't nohow permanent." To: munroe@batroc.dmc.com Message-ID: <009589F0.CA20EEC0.9402@DMC.COM> Subject: disinfectant v2.7.1 Relay-Version: VMS News - V6.0-3 14/03/90 VAX/VMS V5.4; site dmc.com Path: dmc.com!uunet!uunet!usc!orion.oac.uci.edu!cerritos.edu!dhw68k!macintosh Newsgroups: comp.binaries.mac Subject: Disinfectant 2.7.1 (part 1 of 6) Message-ID: From: j-norstad@nwu.edu (John Norstad) Date: Thu, 26 Mar 92 17:00:20 GMT Approved: bytebug@dhw68k.cts.com (Roger L. Long) Supersedes: Lines: 729 Shouldn't this have taken 2 days instead of a few minutes? (Yes, I HAVE reset the MX processes since I changed the LOCAL information last). Dick Munroe -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Mon, 06 Apr 1992 07:28:54 EDT Date: Mon, 06 Apr 1992 13:29:35 EDT From: muth@exp.bessy.de (Matthias Muth, BESSY-Berlin) Reply-To: muth@exp.bessy.de (Matthias Muth, BESSY-Berlin) To: MX-List@vms.ecs.rpi.edu Message-ID: <00958b36.82244e40.282@exp.bessy.de> Subject: SUBSCRIBE SUBSCRIBE MX-LIST ================================================================================ Archive-Date: Mon, 06 Apr 1992 14:04:47 EDT To: mx-list@vms.ecs.rpi.edu Date: 6 Apr 92 14:32:28 GMT From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr6.103228.4268@dmc.com> References: <1992Apr4.230844.4263@dmc.com> Subject: Re: Bug in LOCAL delivery timeout? I just realized that I forgot to provide a bunch of logs detailing the problem. Here they are (from oldest to most recent): 6-APR-1992 10:12:41.46 Processing queue entry number 9491 6-APR-1992 10:12:42.24 Checking local name: BATROC::munroe 6-APR-1992 10:12:42.25 LOCAL_USER: BATROC::munroe looks like a DECnet address. 6-APR-1992 10:12:42.25 This is a regular delivery. 6-APR-1992 10:12:42.51 DELIVER: Using MX%"munroe@DMC.COM" as VMS MAIL From address. 6-APR-1992 10:12:42.51 DELIVER: Using "test" as subject. 6-APR-1992 10:12:42.99 DELIVER: Delivering to BATROC::munroe 6-APR-1992 10:13:42.31 DELIVER: Status=007E803A from MAIL$ routines 6-APR-1992 10:13:42.31 DELIVER: --LOGLINK or OPENOUT failure; will retry. 6-APR-1992 10:13:43.02 Setting up for retry at 6-APR-1992 10:14:43.02 6-APR-1992 10:18:45.83 Processing queue entry number 9491 6-APR-1992 10:18:46.77 Checking local name: BATROC::MUNROE 6-APR-1992 10:18:46.77 LOCAL_USER: BATROC::MUNROE looks like a DECnet address. 6-APR-1992 10:18:46.77 This is a regular delivery. 6-APR-1992 10:18:46.95 DELIVER: Using MX%"munroe@DMC.COM" as VMS MAIL From address. 6-APR-1992 10:18:46.95 DELIVER: Using "test" as subject. 6-APR-1992 10:18:47.26 DELIVER: Delivering to BATROC::MUNROE 6-APR-1992 10:19:47.31 DELIVER: Status=007E803A from MAIL$ routines 6-APR-1992 10:19:47.31 DELIVER: --LOGLINK or OPENOUT failure; will retry. 6-APR-1992 10:19:47.45 No more retries allowed for BATROC::MUNROE, count=1 6-APR-1992 10:19:49.40 All done with this entry. 6-APR-1992 10:19:51.83 Processing queue entry number 9493 6-APR-1992 10:19:52.78 Checking local name: MUNROE 6-APR-1992 10:19:52.92 LOCAL_USER: User MUNROE definitely local. 6-APR-1992 10:19:52.92 This is a regular delivery. 6-APR-1992 10:19:53.09 DELIVER: Using MX%"Postmaster@DMC.COM" as VMS MAIL From address. 6-APR-1992 10:19:53.09 DELIVER: Using "LOCAL delivery error" as subject. 6-APR-1992 10:19:53.53 DELIVER: Delivering to MUNROE 6-APR-1992 10:19:55.12 DELIVER: Status=00000001 from MAIL$ routines 6-APR-1992 10:19:55.32 All done with this entry. I've had at least on problem with RESET/ALL where I actually had to shutdown MX and restart it to get changes to MCP to "take". I haven't tried that yet, in which case this may be a bug in RESET, not in local delivery. Dick -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Tue, 07 Apr 1992 12:42:53 EDT Date: Tue, 7 Apr 92 12:42:29 -0400 From: sumedh@charlie.ece.scarolina.edu (Sathaye Sumedh W (CS)) Reply-To: sumedh@charlie.ece.scarolina.edu (Sathaye Sumedh W (CS)) Message-ID: <9204071642.AA20878@linus.ece.scarolina.edu> To: mx-list@vms.ecs.rpi.edu Dear MX-Masters, I recently reinstalled MX 3.0A onto a new disk other than the system disk and have started facing problems with the outgoing messages. The messages are not delivered. Apparently, the VMS mail does not pass the address on the envelope to the MX router (this is my prediction). I have attached the router LOG file as well as the MC configuration files herewith. Can somebody guide me in this respect? Thanks and regards, Sumedh Sathaye, System Administration, College Of Engg, University Of South Carolina, Columbia, SC 29208. (vax_sumedh@mv3800.engr.scarolina.edu) ================================================================================ The mx_router_log.log file: ================================================================================ 7-APR-1992 12:18:32.74 %PROCESS, Processing entry number 103 7-APR-1992 12:18:32.87 %PROCESS, Status from READ_INFO was 00000001 7-APR-1992 12:18:32.87 %PROCESS, Message originated in VMS Mail. 7-APR-1992 12:18:32.88 %PROCESS, will run domain expander on envelope addresses. 7-APR-1992 12:18:32.89 %PROCESS, will run domain expander on message headers. 7-APR-1992 12:18:33.91 %PROCESS, Finished VMSmail-origin preprocessing. 7-APR-1992 12:18:33.91 %PROCESS, Marking this entry as finished. ================================================================================ ! Configuration file: MX_ROOT:[000000]MX_CONFIG.MXCFG;4 ! MX version id: MX V3.0A DEFINE PATH "mv3800.engr.scarolina.edu" Local DEFINE PATH "*.UUCP" SMTP /ROUTE="uunet.uu.net" DEFINE PATH "*.BITNET" SMTP /ROUTE="cunyvm.cuny.edu" DEFINE PATH "*" SMTP SET SMTP/ACCOUNTING/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/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 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 ================================================================================ ================================================================================ Archive-Date: Tue, 07 Apr 1992 17:04:20 EDT Date: Tue, 07 Apr 1992 16:06:30 CDT From: "Pedro A. Crespo" Reply-To: "Pedro A. Crespo" To: MX-List@vms.ecs.rpi.edu Message-ID: <00958C15.99B0F240.24828@OKCU> Subject: BITNET<=>Internet Before anyone jumps: I apologize, for this is not a purely MX issue! So, with that said, here it is... Our node (OKCU) being connected only to BITNET, and being far from an official BITNET/Internet gateway (i.e. CUNYVM) is prone to mail outtages when any line between OKCU and CUNYVM is down (too frequently). Now, to alleviate this, and taking into account that our parent node (UOKMVSA) has a direct link to an Internet domain, I have defined a couple of re-write rules to route all Internet-style addresses through UOKMVSA.BITNET: DEFINE REWRITE RULE "<{user}@{host}.{something}> - "<{user}%{host}.{something}@UOKMVSA.BITNET>" (BTW, thanks to Earle Ake for posting this as an answer to someone else's question.) Now, I can send mail to the Internet, and it gets out from UOKMVSA (actually from uokmvsa.backbone.uoknor.edu), but it seems that I can't use their node (uokmvsa) to receive mail, because their SMTP does not recognize OKCU.BITNET as a valid address (explanation given by the very helpful person responsible for the system at that location). Now, I have tried sending myself test mail in the form: To: MX%"pedro%okcu.bitnet%uokmvsa.backbone.uoknor.edu@CUNYVM.BITNET" and some other variants, and almost always an error comes back (see attached message) saying that uokmvsa does not recognize okcu.bitnet as a valid host. I know that cunyvm.cuny.edu and mitvma.mit.edu are able to digest a .bitnet address, and send it through the BITNET pipe (yes, that is why they are official gateways) but my question is: would it be possible for them to do this at uokmvsa? Does it require any special software? What is the correct incantation to make SMPT do this? (I asked uokmvsa and the person in charge does not know a way to accomplish it). FWIW: uokmvsa does have a MAILER and it is listed in the XMAILER.NAMES: :nick.UOKMVSA :alias.UOKMVSA :net.BITNET :mailer.MAILER :netsoft.JES2 If anyone has any insight on this, or if you need more info, please let me know... it will be very much appreciated! (Note: I know nothing about Internet or IBM, so I'll have to ask them at uokmvsa for any details you might need, but *please* do not contact them directly. Thanks) Cordially, Pedro. P.S.- saple reply message from smtp@cunyvm.cuny.edu follows .sig ______________________________________________________________________________ Pedro A. Crespo | %include "standard.disclaimer" +------------------------------------------------ Information Systems Director | Voice: (405) 521-5888 | pedro@okcu.bitnet Oklahoma City University | Fax: (405) 521-5411 | attmail!ocumail!pedro ______________________________________________________________________________ "It is not absolutely impossible to categorically deny anything!" -PAC \8^> ______________________________________________________________________________ 8<-------cut-here------------------------------------cut-here--------->8 From: MX%"SMTP@CUNYVM.CUNY.EDU" 6-APR-1992 17:02:38.15 To: PEDRO CC: Subj: Undeliverable Mail Return-Path: Received: from CUNYVM.BITNET (MAILER) by OKCU (MX V2.2-2) with BSMTP; Mon, 06 Apr 1992 17:01:57 CDT Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.08) with BSMTP id 5744; Mon, 06 Apr 92 17:51:20 EDT Date: Mon, 06 Apr 92 17:51:12 EDT From: SMTP@CUNYVM.CUNY.EDU To: pedro@OKCU Subject: Undeliverable Mail CUNYVM.CUNY.EDU unable to deliver following mail to recipient(s): CUNYVM.CUNY.EDU received negative reply: 550 Host 'okcu.bitnet' Unknown ** Text of Mail follows ** Received: from CUNYVM.BITNET by CUNYVM.CUNY.EDU (IBM VM SMTP V2R2) with BSMTP id 0193; Mon, 06 Apr 92 17:51:06 EDT Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.08) with BSMTP id 5724; Mon, 06 Apr 92 17:51:04 EDT Received: from OKCU by CUNYVM.BITNET (Mailer R2.08) with BSMTP id 5723; Mon, 06 Apr 92 17:51:04 EDT Received: by OKCU (MX V2.2-2) id 23206; Mon, 06 Apr 1992 16:55:22 CDT Date: Mon, 06 Apr 1992 16:55:22 CDT From: "Pedro A. Crespo" To: pedro%okcu.bitnet%uokmvsa.backbone.uoknor.edu@CUNYVM.CUNY.EDU Message-ID: <00958B53.43819540.23206@OKCU> Subject: TEST Test to: pedro%okcu.bitnet%uokmvsa.backbone.uoknor.edu@CUNYVM.BITNET ============================================================================= ================================================================================ Archive-Date: Tue, 07 Apr 1992 17:15:26 EDT Sender: Date: Mon, 06 Apr 1992 14:51:10 CDT From: Glamdring Reply-To: Glamdring To: mx-list@vms.ecs.rpi.edu Message-ID: <00958B41.E8BCA520.4047@abel.incstar.com> Subject: Problem with MLF? I have the following configuration: serial DECnet PC LAN ---- uVAXII ---- VAX 6410 UUPC/Extended DECUS uucp MX 3.1 MX 3.1 I have a mailing list set up on the 6410 (adam). I send mail from the PC LAN to subscribe to the mailing list. The mail appears to reach adam but I am not subscribed to the mailing list. I can subscribe to the list from the uVAXII or from the 6410 with no problem. I can send regular mail to/from the PC LAN and the 6410 with no problem. I can post messages to the mailing list from the PC LAN and they get echoed to the list members with no problem. Any idea what might be going on? Any pointers on where to look for help? Thanks much! Rockford Lhotka INCSTAR Corp Applications Project Leader 1990 Industrial Blvd lhotka@incstar.com PO Box 285 612/779-1701 Stillwater, MN 55082 >>>Amiga - The computer for the creative mind<<< ================================================================================ Archive-Date: Wed, 08 Apr 1992 12:37:13 EDT Message-ID: <9204081637.AA26872@relay.CDNnet.CA> Date: 8 Apr 92 9:33 From: Simeon Broughton Reply-To: Simeon Broughton To: mx-list@vms.ecs.rpi.edu Subject: MX030,VMS5.4-3,CMU6.4 I'm trying to install MX V3 on a new Vax 4000/200 running VMS 5.4-3 and CMU V6.4. I don't seem to be able to get any smtp messages to transfer in or out of this system. I have been running an older version of MX on VMS 5.3 on a 750 with no problem. Can anyone give me a clue where I should be looking? SMTP log file follows: 7-APR-1992 20:51:10.34 Processing queue entry number 4 on node NICAD3 7-APR-1992 20:51:10.73 Recipient: , route=dewey 7-APR-1992 20:51:10.73 SMTP_SEND: looking up host name dewey 7-APR-1992 20:51:10.89 SMTP_SEND: Failed, sts=0863815A 7-APR-1992 20:51:10.89 SMTP send failed, sts=0C27804A, sts2=0863815A 7-APR-1992 20:51:10.89 Recipient status=0C27804A for 7-APR-1992 20:51:11.38 1 rcpts need retry, next try 7-APR-1992 21:21:11.38 7-APR-1992 20:51:11.41 *** End of processing pass *** 7-APR-1992 20:33:58.27 Processing queue entry number 2 on node NICAD3 7-APR-1992 20:33:58.57 Recipient: , route=nicad1 7-APR-1992 20:33:58.57 SMTP_SEND: looking up host name nicad1 7-APR-1992 20:33:58.73 SMTP_SEND: Failed, sts=0863815A 7-APR-1992 20:33:58.73 SMTP send failed, sts=0C27804A, sts2=0863815A 7-APR-1992 20:33:58.73 Recipient status=0C27804A for 7-APR-1992 20:33:59.24 1 rcpts need retry, next try 7-APR-1992 21:03:59.24 7-APR-1992 19:03:54.05 *** End of processing pass *** Simeon Broughton, Manager, Computer Services. (604)339-8905 North Island College, 156 Manor Drive, Comox, B.C. V9N 6P7. CANADA broughton@nicad1.nic.bcc.cdn or broughton@admin.nic.bcc.cdn broughton%nicad1.nic.bcc.cdn@relay.cdnnet.ca ================================================================================ Archive-Date: Wed, 08 Apr 1992 13:47:44 EDT Date: Wed, 08 Apr 1992 13:48:22 EDT From: Matt Madison Reply-To: madison@vms.ecs.rpi.edu To: mx-list@vms.ecs.rpi.edu Message-ID: <00958CCB.769AE480.18437@mdmvs.ecs.rpi.edu> Subject: MX V3.1 revision level A now available After receiving a handful of bug reports for MX V3.1, I have produced a maintenance release, called revision A. Everyone who obtains the MX031 kit by anonymous FTP will be getting the updated version (savesets A, C, I, and J are changed from the original V3.1 release). If you have MX V3.1 currently installed and would like to upgrade painlessly to V3.1A, you should get the files 01README.REVA_UPGRADE and MX_REVA_UPGRADE031.A_Z, which is the upgrade kit for existing V3.1 users. The MX031 kit on FILESERV will remain the older version for the time being; request package MX_REVA_UPGRADE031 for the upgrade kit. The following V3.1 bugs are fixed by this maintenance release (excerpted from the release notes): 1. MX_MAILSHR was not performing logical name translations on VMS Mail To-lines in a case-blind fashion, resulting in incorrect RFC822 To: headers in certain cases. This has been fixed. 2. The Sender: header provided for messages originating in VMS Mail was using incorrect syntax for addresses according to RFC 822, although by RFC 1123 it was correct. This was causing some problems with finicky mailers still using the old standard, so the syntax has been changed. In addition, the Sender: header is no longer provided if it matches the From: header, since it is unnecessary to do so. 3. The SITE delivery agent would behave unpredictably, usually dying with an ACCVIO, when a delivery resulted in an error status that caused a message to be requeued for another delivery attempt. This has been fixed. 4. MCP would not update the configuration database when invoked with a one-shot command on the MCP command line, even if that command made a change to the configuration. This has been fixed. 5. The MLF agent would lose its information about mailing lists and file servers when it received a RESET/ACCOUNTING signal. This has been fixed. Also fixed was the error in the installation procedure that caused it to provide an incorrect default answer for the placement of the MX top-level directory on systems where MX had never been installed before. Have fun, -Matt PS: I will be out of town the 9th through the 12th, so if you send me something and don't hear from me, don't think I'm ignoring you. -mdm -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Fri, 10 Apr 1992 04:14:39 EDT To: mx-list@vms.ecs.rpi.edu Date: 9 Apr 92 19:12:38 GMT From: oursler@kenyon.edu Reply-To: oursler@kenyon.edu Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr9.141238.28@kenyon.edu> Subject: Mail and the domain - Part 2 Hullo, Ok, a combination of an MX record in the namserver and an entry defining "kenyon.edu" as local did the trick. Mail to user@kenyon.edu now works. Thanks everyone. Now, the question... ;-) At some point in the future I'd like to make *outgoing* mail come from user@kenyon.edu. Difficult? I am guessing that the logical MX_NODE_NAME needs to be changed. If so, do I just edit MX_LOGICALS.DAT? The manual warns against editing this file. Thanks, - Miles - ------------------------------- Miles Oursler Manager of Networks and Systems Kenyon College oursler@vax001.kenyon.edu (614) 427-5696 ------------------------------- ================================================================================ Archive-Date: Fri, 10 Apr 1992 10:36:42 EDT Sender: Date: Fri, 10 Apr 1992 10:36:13 EDT From: Alan Simon Reply-To: Alan Simon To: mx-list@vms.ecs.rpi.edu Message-ID: <00958E42.F3A43B20.31400@shrsys.hslc.org> Subject: Mailing List File Server Conflict I have a mailing list set up with a file server. When I post to the mailing list, VMS user ARCHIVES gets the post. How do I set up the mailing list and file server so that this doesn't happen? Thanks for your help. -------------------------------------------------------------------------------- Alan Simon simon@shrsys.hslc.org Associate Director VOICE: (215) 222-1532 Health Sciences Libraries Consortium FAX: (215) 222-0416 3600 Market Street, Suite 550 Philadelphia, PA 19104 -------------------------------------------------------------------------------- ================================================================================ Archive-Date: Fri, 10 Apr 1992 16:20:14 EDT Sender: Date: Fri, 10 Apr 1992 16:20:49 EDT From: Jim Gaynor Reply-To: Jim Gaynor To: mx-list@vms.ecs.rpi.edu Message-ID: <00958E73.174886A0.17859@agvax2.ag.ohio-state.edu> Subject: Creating a PATH... Okay, I have a relatively specific question here. Without going into the whys of the thing, I have would like to be able to receive mail of the form: a) smith%bigvax.decnet@agvax2.ag.ohio-state.edu Where 'smith' is the username, 'bigvax' is the name of a DECnet node on our local DECnet network, and 'agvax2.ag.ohio-state.edu' is the Internet host name of my site. The mail, once received here, would actually get sent to: b) bigvax::smith Which was all know is a nice, valid, DECnet address. Does anyone have any inspiration on how I would handle making a SET PATH in MCP that would help me route such a beast in this fashion? Failing that, is there someone knowledgeable in VAX C who'd like to help me re-write part of the PATCH_FROM_LINE routine in Larry Hughes' IUPOP3 POPmail server? That's the thing that's creating a) as the "return address" of a mail message sent by b) and retrieved using IUPOP3 and a POPmail client. Thanks in advance, of course. And beers after a solution is found. :-) --- Jim Gaynor - System Analyst Internet: gaynor@agvax2.ag.ohio-state.edu Ohio State University - ACS/FMS Phone: Voice 614/292-4338 - FAX 614/292-7443 ObDiscl: Everything stated here and above is _my_ opinion. Mine mine mine! ObQuote: "We need bigger guns. Big, big guns" Det. Dick Derkin, "Split Second" ================================================================================ Archive-Date: Fri, 10 Apr 1992 17:21:31 EDT Sender: Date: Fri, 10 Apr 1992 13:18:52 PST From: Carl J Lydick Reply-To: Carl J Lydick To: gaynor@agvax2.ag.ohio-state.edu CC: mx-list@vms.ecs.rpi.edu Message-ID: <00958E59.AC431A00.25356@SOL1.GPS.CALTECH.EDU> Subject: RE: Creating a PATH... >Okay, I have a relatively specific question here. >Without going into the whys of the thing, I have would like to be able >to receive mail of the form: >a) smith%bigvax.decnet@agvax2.ag.ohio-state.edu >Where 'smith' is the username, 'bigvax' is the name of a DECnet node on >our local DECnet network, and 'agvax2.ag.ohio-state.edu' is the >Internet host name of my site. The mail, once received here, would >actually get sent to: >b) bigvax::smith >Which was all know is a nice, valid, DECnet address. >Does anyone have any inspiration on how I would handle making a SET >PATH in MCP that would help me route such a beast in this fashion? You don't want to use SET PATH. You want to use DEFINE REWRITE_RULE: DEFINE REWRITE_RULE - "<{user}@{host}.DECNET>" - "<""{host}::{user}""@AGVAX2.AG.OHIO-STATE.EDU>" ================================================================================ Archive-Date: Mon, 13 Apr 1992 14:32:45 EDT Reply-To: hak@hakvax.kodak.com Sender: Date: Mon, 13 Apr 1992 14:32:58 EDT From: hak@hakvax.kodak.com To: mx-list@vms.ecs.rpi.edu Message-ID: <009590BF.85830FC0.15879@hakvax.kodak.com> Subject: UUencoded files and MX... I don't remember if this has come up before, but has anyone got a solution that will avoid space characters being dropped from the ends of lines? I suspect it's more of an RMS problem than it is an MX problem, but thought I'd ask... Al Killenbeck, Eastman Kodak Co, Rochester, NY hak@kodak.com ================================================================================ Archive-Date: Mon, 13 Apr 1992 14:47:55 EDT Date: Mon, 13 Apr 1992 12:46:36 MDT From: Tom Van Dreser 303-236-4537 USGS-BGRA Reply-To: Tom Van Dreser 303-236-4537 USGS-BGRA To: mx-list@vms.ecs.rpi.edu Message-ID: <009590B0.AA190CE0.1085@sgbsn> Subject: VMS_Share across Platforms? A few weeks ago I wrote asking for directions to VMS_Share. Thank you to all of you who responded. My quest this time is this. VMS_share does exactly what it says it does, however, I want my MX fileserver to be able to send packages across the net to any computer platform and, unless I am mistaken, VMS_share works only with VMS. (please correct me if I am wrong) So can anyone suggest a file packaging program, and its whereabouts, that makes neat packages and does not require VMS to unpack the packages? Thank you for your help. Tom Van Dreser System Manager USGS-BRGA Golden CO 303-236-4537 vandreser@sgbsn.cr.usgs.gov ================================================================================ Archive-Date: Mon, 13 Apr 1992 14:56:44 EDT Date: Mon, 13 Apr 92 14:58 EDT From: Reply-To: Subject: MX in Loop ? To: MX-LIST@vms.ecs.rpi.edu Hello, I am a new MX user. When I send mail to a user on a remote node from VMS mail, adding a Carbon Copy (CC) to a user on that same remote node, i.e., CC: mx%"username@remote_node", I get a very strange, but dangerous thing happen. MX seems to go into a loop. The mail does not get delivered and the number of messages in the queue increases by the second. I monitor the queue using FLQU. All the new entries in the queue are created by the latter operation. Why ? The status of each entry is first INP and then FIN, then, another entry is added, and so on. What am I doing that is causing this to happen ? Any help on this issue would be greatly appreciated. Thanks in advance. Ian Vaz Seneca College North York, Ontario Canada (416) 491-5050 x 7252 ================================================================================ Archive-Date: Mon, 13 Apr 1992 15:48:04 EDT To: mx-list@vms.ecs.rpi.edu Date: Mon, 13 Apr 1992 19:37:16 GMT From: gowen@walt.CS.MsState.Edu (Lon Gowen) Reply-To: gowen@walt.CS.MsState.Edu (Lon Gowen) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr13.193716.24165@ra.msstate.edu> Subject: MX sending too many "receive" commands. Yet another question about MX V3.1. First off, I am using a VAXstation 4000/60, VMS V5.5, and UCX V1.3 (don't laugh). Anyway, I can send mail just fine (now), but my receive operations fail. I am currently trying to send a message from a Sun Unix box to VMS. The message I get back on my Unix account says the following: Rcvd: 554 Received too many times by this host. Needless to say, I assume that MX is sending too many "receive" commands. All the other handshaking between the two hosts seems fine. The VAX just never receives the DATA properly. Does anyone have any ideas or hints? By the way, I sent a message to the VAX by just replying to the message I sent from the VAX to the Unix account. Thanks in advance! Lon Gowen, PhD gowen@cs.msstate.edu ================================================================================ Archive-Date: Mon, 13 Apr 1992 16:09:08 EDT Date: 13 Apr 1992 14:08:02 -0600 (MDT) From: Dan Wing Reply-To: Dan Wing Subject: Re: UUencoded files and MX... To: hak@hakvax.kodak.com CC: mx-list@vms.ecs.rpi.edu Message-ID: <01GISUS5T9FM00008C@VAXF.COLORADO.EDU> Al Killenbeck, hak@kodak.com, writes: >I don't remember if this has come up before, but has anyone got a solution >that will avoid space characters being dropped from the ends of lines? > >I suspect it's more of an RMS problem than it is an MX problem, but thought >I'd ask... Well, most mailers will think your trailing-spaces are not needed (they usually aren't!) and will remove them for efficency. If you're transferring files from VMS to VMS, the best solution is VMS_SHARE available from all over the place. This will encode your file so it won't be "corrupted" by a mailer, and will semi-automatically unpack the file at the destination. Its available from several servers on the Internet. JNET has a better solution for transferring files between sites running Jnet, but it only runs on VMS machines on BITNET. If you're trying to get the file from a VMS machine to a non-VMS machine while preserving trailing blanks, I think UUENCODE/UUDECODE is about the only solution. -Dan Wing, DWING@UH01.Colorado.EDU (or WING_D@UCOLMCC.BITNET) Systems Programmer, University Hospital, Denver ================================================================================ Archive-Date: Mon, 13 Apr 1992 16:46:21 EDT Date: Mon, 13 Apr 92 13:46:40 PDT From: brydon@asl.SINet.SLB.COM (Eschew Obfuscation) Reply-To: brydon@asl.SINet.SLB.COM (Eschew Obfuscation) Message-ID: <9204132046.AA27508@sjosu1.sinet.slb.com> To: mx-list@vms.ecs.rpi.edu CC: BRYDON@asl.SINet.SLB.COM Subject: MX won't deliver messages I am the sysmgr and installed MX on my system. I'm new at the MX game. I think I have read all the docs and configured everything as it should be but MX does not seem to be doing anything for me. I have a number of messages in the queue that are not being delivered. Does somebody have any insight into things? MCP> que show/all Entry Status Size Source Agent Entry Status Size ----- ------ ------ ------ ------- ----- ------ ------ 1 READY 0 MAIL BRYDON "Eschew Obfuscation" 2 READY 2475 MAIL BRYDON 3 READY 1400 MAIL BRYDON 4 READY 920 MAIL BRYDON 5 READY 1315 MAIL BRYDON 6 READY 1010 MAIL BRYDON 7 READY 1580 MAIL BRYDON 8 READY 4142 MAIL BRYDON 9 READY 0 MAIL BRYDON "Eschew Obfuscation" 10 READY 0 MAIL SYSTEM 11 READY 0 MAIL SYSTEM 12 READY 1310 MAIL BRYDON 13 READY 4971 MAIL BRYDON 14 READY 1101 MAIL BRYDON 15 READY 3996 MAIL BRYDON MCP> show local LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. Top headers: 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 headers: (none) MCP> These messages go back almost 2 weeks (this is not a latent April 1 joke). Any illustrations that I screwed something up will be gratefully accepted provided you tell me how to get out of it. :-) ____________________________________________________________________________ Harvey Brydon | Internet: brydon@asl.sinet.slb.com Schlumberger Anadrill | FAX: (713)274-8399 200 Macco Blvd | Telex: 1565030001 SINET ASL SLB Sugar Land, TX 77478 | P.O.T.S.: (713)274-8000 x8281 or 274-8281 (d.i.d.) I bought my VAXstation from my uncle on his deathbead - I wrote him a check. ================================================================================ Archive-Date: Tue, 14 Apr 1992 11:49:10 EDT Sender: Date: Tue, 14 Apr 1992 10:48:07 CDT From: hunterl@uwwvax.uww.edu Reply-To: hunterl@uwwvax.uww.edu To: mx-list@vms.ecs.rpi.edu Message-ID: <00959169.4698CB60.6268@uwwvax.uww.edu> Subject: Error message The message: %Noname-E-NOMSG, message number 0863818A is the only problem that 3.1 did not solve. The only way to solve this problem seems to be, to reboot since the addresses are OK. Restarting MX and/or CMU IP has no effect. Any suggestions. Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Tue, 14 Apr 1992 11:52:33 EDT Message-ID: Date: 14 Apr 92 08:50:00 EST From: "Brian Tillman" Reply-To: "Brian Tillman" Subject: Re: UUencoded files and MX... To: "dwing" CC: "mx-list" Dan Wing (dwing@uh01.colorado.edu) writes: >If you're trying to get the file from a VMS machine to a non-VMS machine >while preserving trailing blanks, I think UUENCODE/UUDECODE is about the only >solution. There is also a pair of programs called HEXIFY and DEHEXIFY which can convert a file to human-readable characters (i.e. the hexadecimal representation of the data in the file) and back again. This is also an option. In fact, Matt Madison uses these programs to help distribut the MX savesets by mail. He compresses the savesets with LZCMP, HEXIFYs them, and then VMS_SHAREs them to make a mailable package. I believe I've seen C versions of HEXIFY and DEHEXIFY available on the Internet. You could check by sending a mail message to one of the following addresses: archie@archie.ans.net archie@archie.mcgill.ca (or archie@cs.mcgill.ca) archie@archie.rutgers.edu archie@archie.sura.net archie@archie.unl.edu If you don't use a signature file, the message can be a single line that looks like this: prog hexify If you do use a signature file, put the line quit immediately after the PROG line. In a day or so you'll receive a message listing all FTP-able files containing the string "hexify". ================================================================================ Archive-Date: Tue, 14 Apr 1992 16:38:20 EDT Date: Tue, 14 Apr 1992 15:21:51 BRAZIL/EAST From: EDSON YOSHIMITSU SHIMABUKO (XYKO) Reply-To: EDSON YOSHIMITSU SHIMABUKO (XYKO) Subject: Re: Error message To: hunterl@uwwvax.uww.edu, mx-list@vms.ecs.rpi.edu CC: zeze@VAX.IFT.UNESP.BR, edson@VAX.IFT.UNESP.BR Message-ID: <0095918F.84643BC0.1321@VAX.IFT.UNESP.BR> Lyle Hunter You write: >The message: >%Noname-E-NOMSG, message number 0863818A >is the only problem that 3.1 did not solve. >The only way to solve this problem seems to be, to reboot since the >addresses are OK. Restarting MX and/or CMU IP has no effect. >Any suggestions. >Lyle Hunter >Computer Center >University Wisconsin-Whitewater >hunterl@uwwvax.uww.edu I had one similar trouble with MX, look for generate messages do it. %MAIL-E-NOMSG, Message number 007E829A %STR-F-ILLSTRCLA, illegal string class %STR-F-ILLSTRCLA, illegal string class. I was thinking that it was related with an unacepted configuration of Cmu-tek but it was not. Actually, it was related with foreign mail protocol. The solution that worked was change the SCSNODE parameter (with reboot, of course). I was working with MX version 1.2. It's possibly not working for you but you can try this and after you tell me what happened. ---------------------------------------------------------------------------- | | | Edson Yoshimitsu Shimabuko | | Instituto de Fisica Teorica | | System and Network manager | | Rua Pamplona, 145 - CEP 01405 | |Sao Paulo - SP - Brazil ANSP: Edson%ift.uesp.ansp.br| |FAX: 363449 BITNET: Edson%ueift1.hepnet@brfapesp.bitnet| |TELEX: 31870 e 79001 DECNET: UEIFT1::Edson or 47553::Edson| |TELEFONE: 288-5643 INTERNET: Edson@vax.ift.unesp.br| | 251-5124 RENPAC: PSI%11122177::Edson| ---------------------------------------------------------------------------- ================================================================================ Archive-Date: Wed, 15 Apr 1992 04:13:18 EDT Sender: Date: Wed, 15 Apr 1992 01:12:41 PDT From: "John F. Sandhoff" Reply-To: sandhoff@csus.edu To: mx-list@vms.ecs.rpi.edu CC: syssand@CCVAX.CCS.CSUS.EDU Message-ID: <009591E2.0E248AC0.3898@CCVAX.CCS.CSUS.EDU> Subject: Re: UUencoded files and MX... >>If you're trying to get the file from a VMS machine to a non-VMS machine >>while preserving trailing blanks, I think UUENCODE/UUDECODE is about the only >>solution. >There is also a pair of programs called HEXIFY and DEHEXIFY which can convert >a file to human-readable characters (i.e. the hexadecimal representation of >the data in the file) and back again. The hexify/dehexify programs are available from Columbia University (watsun.cc.columbia.edu) and are used by them to make VMS executables of Kermit obtainable (watsun is the grandaddy Kermit archive). While I may be mistaken, I believe that hexify is too VMS-oriented to be used as a general-purpose solution. Some versions use 32-bit packing, they encode VMS file attributes, etc. Seems that uuencode is really the best choice - it comes on a flavor for just about anything (built into Unix plus PC, Mac, VMS versions, etc etc). John F. Sandhoff, Network Support California State University, Sacramento sandhoff@csus.edu ================================================================================ Archive-Date: Thu, 16 Apr 1992 10:05:05 EDT From: legoux@gsiserv.gsi.fr Reply-To: legoux@gsiserv.gsi.fr Date: 16 Apr 92 12:26:02 GMT+00.00 Message-ID: 20624161402991/127 GSIDP To: MX-LIST___/#l#A#r#VMS.ECS.RPI.EDU_//FR/ATLAS/////@sirius.gsi.fr Subject: Problem with definition of MX File Server Hello MX users, Does someone of you knows where is my problem ? I have a mail list with a fileserver attached to it. The file VMF_GSID_FORUM.year-month is correctly update, but I can't get it by SENDME command in a mail to VMF_GSID_FORUM. VMF_GSID_FORUM-Mgr said me "Unknown package name". List server: Name: VMM_GSID_FORUM Owner: "legoux@GPCX01" Reply-to: List, Sender Archive: MX_ROOT:[MLF.FILE_SERVERS.VMM_GSID_FORUM]VMF_GSID_FORUM Description: Mail Forum de Gsi Distribution Paris Errors-to: legoux@GPCX01 Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWE) File server: Name: VMF_GSID_FORUM, Manager: legoux@GPCX01 Root: $1$DIA0:[MX.MLF.FILE_SERVERS.VMM_GSID_FORUM.] Linked to mailing list: VMM_GSID_FORUM No delay threshold. Daily limits: Server: 0 Host: 0 User: 0 Directory contents: Directory MX_ROOT:[MLF.FILE_SERVERS.VMM_GSID_FORUM] VMF_GSID_FORUM.1992-04;1 VMF_GSID_FORUM.DESCRIPTION;1 Total of 2 files. Thanks, Patrice Legoux. +--------------------------------------+---------------------------------------+ | Patrice LEGOUX | e-mail : Patrice.Legoux@gsi.fr | +--------------------------------------+---------------------------------------+ | GSI DISTRIBUTION | Decnet : GPCL01::LEGOUX | | 38 Rue Jacques IBERT +---------------------------------------+ | BP 108 | Tel : (33.1) 47.48.18.19 | | 75821 PARIS Cedex 17 | Fax : (33.1) 47.48.04.83 | | France | Telex : 611 581 F | +--------------------------------------+---------------------------------------+ | X400 : C=FR; ADMD=ATLAS; PRMD=GSIDISTPAR; S=LEGOUX; G=PATRICE | +------------------------------------------------------------------------------+ ================================================================================ Archive-Date: Thu, 16 Apr 1992 14:32:12 EDT Date: Thu, 16 Apr 1992 13:28:21 CDT From: "George D. Greenwade" Reply-To: "George D. Greenwade" To: legoux@gsiserv.gsi.fr CC: mx-list@vms.ecs.rpi.edu Message-ID: <00959311.FE96A3A0.136@SHSU.edu> Subject: RE: Problem with definition of MX File Server On 16 Apr 92 12:26:02 GMT+00.00, Patrice LEGOUX posted: > I have a mail list with a fileserver attached to it. > > The file VMF_GSID_FORUM.year-month is correctly update, but I can't > get it by SENDME command in a mail to VMF_GSID_FORUM. > > VMF_GSID_FORUM-Mgr said me "Unknown package name". > >List server: > > Name: VMM_GSID_FORUM > Archive: MX_ROOT:[MLF.FILE_SERVERS.VMM_GSID_FORUM]VMF_GSID_FORUM > > >File server: > > Name: VMF_GSID_FORUM, Manager: legoux@GPCX01 > Root: $1$DIA0:[MX.MLF.FILE_SERVERS.VMM_GSID_FORUM.] You're telling the list to put the archives in the directory MX_ROOT:[MLF.FILE_SERVERS.VMM_GSID_FORUM] and the file server that it's root directory is $1$DIA0:[MX.MLF.FILE_SERVERS.VMM_GSID_FORUM.] (I assume MX_ROOT is defined to $1$DIA0:[MX.]) so here's the catch: The file server is looking for the file MX_ROOT:[MLF.FILE_SERVERS.VMM_GSID_FORUM.VMM_GSID_FORUM]VMM_GSID_FORUM.* and you have defined your archive to reside in MX_ROOT:[MLF.FILE_SERVERS.VMM_GSID_FORUM]VMM_GSID_FORUM.* The file server is going to look for packages in subdirectories of the file server's root directory, with package_name as the name of the subdirectory and package_name as the file name of the package (using extensions to discriminate between files within a package). Either (a) create the extra directory level or (b) redefine the root of the file server to get it to look where you have defined the archives to exist. Use case (a) if you have packages other than the archives you wish them to have access to; use case (b) if you have packages you truly wish to restrict to the list membership. If this isn't clear enough, let me know and I'll try again; it's really a pretty simple and straightforward problem, but one new users often come up against. 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: Thu, 16 Apr 1992 17:17:50 EDT Date: Thu, 16 Apr 1992 17:17 EDT From: Miles Reply-To: Miles Subject: Help with stalled ROUTER To: mx-list@vms.ecs.rpi.edu Message-ID: <01GIX8HJEGKW9GV6Q0@miavx2.ham.muohio.edu> Hullo, I'm having problems. BIG problems. I'm using MX 3.1. Things have been running smoothly until yesterday. At that time, mail stopped being delivered. Mail still comes in, but everything sits in the queue as READY. I can't figure out what's wrong. I've turned debugging on for everything but no log files except for the SMTP server get generated. I've tried resetting everything. I've tried shutting everything down and restarting. That seemed to work for a while, then mail delivery stopped again. Anything anyone can offer would be GREATLY appreciated. It was my idea to switch to MX and now I'm up the creek without a paddle as it were. Thanks. - Miles - P.S. Oh, since the mailer isn't working at my site, please send mail to maoursler@miavx2.ham.muohio.edu. ------------------------ Miles Oursler Manager of Networks and Systems Kenyon College 614-427-5696 ------------------------- ================================================================================ Archive-Date: Thu, 16 Apr 1992 17:51:33 EDT To: mx-list@vms.ecs.rpi.edu Date: 16 Apr 92 11:22:57 MDT From: bjorndahl@augustana.ab.ca (Sterling G. Bjorndahl) Reply-To: bjorndahl@augustana.ab.ca (Sterling G. Bjorndahl) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <3008@augustana.ab.ca> References: <009591E2.0E248AC0.3898@CCVAX.CCS.CSUS.EDU> Subject: Re: UUencoded files and MX... In article <009591E2.0E248AC0.3898@CCVAX.CCS.CSUS.EDU>, syssand@CCVAX.CCS.CSUS.EDU (John F. Sandhoff) writes: ... > packing, they encode VMS file attributes, etc. Seems that uuencode > is really the best choice - it comes on a flavor for just about > anything (built into Unix plus PC, Mac, VMS versions, etc etc). > > John F. Sandhoff, Network Support > California State University, Sacramento > sandhoff@csus.edu UUencode is fine if you know that your file won't have to pass through any EBCDIC-using nodes (e.g. BITNET). When I was using BITNET several years ago, uuencode was useless because there was no standard mapping between ASCII and EBCDIC for certain characters used by uuencode. If you can find XXencode somewhere, it's a better bet. C source code for XXencode and -decode is available from a number of sources. -- Sterling G. Bjorndahl, bjorndahl@Augustana.AB.CA or bjorndahl@camrose.uucp Augustana University College, Camrose, Alberta, Canada (403) 679-1516 ================================================================================ Archive-Date: Thu, 16 Apr 1992 23:18:22 EDT Date: Thu, 16 Apr 1992 23:16:40 EDT From: "Jonathan E. Hardis" Reply-To: "Jonathan E. Hardis" To: pedro%okcu.bitnet@vax844.phy.nist.gov, MX-List@vms.ecs.rpi.edu CC: hardis@vax844.phy.nist.gov Message-ID: <00959364.2E0240C0.692@vax844.phy.nist.gov> Subject: Re: BITNET<=>Internet In reference to Message: <00958C15.99B0F240.24828@OKCU> From: "Pedro A. Crespo" > Our node (OKCU) being connected only to BITNET, and being far from an > official BITNET/Internet gateway (i.e. CUNYVM) is prone to mail outtages > when any line between OKCU and CUNYVM is down (too frequently). Now, to > alleviate this, and taking into account that our parent node (UOKMVSA) > has a direct link to an Internet domain, I have defined a couple of > re-write rules to route all Internet-style addresses through UOKMVSA.BITNET: > > DEFINE REWRITE RULE "<{user}@{host}.{something}> - > "<{user}%{host}.{something}@UOKMVSA.BITNET>" Whoa! What about... DEFINE PATH "OKCU.BITNET" LOCAL DEFINE PATH *.BITNET JNET DEFINE PATH * JNET/ROUTE="UOKMVSA.BITNET" Instead of YOU trying to coerse UOKMVSA into gatewaying your mail onto the Internet, let it figure it out for itself. The same goes for UUCP. The part of your question that this doesn't address is people sending mail to you. If you advertise your name as OKCU.BITNET, people already on BITNET should have no trouble reaching you. People on the Internet will end up using whatever gateway is convenient for them. (Check out where this message is gatewayed from me.) The conflict here seems to be that you want to coerse others on the Internet to use UOKMVSA to reach you, which as I said above may be the wrong strategy. You make it sound like UOKMVSA doesn't know where OKCU is. (This you can test separately.) However, could it be that UOKMVSA isn't configured to allow any random outsider to use it as a router? ================================================================================ Archive-Date: Sat, 18 Apr 1992 19:25:18 EDT To: mx-list@vms.ecs.rpi.edu Date: 18 Apr 92 23:19:26 GMT From: moore@cs.utk.edu (Keith Moore) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: References: <009591E2.0E248AC0.3898@CCVAX.CCS.CSUS.EDU>, <3008@augustana.ab.ca> Reply-To: moore@cs.utk.edu Subject: MIME (was Re: UUencoded files and MX...) In article <3008@augustana.ab.ca>, bjorndahl@augustana.ab.ca (Sterling G. Bjorndahl) writes: > In article <009591E2.0E248AC0.3898@CCVAX.CCS.CSUS.EDU>, syssand@CCVAX.CCS.CSUS.EDU (John F. Sandhoff) writes: > ... > UUencode is fine if you know that your file won't have to pass through any > EBCDIC-using nodes (e.g. BITNET). When I was using BITNET several years > ago, uuencode was useless because there was no standard mapping between > ASCII and EBCDIC for certain characters used by uuencode. If you can find > XXencode somewhere, it's a better bet. C source code for XXencode and > -decode is available from a number of sources. The forthcoming MIME standard for Internet mail defines a scheme for encoding binary data (BASE64) that is similar to uuencode, but uses only characters that are in all variants of both EBCDIC and ASCII. MIME is an extension of RFC 822 that defines a mechanism for multiple typed body parts per message, "rich" text as well as text in other character sets besides ASCII, image and audio data, and more. The spec has been in development over a year now, and should be released as an Internet Proposed Standard RFC within a few weeks. -- Keith Moore / U.Tenn CS Dept / 107 Ayres Hall / Knoxville TN 37996-1301 Internet: moore@cs.utk.edu BITNET: moore@utkvx ================================================================================ Archive-Date: Sun, 19 Apr 1992 09:42:00 EDT Sender: Date: Sun, 19 Apr 1992 05:37:36 PST From: Carl J Lydick Reply-To: Carl J Lydick To: mx-list@vms.ecs.rpi.edu Message-ID: <0095952B.BA1EC9C0.25708@SOL1.GPS.CALTECH.EDU> Subject: Another item for the wishlist It'd be nice if MX could be configured to send notification each time an attempt to send a mail message fails, preferably if it could be so configured on a per-user basis. ================================================================================ Archive-Date: Mon, 20 Apr 1992 09:52:45 EDT To: mx-list@vms.ecs.rpi.edu Date: 20 Apr 92 14:23:47 GMT From: dvbig@dymaxion.ns.ca Reply-To: dvbig@dymaxion.ns.ca Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr20.102347.1@dymaxion.ns.ca> Subject: Insert angle brackets in MAIL replies with TPU I am running MX on VMS 5.4. I would like to be able to automatically insert angle brackets in front of replied-to or forwarded messages. It is not obvious to me how this is done. My guess is that it would require specifying a TPU command file to execute whenever MAIL invokes TPU, but there doesn't appear to be any way to do this via logical names or MAIL settings. --- Ben Armstrong, Software Development bus: (902)422-1973 Dymaxion Research Ltd., fax: (902)421-1267 Halfiax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca ================================================================================ Archive-Date: Mon, 20 Apr 1992 11:38:13 EDT Date: Mon, 20 Apr 92 11:34 EDT From: Reply-To: Subject: MX SMTP delivery agent and Domain Name Servers To: MX-LIST@vms.ecs.rpi.edu Hello, ENVIRONMENT: ============ We have a VAX running CMU-TEK TCP/IP version 6.6 and MX version 2.3. Our network is hierarchical, i.e., we use a domain name server on a unix machine to resolve all network names. No host tables. The namres$config file has enabled domain name services provided by the unix machine. I have defined the following logical so that the SMTP delivery agent of MX knows what to do with mail that it cannot deliver on the local VAX, i.e., use the Domain Name Server: $ define/system/exec netlib_nameservers "192.132.21.12" The IP address is supposed to be that of my nameserver. PROBLEM: ======== When I send mail to an address that is not local to the VAX, lets say to the unix machine, MX goes into a weird mail loop. The result is a mail queue that gets larger by the minute with the same UNDELIVERED mail. OBSERVATION: ============ All of the above PROBLEM works in a flat network environment, i.e., disabled domain services in the namres$config file and a legitimate hosts.txt file. SUSPICION: ========== MX SMTP delivery agent still does not know about my NAME SERVER ? If so, why ? REQUEST: ======== Heeeeeeeeeelp ? If you have any ideas please reply to this list or to my bitnet mail address: IAN@SENECA.BITNET Thanks in advance. Ian Vaz Seneca College ================================================================================ Archive-Date: Mon, 20 Apr 1992 13:28:34 EDT Date: Mon, 20 Apr 1992 13:27:12 EDT From: "Jonathan E. Hardis" Reply-To: "Jonathan E. Hardis" To: ian%seneca.bitnet@vax844.phy.nist.gov, MX-LIST@vms.ecs.rpi.edu CC: hardis@vax844.phy.nist.gov Message-ID: <00959636.7EADAF80.762@vax844.phy.nist.gov> Subject: Re: MX SMTP delivery agent and Domain Name Servers > ENVIRONMENT: > ============ > We have a VAX running CMU-TEK TCP/IP version 6.6 and MX version 2.3. > Our network is hierarchical, i.e., we use a domain name server on a > unix machine to resolve all network names. No host tables. > The namres$config file has enabled domain name services provided by > the unix machine. I have defined the following logical so that > the SMTP delivery agent of MX knows what to do with mail that it > cannot deliver on the local VAX, i.e., use the Domain Name Server: > > $ define/system/exec netlib_nameservers "192.132.21.12" > > The IP address is supposed to be that of my nameserver. Okay, stop right there. Since you're running CMU-TEK TCP/IP, you should _not_ try to tell MX where the name server is. It will do the right thing, provided you have the TCP/IP layer connfigured properly. You want to make sure that CMUTEK_ROOT:[SYSMGR]NAMRES.CONFIG is correct. In the documentation, check out pages 2-10 (where the file was created in the first place) and 3-8. ================================================================================ Archive-Date: Mon, 20 Apr 1992 17:25:55 EDT To: mx-list@vms.ecs.rpi.edu Date: 20 Apr 92 10:48:16 GMT From: lhotka@abel.incstar.com Reply-To: lhotka@abel.incstar.com Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <2795.29f2a170@abel.incstar.com> Subject: Inbound mail via DECUS uucp I asked this question before and got a couple answers, but the ideas didn't work... I am wondering exactly how MX manipulates addresses as they come into a system via DECUS uucp. We recieve our mail from cs.umn.edu (umn-cs.UUCP). Their mailer sends us return addresses in the form: umn-cs!user%host and they can not change this (I checked). In the past (before MX) the mail was From: UUCP%"umn-cs!user%host" and this worked fine, though it was perhaps not the best. Now, with MX mail is From: MX%"user%host%umn-cs.UUCP@ABEL.INCSTAR.COM" and this is definately not good. To make matters worse, somehow MX is thinking it recieved the mail from umn.UUCP instead of umn-cs.UUCP and this is causing *lots* of trouble. I don't have any idea where the umn.UUCP is coming from and as it is not a real machine...BOUNCE! In any case, in an effort to get rid of the umn-cs in the addresses I added the following rules to UUCP_CFG:MAIL_REWRITE.RULES as was suggested in response to my previous question. [INBOUND-FROM] *%*@umn-cs \001@\002 umn-cs!*@* \001@\002 umn-cs!*!* \001!\002 umn-cs!*%* \001@\002 # This has had literally no effect what so ever. Does MX actually use the MAIL_REWRITE.RULES file for inbound mail? In any case, does anyone have a suggestion as to how I can get my return addresses to be MX%"user@host" instead of MX%"user%host%umn-cs.UUCP@ABEL.INCSTAR.COM" ??? Thanks for any help! Rockford Lhotka INCSTAR Corp Applications Project Leader 1990 Industrial Blvd lhotka@incstar.com PO Box 285 612/779-1701 Stillwater, MN 55082 >>>Amiga - The computer for the creative mind<<< ================================================================================ Archive-Date: Mon, 20 Apr 1992 21:59:47 EDT To: mx-list@vms.ecs.rpi.edu Date: 15 Apr 92 12:29:39 EDT From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr15.122939.4280@dmc.com> Subject: Problem with GATENEWS news/mail gateway. For those of you using MX 3.1 and running mailing list to news gateways, I ran into a bug in GATENEWS yesterday. You can cause it as follows: 1. Post a message to a news group gatewayed to a mailing list. 2. Cancel the message. 3. Post another message to the same group. When GATENEWS runs (in NEWSSKIM.COM), MX_ENTER croaks because one of the temporary files used to share state between the processes is still in use by another user (presumably GATENEWS). I haven't had time to find out which one is the problem, but I thought you'ld like to know about it. It has the unfortunate side effect of throwing NEWSSKIM.COM into an infinite loop, which is how I noticed the problem. If I have some time, I'll chase it a bit more myself. Anybody fixing this in the meantime, let me know.] Thanks -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Mon, 20 Apr 1992 21:59:56 EDT To: mx-list@vms.ecs.rpi.edu Date: 15 Apr 92 12:31:43 EDT From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr15.123143.4281@dmc.com> References: <00958E42.F3A43B20.31400@shrsys.hslc.org> Subject: Re: Mailing List File Server Conflict In article <00958E42.F3A43B20.31400@shrsys.hslc.org>, simon@shrsys.hslc.org (Alan Simon) writes: > I have a mailing list set up with a file server. When I post to the mailing > list, VMS user ARCHIVES gets the post. How do I set up the mailing list and > file server so that this doesn't happen? > > Thanks for your help. Remove the file server from the mailing list and add it again with the /NOMAIL characteristic: remove fileserv@yournode add /nomail fileserv@yournode And that should do it. -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Mon, 20 Apr 1992 22:06:58 EDT To: mx-list@vms.ecs.rpi.edu Date: 15 Apr 92 23:09:54 EDT From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr15.230954.4288@dmc.com> References: <1992Apr15.122939.4280@dmc.com> Subject: Re: Problem with GATENEWS news/mail gateway. (fixed) In article <1992Apr15.122939.4280@dmc.com>, munroe@dmc.com (Dick Munroe) writes: > For those of you using MX 3.1 and running mailing list to news gateways, I ran > into a bug in GATENEWS yesterday. You can cause it as follows: > > 1. Post a message to a news group gatewayed to a mailing list. > 2. Cancel the message. > 3. Post another message to the same group. > The bug was pretty basic and triggered any time a news batch file had more than one message in it. I've fixed the problem on my system and submitted new kits to VMSNET.SOURCES and to Matt for inclusion in the MX Contributions. Anybody desiring a copy of the new GATENEWS set me know and I'll send you a copy (at least until the sources make it into VMSNET.SOURCES, then you can scrounge them from a fileserver near you). -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Tue, 21 Apr 1992 05:35:52 EDT To: mx-list@vms.ecs.rpi.edu Date: 20 Apr 92 16:31:11 GMT From: lhotka@abel.incstar.com Reply-To: lhotka@abel.incstar.com Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <2796.29f2f1d1@abel.incstar.com> Subject: Odd outbound mail... Is this explainable? In particular note the 'To:' line - where did this address come from??? ADAM has no mail rewrite rules BTW. ---------------------------------------------------------------- From !adam.incstar.com!Postmaster Mon, 20 Apr 92 16:02:08 CDT remote from incstar Received: by abel.incstar.com (DECUS UUCP /1.3-1/2.5/); Mon, 20 Apr 92 16:01:55 CDT Received: from ADAM (ADAM::SYSTEM) by ABEL (MX X3.1) with SMTP (DECnet); Mon, 20 Apr 1992 16:01:36 CDT Date: Mon, 20 Apr 1992 16:01:49 CDT From: Postmaster@adam.incstar.com (Mailing list & file server) To: <@umn.UUCP:bd%Dartmouth.EDU@fluent.UUCP> ^^^^^^^^^^^^^^^^^^^^^^^^^ [ This is quite odd, no?? ] Subject: Mailing list or file server error Note: this message was generated automatically. The following error(s) occurred during local delivery of your message. Error in delivery to mailing list l-cim: unknown command: I would like to SUBSCRIBE to cim. Thanks. BD Message follows. Received: from ABEL (ABEL::SYSTEM) by ADAM (MX X3.1) with SMTP (DECnet); Mon, 20 Apr 1992 16:01:46 CDT Received: from umn by abel.incstar.com (MX X3.1) with UUCP; Mon, 20 Apr 1992 16:00:40 CDT Received: from dartvax.dartmouth.edu by cs.umn.edu (5.61/1.14) id AA28012; Mon, 20 Apr 92 15:06:52 -0500 Received: from fluent.UUCP by dartvax.dartmouth.edu (5.65+D4/4.4HUB) id AA09151; Mon, 20 Apr 92 16:06:30 -0400 Received: by fluent (4.1/SMI-4.1) id AA08813; Mon, 20 Apr 92 16:02:06 EDT Date: Mon, 20 Apr 92 16:02:06 EDT From: Message-ID: <9204202002.AA08813@fluent> To: l-cim-request@adam.incstar.com Subject: SUBSCRIBE to cim I would like to SUBSCRIBE to cim. Thanks. BD ---------------------------------------------------------------- Rockford Lhotka INCSTAR Corp Applications Project Leader 1990 Industrial Blvd lhotka@incstar.com PO Box 285 612/779-1701 Stillwater, MN 55082 >>>Amiga - The computer for the creative mind<<< ================================================================================ Archive-Date: Tue, 21 Apr 1992 15:11:57 EDT Sender: Date: Tue, 21 Apr 1992 12:09:44 PDT From: "John F. Sandhoff" Reply-To: sandhoff@csus.edu To: dvbig@dymaxion.ns.ca CC: mx-list@vms.ecs.rpi.edu, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <009596F4.D6D5A500.9238@CCVAX.CCS.CSUS.EDU> Subject: RE: Insert angle brackets in MAIL replies with TPU >I am running MX on VMS 5.4. I would like to be able to automatically insert >angle brackets in front of replied-to or forwarded messages. There is a command procedure written by Harry Flowers that will provide this functionality. It is available on certain DECUS tapes, but I don't think that it's made it to the user contributions section on Matt's FTP server (vms.ecs.rpi.edu) (at least it's not in the MX031 saveset). Since it's relatively short I've taken the liberty to attach it to this message. DISCLAIMER: It *looks* neat but I haven't actually tried it yet. At the very least it shows several nifty things that you can do with VMS Mail. Play with it before going live with it. I've heard a couple mutterings from others around here that when they try to send a file it does nasties to them. I haven't followed up so I can't be more specific. John F. Sandhoff, Network Support California State University, Sacramento sandhoff@csus.edu - - - - Begin Included File - - - - $ SAVERIFY = 'F$VERIFY(0)' ! Save and turn off verify $!----------------------------------------------------------------------------+ $! MAIL_EDIT.COM - Used when editing mail to send; quote and spell check | $!----------------------------------------------------------------------------+ $! To use this procedure, you should place this in SYS$LOGIN:LOGIN.COM: $! $! $ MAI*L == "MAIL/EDIT=(SEND,REPLY=EXTRACT,FORWARD)" $! $ DEFINE MAIL$EDIT SYS$LOGIN:MAIL_EDIT.COM $! $! This file should be in SYS$LOGIN. If a file MAIL_EDIT.SIG exists there $! as well, it will automatically be appended to the end of the message as $! a signature after you exit your editing and spelling checking sessions. $! $! You may re-define the following symbols to suit personal preference: $ QUOTE_CHR = "> " ! Quote character(s) $ EDITOR = "EDT" ! Editor: may be EDT or TPU $ SIG_FILE = "SYS$LOGIN:MAIL_EDIT.SIG" ! Name and location of sig file $! $!----------------------------------------------------------------------------- $! $ IF F$TRNLNM("SYS$INPUT",,,"USER",,"ACCESS_MODE") .EQS. "USER" THEN - DEASSIGN/USER_MODE SYS$INPUT ! Just in case $ IF P1 .EQS. P2 ! READ/EDIT; no quote or spell $ THEN DEFINE/USER SYS$INPUT SYS$COMMAND ! Re-direct input for edit $ EDIT/'EDITOR'/READ_ONLY 'P2' ! Edit the message to read $ EXIT 1 + 0*F$VERIFY(SAVERIFY) ! Exit with success $ ENDIF ! EndIf READ/EDIT $ IF P1 .EQS. "" THEN GOTO NO_INPUT ! SEND; no quote $ WRITE SYS$OUTPUT "Quoting mail message with ""''QUOTE_CHR'""..." $ OPEN/READ/ERR=FINISHED INFIL 'P1' ! Open input file $ CREATE/FDL=SYS$INPUT 'P1' ! Create new input text file RECORD FORMAT Variable $ OPEN/READ/WRITE/ERR=FINISHED OUTFIL 'P1' ! Open new input file $ READ/END=DONE INFIL LINE ! Line #1: From $ SMTP_SKIP = (F$LOCATE("%",LINE) .NE. F$LENGTH(LINE)) ! Skip routing info $ WRITE OUTFIL QUOTE_CHR + LINE ! Write out From $ READ/END=DONE INFIL LINE ! Line #2: To (skip) $ READ/END=DONE INFIL LINE ! Line #3: CC (skip) $ READ/END=DONE INFIL LINE ! Line #4: Subject $ WRITE OUTFIL QUOTE_CHR + LINE ! Write out Subject $ READ/END=DONE INFIL LINE ! Line #5: blank $ WRITE OUTFIL "" ! Write out blank line $ LOOP: ! Loop for rest of file $ READ/END=DONE INFIL LINE ! Get a line $ IF SMTP_SKIP ! Are we skipping this? $ THEN LINE = F$EDIT(LINE,"TRIM") ! Blank line for end of garbage $ IF LINE .EQS. "" THEN SMTP_SKIP = "FALSE" ! Don't skip anymore $ GOTO LOOP ! Get another line $ ENDIF ! EndIf SMTP skip $ WRITE OUTFIL QUOTE_CHR + LINE ! Quote and write out line $ GOTO LOOP ! Get another line $ DONE: ! We're done quoting input file $ CLOSE/NOLOG INFIL ! Close original input file $ CLOSE/NOLOG OUTFIL ! Close new input file $ PURGE/NOLOG/NOCONFIRM 'P1' ! Purge input file $ DEFINE/USER SYS$INPUT SYS$COMMAND ! Re-direct input for edit $ EDIT/'EDITOR'/OUTPUT='P2' 'P1' ! Edit the message to send $ GOTO FINISHED ! All finished editing $ NO_INPUT: ! No input file specified $ DEFINE/USER SYS$INPUT SYS$COMMAND ! Re-direct input for edit $ EDIT/'EDITOR' 'P2' ! Edit the message to send $ FINISHED: ! All finished editing $ CLOSE/NOLOG INFIL ! Close input files just to $ CLOSE/NOLOG OUTFIL ! be on the safe side $ IF F$SEARCH(P2) .NES. "" ! Check for mail message $ THEN DEFINE/USER SYS$INPUT SYS$COMMAND ! Re-direct input for spell $ SPELL 'P2' ! Correct spelling errors $ IF F$SEARCH(SIG_FILE) .NES. "" THEN APPEND 'SIG_FILE' 'P2' !sig $ PURGE/NOLOG/NOCONFIRM 'P2' ! Purge older version(s) $ ENDIF ! EndIf message exists $ EXIT 1 + 0*F$VERIFY(SAVERIFY) ! Exit with success $! $!----------------------------------------------------------------------------- $! $! This is an example signature file. Signature files should contain a $! blank line followed by (at most) four lines of information. This is $! common network curtesy: to be sensitive to bandwith restrictions and $! give a replyable address (which what appears in "From:" may not be). $! $!___ ___ _____ ___ ___ Harry Flowers, Tech Support, Memphis State University $!| \/ | / ____\ | | | | 112 Admin Building | Domain: FLOWERS@MSUVX1.MEMST.EDU $!| \ / | \____ \ | |_| | Memphis, TN 38152 | Bitnet: FLOWERS@MEMSTVX1 $!|_|\/|_| \_____/ \_____/ Ph: (901) 678-2663 | TBRnet: 7171::FLOWERS ================================================================================ Archive-Date: Tue, 21 Apr 1992 16:39:39 EDT To: mx-list@vms.ecs.rpi.edu Date: 21 Apr 92 15:33:56 -0600 From: flowers@admin1.memst.edu (Harry Flowers) Reply-To: flowers@admin1.memst.edu (Harry Flowers) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr21.153356.1903@admin1.memst.edu> References: <009596F4.D6D5A500.9238@CCVAX.CCS.CSUS.EDU> Subject: RE: Insert angle brackets in MAIL replies with TPU In article <009596F4.D6D5A500.9238@CCVAX.CCS.CSUS.EDU>, syssand@CCVAX.CCS.CSUS.EDU (John F. Sandhoff) writes: > There is a command procedure written by Harry Flowers that will provide > this functionality. It is available on certain DECUS tapes, but I don't > think that it's made it to the user contributions section on Matt's FTP > server (vms.ecs.rpi.edu) (at least it's not in the MX031 saveset). Since > it's relatively short I've taken the liberty to attach it to this message. I've recently submitted a slightly updated version to vmsnet.sources (it hasn't been sent out yet as far as I know). By posting it to vmsnet.sources, it should wind up on vmsnet archive sites as well. I've fixed a problem with quoting files using "SEND filename" (which I never use so didn't spot), and made the use of the spelling corrector and stripping internal SMTP mail header lines configurable. You might wish to wait for it there. Feel free to distribute it as widely as possible, and send reports of any problems you may have back to me. It's fine with me if Matt wishes to include it in the contributions for MX, too. -- Harry Flowers Internet: FLOWERS@MEMSTVX1.MEMST.EDU Memphis State University & Bitnet: FLOWERS@MEMSTVX1 ================================================================================ Archive-Date: Wed, 22 Apr 1992 11:06:40 EDT To: mx-list@vms.ecs.rpi.edu Date: 22 Apr 92 10:07:51 EDT From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr22.100751.6003@dayton.saic.com> References: <2795.29f2a170@abel.incstar.com> Subject: Re: Inbound mail via DECUS uucp In article <2795.29f2a170@abel.incstar.com>, lhotka@abel.incstar.com writes: > I asked this question before and got a couple answers, but the ideas didn't > work... I am wondering exactly how MX manipulates addresses as they come > into a system via DECUS uucp. > > We recieve our mail from cs.umn.edu (umn-cs.UUCP). Their mailer sends us > return addresses in the form: > > umn-cs!user%host > > and they can not change this (I checked). In the past (before MX) the mail > was > From: UUCP%"umn-cs!user%host" > and this worked fine, though it was perhaps not the best. > > Now, with MX mail is > From: MX%"user%host%umn-cs.UUCP@ABEL.INCSTAR.COM" > > and this is definately not good. To make matters worse, somehow MX is > thinking it recieved the mail from umn.UUCP instead of umn-cs.UUCP and this > is causing *lots* of trouble. I don't have any idea where the umn.UUCP is > coming from and as it is not a real machine...BOUNCE! The return address should be replyable I would think. See below about the umn-cs -> umn.uucp problem. > In any case, in an effort to get rid of the umn-cs in the addresses I added > the following rules to UUCP_CFG:MAIL_REWRITE.RULES as was suggested in > response to my previous question. > > [INBOUND-FROM] > *%*@umn-cs \001@\002 > umn-cs!*@* \001@\002 > umn-cs!*!* \001!\002 > umn-cs!*%* \001@\002 > # Currently MX does not use the UUCP rewrite rules. > This has had literally no effect what so ever. Does MX actually use the > MAIL_REWRITE.RULES file for inbound mail? In any case, does anyone have a > suggestion as to how I can get my return addresses to be > > MX%"user@host" > instead of > MX%"user%host%umn-cs.UUCP@ABEL.INCSTAR.COM" > ??? I tracked down the problem. There are two things going on here. The first is when MX_RMAIL handles the first record of the mail message which is a "From" header, somewhere along the line it truncates the record at 80 characters. In the problem report above, the umn-cs starts in column 78 and the "-cs" string is in columns 81-83. Thats why they are truncated and the user gets umn.uucp instead of umn-cs.uucp. Here is a portion of a debug file to show this. RMAIL: Input file opened, now looking for From_ line(s). RMAIL: Read: From GLAMDRING%BSU.DECNET%MSUS1.BITNET Mon Apr 20 20:55:43 1992 remote from umn-cs RMAIL: This is a From_ line, host=umn, user=GLAMDRING%BSU.DECNET%MSUS1.BITNET RMAIL: Sender string now reads The second problem is MX does not use the UUCP mail_rewrite.rules file at all. The only time UUCP uses the INBOUND rules are when a message is sent via mail/proto=uucp_mailshr. This is not used if you apply the hook into MX. I have proposed a solution to Matt. Using the UUCP utility checkaddr, he can pass both the to and from addresses through checkaddr and it will apply the rewrite rules and return the new addresses just like DECUS UUCP now does. If someone wants to see how this works, define a foreign symbol to point to the uucp_bin:checkaddr program and try something like $ checkaddr :== $uucp_bin:checkaddr $ checkaddr -inbound-from "node!user" This will run the "node!user" through the inbound-from rules and produce the new return address. -Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Thu, 23 Apr 1992 23:13:56 EDT Sender: manager%LEMOYNE.bitnet@VM.ITS.RPI.EDU Date: Thu, 23 Apr 1992 23:12:00 EDT From: Dan Wheeler Reply-To: Dan Wheeler To: mx-list@vms.ecs.rpi.edu CC: manager@LEMOYNE.BITNET Message-ID: <009598E3.B001E4C0.10171@LEMOYNE> Subject: Do I need percent hacking? I would like to know if my internal addresses (VMS mail and mail header) need to look like the example below. I presume this a result of percent hacking because my machine is a gateway of sorts, but I would rather the addresses not include the @LEMOYNE since it confuses my users. My configuration: Single VMS node LEMOYNE JNET/BITNet external network - nodename LEMOYNE TCP/IP (UCX) *local* network - nodename socrates.lemoyne.edu Do I need to keep router/jnet percent hacking enabled? >From: MX%"EDTECH%OHSTVMA.BITNET@LEMOYNE" 22-APR-1992 23:33:46.56 >... >Return-Path: >Received: from SUVM (BITMAIL) by LEMOYNE (MX V3.1) with BSMTP; Wed, 22 Apr 1992 > 23:33:42 EDT >Received: by SUVM (Mailer R2.08) id 9565; Wed, 22 Apr 92 23:30:06 LCL >Date: Wed, 22 Apr 1992 23:21:22 EDT >Reply-To: "EDTECH - Educational Technology" > >Sender: "EDTECH - Educational Technology" >From: MARYGARRETT@lcc.edu >Subject: RE: Use of email as a mentoring tool >To: Dan Wheeler --dan ------------------------------------------------------------------------------ Dan Wheeler, Academic Support Specialist & VMS System Manager Office of Information Systems, Le Moyne College, Syracuse, NY 13214-1399 Phone 315.445.4582/4565 (Home 315.655.8193) WHEELER@LEMOYNE.BITNET ------------------------------------------------------------------------------ Some of my MCP configuration follows: ------------------------------------------------------------ SITE agent settings: Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;48 MX version id is: MX V3.1 Address-rewriting rules: Rewrite "<{u}@lemoyne>" => "<{u}@lemoyne>" Rewrite "<{u}@lemoyne.BITNET>" => "<{u}@lemoyne>" Rewrite "<@{stuff}:{user}@{host}.UUCP>" => "<{user}%{host}%uunet.uu.net@INTERB IT.BITNET>" Rewrite "<{user}@{host}.UUCP>" => "<{user}%{host}%uunet.uu.net@INTERBIT.BITNET >" Rewrite "<@{stuff}:{user}@{host}.CSNET>" => "<{user}%{host}.CSNET%relay.cs.net @INTERBIT.BITNET>" Rewrite "<{user}@{host}.CSNET>" => "<{user}%{host}.CSNET%relay.cs.net@INTERBIT .BITNET>" Rewrite "<@{route}:{user}@{host}.BITNET>" => "<{user}@{host}.BITNET>" Rewrite "<{user}@{host}.BITNET>" => "<{user}@{host}.BITNET>" Rewrite "<@{route}:{user}@{host}>" => "<{user}%{host}@INTERBIT.BITNET>" Domain-to-path mappings: Domain="[192.77.176.100]", Path=Local Domain="lemoyne.edu", Path=Local Domain="socrates.lemoyne.edu", Path=Local Domain="lemoyne", Path=Local Domain="lemoyne.BITNET", Path=Local Domain="*.BITNET", Path=Jnet Domain="admin1", Path=SMTP, Route="ADMIN1" Domain="SOCRATES", Path=Local Domain="admint", Path=SMTP, Route="[192.77.176.1]" SMTP agent settings: Retry interval: 0 00:05:00.00 Maximum number of retries: 96 Number of DNS failure retries: 12 Accounting: disabled Default router: (none) LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. Top headers: 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 headers: (none) ROUTER agent settings: Automatic percent-hack handling: enabled JNET agent settings: Automatic percent-hack handling: enabled BSMTP replies: disabled Accounting: disabled Lenient about gatewaying mail: no No mailer username set. ================================================================================ Archive-Date: Fri, 24 Apr 1992 09:30:06 EDT Sender: clee@madoka.intel.com Date: Fri, 24 Apr 1992 06:29:55 PDT From: Not An Evil Tempter Being Reply-To: Not An Evil Tempter Being To: MX-LIST%VMS.ECS.RPI.EDU@hermes.intel.com CC: clee@madoka.intel.com Message-ID: <00959920.DD5005A0.1982@madoka.intel.com> Subject: Default routes - and do I need to use them? I have a question about routes. All my mail goes through an Ultrix gateway called hermes. I've been having to send mail is the following manner mx-list%vms.ecs.rpi.edu@hermes I would like to find a way to avoid having to enter "@hermes" every time I try sending mail to the outside world. I've tried using SET SMTP/DEFAULT_ROUTE="hermes" but no luck. I've also tried DEFINE PATH * SMTP/ROUTE="hermes" Do I need to restart MX after making changes? Anybody with ideas or suggestions? I'm running MX V3.1A. thx ================================================================================ Archive-Date: Fri, 24 Apr 1992 10:03:42 EDT Sender: clee@madoka.intel.com Date: Fri, 24 Apr 1992 07:03:38 PDT From: Not An Evil Tempter Being Reply-To: Not An Evil Tempter Being To: MX-LIST@VMS.ECS.RPI.EDU CC: clee@madoka.intel.com Message-ID: <00959925.9312A4C0.2000@madoka.intel.com> Subject: Thx: default routes Thanks to everybody who replied to my question about default routes. Everything appears to be working the way I want it to. thx / again ================================================================================ Archive-Date: Fri, 24 Apr 1992 13:17:45 EDT To: mx-list@vms.ecs.rpi.edu Date: 24 Apr 92 15:20:27 GMT From: ake@dayton.saic.com (Earle Ake) Reply-To: ake@dayton.saic.com (Earle Ake) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr24.112028.6011@dayton.saic.com> References: <00959920.DD5005A0.1982@madoka.intel.com> Subject: Re: Default routes - and do I need to use them? In article <00959920.DD5005A0.1982@madoka.intel.com>, clee@madoka.intel.com (Not An Evil Tempter Being) writes: > I have a question about routes. All my mail goes through an Ultrix > gateway called hermes. I've been having to send mail is the following manner > > mx-list%vms.ecs.rpi.edu@hermes > > > I would like to find a way to avoid having to enter "@hermes" every > time I try sending mail to the outside world. I've tried using SET > SMTP/DEFAULT_ROUTE="hermes" but no luck. > > I've also tried DEFINE PATH * SMTP/ROUTE="hermes" > > Do I need to restart MX after making changes? Anybody with ideas or > suggestions? I'm running MX V3.1A. Your problem might be there is a previous path that MX is picking up on and your new rule never is tried. Try this: $ MCP MCP> show all/command/out=config.mcp MCP> exit Now manually edit the file and put your DEFINE PATH statement in there. Remember that MX tries these in the order listed. You can e-mail me offline if you need more help. Now to get this back again, do the following: $ mcp/nofile MCP> @config.mcp MCP> save mx_dir:mx_config.mxcfg MCP> reset/all MCP> exit That should take care of it. -Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake ================================================================================ Archive-Date: Fri, 24 Apr 1992 15:02:41 EDT Date: Fri, 24 Apr 1992 12:29:47 CDT From: "George D. Greenwade" Reply-To: "George D. Greenwade" To: clee@madoka.intel.com CC: mx-list@vms.ecs.rpi.edu Message-ID: <00959953.22B7E4A0.23587@SHSU.edu> Subject: RE: Default routes - and do I need to use them? On Fri, 24 Apr 1992 06:29:55 PDT, Not An Evil Tempter Being posted: > I have a question about routes. All my mail goes through an Ultrix > gateway called hermes. I've been having to send mail is the following > manner > > mx-list%vms.ecs.rpi.edu@hermes > > I would like to find a way to avoid having to enter "@hermes" every > time I try sending mail to the outside world. I've tried using SET > SMTP/DEFAULT_ROUTE="hermes" but no luck. > > I've also tried DEFINE PATH * SMTP/ROUTE="hermes" > > Do I need to restart MX after making changes? Anybody with ideas > or suggestions? I'm running MX V3.1A. Try this (I did this just yesterday on one of our machines): $ MCP :== $MX_EXE:MCP $ MCP MCP> DELETE PATH * MCP> DEFINE PATH * SMTP/ROUTE="hermes.intel.com" MCP> SAVE MCP> RESET/ALL MCP> EXIT If you set the route to the FQDN for the /ROUTE qualifier, you ought to be able to pass your mail transparently (i.e., to mx%"user@node" instead of mx%"user%node@hermes"). Hermes (from what I can tell in the headers, "hermes.intel.com" is the FQDN for the "hermes" you refer to) ought to be able to handle the rest (as it did with this posting) and you ought to have repliable mail, as well. The reason I suggest DELETE then DEFINE for the PATH is that the last PATH DEFINEd is at the end (where it needs to be) and this method ensures that. 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: Fri, 24 Apr 1992 15:44:56 EDT Message-ID: Date: 24 Apr 92 15:22:00 EST From: "Brian Tillman" Reply-To: "Brian Tillman" Subject: RE: Thx: default routes To: "clee" CC: "mx-list" All *what* answers? I saw your question, I saw one reply, and I saw your thanks for all the answers. Could you post the answers you received to the mailing list, please? Many of us would like to know what they were. ================================================================================ Archive-Date: Fri, 24 Apr 1992 20:11:58 EDT Message-ID: <9204250011.AA27783@relay1.UU.NET> Date: Fri, 24 Apr 92 18:17:37 -0400 From: raxco!galaxy.dnet!gleeve@uunet.UU.NET Reply-To: raxco!galaxy.dnet!gleeve@uunet.UU.NET To: "mx-list@vms.ecs.rpi.edu"@uunet.UU.NET Subject: sub subscribe mx-list "Glenn C. Everhart" ================================================================================ Archive-Date: Sun, 26 Apr 1992 20:10:40 EDT To: mx-list@vms.ecs.rpi.edu Date: 27 Apr 92 11:56:50 From: genie@zephyr.dsir.govt.nz (Mark Stephens) Reply-To: genie@zephyr.dsir.govt.nz (Mark Stephens) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: Subject: rewrite rules Hi. I'm currently testing MX to see what it can do. I have a problem with rewriting rules. Following the example in the Management manual, I defined a rewrite rule that looks like this (the names used are not real): define rewrite "<{user}@x25-host.domain>" "<""nnn::{user}""@local-host.domain>" (without the line feed) where x25-host is a VMS machine whose only connection to us is an X25 link, nnn is that machine's X25 number, and local-host is a local machine with PSI. The intention is to direct mail addressed to joebloggs@x25-host.domain to something like "123456789::joebloggs"@psi-host.domain When I send a test message, I get a bounce to say no such host as x25-host.domain. I appears that the rewrite rule hasn't even been applied. The machine I sent from is not the same as psi-host, but is in the same cluster. I'm unclear about the syntax of the rewrite rules. I can only find one example in the manual of a rewrite rule. In both the pattern and rewrite strings, the whole address is enclosed in angle-brackets, and then in double quotes. Are the angle brackets required? I tried my little problem above both with and without them, but the result is the same either way. Any help would be appreciated. Other than this, MX looks like a really neat package, and alot cheaper than PMDF ;-) --- Mark Stephens DSIR Physical Sciences Information Technology Group Wellington, New Zealand -- --- Mark Stephens DSIR Physical Sciences Information Technology Group Wellington ================================================================================ Archive-Date: Sun, 26 Apr 1992 20:20:19 EDT To: mx-list@vms.ecs.rpi.edu Date: 27 Apr 92 00:12:41 GMT From: shuford@cs.utk.edu (Richard Shuford) Reply-To: shuford@cs.utk.edu (Richard Shuford) Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: References: <01GJ9PS1TEJI9BVF0K@HMCVAX.CLAREMONT.EDU> Subject: Re: UUCP and AT&T Mailers (Query) Things are also bad for mail that ATTmail forwards onto Internet from an X.400 source via the AT&T MHS service. We had one poor soul, thus connected, wanting to join the Info-Stratus mailing list, and the From: line that her mail bears when it comes in via SMTP looks like mhs!mc!Patricia_Sherman/OU=0205925@attmail.com OK, so bangpaths as the local part of an RFC822 address are sometimes a necessary evil. But to stick in the "Organizational Unit" field, RFC987-style, of an X.400 Originator/Recipient address is a new extreme of address klugery. To add insult to kluge, the address is un-replyable; ATTmail cannnot find a way to get mail through in the reverse direction, sent back to this same address. If you put in more pieces of the O/R address (derived from inspecting the voluminous header), the mail bounces with the complaint "Inaccessible X.400 administrative domain". You have to use a better-formed address, with no O/R stuff, for ATTmail to send mail back to her: mhs!mc!Patricia_Sherman@attmail.com On the list host, running MX 2.3, we eventually installed some address-rewrite rules that seem to work when the phase of the moon is right to allow her to receive mail from the list. But figuring out what would work was a lot of trouble, and the ATT people whom we contacted seemed either to misunderstand or to be unable to help. -- ....Richard S. Shuford | "A prudent man sees danger and takes refuge, ....shuford@cs.utk.edu | but the simple keep going and suffer for it." ....BIX: richard | Proverbs 22:3 NIV ================================================================================ Archive-Date: Mon, 27 Apr 1992 06:58:40 EDT To: mx-list@vms.ecs.rpi.edu Date: 27 Apr 92 10:49:22 GMT From: kevin@vulcan.mentec.ie Reply-To: kevin@vulcan.mentec.ie Sender: mx-list-request@vms.ecs.rpi.edu Message-ID: <1992Apr27.104922.2879@vulcan.mentec.ie> Subject: MX to PMDF Anyone know if it possible to have MX talk to PMDF using SMTP over DECnet?. We currently use PMDF on our mail router but would like to install MX at remote sites. Any help/suggestions would be greatly appreciated. -- Kevin. ---------------- Kevin O'Farrell Internet Kevin@Mentec.ie Mentec Computer Systems, UUCP ...mcsun!mentec.ie!kevin Pottery Road, DunLaoire, MCIMail 390-4994 Co Dublin, Ireland. Voice/Fax +353-1-285-8444 / 285-8005 ================================================================================ Archive-Date: Mon, 27 Apr 1992 12:39:20 EDT Date: Mon, 27 Apr 1992 12:39 EST From: GREENEBL@PEOCU1.NAVY.MIL (Barry L. Greene) Reply-To: GREENEBL@PEOCU1.NAVY.MIL (Barry L. Greene) To: mx-list@vms.ecs.rpi.edu CC: Subject: Need Help - Receiving errors when outside host query a MX list. Hi All, I just brought up MX on my system. I'm getting errors from users on the Internet when they send a message to a list: >Subject: Mailing list or file server error > >Note: this message was generated automatically. > >The following error(s) occurred during local delivery of your message. > >Error in delivery to mailing list NAVGUIDE: > access denied; send subscription requests to NAVGUIDE-Request@PEOCU1.NAVY.MIL >Message follows. I'm able to use my local SMTP mailer to send message to the list A-OK. The users receive the message, but when they try to send a message back they get the above error message. Any suggestions would be helpful.... Barry L. Greene Internet: greenebl@PEOCU1.NAVY.MIL ______________________________________________________________________ ____ ____ ___ /___ /___/ / / Science Applications International Corporation ____// / / /__ Crystal City, Virginia ---------------------------------------------------------------------- ================================================================================ Archive-Date: Mon, 27 Apr 1992 12:54:48 EDT Date: Mon, 27 Apr 1992 12:54:58 EDT From: Matt Madison Reply-To: madison@vms.ecs.rpi.edu To: mx-list@vms.ecs.rpi.edu Message-ID: <00959BB2.269E99E0.19749@mdmvs.ecs.rpi.edu> Subject: MX V3.1B now available After receiving two more reports of defects in MX V3.1A, I have produced a second maintenance release, called (surpisingly enough) revision B. Everyone who obtains the MX031 kit by anonymous FTP -- or from FileServ -- will get the updated version (savesets A, C, I and J are changed from the original V3.1 release; only savesets A, C, and J are changed from V3.1A). If you have MX V3.1 or V3.1A currently installed and would like to upgrade painlessly to V3.1B, you should get the file 01README.REVB_UPGRADE and the file MX_REVB_UPGRADE031.A_Z, which is the upgrade kit for existing V3.1/V3.1A users. The upgrade kit is also available from FileServ as package MX_REVB_UPGRADE031. The revision B kit includes all of the fixes from revision A, plus the following: 1. Error messages from the Router appeared to have mangled destination addresses (when looked at with MCP QUEUE SHOW/FULL, for example), even though they may have gone through ok. 2. When a list was set to /REPLY_TO=LIST and a message was sent to that list and others (with /REPLY_TO=SENDER) on the same MLF, the reply-to headers in the messages sent via the other lists would incorrectly direct replies to the REPLY_TO=LIST list. -Matt -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Mon, 27 Apr 1992 13:00:14 EDT Date: Mon, 27 Apr 1992 13:00:13 EDT From: Matt Madison Reply-To: madison@vms.ecs.rpi.edu To: mx-list@vms.ecs.rpi.edu Message-ID: <00959BB2.E26A77C0.19751@mdmvs.ecs.rpi.edu> Subject: Spring '92 DECUS Symposium If you are planning on attending the Spring 1992 DECUS Symposium in Atlanta next week, keep an eye out for a BoF (Birds-of-a-Feather) session for MX users. Besides updating everyone on the V3.1B release, I will have some _big_ news -- don't miss out! -Matt -- Matthew Madison, Systems Programmer | Internet: madison@vms.ecs.rpi.edu Engineering Computing Services | Bitnet: MADISON@RPIECSVX Rensselaer Polytechnic Institute | Troy, New York 12180-3590 USA | ================================================================================ Archive-Date: Mon, 27 Apr 1992 14:03:00 EDT Date: Mon, 27 Apr 1992 14:02 EST From: GREENEBL@PEOCU1.NAVY.MIL (Barry L. Greene) Reply-To: GREENEBL@PEOCU1.NAVY.MIL (Barry L. Greene) To: mx-list@vms.ecs.rpi.edu Subject: Repost - Receiving errors when outside host query a MX list. Hi All, Here is a repost of my question with the MX 'show list' included. I'm getting errors from users on the Internet when they send a message to a list: >Subject: Mailing list or file server error > >Note: this message was generated automatically. > >The following error(s) occurred during local delivery of your >message. > >Error in delivery to mailing list NAVGUIDE: > access denied; send subscription requests to >NAVGUIDE-Request@PEOCU1.NAVY.MIL >Message follows. The list configurations is: >Mailing lists: > Name: NAVGUIDE > Owner: "greenebl@PEOCU1.NAVY.MIL" > "maddox@PEOCU1.NAVY.MIL" > Reply-to: NOList, Sender > Archive: DUA1:[NETWARE_DATA1.MAILLIST.NAVGUIDE] > Add message: MX_ROOT:[MLF.MAILING_LISTS]NAVGUIDE_ADD_MESSAGE.TXT > Forwarded-to-owner message: > MX_ROOT:[MLF.MAILING_LISTS]NAVGUIDE_FORWARD_MESSAE.TXT > Description: PEO(CU)'s NAVGUIDE E-Mail Conference > Errors-to: greenebl@PEOCU1.NAVY.MIL > Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RW,WORLD) I'm able to use my local SMTP mailer to send message to the list A-OK. The users receive the message, but when they try to send a message back they get the above error message. Any suggestions would be helpful.... Barry L. Greene Internet: greenebl@PEOCU1.NAVY.MIL ______________________________________________________________________ ____ ____ ___ /___ /___/ / / Science Applications International Corporation ____// / / /__ Crystal City, Virginia ---------------------------------------------------------------------- ================================================================================ Archive-Date: Mon, 27 Apr 1992 16:29:01 EDT Sender: Date: Mon, 27 Apr 1992 13:27:05 PDT From: "John F. Sandhoff" Reply-To: sandhoff@csus.edu To: madison@vms.ecs.rpi.edu CC: mx-list@vms.ecs.rpi.edu, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <00959BB6.A385DD20.15684@CCVAX.CCS.CSUS.EDU> Subject: RE: Spring '92 DECUS Symposium Matt writes: > If you are planning on attending the Spring 1992 DECUS Symposium in Atlanta > next week... I will have some _big_ news -- don't miss out! And for those of us stuck on the West Coast, I trust you'll post the news to the net as soon as applicable? :-) John F. Sandhoff, University Network Support California State University, Sacramento sandhoff@csus.edu ================================================================================ Archive-Date: Mon, 27 Apr 1992 16:30:54 EDT Date: Mon, 27 Apr 1992 16:30:55 EDT From: Matt Madison Reply-To: madison@vms.ecs.rpi.edu To: sandhoff@csus.edu CC: mx-list@vms.ecs.rpi.edu Message-ID: <00959BD0.51D67600.19800@mdmvs.ecs.rpi.edu> Subject: RE: Spring '92 DECUS Symposium >Matt writes: >> If you are planning on attending the Spring 1992 DECUS Symposium in Atlanta >> next week... I will have some _big_ news -- don't miss out! > >And for those of us stuck on the West Coast, I trust you'll post the >news to the net as soon as applicable? :-) Yes, I will also post the news to the list. -Matt ================================================================================ Archive-Date: Mon, 27 Apr 1992 19:26:05 EDT Date: Mon, 27 Apr 1992 17:03:55 CDT From: "George D. Greenwade" Reply-To: "George D. Greenwade" To: mx-list@vms.ecs.rpi.edu Message-ID: <00959BD4.EE070FE0.31528@SHSU.edu> Subject: Problem with Internet MX record sites Over the past few days, we've had a problem getting mail to sites on the Internet which do not have an A record, but instead use an MX record (mail exchanger, pref, etc.). We are using our MultiNet machine as our nameserver, and we can otherwise do just about everything via TCP/IP. We've added a few machines, so maybe......... but what? I'm adequately ignorant on this that I don't even have an inkling of what other information might be useful to an audience which might be able to assist; in all likelihood, I can provide whatever anyone might need. Any ideas? Regards and thanks in advance, 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, 27 Apr 1992 19:29:22 EDT Date: Mon, 27 Apr 1992 16:49:36 CDT From: "George D. Greenwade" Reply-To: "George D. Greenwade" To: GREENEBL@PEOCU1.NAVY.MIL CC: mx-list@vms.ecs.rpi.edu Message-ID: <00959BD2.EE619DE0.31486@SHSU.edu> Subject: RE: Repost - Receiving errors when outside host query a MX list. On Mon, 27 Apr 1992 14:02 EST, GREENEBL@PEOCU1.NAVY.MIL (Barry L. Greene) posted: > I'm getting errors from users on the Internet when they send a message to a > list: > >>Subject: Mailing list or file server error >> >> >>Error in delivery to mailing list NAVGUIDE: >> access denied; send subscription requests to >>NAVGUIDE-Request@PEOCU1.NAVY.MIL >>Message follows. > > The list configurations is: > >>Mailing lists: >> Name: NAVGUIDE >> Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RW,WORLD) ^^^ There's the problem, most likely. Your definition is for only list members to be able to post. Sites which use various names (both Internet and BITNET) for machines cause problems if a user subscribes on one system, then attempts to use mail on another system (this is especially true on the Internet, where new node appear constantly). Short of telling them to re-configure their mail software to use one and only one consistent node name, you might consider defining the list so that you have W:W privs (that way, anyone can post, but only subscribers can review, and all subscriptions can be controlled by you). Hope this helps, 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, 29 Apr 1992 09:24:39 EDT Date: Wed, 29 Apr 1992 09:24 EST From: GREENEBL@PEOCU1.NAVY.MIL (Barry L. Greene) Reply-To: GREENEBL@PEOCU1.NAVY.MIL (Barry L. Greene) To: mx-list@vms.ecs.rpi.edu CC: Subject: Thanks for the help..... Hi All, Thanks for the help. Once I set the protections correctly everything worked fine. One minor point. When someone on another host sends a message to the list, the message has a MX-Warning error in the header. For example: >From: "\"\"Sakamoto, Junko Esther\"\"" >Reply-To: "\"\"Sakamoto, Junko Esther\"\"" > >X-MX-Warning: Warning -- Invalid "To" header. >To: NAVGUIDE"