Archive-Date: Thu, 01 Jul 1993 00:06:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 01 Jul 1993 00:06:00 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096ED2B.F7CECBE0.26209@WKUVX1.BITNET> Subject: MX-LIST Administrivia: Monthly Post Last modified: 31-MAY-1993 23:55 (Added digest info.) Welcome to MX-List@WKUVX1.BITNET, an electronic mailing list established for the discussion of the Message Exchange mail software. This is a routine posting you will see from time to time on MX-List. MX-List postings are also available in a daily digest format. To subscribe to the digest, send the following command in the body of a mail message to MXserver@WKUVX1.BITNET: SUBSCRIBE MX-List-Digest "Your real name here" The MX-List archives are maintained at ARCHIVES@WKUVX1.BITNET. To get a copy of any month's postings, send an e-mail message with the body SEND MX-List.yyyy-mm to ARCHIVES@WKUVX1.BITNET, where "yyyy" is the year and "mm" is the numeric representation of the month. For example, the message SENDME MX-List.1992-04 will send the archives for April 1992. To remove yourself from the mailing list, send the following command to MXserver@WKUVX1.BITNET: SIGNOFF MX-List MXserver supports a few other commands for your convenience. The following commands can be handled automatically by the list processor: SIGNOFF MX-List - to remove yourself from the list REVIEW MX-List - to get a list of subscribers QUERY MX-List - to get the status of your entry on the list SET MX-List NOMAIL - to remain on the list but not receive mail SET MX-List MAIL - to resume receiving mail from the list SET MX-List CONCEAL - to not report your address in a REVIEW SET MX-List NOCONCEAL - to report your address in a REVIEW SET MX-List REPRO - to receive posts you make to MX-List SET MX-List NOREPRO - to not receive posts you make to MX-List LIST - to get a list of mailing lists served by WKUVX1 HELP - to receive a help file By default, subscriptions are set to MAIL, REPRO, NOCONCEAL. If you have any questions, comments, or suggestions about MX-List, please contact the list owner at the address below. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Hunter Goatley, VAX Systems Programmer goathunter@WKUVX1.BITNET Western Kentucky University Academic Computing, STH 226 (502) 745-5251 Bowling Green, KY 42101 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ================================================================================ Archive-Date: Thu, 01 Jul 1993 05:53:33 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX generates host but no domain part in From: Message-ID: <1993Jul1.105949.6953@dct.ac.uk> Date: 1 Jul 93 10:59:49 +0100 To: MX-List@WKUVX1.BITNET Because of trouble with UCX SMTP I've installed MX 3.3 on one of our machines and it works fine... except for the From: field. External sites see a from line of the form From: which is useless. If I leave MX_VMSMAIL_FROM_FORMAT undefined then it does this. If I define it as given below then it still strips to vaxd. If I define it as something else then it uses that string but generates an extra Reply-to: ccdarg@vaxd which again breaks reply. This is all with MX3.3 latest version. Here's the output of SHO LOG *MX* if it helps. "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "$255$DUA0:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_DIR" = "SYS$SYSDEVICE:[MX.QUEUE]" "MX_FLQ_NODE_NAME" = "VAXD" "MX_FLQ_RECLAIM_WAIT" = "0 02:00:00" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "vaxd.dct.ac.uk" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_TIMEZONE" = "+0100" "MX_VMSMAIL_FROM_FORMAT" = "" "MX_VMSMAIL_LOCALHOST" = "@vaxd.dct.ac.uk" -- Alan Greig Janet: A.Greig@uk.ac.dct Dundee Institute of Technology Internet: A.Greig@dct.ac.uk Tel: (0382) 308810 (Int +44 382 308810) ** Never underestimate the power of human stupidity ** ================================================================================ Archive-Date: Thu, 01 Jul 1993 05:58:47 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 01 Jul 1993 05:58:33 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096ED5D.3806BBF1.1965@WKUVX1.BITNET> Subject: RE: MX generates host but no domain part in From: writes: > >Because of trouble with UCX SMTP I've installed MX 3.3 >on one of our machines and it works fine... except for >the From: field. > >External sites see a from line of the form From: >which is useless. If I leave MX_VMSMAIL_FROM_FORMAT undefined >then it does this. If I define it as given below then it >still strips to vaxd. If I define it as something else then >it uses that string but generates an extra Reply-to: ccdarg@vaxd >which again breaks reply. > Sounds like you don't have your fully-qualified domain name listed first in your UCX host definitions. From the MX release notes: 1.3 VMS/ULTRIX Connection Notes If you are using DEC VMS/ULTRIX Connection (UCX) V1.2 through V2.0, you should review your UCX configuration to ensure that you are using your fully-qualified domain name (FQDN) as your primary local host name in your UCX host table. If you followed the UCX documentation when configuring UCX with UCX$CONFIG, it is highly likely that you did not specify your FQDN as your primary host name. If your abbreviated host name is listed as the primary in your UCX host table, then messages sent from the local system will go out with an unreplyable return address. To check your local host name, use the UCX utility: $ UCX UCX> SHOW HOST/LOCAL x.x.x.x ! use your IP address here To ensure that your FQDN is the primary host name for your address, use the UCX commands: UCX> SET NOHOST x.x.x.x ! use your IP address here UCX> SET HOST "full.qual.dom.name"/ADDR=x.x.x.x/ALIAS="abbrev" You will be asked for confirmation on the SET NOHOST command. Substitute your FQDN and IP address in the SET HOST command, and if you would still have your shortened host name in the host table, use the /ALIAS qualifier, as shown. Once you have updated your host table, you should review the file SYS$MANAGER:UCX$INET_SET_ INTERFACES.COM and replace all instances of your abbreviated host name with your FQDN. Note: Remember that UCX is case sensitive with regard to host names! Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 01 Jul 1993 11:41:49 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: MX generates host but no domain part in From: Message-ID: <1993Jul1.163935.6971@dct.ac.uk> Date: 1 Jul 93 16:39:35 +0100 To: MX-List@WKUVX1.BITNET In article <0096ED5D.3806BBF1.1965@WKUVX1.BITNET>, "Hunter Goatley, WKU" writes: > Sounds like you don't have your fully-qualified domain name listed > first in your UCX host definitions. From the MX release notes: Thanks. That's solved it. Don't know how I missed that in the release notes. -- Alan Greig Janet: A.Greig@uk.ac.dct Dundee Institute of Technology Internet: A.Greig@dct.ac.uk Tel: (0382) 308810 (Int +44 382 308810) ** Never underestimate the power of human stupidity ** ================================================================================ Archive-Date: Thu, 01 Jul 1993 13:41:04 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 01 Jul 1993 14:38:37 EDT From: Kipp Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET Message-ID: <0096EDA5.DF16D280.20361@ACAVAX.LYNCHBURG.EDU> Subject: Using multiple SMTP components I've offered to take over a very large mailing list, and I didn't realize the implication. I was using only one SMTP component of MX and while processing a single queue entry, all other outgoing SMTP mail was held up. I've now created 5 SMTP components at startup, but the potential still exists for five mailing list messages to hold up "regular" mail in the queue. This mailing list has hundreds of addresses and at times, the traffic could become heavy. Some questions: - How many SMTP components are practical, and what sort of performance impact is caused by using multiple components? (I'm running a MicroVAX 3100) - Is there any way to direct my mailing list to a dedicated SMTP server, or in other words, is there any way to prevent my system from simultaneously processing multiple mailing list messages while at the same time always having one or more SMTP processes available for handling light requests? - Could any combination of Multinet SMTP handling and MX provide a workaround? Any suggestions for resolving this problem are appreciated, including any suggestions for an alternate approach to the problem. -------------------------------------------------------------------------------- Kipp Teague E-Mail: teague@acavax.lynchburg.edu Lynchburg College, Lynchburg, Virginia Phone: (804) 522-8358 ================================================================================ Archive-Date: Thu, 01 Jul 1993 14:38:04 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: PMDF-MX mailing list incompatibility Date: Thu, 1 Jul 1993 18:06:59 GMT Message-ID: <1993Jul1.180659.24984@cpu.com> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET I'm experiencing the following problem when receiving mail from a PMDF mailing list: The FROM line is not the mailing list. Please see below the reply from a message that I sent the mailing list manager: ======================================================================== >> The following message was sent to the LIST. This list's >> reply-to is supposed to be the list, however, the reply-to field is the >> poster and the reset-reply-to field is the list. > >I'm pretty sure that your mail to the list arrived with a >Reply-to:-header already in it, and that PMDF's action in this case is >to create a Resent-reply-to:-header. [It normally creates a Reply-to:- >header.] > >> At least with a basicaly default MX configuration this causes replies >> to go to the poster not the list. > >That seems to be a PMDF-MX incompatibility. According to my PMDF manual, >when PMDF receives a message with both a Resent-reply-to and a Reply-to, >it will use the first to create the VMSmail From line. It's precendence >order is: > Resent-reply-to > Resent-from > Reply-to > From > Resent-sender > Sender > envelope return address > >From your example message, it appears that MX doesn't work the same >way. I don't know if this is a difference in philosophy, or if it's >an oversight on MX's part, or if it's a config option for you. > >> Please look into this and inform me of the results. > >Could you get some feedback from Mike Madison regarding how MX should >be acting in this area? If he thinks it's doing the right thing, then >I'll bring up the discrepancy for discussion on info-pmdf. Anybody know for sure what is supposed to be going on? > >Of course, if you can arrange to have your mail sent without a >Reply-to:-header, you won't have any problems. Is the last possible without changing the configuration (I did not see anything about this). > >>From the rfc822 headers at the end: >> To: foo.org!list >> Resent-Reply-To: rex!foo.Org!list@dumbo.cpu.com >> Reply-To: rex!cpu.com!gwlester@dumbo.cpu.com >> Resent-Message-ID: <01H00Y0X5AC29AO1AT@foo.Org> >> Message-ID: <0096ED7C.CF70C440.15708@cpuvs3.cpu.com> Thanks in advance for any ideas/facts ========================================================================== * Gerald W. Lester ! Voice: (504)-889-2784 * * Computerized Processes Unlimited ! FAX: (504)-889-2799 * * 4200 S. I-10 Service Road, Suite #205 ! E-Mail: gwl@cpu.com * * Metairie, LA 70001 ! * ========================================================================== ================================================================================ Archive-Date: Thu, 01 Jul 1993 17:55:59 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: PMDF-MX mailing list incompatibility Message-ID: <1993Jul1.205635.3762@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Thu, 1 Jul 1993 20:56:35 GMT To: MX-List@WKUVX1.BITNET In article <1993Jul1.180659.24984@cpu.com>, gwlester@cpu.com (Gerald W. Lester) writes: >>That seems to be a PMDF-MX incompatibility. According to my PMDF manual, >>when PMDF receives a message with both a Resent-reply-to and a Reply-to, >>it will use the first to create the VMSmail From line. It's precendence >>order is: >> Resent-reply-to >> Resent-from >> Reply-to >> From >> Resent-sender >> Sender >> envelope return address >> >>From your example message, it appears that MX doesn't work the same >>way. I don't know if this is a difference in philosophy, or if it's >>an oversight on MX's part, or if it's a config option for you. It's a "difference in philosophy". RFC822 provides for Resent- headers, but doesn't specify how they should be used. To quote: > 4.2. FORWARDING > > Some systems permit mail recipients to forward a message, > retaining the original headers, by adding some new fields. This > standard supports such a service, through the "Resent-" prefix to > field names. > > Whenever the string "Resent-" begins a field name, the field > has the same semantics as a field whose name does not have the > prefix. However, the message is assumed to have been forwarded > by an original recipient who attached the "Resent-" field. This > new field is treated as being more recent than the equivalent, > original field. For example, the "Resent-From", indicates the > person that forwarded the message, whereas the "From" field indi- > cates the original author. > > Use of such precedence information depends upon partici- > pants' communication needs. For example, this standard does not > dictate when a "Resent-From:" address should receive replies, in > lieu of sending them to the "From:" address. Now, MX uses Resent- headers when it forwards mail to a VMS MAIL SET FORWARD address. It wouldn't make sense for replies to go to the Resent-From address for this sort of forwarding. My feeling at the time was that if a user is going to manually forward a message, that a new message should be created that encapsulates the original... I believe PMDF does that as well, implementing it with MIME multi-part messages. I've never seen a mailing list processor use Resent- headers for its messages. The two approaches I have seen are the "leave it alone" approach, used by most Internet mailing lists (the 822 headers are left completely intact), and the "reformat" approach used by LISTSERV (just about all the headers are rewritten). Sounds like this mailing list is shooting for something in the middle, wanting to provide LISTSERV-like redirection features without touching the original headers. >>Could you get some feedback from Mike Madison regarding how MX should >>be acting in this area? If he thinks it's doing the right thing, then >>I'll bring up the discrepancy for discussion on info-pmdf. Tell him "Mike" says neither MX nor PMDF are necessarily doing anything wrong in terms of processing of Resent- headers [although I would be inclined to say that the list server in question isn't quite up to snuff], it's just a matter of interpreting a purposely ambiguous standard. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Fri, 02 Jul 1993 13:56:30 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Using multiple SMTP components Message-ID: <0096EE41.038C2700@buckie> Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 2 Jul 1993 15:11:24 GMT To: MX-List@WKUVX1.BITNET In article <0096EDA5.DF16D280.20361@ACAVAX.LYNCHBURG.EDU>, Kipp writes: >I've offered to take over a very large mailing list, and I didn't realize >the implication. I was using only one SMTP component of MX and while >processing a single queue entry, all other outgoing SMTP mail was held up. >I've now created 5 SMTP components at startup, but the potential still >exists for five mailing list messages to hold up "regular" mail in the >queue. This mailing list has hundreds of addresses and at times, the >traffic could become heavy. > >Some questions: > - How many SMTP components are practical, and what sort of > performance impact is caused by using multiple components? > (I'm running a MicroVAX 3100) MX processes the shortest entries first, so if there really is a small mail message that needs to go out ahead of the mailing lists, it will be processed first (I don't believe this is in the MX documentation, but Matt mentioned it once on MX-List). Most of performance impact would only be felt when the processes are actually sending outgoing SMTP mail. What actually goes on within the processes, if anything, while they aren't sending mail would best be described by Matt or Hunter. As to how many are practical, I'll defer to people who are running large MX mailing lists using SMTP. It really all depends on how many remote sites you're sending mail to that are 'slow' in responding (or how many fail to respond), and how often you retry failed SMTP mail [both of which will cause an outgoing SMTP thread to get tied up]. You might also want to investigate increasing the number of incoming SMTP threads from the default of 4 if a lot of people are sending your node SMTP mail. If you can isolate a specific site that has several users sending mail, you could ask the postmaster how often his SMTP mailer is forced to retry sending mail to your node. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Sun, 04 Jul 1993 09:26:16 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Resending errors to local Postmaster Date: 1 Jul 1993 13:54:35 +0400 Message-ID: <20uc8r$91s@lpuds.oea.ihep.su> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Is there any way in MX 3.3 to send copies of error messages to local Postmaster ? I mean messages like "unknown user" or "host unknown" etc. Thank you. -- Igor Mandrichenko ================================================================================ Archive-Date: Sun, 04 Jul 1993 09:26:21 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: flqu Date: 26 Jun 1993 20:43:15 GMT Message-ID: <20icd3$1k6@lpuds.oea.ihep.su> To: MX-List@WKUVX1.BITNET "David Scott Cunningham, TRIUMF, 604 222-1047" wrote: : Hello, : : So I've just finished upgrading to MX 3.3, and there's no FLQU program. : : Is this no longer supported? If not, why not; I used it a lot. There is new option of mcp que show: $ mcp que show/brief -- is equivalent to flqu show. -- Igor. ================================================================================ Archive-Date: Sun, 04 Jul 1993 10:45:16 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sun, 04 Jul 1993 10:45:01 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096EFE0.BC3CC36D.2735@WKUVX1.BITNET> Subject: RE: Resending errors to local Postmaster writes: > > Is there any way in MX 3.3 to send copies of error messages >to local Postmaster ? I mean messages like "unknown user" or >"host unknown" etc. > No, there's not. That ability is a planned feature of MX V3.4. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sun, 04 Jul 1993 13:51:04 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX and MX records Date: 4 Jul 1993 17:30:36 +0400 Message-ID: <216m1s$1m0@lpuds.oea.ihep.su> To: MX-List@WKUVX1.BITNET I have a question about the way MX processes DNS MX RR's. Suppose, we are running MX on host A.A.A and MX receives message for host B.B.B and DNS gives the following MX RR's for the host B.B.B: B.B.B MX 10 B.B.B 20 A.A.A 30 C.C.C So the message reached host with preference 20 and MX may choose between lower and higher preference. When target host B.B.B is ok, then the message will go there. But what will happen when host B.B.B is unreachable for now ? I am suspecting that the message will go to C.C.C. Right ? I am not sure but it seems to be normal way for MX to keep the message in retry queue not to send it to a host with lower preference. Is there a way to make MX keep the message ? Thank you. ================================================================================ Archive-Date: Sun, 04 Jul 1993 13:51:33 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Using multiple SMTP components Date: 3 Jul 1993 14:52:27 +0400 Message-ID: <213odb$ou3@lpuds.oea.ihep.su> To: MX-List@WKUVX1.BITNET Kipp (teague@ACAVAX.LYNCHBURG.EDU) wrote: : I've offered to take over a very large mailing list, and I didn't realize : the implication. I was using only one SMTP component of MX and while : processing a single queue entry, all other outgoing SMTP mail was held up. : I've now created 5 SMTP components at startup, but the potential still : exists for five mailing list messages to hold up "regular" mail in the : queue. This mailing list has hundreds of addresses and at times, the : traffic could become heavy. : Some questions: : - How many SMTP components are practical, and what sort of : performance impact is caused by using multiple components? : (I'm running a MicroVAX 3100) I think it depends on your computer performance, number of CPUs on your machine, performance of your network and many other factors. : - Is there any way to direct my mailing list to a dedicated SMTP : server, or in other words, is there any way to prevent my system from : simultaneously processing multiple mailing list messages while : at the same time always having one or more SMTP processes available : for handling light requests? If you have a VAXcluster or another host reachable via DECnet then you may use the following: 1. Install MX on another host that will process your mailing-list. 2. Isolate this host from main MX cluster creating serarated queue directory tree and defining MX_FLQ_NODE_NAME and MX_NODE_NAME. 3. On main MX cluster make alias like this: the-list "the-list@mlf.node" 4. Make MX path entry "mlf.node" DECnet-nsmtp/"mlf-node-decnet-name" 5. Run ROUTER, MLF and SMTP agents on isolated node. Then incoming mail to the list will be forwarded to the "specialized" node using SMTP-over-DECnet agent, leaving SMTP agent free for normal mail. And the mailing list will be isolated on the single node. If this way and/or my explanation seem to be not very simple but acceptable please feel free to mail me directly. -- Igor Mandrichneko (mandrichenko@mx.ihep.su) ================================================================================ Archive-Date: Mon, 05 Jul 1993 07:51:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 05 Jul 1993 09:45:18 -0300 (ADT) From: "Eric R. Rountree" Subject: Aliasing an address to a distribution list file. To: mx-list@WKUVX1.BITNET Reply-To: MX-List@WKUVX1.BITNET Message-ID: Content-Transfer-Encoding: 7BIT I am currently using the SMTP_ALIASES file in MULTINET to hold some distribution lists that are used by the faculty here, but it's really a pain having to make changes all the time when the users who deal with the list members on a day to day basis could be maintaining the lists themselves. What I would like to be able to do is set up a number of distribution lists as text files residing in various directories around the system so that users other than myself could maintain them. I would then just have to maintain the central database of aliases to those lists. Looking at the MX documentation, I see lots of support for LISTSERV-type lists, but I can't find anything that relates to what I describe above. Will MX do this kind of thing? If not, do you know of something that will? Thanks for any information you may have. Eric Rountree System Manager School of Business Site Academic Computing Services Dalhousie University Halifax, N.S. Canada Rountree@SBACOOP.SBA.Dal.CA ================================================================================ Archive-Date: Mon, 05 Jul 1993 09:37:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 05 Jul 1993 09:37:05 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F0A0.68E62DEC.2857@WKUVX1.BITNET> Subject: RE: Aliasing an address to a distribution list file. "Eric R. Rountree" writes: > >I am currently using the SMTP_ALIASES file in MULTINET to hold some >distribution lists that are used by the faculty here, but it's really a pain >having to make changes all the time when the users who deal with the list >members on a day to day basis could be maintaining the lists themselves. > >What I would like to be able to do is set up a number of distribution lists >as text files residing in various directories around the system so >that users other than myself could maintain them. I would then just have to >maintain the central database of aliases to those lists. > >Looking at the MX documentation, I see lots of support for LISTSERV-type >lists, but I can't find anything that relates to what I describe above. Will >MX do this kind of thing? If not, do you know of something that will? > By defining lists (using MCP DEFINE LIST), you can create real mailing lists (the "LISTSERV-type lists" you mentioned). You can specify any address as the /OWNER of the list, allowing the people who should maintain those lists to send mail to the -Request address to add and remove users. All of this is documented in the MLF guide, though it may not be real clear that *any* user can be established as a list owner (multiple users can be specified to). For example: DEFINE LIST TEST-L- /DESCRIPTION="Test list"- /OWNER=("goathunter@WKUVX1.BITNET",- "someone@SOMEWHERE.COM",- "someone-else@SOMEWHERE.ELSE.COM")- /PROTECTION=(S:RWED,O:RWED,G:RWE,W:W)- /REPLY=(LIST,NOSENDER)- /STRIP_HEADER=RECEIVED Any of the three users listed could add/remove users by sending ADD and REMOVE commands to TEST-L-Request. One thing: be sure that the addresses are specified in the same case that they arrive, otherwise MX won't make the match. For example, if someone's mail comes in as SOMEONE@SOMEWHERE.COM, then you should specify all caps. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Mon, 05 Jul 1993 09:46:56 CDT Sender: list-mgr@WKUVX1.BITNET From: daveh@vax.oxford.ac.uk Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Using multiple SMTP components Message-ID: <1993Jul5.141738.15099@vax.oxford.ac.uk> Date: 5 Jul 93 14:17:38 BST To: MX-List@WKUVX1.BITNET In article <0096EE41.038C2700@buckie>, dwing@uh01.colorado.edu (Dan Wing) writes: > In article <0096EDA5.DF16D280.20361@ACAVAX.LYNCHBURG.EDU>, Kipp > writes: > > > MX processes the shortest entries first, so if there really is a small > mail message that needs to go out ahead of the mailing lists, it will > be processed first (I don't believe this is in the MX documentation, but > Matt mentioned it once on MX-List). > Does MX really process the smallest entry first? Dave -- David Hastings | "The technical axiom that nothing is VAX Systems Programmer | impossible sinisterly conditions one to Oxford University Computing Services| the pitfall corollary that nothing is daveh@vax.oxford.ac.uk | ridiculous" ================================================================================ Archive-Date: Mon, 05 Jul 1993 09:47:06 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: vms mail -> unix mail Message-ID: Date: Sun, 27 Jun 1993 15:28:44 GMT To: MX-List@WKUVX1.BITNET In <1vqraq$esi@umd5.umd.edu> bleau@umdsp.umd.edu writes: >In article <131607@netnews.upenn.edu>, wang@anvil.wharton.upenn.edu (jia wang) writes: >> >>Hello, all the unix and vms experts out there, >> >>I have a vms-unix mail question which needs your help. I would like >>to transfer all the files under the [.mail] directory on a VAX >>machine, which includes all *.mai files, to a unix machine. And is >>it possible to access these mail messages from unix with all the >>folder information preserved? I was told that someone has done >>that successfully. I understand that some conversion or programming >>could be involved, and will appreciate any hint. >You should be able to do so, but as you noted above, it'll be a fair amount of >programming work. The file mail.mai is an indexed file, and it has pointers to >Another, perhaps less clean, way of transferring the messages is to log onto >the vms system, get into the mail utility, and do a dir/folder. Now, for each >folder, do a > select folder-name > extract/all folder-name.list There's been two programs posted recently that did this; one took the extracted text files and put them in something that the "mh" mailer on Unix could read. Unfortunately, that was the ONLY mailer that could read it, as far as I know, but at least it kept the folder info... The other one took the indexed .MAI files and made standard Unix mbox format files, one file per folder, out of it, but the headers were a little messy IMHO... I finished a C program last night that'll make one mbox file from a single extracted text file (so it dosen't handle folders exactly), and do some header cleanup while it's at it. It works well enough that I can use Mush on my NeXT to read my old VMS mail... and since it's in C, it'll run on either VMS or Unix, take your pick. I'll post it once I make sure it really does work like I want, but in the meantime, if you want it, feel free to mail me... I've seen a LOT of requests for this kinda thing. -- Mike Andrews root@fragile.termfrost.org [NeXTmail OK] kramer@wittenberg.edu (school) "This guy's pretty bizarre, Gus." kramer@mik.uky.edu (hometown) -- Primus ================================================================================ Archive-Date: Mon, 05 Jul 1993 09:50:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 05 Jul 1993 09:50:06 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F0A2.3A85C8A7.2875@WKUVX1.BITNET> Subject: Re: Using multiple SMTP components daveh@vax.oxford.ac.uk writes: > >In article <0096EE41.038C2700@buckie>, dwing@uh01.colorado.edu (Dan Wing) > writes: >> >> MX processes the shortest entries first, so if there really is a small >> mail message that needs to go out ahead of the mailing lists, it will >> be processed first (I don't believe this is in the MX documentation, but >> Matt mentioned it once on MX-List). >> >Does MX really process the smallest entry first? > Yes. The processing of all READY messages is based on size, with smallest handled first. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Mon, 05 Jul 1993 10:17:22 CDT Sender: list-mgr@WKUVX1.BITNET Reply-To: MX-List@WKUVX1.BITNET Date: Sat, 03 Jul 1993 21:43:17 MDT From: I Hate When That Happens To: MX-List@WKUVX1.BITNET Message-ID: <0096EF73.87788B20.26358@CEDAR.ATMEL.COM> Subject: MAILSHR patch behavior for VMS V5.5-2 I am currently running MX V3.1C. I have received and installed the mailshr patch for VMS V5.5-2 when I did my VMS upgrade this weekend. I had been running the previous mailshr patch with VMS V5.5. With the previous version of the mailshr patch I could send a message to user@node (when sending to a node in the same domain) without using the MX% prefix (of course). However, after my upgrade and subsequent patch to the mailshr patch, I can no longer just send to user@node I must send as user@host.mycompany.com. It doesn't appear that it is figuring out that I need to use the MX mail transport, because if I tell it up front that I am using the MX transport it works fine. With this in mind a rewrite rule would not seem appropriate since the send request never gets to MX. What do I need to do to get back to the previously desirable behavior? By the way I have the exec system-wide logical MAIL$SYSTEM_FLAGS set to 7. I have also tried values 0-6 and deassigned it completely with no luck. I figure that this should not be relevent since this logical is used by the VMS mail transport. MAIL> s To: jpsmith@taos %MAIL-E-LOGLINK, error creating network link to node TAOS -SYSTEM-F-NOSUCHNODE, remote node is unknown MAIL> MAIL> s To: jpsmith@taos.atmel.com CC: Subj: This works fine ... MAIL> s To: MX%"jpsmith@taos" CC: Subj: This also works fine ... ***************************************************************************** * Jody Smith * * jpsmith@atmel.com * * * * ATMEL Corporation * * 1150 E. Cheyenne Mtn Blvd * * Colorado Springs, Colorado 80906 * ***************************************************************************** ***************************************************************************** * Jody Smith * * jpsmith@atmel.com * * * * ATMEL Corporation * * 1150 E. Cheyenne Mtn Blvd * * Colorado Springs, Colorado 80906 * ***************************************************************************** ================================================================================ Archive-Date: Mon, 05 Jul 1993 11:23:51 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: MX and MX records Message-ID: <1993Jul5.160145.24614@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Mon, 5 Jul 1993 16:01:45 GMT To: MX-List@WKUVX1.BITNET In article <216m1s$1m0@lpuds.oea.ihep.su>, igor@lpuds.oea.ihep.su (Igor Mandrichenko) writes: > I have a question about the way MX processes DNS MX RR's. >Suppose, we are running MX on host A.A.A and MX receives message for >host B.B.B and DNS gives the following MX RR's for the host B.B.B: > > B.B.B MX 10 B.B.B > 20 A.A.A > 30 C.C.C > > So the message reached host with preference 20 and MX may choose >between lower and higher preference. When target host B.B.B is ok, then >the message will go there. But what will happen when host B.B.B is >unreachable for now ? > > I am suspecting that the message will go to C.C.C. Right ? You are correct. MX currently behaves incorrectly and will forward the message to C.C.C if B.B.B is not reachable. This is a long-standing problem in MX which I just recently brought to Hunter's attention. MX _should_ throw out all MX RR's with a preference >= the preference of the MX RR pointing at the local host. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Tue, 06 Jul 1993 06:50:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 06 Jul 1993 06:50:27 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F152.4C536683.3117@WKUVX1.BITNET> Subject: RE: MAILSHR patch behavior for VMS V5.5-2 I Hate When That Happens writes: > >I am currently running MX V3.1C. I have received and installed the mailshr >patch for VMS V5.5-2 when I did my VMS upgrade this weekend. I had been >running the previous mailshr patch with VMS V5.5. With the previous version of >the mailshr patch I could send a message to user@node (when sending to a node >in the same domain) without using the MX% prefix (of course). However, after >my upgrade and subsequent patch to the mailshr patch, I can no longer just >send to user@node I must send as user@host.mycompany.com. [...] >MAIL> s >To: jpsmith@taos >%MAIL-E-LOGLINK, error creating network link to node TAOS >-SYSTEM-F-NOSUCHNODE, remote node is unknown > The patch is automatically converting that address to TAOS::JPSMITH. There are instructions in the patch for enabling/disabling this. Apparently the last person I got the patch from enabled that feature. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 06 Jul 1993 10:47:03 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 06 Jul 1993 10:37:52 EDT From: kenm@adhe.arknet.edu Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096F172.11775F40.372@adhe.arknet.edu> Subject: All-In-1 rewrite rule Arkansas Department of Higher Education I N T E R O F F I C E M E M O R A N D U M Date: 07-06-1993 10:35am GMT From: KEN MCCOY KENM Dept: Information Services Tel No: 501-324-9300 FAX 501-324-9308 TO: Remote Addressee ( _MX-List@WKUVX1.BITNET ) Subject: All-In-1 rewrite rule Hello All-In-1 fans, How do you specify a rewrite rule in MX so that when the message is received into All-In-1 the return address (FROM: line) would look like _MX-List@WKUVX1.BITNET instead of MX%"MX-ListWKUVX1.BITNET". I've included the header that I see in All-In-1? Thanks in advance!!! Ken McCoy Arkansas Dept. of Higher Ed. ====================================================================== ====================================================================== Arkansas Department of Higher Education I N T E R O F F I C E M E M O R A N D U M Date: 06-30-1993 06:22pm GMT From: MX%"MX-List@WKUVX1.BITNET" MX%"MX-List@WKUVX1.BITNET"@MRGATE@SPEEDY Dept: Tel No: TO: kenm@A1 Subject: Rewrite Rules Return-Path: <@ULKYVM.LOUISVILLE.EDU:list-mgr@WKUVX1.BITNET> Received: from ULKYVM.LOUISVILLE.EDU by speedy.adhe.arknet.edu (MX V3.3 VAX) with SMTP; Wed, 30 Jun 1993 18:18:01 EDT Received: from ULKYVM.LOUISVILLE.EDU by ULKYVM.LOUISVILLE.EDU (IBM VM SMTP V2R1) with BSMTP id 5681; Wed, 30 Jun 93 19:18:34 EDT Received: from WKUVX1.BITNET by ULKYVM.LOUISVILLE.EDU (Mailer R2.08 R208004) with BSMTP id 7512; Wed, 30 Jun 93 19:18:32 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: list-mgr@WKUVX1.BITNET Sender: list-mgr@WKUVX1.BITNET Date: Thu, 01 Jul 1993 01:13:12 +0100 From: Per Hogstedt Reply-To: MX-List@WKUVX1.BITNET Subject: Rewrite Rules To: MX-List@WKUVX1.BITNET Message-ID: <0096ED35.5AEC8CE0.9960@plab.se> ================================================================================ Archive-Date: Tue, 06 Jul 1993 16:15:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 06 Jul 1993 17:08:41 EDT From: Dan Wheeler Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET CC: manager@LEMOYNE.BITNET Message-ID: <0096F1A8.A9FC91A0.19385@LEMOYNE> Subject: Mail to DISUSER accounts bounced? I'm chasing some weirdness here since upgrading to MX 3.3 and have a question: Does MX reject mail to accounts which have been flagged DISUSER? I have been using BULLETIN to provide public access to various network mailing lists. BULLETIN feeds mail to selected folders directly from specific accounts, which must be DISUSERed. I have been using this feature for some time and it broke recently. I just discovered the apparent fact that MX rejects mail to accounts which have been so flagged. If so, is there a way to change this? (This is not urgent, since NODISUSERed accounts work after initial BULLETIN configuration). As I look for a sample BSMTP error message (below) I found that I also have many other incoming messages in an error state for some unknown (to me) reasons. Are there other factors (such as exceeding disk quota) that will return a "No such local user" error (as indicated in the attached local message to Postmaster). --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) MANAGER@LEMOYNE.BITNET ------------------------------------------------------------------------------ Sample *.error_msg follows: ================================================== From: Message Exchange Jnet Interface To: MAILER@UBVM Date: Tue, 06 Jul 1993 17:00:41 EDT Subject: Error in BSMTP message proccessing BSMTP transcript: 220 LEMOYNE.BITNET MX MX V3.3 VAX SMTP server ready at Tue, 06 Jul 1993 17:00:41 EDT 050 HELO UBVM.CC.BUFFALO.EDU 250 Hello, UBVM.CC.BUFFALO.EDU 050 MAIL FROM:<@UBVM.CC.BUFFALO.EDU:owner-diet@UBVM.CC.BUFFALO.EDU> 250 MAIL command accepted. 050 RCPT TO: 250 Recipient okay (at least in form) 050 DATA 354 Start mail input; end with . 050 Received: from UBVM.CC.BUFFALO.EDU (NJE origin LISTSERV@UBVM) by 050 UBVM.CC.BUFFALO.EDU (LMail V1.1d/1.7f) with BSMTP id 0872; Tue, 050 6 Jul 1993 16:52:46 -0400 050 Date: Tue, 6 Jul 1993 16:52:41 -0400 050 Reply-To: Support and Discussion of Weight Loss 050 Sender: Support and Discussion of Weight Loss 050 From: Jill Baldwin 050 Subject: Latest Labor Day Challenge Details 050 To: Multiple recipients of list DIET ... 050 Greenville, NC 050 (919)757-6985 050 . 250 Message received and queued. 050 QUIT 221 LEMOYNE.BITNET Closing transmission channel =========================================================================== Sample locally received error message: =========================================================================== From: MX%"Postmaster@lemoyne" 6-JUL-1993 16:38:13.13 To: MANAGER CC: Subj: LOCAL delivery error Return-Path: <> Date: Tue, 06 Jul 1993 16:38:03 EDT From: Local delivery agent To: Subject: LOCAL delivery error X-Report-Type: Nondelivery; boundary="> Error description:" Note: this message was generated automatically. An error was detected while processing the enclosed message. A list of the affected recipients follows. This list is in a special format that allows software like LISTSERV to automatically take action on incorrect addresses; you can safely ignore the numeric codes. --> Error description: Error-For: food@lemoyne Error-Code: 3 Error-Text: No such local user Error-End: 1 error detected ------------------------------ Rejected message ------------------------------ Received: by LEMOYNE (MX V3.3 VAX) id 19349; Tue, 06 Jul 1993 16:38:00 EDT Date: Tue, 06 Jul 1993 16:37:58 EDT From: Dan Wheeler To: infoibm@lemoyne.bitnet, election@lemoyne.bitnet, food@lemoyne.bitnet CC: manager@lemoyne Message-ID: <0096F1A4.5F961400.19349@LEMOYNE> Subject: test test message ================================================================================ Archive-Date: Tue, 06 Jul 1993 16:31:54 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 06 Jul 1993 16:31:27 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F1A3.76538E58.3313@WKUVX1.BITNET> Subject: RE: Mail to DISUSER accounts bounced? Dan Wheeler writes: > >I'm chasing some weirdness here since upgrading to MX 3.3 and have a >question: > >Does MX reject mail to accounts which have been flagged DISUSER? > Yes, it does. >I have been using BULLETIN to provide public access to various network >mailing lists. BULLETIN feeds mail to selected folders directly from >specific accounts, which must be DISUSERed. I have been using this >feature for some time and it broke recently. I just discovered the >apparent fact that MX rejects mail to accounts which have been so >flagged. If so, is there a way to change this? (This is not urgent, >since NODISUSERed accounts work after initial BULLETIN configuration). > No, there's no way to change it, though I can look into making it optional in the next release. >As I look for a sample BSMTP error message (below) I found that I also >have many other incoming messages in an error state for some unknown (to >me) reasons. Are there other factors (such as exceeding disk quota) that >will return a "No such local user" error (as indicated in the attached >local message to Postmaster). > Just non-existent and DISUSERed (which is non-existent, if it can't be used). That was the thinking behind that. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 06 Jul 1993 22:27:32 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 06 Jul 1993 22:43:39 EDT From: Dan Wheeler Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST@WKUVX1.BITNET CC: manager@LEMOYNE.BITNET Message-ID: <0096F1D7.759BB600.20315@LEMOYNE> Subject: Queue *.ERROR_MSG files I'm a bit confused about the use of the files in the MX queue directories names *.ERROR_MSG. In the past I learned to ignore them within our BITNet-only world, assuming they were created for each BSMTP transaction and actually sent only when an error occurred (this because the addressee of most of our *.ERROR_MSG files wasn't seeing them, although now I'm not sure whether this was because my JNET BSMTP reply was disabled). How far off base am I? Chasing another problem I encountered these files again and they seemed to be there for properly received and rejected messages. Should I be R'ingTFM somewhere? --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) MANAGER@LEMOYNE.BITNET ------------------------------------------------------------------------------ ================================================================================ Archive-Date: Tue, 06 Jul 1993 22:27:59 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: a problem with MCP>SHOW QUEUE command Date: 6 Jul 1993 22:16:38 GMT Message-ID: <21ctk6INNlju@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096F195.D75FCF80.25779@VMSVAX.SIMMONS.EDU>, lsoltzberg@VMSVAX.SIMMONS.EDU writes: =We are running MX 3.1 with CMU-TEK 6.5 and have just upgraded from a =MicroVAX II to a VAX4100. MX seems to be running OK, except that when =I run MCP and do an MCP> SHOW QUEUE command, I get an error message =that says "access violation" and then a get a small dump with info about =the PC and so forth. =Can someone shed light on this problem? =Thanks. It may be that your queue file is corrupted. Of course, nobody's going to be able to say anything at all definitive unless you provide some obviously unimportant information like the reason mask, the virtual address, the PC, the PSL, and the calling sequence displayed by the stack dump. I mean, VMS obviously only displayed all that information to annoy you; it's not as if it might be useful for figuring out what's going on, right? -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Tue, 06 Jul 1993 23:03:58 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 06 Jul 1993 23:02:02 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F1DA.06C836B0.3415@WKUVX1.BITNET> Subject: RE: Queue *.ERROR_MSG files Dan Wheeler writes: > >I'm a bit confused about the use of the files in the MX queue >directories names *.ERROR_MSG. In the past I learned to ignore them >within our BITNet-only world, assuming they were created for each BSMTP >transaction and actually sent only when an error occurred (this because >the addressee of most of our *.ERROR_MSG files wasn't seeing them, >although now I'm not sure whether this was because my JNET BSMTP reply >was disabled). > That is correct---when MX processes a BSMTP file, it creates the .ERROR_MSG *in case* there's an error. If there's no error, the file is ignored (and eventually deleted when that entry is purged). >How far off base am I? Chasing another problem I encountered these files >again and they seemed to be there for properly received and rejected >messages. Should I be R'ingTFM somewhere? > No, there's nothing wrong. The manual should probably mention that that's what they are, if it doesn't already. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 06 Jul 1993 23:16:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 06 Jul 1993 23:05:05 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F1DA.73C1F323.3419@WKUVX1.BITNET> Subject: Re: a problem with MCP>SHOW QUEUE command writes: > >In article <0096F195.D75FCF80.25779@VMSVAX.SIMMONS.EDU>, > lsoltzberg@VMSVAX.SIMMONS.EDU writes: >=We are running MX 3.1 with CMU-TEK 6.5 and have just upgraded from a >=MicroVAX II to a VAX4100. MX seems to be running OK, except that when >=I run MCP and do an MCP> SHOW QUEUE command, I get an error message >=that says "access violation" and then a get a small dump with info about >=the PC and so forth. >=Can someone shed light on this problem? >=Thanks. > >It may be that your queue file is corrupted. Of course, nobody's going to be >able to say anything at all definitive unless you provide some obviously >unimportant information like the reason mask, the virtual address, the PC, the >PSL, and the calling sequence displayed by the stack dump. I mean, VMS >obviously only displayed all that information to annoy you; it's not as if it >might be useful for figuring out what's going on, right? There is an apparent conflict that shows up every now and then. I've been unable to dupicate it consistently, making it a real pain to fix, but it appears that there are times when MCP is gathering info for a queue entry and, while it's doing so, the MX Router purges the entry, leaving MCP with partial data that it doesn't handle correctly. It should not happen every time---if it does, then Carl is right---you may have a corrupted queue file, or at least a corrupted entry. MCP QUEUE CANCEL on the entry that causes the accvio may take care of it too. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 07 Jul 1993 01:47:49 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 06 Jul 1993 23:24:07 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET CC: rharwood@Data.Basix.COM Message-ID: <0096F1DD.1CD843C0.446@Data.Basix.COM> Subject: Replying to DECnet->UCX->MX mail Here's a rather strange thing (to me!) I found. Situation: Someone on a college VAX sent a message to my account on another VAX, which in turn forwards messages to me here at Data.Basix.COM. When I REPLYd to his message, the (intermediate) VAX sent the reply back as undeliverable. Originator->(DECnet)->Intermediate->(SMTP)->(MX) Here this was okay, but Here (MX) ->(SMTP)->Intermediate was returned. My Configuration: (Data.Basix.COM) MicroVAX II, MX 3.2, MultiNet 3.2A, VMS 5.5, on a SLIP connection. I have done a SET TRANSPORT MX% on my userID. Intermediate Configuration: (East.Pima.EDU or EAST::) VAX 4500 running UCX (version 2.something) with no special mail systems in place. Originating Configuration: (PimaCC.Pima.EDU or PIMACC::) Original message sent via DECnet mail, though they do have MultiNet. Here's the header from the originating mail: ================================================== From: MX%"'PIMACC::RELLISON'@east.pima.edu" 6-JUL-1993 13:40:41.79 To: RHARWOOD CC: Subj: [...] Return-Path: <"PIMACC::RELLISON"@east.pima.edu> Received: from east.pima.edu by Basix.COM (MX V3.2) with SMTP; Tue, 06 Jul 1993 13:40:26 -0700 Date: Tue, 6 Jul 1993 13:14:46 -0700 From: "PIMACC::RELLISON"@east.pima.edu (Mr. Classic Chevrolet) To: rharwood@data.basix.com Subject: [...] X-VMS-To: RHARWOOD ================================================== Here's what I got back from East.Pima.EDU's UCX SMTP: ================================================== From: MX%"UCX_SMTP@east.pima.edu" 6-JUL-1993 14:43:53.75 To: RHARWOOD CC: Subj: Return-Path: Received: from east.pima.edu by Basix.COM (MX V3.2) with SMTP; Tue, 06 Jul 1993 14:43:39 -0700 ---- Transcript of session follows ---- %UCX-E-SMTP_SNDERROR, Error detected while sending mail to "PIMACC::RELLISON"@east.pima.edu -RMS-E-RNF, record not found ---- Recipients of this delivery ---- "PIMACC::RELLISON"@east.pima.edu (bounced) ---- Unsent message follows ---- Received: by east.pima.edu (UCX V2.0) Tue, 6 Jul 1993 14:43:31 -0700 Received: by Data.Basix.COM (MX V3.2) id 421; Tue, 06 Jul 1993 14:42:53 -0700 Date: Tue, 06 Jul 1993 14:42:38 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" To: "PIMACC::RELLISON"@east.pima.edu CC: rharwood@Data.Basix.COM Message-ID: <0096F194.4325C140.421@Data.Basix.COM> Subject: RE: [...] ================================================== If I remember correctly, prior to installing MX, the return address had "quoted" single-quotes similar to \'PIMACC::RELLISON\'@east.pima.edu , and I have REPLYd to his messages many times with success. Thanks for any helpful hints. I promise to load MX 3.3 soon! ;( Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal Internet: | rharwood@Data.Basix.COM | rharwood@east.pima.edu ** For info on Data Basix, send EMail with no subject to Info@Data.Basix.COM ** ================================================================================ Archive-Date: Wed, 07 Jul 1993 08:26:15 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 07 Jul 1993 08:45:47 EDT From: "Brian Tillman, Smiths Industries, VAX Support, x8425" Reply-To: MX-List@WKUVX1.BITNET To: WKUVX1.BITNET!MX-list@esseye.si.com Message-ID: <0096F22B.937C22A0.27158@swdev.si.com> Subject: Re: a problem with MCP>SHOW QUEUE command In article <0096F195.D75FCF80.25779@VMSVAX.SIMMONS.EDU>, lsoltzberg@VMSVAX.SIMMONS.EDU writes: =We are running MX 3.1 with CMU-TEK 6.5 and have just upgraded from a =MicroVAX II to a VAX4100. MX seems to be running OK, except that when =I run MCP and do an MCP> SHOW QUEUE command, I get an error message =that says "access violation" and then a get a small dump with info about =the PC and so forth. =Can someone shed light on this problem? =Thanks. This happens periodically with me, too. I've told Hunter (and this group) about it in the past. As far as I can determine, it happens when the queue file has been locked by one of the other MX processes. Typically, if one tries again in a few minutes, everything's OK. At least, that seems to be the case for me. -- Brian Tillman tillman_brian@si.com ================================================================================ Archive-Date: Wed, 07 Jul 1993 17:31:45 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Mail to DISUSER accounts bounced? Message-ID: <1993Jul7.214158.14888@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 7 Jul 1993 21:41:58 GMT To: MX-List@WKUVX1.BITNET In article <0096F1A8.A9FC91A0.19385@LEMOYNE>, Dan Wheeler writes: >I'm chasing some weirdness here since upgrading to MX 3.3 and have a >question: > >Does MX reject mail to accounts which have been flagged DISUSER? Yes; MX V3.3 doesn't send mail to accounts which are DisUsered. See [.LOCAL]LOCAL_USER.B32. This is an enhancement made to V3.3 (it isn't in V3.2). >I have been using BULLETIN to provide public access to various network >mailing lists. BULLETIN feeds mail to selected folders directly from >specific accounts, which must be DISUSERed. I have been using this >feature for some time and it broke recently. I just discovered the >apparent fact that MX rejects mail to accounts which have been so >flagged. If so, is there a way to change this? (This is not urgent, >since NODISUSERed accounts work after initial BULLETIN configuration). > >As I look for a sample BSMTP error message (below) I found that I also >have many other incoming messages in an error state for some unknown (to >me) reasons. Are there other factors (such as exceeding disk quota) that >will return a "No such local user" error (as indicated in the attached >local message to Postmaster). Unfortunately, several events return "no such local user", including no such local user, as well as a user with DisUser or DisMail set. The MX Local agent has EXQUOTA privilege enabled, so I don't think disk quota problems can prevent delivery of Email through MX. -d -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Thu, 08 Jul 1993 01:55:14 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: Mail to DISUSER accounts bounced? Date: 8 Jul 1993 05:30:29 GMT Message-ID: <21gbdlINN9k2@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096F1A3.76538E58.3313@WKUVX1.BITNET>, "Hunter Goatley, WKU" writes: =>Does MX reject mail to accounts which have been flagged DISUSER? => =Yes, it does. = =>As I look for a sample BSMTP error message (below) I found that I also =>have many other incoming messages in an error state for some unknown (to =>me) reasons. Are there other factors (such as exceeding disk quota) that =>will return a "No such local user" error (as indicated in the attached =>local message to Postmaster). => =Just non-existent and DISUSERed (which is non-existent, if it can't be =used). That was the thinking behind that. At least under VMS v5.4-2, VMS MAIL will gladly deliver mail to DISUSERed accounts. It would be nice if MX were to default to the same behavior as VMS mail. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Fri, 09 Jul 1993 01:44:31 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 09 Jul 1993 17:19:50 NZST From: "Andrew Carman, IGNS" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F405.B8245100.521@m2g.gns.cri.nz> Subject: RE: Mail to DISUSER accounts bounced? >> >>Does MX reject mail to accounts which have been flagged DISUSER? >> >Yes, it does. > >>I have been using BULLETIN to provide public access to various network >>mailing lists. BULLETIN feeds mail to selected folders directly from >>specific accounts, which must be DISUSERed. I have been using this >>feature for some time and it broke recently. I just discovered the >>apparent fact that MX rejects mail to accounts which have been so >>flagged. If so, is there a way to change this? (This is not urgent, >>since NODISUSERed accounts work after initial BULLETIN configuration). >> >No, there's no way to change it, though I can look into making it >optional in the next release. > Hunter - I for one would like the option. On our system anyone could (if they so wished) render another user's account DISUSER simply by attempting to login several times, as that user, with an incorrect password. If, as system manager, I need to disable an account then I set both the DISUSER and DISMAIL flags on that account. Regards, Andrew Carman Institute of Geological & Nuclear Sciences phone +64 4 474 3671 Kelburn Centre, 32 Salamanca Rd fax: +64 4 471 0977 PO Box 1320, Wellington, New Zealand. ================================================================================ Archive-Date: Fri, 09 Jul 1993 05:37:12 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 9 Jul 93 06:09:22 -0400 Message-ID: <9307091009.AA00476@genrad.com> From: Reply-To: MX-List@WKUVX1.BITNET X-MX-Warning: Warning -- Invalid "To" header. To: "mx-list%wkuvx1.bitnet@ukcc.uky.edu" Subject: SMTP protocol errors? I am repeated getting protocol errors when sending messages from a MicroVAX 3100 (VMS 5.5-2, CMU-OpenVMS-IP 6.6-5, MX 3.3) to either of two clusters; cluster 1 is a VAX 4000-300, Vaxserver 3400, MicroVAX II plus many workstations (which don't run UCX) running VMS 5.5-2, UCX 1.3A, MX 3.3; the other is a VAXserver 4000-200, MicroVAX II and many workstations, same software. The debug logs show ... 8-JUL-1993 16:36:37.96 Processing queue entry number 4573 on node CD3101 8-JUL-1993 16:36:38.26 Recipient: , route=CDCLU1 8-JUL-1993 16:36:38.26 SMTP_SEND: looking up host name CDCLU1 8-JUL-1993 16:36:38.29 SMTP_SEND: Attempting to start session with CDCLU1 [128.1.0.41] 8-JUL-1993 16:36:38.73 SMTP_SEND: Connected 8-JUL-1993 16:36:44.36 SMTP_SEND: Rcvd: 8-JUL-1993 16:36:44.56 SMTP send failed, sts=0C27804A, sts2=0C278042 8-JUL-1993 16:36:44.56 Recipient status=0C27804A for 8-JUL-1993 16:36:45.21 1 rcpts need retry, next try 8-JUL-1993 17:06:45.21 8-JUL-1993 16:36:45.24 *** End of processing pass *** The problem seem to be cleared (for a while) by TELNETting to port 25 on each cluster, hitting return and getting 2 blank lines, the MX banner and a request to type HELO, and then typing QUIT. Has anyone else seen this problem and can suggest a permanent fix? I have wondered whether it's an effect of UCX cluster aliasing and if it would be fixed by routing all the cluster directed messages to a specific node in the cluster. Thoughts? -------------------------------------------------------------------------------- Name :Derek Dongray, Systems Manager, GenRad Ltd. Phone :061 486 1511 InterNet : Dongray@GenRad.com UKnet : Derek.Dongray@GenRad.co.uk PSS : 234261600119::Dongray CompuServe : 70374,2745 Address : Monmouth House, Monmouth Road, Cheadle Hulme, Cheshire, SK8 7AY, UK. ================================================================================ Archive-Date: Fri, 09 Jul 1993 07:02:46 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Zero sized entries in MCP queue Message-ID: <1993Jul9.104416.8136@aragorn.unibe.ch> Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 9 Jul 1993 10:44:16 GMT To: MX-List@WKUVX1.BITNET Some time ago I asked about removing zero sized entries from the MCP queue. As this is not possible with wildcards, I wrote a little procedure. Perhaps somebody else can use it. Martin --- CUT --- $ $! Remove zero size entries from MCP queue $! Tested with MX 3.3 $! Eg / 9.7.1993 $ $ mcp queue show /output=sys$scratch:mcp.lis $ open /write mcpcmd sys$scratch:mcpcmd.com $ tmp := write mcpcmd $ tmp "$ mcp" $ open /read mcplis sys$scratch:mcp.lis $ read /error=done /end=done mcplis string $ read /error=done /end=done mcplis string $ loop: read /error=done /end=done mcplis string $ string = f$edit(string,"trim,compress") $ number = f$element(0," ",string) $ size = f$element(2," ",string) $ if size .eqs. "0" $ then $ tmp "queue cancel ''number'" $ endif $ goto loop $ done: close mcplis $ tmp "queue purge" $ tmp "$ exit" $ close mcpcmd $ @sys$scratch:mcpcmd.com $ delete sys$scratch:mcpcmd.com;* $ delete sys$scratch:mcp.lis;* $ exit --- CUT --- ******************************************************************************* Martin Egger, Ph.D., Computing Services - Head of System/User Support Group University of Bern, P.O. Box, Laenggassstrasse 51, CH-3012 Bern, Switzerland Phone: ++41 (0)31 65 38 45, Fax: ++41 (0)31 65 38 65, Telex: 912 643 pibe ch RFC: egger@id.unibe.ch, X.400: S=egger;OU=id;O=unibe;P=switch;A=arcom;C=ch; HEPNET/SPAN: 20579::49202::egger, DECnet (Switzerland): 49202::egger ******************************************************************************* ================================================================================ Archive-Date: Fri, 09 Jul 1993 10:03:51 CDT Sender: list-mgr@WKUVX1.BITNET From: robert@cpvax.cpses.tu.com Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Mail to DISUSER accounts bounced? Message-ID: <1993Jul9.084555.465@cpvax.cpses.tu.com> Date: 9 Jul 93 08:45:55 CST To: MX-List@WKUVX1.BITNET In article <0096F405.B8245100.521@m2g.gns.cri.nz>, "Andrew Carman, IGNS" writes: >>> >>>Does MX reject mail to accounts which have been flagged DISUSER? >>> >>Yes, it does. >> > Hunter - I for one would like the option. I'd second that. Another item for the wish list is bouncing mail when the current date is beyond /EXPIRED and no forwarding address is sent. We terminate employees (he he) by setting /EXPIRED to their termination date. Every once in a while we pull up a list of all expired accounts and pull them off the system. DISUSER is only used to temporarily disable an account. -- ------------------------------------------------------------------------- Robert Eden 817-897-0491 Glen Rose, TX Comanche Peak Steam Electric Station robert@cpvax.cpses.tu.com ^^^^^^^^^^^^^^^^^^^^^ politicese for a nuke plant ------------------------------------------------------------------------- ================================================================================ Archive-Date: Fri, 09 Jul 1993 15:30:39 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 09 Jul 1993 14:26:10 EDT From: fraser_h@qis.dofasco.ca Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096F3ED.755371C0.32065@qis.dofasco.ca> Subject: Name translations I've been following the discussions concerning forwarding messages from MX to Allin1. We've had little success solving the problem in a transparent way (ie. I'd like to be able to directly reply to an incoming message regardless of the source). Rewrite rules to add the mrgate path to the destination provided a crude solution. We've been slowly migrating people to MSMail using Microsoft's SMTP gateway, which works terrific. Slowly but surely, people on Allin1 are being moved over, so I'm reluctant to spend much more time on the MX<->Allin1 problem. But the move has introduced a new problem. Many of the people here have published their Internet address on their business cards. As they move from one network node to another, I have to find some way of forwarding their mail to the new address. For example, I'm at fraser_h@eis.dofasco.ca. That site no longer exists. I've since moved to fraser_h@qis.dofasco.ca. Since eis.dofasco.ca physically no longer exists, I can't set my forwarding address there to qis.dofasco.ca. I'd like to set up a directory service in MX to translate fraser_h@dofasco.ca into fraser_h@qis.dofasco.ca, but not everybody's on qis.dofasco.ca either. The contribs directory in MX has code to translate host names and nicknames. Nicknames sound close, but it's only designed to modify the name part of an address, and is only called when sending a message from VMS mail (ie. it isn't used to translate messages coming into MX from outside sources). The only apparent way to translate an entire address is to do a rewrite rule. I've got about 3500 of these to do, and MX's rewrite rule managing isn't the friendliest to use. So in a nutshell, has anybody got a solution for directory lookups to translate an 'alias' into a complete mail address. ================================================================================ Archive-Date: Fri, 09 Jul 1993 20:32:33 CDT Sender: list-mgr@WKUVX1.BITNET From: system@dmc.com Reply-To: MX-List@WKUVX1.BITNET Subject: Bad From addresses... Message-ID: <1993Jul9.170653.1838@dmc.com> Date: 9 Jul 93 17:06:53 EDT To: MX-List%WKUVX1.BITNET@ricevm1.rice.edu I just got the following report from a client: -------------------------------------------------------------------------------- From: ABYSS::"alex!nedspc!ned" 6-JUL-1993 18:57:25.80 To: alex!nedspc!ned CC: Subj: Returned mail: Remote protocol error ----- Transcript of session follows ----- While talking to HULK.DMC.COM: >>> MAIL From: <<< 501 Invalid address: 554 herbison.dmc.com!bj... Remote protocol error ----- Unsent message follows ----- Received: by decvax.dec.com (5.65/DEC-ULTRIX-8/19/92) id AA14464; Tue, 22 Jun 1993 16:56:25 -0400 Received: by alex.hollis.nh.us (smail2.5.3-coh) id AA11213; 22 Jun 93 20:42:13 GMT (Tue) Received: by nedspc.UUCP (UUPC/extended 1.11v); Tue, 22 Jun 1993 13:59:49 EDT Date: Tue, 22 Jun 1993 13:59:47 EDT From: "Ned Santee" Message-Id: <2c274895.nedspc@nedspc.UUCP> To: bj@herbison.dmc.com Subject: Testing mail to "bj@herbison.dmc.com" -------------------------------------------------------------------------------- Why is the MX SMTP server complaining about the FROM address and rejecting it? If it's right, how do I fix this. MCP Rewrite rules apply to the To field. Dick Munroe ================================================================================ Archive-Date: Fri, 09 Jul 1993 20:34:34 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Bad From addresses... Message-ID: <1993Jul10.002742.16371@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Sat, 10 Jul 1993 00:27:42 GMT To: MX-List@WKUVX1.BITNET In article <1993Jul9.170653.1838@dmc.com>, system@dmc.com writes: >While talking to HULK.DMC.COM: >>>> MAIL From: ><<< 501 Invalid address: >554 herbison.dmc.com!bj... Remote protocol error [...] >Why is the MX SMTP server complaining about the FROM address and rejecting it? Because it's not in RFC821 format. The sender should fix his/her mailer to emit properly formatted addresses. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Fri, 09 Jul 1993 23:27:48 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 09 Jul 1993 21:21:39 PDT From: "W. Todd Wipke" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096F427.801A2F60.7421@SECS.UCSC.EDU> Subject: Re: mail to DISUSER accts I also use BULLETIN with many disusered accounts. Since DEC provides DISMAIL, I suggest you use that flag, rather than the DISUSER flag for bouncing mail. The two flags have two different meanings, one of them specifically pertains to mail, that is the one that should signify don't deliver mail. DISUSER is used for other purposes, primarily security purposes in our environment. We have a good DEC vocabulary, lets use it logically. 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 =================== Banana Slug Chosen "Best College Mascot" in 1992 by National Directory of College Athletics ================================================================================ Archive-Date: Fri, 09 Jul 1993 23:31:31 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 09 Jul 1993 23:31:16 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F439.9B9A6C5C.4904@WKUVX1.BITNET> Subject: Re: mail to DISUSER accts "W. Todd Wipke" writes: > >I also use BULLETIN with many disusered accounts. Since DEC provides >DISMAIL, I suggest you use that flag, rather than the DISUSER flag for >bouncing mail. The two flags have two different meanings, one of them >specifically pertains to mail, that is the one that should signify don't >deliver mail. DISUSER is used for other purposes, primarily security >purposes in our environment. We have a good DEC vocabulary, lets use >it logically. > As someone else mentioned, MX does bounce mail to DISMAILed accounts. And as I've said, something about this will be done in MX V3.4. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sat, 10 Jul 1993 05:41:49 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Getting all mail out in a short time window Message-ID: <1993Jul9.200218.8@macro.demon.co.uk> From: neill@macro.demon.co.uk Reply-To: MX-List@WKUVX1.BITNET Date: 9 Jul 93 20:02:18 GMT To: MX-List@WKUVX1.BITNET Hello all, I am currently using CMU TCPIP to connect via a SLIP line to the internet. Since I use a modem to connect to my news provider I only have the link up for a short period of time. I am just about to start automatic dialups in the middle of the night to get news and would also like to have all my mail go at the same time. If I am actualy awake at the time I can READY any pending mail with the $ mcp queue ready nnn command. Before I go and write a command procedure to parse the output of $ mcp sh queue and ready all waiting mail is there a better way of doing this? Thanks. Neill. ================================================================================ Archive-Date: Sat, 10 Jul 1993 10:24:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 10 Jul 93 15:18 GMT From: "UK TeX Archive Manager " Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST%BITNET.WKUVX1@NSFNET-RELAY.AC.UK Subject: RE: Name translations In message <0096F3ED.755371C0.32065@qis.dofasco.ca> dated Fri, 09 Jul 1993 14:26:10 EDT, fraser_h@ca.dofasco.qis wrote: > ... > MX<->Allin1 problem. But the move has introduced a new problem. Many of > the people here have published their Internet address on their business > cards. As they move from one network node to another, I have to find > some way of forwarding their mail to the new address. For example, I'm > at fraser_h@eis.dofasco.ca. That site no longer exists. I've since moved > to fraser_h@qis.dofasco.ca. Since eis.dofasco.ca physically no longer > exists, I can't set my forwarding address there to qis.dofasco.ca. I'd If eis.dofasco.ca no longer exists, why not insert a CNAME into the DNS, such that eis.dofasco.ca is transformed into qis.dofasco.ca? Any forwarding, for those former users of eis.dofasco.ca that *haven't* been transferred onto qis.dofasco.ca can be established on that latter machine. But of course, the set-up in the first place would have been for a (possibly fictitious) node called dofasco.ca which everyone would use as their only true address. Brian {Hamilton Kelly} System Manager for the UK TeX Archive at Aston University ================================================================================ Archive-Date: Sat, 10 Jul 1993 22:44:23 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 10 Jul 1993 23:04:36 EDT From: Ian Vaz Reply-To: MX-List@WKUVX1.BITNET To: mx-list@RPIECSVX.BITNET Message-ID: <0096F4FF.0C06ABC0.25327@mars.senecac.on.ca> Subject: MX having a problem delivering to one user. Hello, I am running MX v3.1C and am having a rather strange problem. A certain user on our system is having a problem receiveing mail. When I do: $ mcp queue show/full I not that this users problem, according to MX is: Error count: 96 Last error: %MAIL-E-OPENOUT, error opening !AS as output Now, I have checked his diskquota. It is okay. I thought perhaps if his quota was low then this could cause such a problem. He does not have an e-mail forwarding address. He is on a subscription list that delivers to both him and another user. The other user gets his mail. What's up/down? Anybody have any ideas? Thanks in advance for any help. Regards, Ian Vaz, Seneca College, Ph:(416) 491-5050, Ext. 7252 e-mail: ian@mars.senecac.on.ca OR ian@phobos.senecac.on.ca ================================================================================ Archive-Date: Sat, 10 Jul 1993 22:47:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 10 Jul 1993 22:47:34 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F4FC.AAD98FA9.5078@WKUVX1.BITNET> Subject: RE: MX having a problem delivering to one user. Ian Vaz writes: > >Hello, > >I am running MX v3.1C and am having a rather strange problem. A certain >user on our system is having a problem receiveing mail. When I do: >$ mcp queue show/full >I not that this users problem, according to MX is: > >Error count: 96 >Last error: %MAIL-E-OPENOUT, error opening !AS as output > >Now, I have checked his diskquota. It is okay. I thought perhaps if >his quota was low then this could cause such a problem. He does not have >an e-mail forwarding address. He is on a subscription list that delivers >to both him and another user. The other user gets his mail. >What's up/down? Anybody have any ideas? > I'm willing to bet that that user can't receive non-MX mail either. Sounds like he has a problem with his MAIL.MAI file (not indexed, etc.). Have you tried just sending normal VMS Mail to him? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sun, 11 Jul 1993 00:46:49 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sun, 11 Jul 1993 00:10:24 CDT From: Larry Horn Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: hornlo@okra.millsaps.edu Message-ID: <0096F508.3DABA140.4596@okra.millsaps.edu> Subject: RE: MX having a problem delivering to one user. >Last error: %MAIL-E-OPENOUT, error opening !AS as output > >Now, I have checked his diskquota. It is okay. I thought perhaps if Then check system protection on directories and file MAIL.MAI (S:RWE). loh ================================================================================ Archive-Date: Mon, 12 Jul 1993 07:49:07 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX talking to itself Message-ID: <1993Jul12.094620.7075@dct.ac.uk> Date: 12 Jul 93 09:46:20 +0100 To: MX-List@WKUVX1.BITNET Can anyone tell me why I might have got the following strange self-relaying behaviour from MX. Why did it relay to itself when it knows vaxc.dct.ac.uk is valid and why did it break the loop? No config files were altered during the delivery. Return-Path: Received: from vaxc.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, 09 Jul 1993 20:38:08 +0100 Received: from vaxc.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, 09 Jul 1993 20:38:02 +0100 Received: from vaxc.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, 09 Jul 1993 20:37:56 +0100 Received: from vaxc.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, 09 Jul 1993 20:37:50 +0100 Received: from vaxc.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, 09 Jul 1993 20:37:44 +0100 Received: from gemini.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, 09 Jul 1993 20:37:39 +0100 Received: by gemini.dct.ac.uk (5.65/DEC-Ultrix/4.3) id AA08635; Fri, 9 Jul 1993 20:36:57 +0100 Date: Fri, 9 Jul 1993 20:36:57 +0100 From: ccdgc@gemini.dct.ac.uk (GEORGE CHENG) Message-ID: <9307091936.AA08635@gemini.dct.ac.uk> To: ccdarg@vaxc.dct.ac.uk Subject: printer queue [etc] -- Alan Greig Janet: A.Greig@uk.ac.dct Dundee Institute of Technology Internet: A.Greig@dct.ac.uk Tel: (0382) 308810 (Int +44 382 308810) ** Never underestimate the power of human stupidity ** ================================================================================ Archive-Date: Mon, 12 Jul 1993 09:20:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: 12 Jul 1993 10:07:05 -0400 (EDT) From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET Subject: RE: MX talking to itself To: MX-List@WKUVX1.BITNET CC: ccdarg@dct.ac.uk, hardis@garnet.nist.gov Message-ID: <0096F624.C2EA7800.18106@garnet.nist.gov> Content-Transfer-Encoding: 7BIT > Can anyone tell me why I might have got the following strange > self-relaying behaviour from MX. > Received: from vaxc.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, > 09 Jul 1993 20:38:02 +0100 I give you ten-to-one odds that the configuration file is wrong. Use the MCP SHOW PATHS command to see how MX is currently configured, and remember that the mail will be sent to the _first_ match found. (That is, the rule had better be at the end. Also, please check the manual to see how to enable debugging. That will show you why each message was routed as it was. ================================================================================ Archive-Date: Mon, 12 Jul 1993 15:03:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 12 Jul 1993 16:02:17 EDT From: Ian Vaz Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096F656.61DA1160.25923@mars.senecac.on.ca> Subject: Still having a problem delivering e-mail to that user. Hi, MX still gives the following error when delivering e-mail to a user: %MAIL-E-OPENOUT, error opening !AS as output 1) The user does not have a forwarding mail address. 2) Protections on the users directory and mail.mai file is: RWE,RWE,, 3) The user receives VMS mail locally with no problems, i.e., no "not ISAM" file errors. 4) The user has lots of disk quota. Help! Ian Vaz, Seneca College, Ph:(416) 491-5050, Ext. 7252 e-mail: ian@mars.senecac.on.ca OR ian@phobos.senecac.on.ca ================================================================================ Archive-Date: Mon, 12 Jul 1993 15:25:21 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 12 Jul 1993 08:36:39 EDT From: fraser_h@qis.dofasco.ca Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F618.2107B680.32174@qis.dofasco.ca> Subject: RE: Name translations That works fine if it's a simple site move, as would a rewrite rule in MX. However, not all of the users on eis.dofasco.ca moved to the same place. Some of them moved to qis.dofasco.ca, another VAX Cluster here. Others, with PCs on their task, moved to dqc.dofasco.ca, an MSMail system connected via SMTP. So I need a way to selectively re-address individual users on eis.dofasco.ca to one of the two (there's actually 4) possible destinations. Rewrite rules will do this, but I was hoping for a more elegant solution. Nicknames only take care of the user part of the address, and only seem to work when sending mail from VMS Mail, although the documentation says that MX Router uses it as well. Either way, I still need to rewrite the entire address. ================================================================================ Archive-Date: Mon, 12 Jul 1993 18:49:01 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 1993 10:05:59 NZST From: "Andrew Carman, IGNS" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096F6ED.C5BBCE20.842@m2g.gns.cri.nz> Subject: MXALIAS 'invalid address specification' Hi, If I need to send mail to a user whose only link to the Internet is via a DECnet link, I use an address of the form MX%"'v1g::user'@m2g.gns.cri.nz". If I try to enter such an address into MXALIAS, eg: $ MXALIAS ADD user1 "'v1g::user1'@m2g.gns.cri.nz" "user1 at v1g" MXALIAS responds with the error message: %MXALIAS-E-INVADDR, invalid address specification: 'v1g::user1'@m2g.gns.cri.nz MXALIAS _will_ accept: $ MXALIAS ADD user1 """v1g::user1""@m2g.gns.cri.nz" "user1 at v1g" but then using that alias to send mail fails - no error messages, no bounce, but the mail never arrives at its destination. Turning on debugging while I send mail to this alias results in the following (rather short) log file in MX_ROUTER_DIR 13-JUL-1993 09:36:58.88 %PROCESS, Processing entry number 834 13-JUL-1993 09:36:59.22 %PROCESS, Status from READ_INFO was 00000001 13-JUL-1993 09:36:59.22 %PROCESS, Message originated in VMS Mail. 13-JUL-1993 09:36:59.30 %PROCESS, will run domain expander on envelope addresses. 13-JUL-1993 09:36:59.30 %PROCESS, will run domain expander on message headers. 13-JUL-1993 09:37:02.84 %PROCESS, Finished VMSmail-origin preprocessing. 13-JUL-1993 09:37:02.85 %PROCESS, Marking this entry as finished. No other log files are produced. Is there any way to get MXALIAS to use addresses of this sort, or do I have to stick with defining logicals? Thanks in advance for any help, Andrew Carman Institute of Geological & Nuclear Sciences phone +64 4 474 3671 Kelburn Centre, 32 Salamanca Rd fax: +64 4 471 0977 PO Box 1320, Wellington, New Zealand. ================================================================================ Archive-Date: Mon, 12 Jul 1993 20:14:20 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 12 Jul 1993 20:14:14 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F679.9421DCD9.5609@WKUVX1.BITNET> Subject: RE: MXALIAS 'invalid address specification' "Andrew Carman, IGNS" writes: > >If I need to send mail to a user whose only link to the Internet is via a >DECnet link, I use an address of the form MX%"'v1g::user'@m2g.gns.cri.nz". > >If I try to enter such an address into MXALIAS, eg: >$ MXALIAS ADD user1 "'v1g::user1'@m2g.gns.cri.nz" "user1 at v1g" >MXALIAS responds with the error message: >%MXALIAS-E-INVADDR, invalid address specification: 'v1g::user1'@m2g.gns.cri.nz > >MXALIAS _will_ accept: >$ MXALIAS ADD user1 """v1g::user1""@m2g.gns.cri.nz" "user1 at v1g" >but then using that alias to send mail fails - no error messages, no bounce, >but the mail never arrives at its destination. Cool! 8-) I hadn't thought about that case when I did MXALIAS. For now, you'll have to stick with logicals. The problem is that MX just blindly subs in the defined address, so you end up with a final address like MX%""v1g::user1"@m2g.gns.cri.nz", which is, of course invalid. MXALIAS needs to be modified to either accept the single quotes as valid, or convert the double quotes to single quotes when fetching the address. I'll try to fix that in MX V3.4. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Mon, 12 Jul 1993 21:56:55 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 1993 03:53:16 BST From: "Jamie Jones, HICOM Software Development" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F6B9.B46CA4C0.2304@hicom.lut.ac.uk> Subject: RE: VMSMAIL To: field does not contain original address. To: MX-List@WKUVX1.BITNET Subject: RE: VMSMAIL To: field does not contain original address. From: Jamie Jones Hunter Goatley writes: : writes: : > : >The To: field in VMSMAIL does not reflect the actual To: field in the : >original : >mail message sent over SMTP to our vax running MX V3.3, rather it contains : >my : >username in capital letters. I would really like to see the original To: : >field : >in there, as it might be the name of a distribution list. I know I can set : >the : >headers such that the To: field is included in the body of the message. Is : >there : >a way to get the VMSMAIL To: field to be "correct"? : > : Not currently, no. I've got on the wish list to look into for the : next version.... : : Hunter Just a small note to say that I too would like MX to work as described above. We have set up a number of local email addresses that are used for access to certain local NOTES conferences by remote email users. These "usernames" are really just VMSMAIL forwards to a general username, which has a server program running, serving the conferences. Before we installed MX (when we only had our UK JANET X25 mailer transport), the server program was able to establish which NOTES conference was being accessed by checking the VMSMAIL "To:" field. Now it has had to be hacked to try to extract the same information from the "To:" field in the body of the message, which is messy, and usually inconclusive when the message has come from a mailing list. Being able to rely on the VMSMAIL "To:" would makes things easy again :-) Thanks, Jamie. ================================================================================ Archive-Date: Mon, 12 Jul 1993 22:27:57 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 1993 04:24:19 BST From: "Jamie Jones, HICOM Software Development" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F6BE.0B4FD9C0.2323@hicom.lut.ac.uk> Subject: RE: Still having a problem delivering e-mail to that user. => Hi, => => MX still gives the following error when delivering e-mail to a user: => => %MAIL-E-OPENOUT, error opening !AS as output => => 1) The user does not have a forwarding mail address. => 2) Protections on the users directory and mail.mai file is: => RWE,RWE,, => 3) The user receives VMS mail locally with no problems, i.e., no => "not ISAM" file errors. => 4) The user has lots of disk quota. => => Help! I recently had exactly the same problem (with my own mail file!). My situation re: points 1) to 4) were the same as yours. I don't know why the problem occured, but I decided to clear up my mailbox, as I had rather alot in there. I deleted about 200 messages, and did a "purge/reclaim". Once the "purge/reclaim" had completed, MX managed to get the mail to me. Seeing as no-one else has replied to your problem with a certain answer, I'll provide you with my "guess" solution : Rebuild the users mailbox (i.e. the mail.mai file). Delete any junk messages (if there are many/any), do a "MAIL> purge/reclaim" , then even try a "MAIL> compress" If you don't want to do that, you could always check if this is the problem by : $ rename mail.dir oldmail.dir $ create/dir [.mail] i.e. creating a brand new mail.mai file This may work.. Jamie. ================================================================================ Archive-Date: Tue, 13 Jul 1993 04:22:29 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: MX talking to itself Message-ID: <1993Jul13.095449.7082@dct.ac.uk> Date: 13 Jul 93 09:54:49 +0100 To: MX-List@WKUVX1.BITNET In article <0096F624.C2EA7800.18106@garnet.nist.gov>, "Jonathan E. Hardis" writes: >> Can anyone tell me why I might have got the following strange >> self-relaying behaviour from MX. > >> Received: from vaxc.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, >> 09 Jul 1993 20:38:02 +0100 > > I give you ten-to-one odds that the configuration file is wrong. Nope... > > Use the MCP SHOW PATHS command to see how MX is currently configured, and > remember that the mail will be sent to the _first_ match found. (That is, > the rule had better be at the end. And it is. For anyone else that missed it note that MX didn't go into loop then abort after 10(?) times mode. It *did* deliver the message; just after looping a few times first. Messages sent previously and subsequently did not exhibit this behaviour. Presumably it was running through the same section of MX router code each time. It just got a different result one time round. Maybe I'll just put it down to cosmic rays :-) -- Alan Greig Janet: A.Greig@uk.ac.dct Dundee Institute of Technology Internet: A.Greig@dct.ac.uk Tel: (0382) 308810 (Int +44 382 308810) ** Never underestimate the power of human stupidity ** ================================================================================ Archive-Date: Tue, 13 Jul 1993 05:12:20 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 93 10:03 GMT From: "UK TeX Archive Manager " Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST%BITNET.WKUVX1@NSFNET-RELAY.AC.UK Subject: RE: MXALIAS 'invalid address specification' In message <0096F679.9421DCD9.5609@WKUVX1.BITNET> dated Mon, 12 Jul 1993 20:14:14 CST, "Hunter Goatley, WKU" wrote: >"Andrew Carman, IGNS" writes: >> >>If I need to send mail to a user whose only link to the Internet is via a >>DECnet link, I use an address of the form MX%"'v1g::user'@m2g.gns.cri.nz". >> >>If I try to enter such an address into MXALIAS, eg: >>$ MXALIAS ADD user1 "'v1g::user1'@m2g.gns.cri.nz" "user1 at v1g" >>MXALIAS responds with the error message: >>%MXALIAS-E-INVADDR, invalid address specification: 'v1g::user1'@m2g.gns.cri.nz >> >>MXALIAS _will_ accept: >>$ MXALIAS ADD user1 """v1g::user1""@m2g.gns.cri.nz" "user1 at v1g" >>but then using that alias to send mail fails - no error messages, no bounce, >>but the mail never arrives at its destination. > >Cool! 8-) I hadn't thought about that case when I did MXALIAS. For >now, you'll have to stick with logicals. The problem is that MX just >blindly subs in the defined address, so you end up with a final >address like MX%""v1g::user1"@m2g.gns.cri.nz", which is, of course >invalid. MXALIAS needs to be modified to either accept the single >quotes as valid, or convert the double quotes to single quotes when >fetching the address. > >I'll try to fix that in MX V3.4. Is there any overwhelming reason why MX cannot accept a string that's to remain sacrosanct enclosed in double-quotes: after all, this is what RFC-822 specifies, so why do mailer designers keep on using other syntaxes (apostrophes in MX, \d in PMDF, etc.)? Of course, I'll acknowledge that a *user* inputting an address as MX%""v1g::user1"@m2g.gns.cri.nz" *is* using incorrect syntax: s/he needs to write MX%"""v1g::user1""@m2g.gns.cri.nz". On the other hand, if we're now at a stage past the HCI, such as accessing stored aliases, then the enclosing MX%"..." can be assumed, and it surely is valid (or could be) to pass on to the MX transport a string which contains, and here I use grave and acute as quotation marks (in a meta-DCL, meta-MX sense) `"v1g::user1"@m2g.gns.cri.nz'. For this format, MXALIAS would just have to accept the command in the form: >>$ MXALIAS ADD user1 """v1g::user1""@m2g.gns.cri.nz" "user1 at v1g" on the other hand, if it really were necessary to retain the quotes doubled, then one would need to write: >>$ MXALIAS ADD user1 """""v1g::user1""""@m2g.gns.cri.nz" "user1 at v1g" Brian {Hamilton Kelly} System Manager for the UK TeX Archive at Aston University ================================================================================ Archive-Date: Tue, 13 Jul 1993 06:02:02 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 93 10:53 GMT From: "UK TeX Archive Manager " Reply-To: MX-List@WKUVX1.BITNET To: MX-LIST%BITNET.WKUVX1@NSFNET-RELAY.AC.UK Subject: RE: VMSMAIL To: field does not contain original address. In message <0096F6B9.B46CA4C0.2304@hicom.lut.ac.uk> dated Tue, 13 Jul 1993 03:53:16 BST, "Jamie Jones, HICOM Software Development" wrote: >Hunter Goatley writes: > >: writes: >: > >: >The To: field in VMSMAIL does not reflect the actual To: field in the >: >original >: >mail message sent over SMTP to our vax running MX V3.3, rather it contains >: >my >: >username in capital letters. I would really like to see the original To: >: >field >: >in there, as it might be the name of a distribution list. I know I can set >: >the >: >headers such that the To: field is included in the body of the message. Is >: >there >: >a way to get the VMSMAIL To: field to be "correct"? >: > >: Not currently, no. I've got on the wish list to look into for the >: next version.... >: >: Hunter > >Just a small note to say that I too would like MX to work as described >above. > >We have set up a number of local email addresses that are used for access to >certain local NOTES conferences by remote email users. > >These "usernames" are really just VMSMAIL forwards to a general username, >which has a server program running, serving the conferences. >Before we installed MX (when we only had our UK JANET X25 mailer transport), >the server program was able to establish which NOTES conference was being >accessed by checking the VMSMAIL "To:" field. >Now it has had to be hacked to try to extract the same information from >the "To:" field in the body of the message, which is messy, and usually >inconclusive when the message has come from a mailing list. > >Being able to rely on the VMSMAIL "To:" would makes things easy again :-) Hear, hear!! I'm not so sure that I agree with the original poster, saying that the VMSMAIL To: field should *reflect* the RFC-822 To: header; unless he meant that it should reproduce the therein --- I know of no VMS mail interface that persists in including things like the @host clause in the VMSMAIL header. But other mailers, even including the infamous CBS mailer that receives incoming Grey-Book Mail under Janet, *do* correctly display in the VMSMAIL To: field the local part of the RFC-822 and/or GBM To: header; this even includes preserving the original case, which is really amazing when one considers that CBS persists in upcasing the username in the VMSMAIL From: field (although versions before the current V5.2 *didn't* commit this solecism). What MX appears to do is to pass VMSMAIL the addressee after resolution of any forwarding stored in SYS$SYSTEM:VMSMAIL_PROFILE.DATA --- I'll agree that MX needs to perform this resolution, but the address passed should be that *before* applying it. Like Jamie, I too run a pile of mail exploders. I'm still only using CBS as an incoming transport (apart from the odd bit of illegal SMTP traffic sent directly by systems that don't appear to look at DNS MX records) because all mail intercepted by MX, no matter to what addressee it was sent, ends up with the VMSMAIL To header (and the Deliver_Mailshr TO, QTO and QQTO symbols) set to the string "DELIVER%List_Server", which is of exceedingly little utility. So I'd *really* like to see this fixed in V3.4. It wouldn't break anything else for anyone out tthere, would it? The other big big wish (for me, at least) is a facility to insert arbitrary header lines, such as I can with the MAIL$RFC_OPTIONS logical when using Janet-Mailshr (the sensible alternative, for outgoing traffic, to CBS_Mailshr) (Actually, whilst I can *add* any headers I want, I can't override the Date:, From: or To: headers --- sometimes, I'd quite like to write my own From: header --- if I do, of course, the mailer should insert a Sender: header so that any masquerading could be recognized, by human beings, at least:-) Brian {Hamilton Kelly} System Manager for the UK TeX Archive at Aston University ================================================================================ Archive-Date: Tue, 13 Jul 1993 06:28:13 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 1993 06:28:11 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F6CF.58892717.5738@WKUVX1.BITNET> Subject: RE: MX talking to itself writes: > >In article <0096F624.C2EA7800.18106@garnet.nist.gov>, "Jonathan E. Hardis" > writes: >>> Can anyone tell me why I might have got the following strange >>> self-relaying behaviour from MX. >> >>> Received: from vaxc.dct.ac.uk by vaxc.dct.ac.uk (MX V3.3 VAX) with SMTP; Fri, >>> 09 Jul 1993 20:38:02 +0100 >> [...] >For anyone else that missed it note that MX didn't go into loop then >abort after 10(?) times mode. It *did* deliver the message; just >after looping a few times first. Messages sent previously and >subsequently did not exhibit this behaviour. Presumably it >was running through the same section of MX router code each >time. It just got a different result one time round. Maybe I'll >just put it down to cosmic rays :-) > Sounds reasonable to me! ;-) Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 13 Jul 1993 06:30:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 1993 06:30:28 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F6CF.AA4CA90C.5740@WKUVX1.BITNET> Subject: RE: MXALIAS 'invalid address specification' "UK TeX Archive Manager " writes: > >Is there any overwhelming reason why MX cannot accept a string that's to remain >sacrosanct enclosed in double-quotes: after all, this is what RFC-822 >specifies, so why do mailer designers keep on using other syntaxes (apostrophes >in MX, \d in PMDF, etc.)? > I'd guess that the reason Matt used the apostrophes was to keep users from having to remember how many double-quotes to specify when typing an address. >Of course, I'll acknowledge that a *user* inputting an address as >MX%""v1g::user1"@m2g.gns.cri.nz" *is* using incorrect syntax: s/he needs to >write MX%"""v1g::user1""@m2g.gns.cri.nz". On the other hand, if we're now at a >stage past the HCI, such as accessing stored aliases, then the enclosing >MX%"..." can be assumed, and it surely is valid (or could be) to pass on to the >MX transport a string which contains, and here I use grave and acute as >quotation marks (in a meta-DCL, meta-MX sense) `"v1g::user1"@m2g.gns.cri.nz'. > Agreed---that's what I plan to do for MX V3.4. What's going on is that MX is looking up the alias, then passing that value directly into the code that expects single-quotes. I just need to bypass that conversion. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 13 Jul 1993 09:56:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 1993 10:49:51 EDT From: Irv Eisen Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F6F3.E6A29960.17585@ccstat.mc.duke.edu> Subject: mlf and nodename A note on a problem I ran into after upgrading to v 3.3 last week. I noticed today that a message for one of our mailing lists had been in the queue for a few days and that the MX MLF process was not running. I tried resetting it, stopping and restarting MX to no avail. As I was going over MX___STARTUP.COM I noticed that it was checking for the nodename in MX_STARTUP_INFO.DAT and comparing it to the result of F$GETSYI("NODENAME"). MX_STARTUP_INFO.DAT contained my FQDN and therefore failed the above comparison. When I changed it to just the node name and restarted MX, every thing worked, and I almost immediately received the three list messages that were waiting in the queue. ========================================================================= | Irv Eisen, Systems Manager Bitnet : EISEN001@DUKEMC | | Cancer Center Internet: IRV@CCSTAT.MC.DUKE.EDU | | Box 3958 | | Duke University Medical Center Voice : (919) 286-7774 | | Durham, NC 27710 Fax : (919) 286-3956 | ========================================================================= ================================================================================ Archive-Date: Tue, 13 Jul 1993 10:05:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 1993 10:04:53 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F6ED.9E99BAC3.5772@WKUVX1.BITNET> Subject: RE: mlf and nodename Irv Eisen writes: > >A note on a problem I ran into after upgrading to v 3.3 last week. > >I noticed today that a message for one of our mailing lists had been >in the queue for a few days and that the MX MLF process was not running. >I tried resetting it, stopping and restarting MX to no avail. As I was >going over MX___STARTUP.COM I noticed that it was checking for the nodename >in MX_STARTUP_INFO.DAT and comparing it to the result of F$GETSYI("NODENAME"). > >MX_STARTUP_INFO.DAT contained my FQDN and therefore failed the above >comparison. When I changed it to just the node name and restarted MX, >every thing worked, and I almost immediately received the three list >messages that were waiting in the queue. > Perhaps this will help someone else, but MX_STARTUP_INFO.DAT is *supposed* to have only the cluster node name, not the FQDN. So you had an incorrect setup (as opposed to a bug in MX). Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 13 Jul 1993 15:30:38 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 13 Jul 1993 15:55:41 GMT From: "Glenn C. Everhart" Reply-To: MX-List@WKUVX1.BITNET To: mx-list%wkuvx1.bitnet@cunyvm.cuny.edu Message-ID: <930713155541.a0@arisia.gce.com> Subject: makepolite As some of you may recall, I had suggested that a good and amusing thing might be done to a mailer by way of adding a "MakePolite" filter on text contents that would embody a site's default perceptions of what should be said in the mail. While this kind of thing has great potential for abuse, consider that replacements in text can sometimes encourage politeness. Suppose for example we took the copy_file routine in MX and added a hook to a little text filter to it. The filter might be designed so as to turn messages that are designed to turn the air blue into somthing that sounds like it came from one of Queen Victoria's censors. Take the following for starters: damn -> dratted hell -> pooh motherfucker -> dear asshole -> sweetie moron -> clod God -> gosh idiot -> churl you get the idea... The copy_file.b32 source is somewhat difficult to do this with since not too many of us have Bliss compilers. What's the chance of having some such callout made available so a site wanting to do weird things with the mail (and take responsibility for the heat that would be generated :-) by it) could do so? There are also circumstances where special formatting and so forth might be desired; this location could be a good place to add a data scrambling routine, for example, if it were desired to pass files around that way. I have some folks I correspond with who need special headers in the text body also. What do y'all think? glenn Everhart@Arisia.gce.com ================================================================================ Archive-Date: Wed, 14 Jul 1993 10:20:26 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Still having a problem delivering e-mail to that user. Date: 13 Jul 1993 22:20:30 GMT Message-ID: <21vcfeINNkg@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096F656.61DA1160.25923@mars.senecac.on.ca>, Ian Vaz writes: =Hi, = =MX still gives the following error when delivering e-mail to a user: = = %MAIL-E-OPENOUT, error opening !AS as output = =1) The user does not have a forwarding mail address. =2) Protections on the users directory and mail.mai file is: = RWE,RWE,, =3) The user receives VMS mail locally with no problems, i.e., no = "not ISAM" file errors. =4) The user has lots of disk quota. How badly is the user's disk fragmented? How big are the VMS mail messages the user can receive locally with no problems? How big are the MX messages (including RFC821 headers) that are bounced? If the answers are "Badly," "Less than three blocks," and "More than three blocks," then the problem is that VMS can't extend the user's mail directory. Now for the details: Messages under three blocks in length are stored entirely within MAIL.MAI. That means that delivering such messages doesn't affect the user's MAIL directory. Larger messages are stored in external files in the user's MAIL directory. This means that when such messages are delivered, the external file must be entered in the directory. If the directory is full, it must be extended in order to allow the new directory entry. But directories must be contiguous, so you can't just to an RMS EXTEND operation. Instead, VMS attempts to allocate a set of contiguous blocks on the disk, move the contents of the directory file to these new block, and update the retrieval pointers in the directory's file header. If there's no sufficiently large set of contiguous free blocks on the disk, then the attempt to create the new file will fail, resulting in the problem you report. To check to see whether this is actually the problem, try creating a few new, empty files in the user's MAIL directory. Give them names that are 21 characters long with a three-character file type. If you can't do so, then this is the problem. The solution is to defragment the disk. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 14 Jul 1993 10:22:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 01:33:07 BST From: "Jamie Jones, HICOM Software Development" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F76F.4ADE1FA0.2610@hicom.lut.ac.uk> Subject: RE: VMSMAIL To: field does not contain original address. To: MX%"MX-List@WKUVX1.BITNET" Subject: RE: VMSMAIL To: field does not contain original address. From: Jamie Jones UK TeX Archive Manager writes: : [ ...deleted... ] : : Like Jamie, I too run a pile of mail exploders. I'm still only using CBS as a n : incoming transport (apart from the odd bit of illegal SMTP traffic sent : directly by systems that don't appear to look at DNS MX records) because all : mail intercepted by MX, no matter to what addressee it was sent, ends up with : the VMSMAIL To header (and the Deliver_Mailshr TO, QTO and QQTO symbols) set t o : the string "DELIVER%List_Server", which is of exceedingly little utility. : Ah ha! We've taken the opposite approach here. Once we'd got our internet connection and MX working correctly, we changed our NRS entry so that our grey book X25 mail would be sent to "uk.ac.lut" instead of us directly. "uk.ac.lut" then forwards it to us, via SMTP, so now we get all internet and Janet mail via MX. The problems with MX and servers mentioned above was decided to be an acceptable disadvantage, considering we wouldn't have to use CBS any more :-) Also, we use the MLF lists alot, and found this approach easier than trying to make CBS compatible with MLF. : So I'd *really* like to see this fixed in V3.4. It wouldn't break anything : else for anyone out tthere, would it? ... and if it would, the choice could always be made in the config. file, or via a system logical. : Brian {Hamilton Kelly} : System Manager for the UK TeX Archive at Aston University : Jamie. -- Jamie Jones, HICOM Operations Group. ================================================================================ Archive-Date: Wed, 14 Jul 1993 11:17:28 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Still having a problem delivering e-mail to that user. Message-ID: <1993Jul14.151620.16092@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 14 Jul 1993 15:16:20 GMT To: MX-List@WKUVX1.BITNET In article <0096F656.61DA1160.25923@mars.senecac.on.ca>, Ian Vaz writes: >MX still gives the following error when delivering e-mail to a user: > > %MAIL-E-OPENOUT, error opening !AS as output > >1) The user does not have a forwarding mail address. >2) Protections on the users directory and mail.mai file is: > RWE,RWE,, >3) The user receives VMS mail locally with no problems, i.e., no > "not ISAM" file errors. >4) The user has lots of disk quota. o Just to verify: is the problem only to one specific user? o Are you getting this error when you hit CTRL-Z within mail, or are you getting a 'bounce' from MX (that is, is mail coming from Postmaster with this error in the mail message)? o Are any security alarms tripped when you get this error message? o What is the protection of the directory that contains MAIL.MAI (the reason I'm asking is that an external MAIL$xxxxx.MAI file may be getting created but the System protection disallows access)? o Is this a VMScluster? Is the user's disk accessible to all nodes running MX Local? o Have you enabled Local debugging to get more information about the problem? -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Wed, 14 Jul 1993 13:43:20 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Still having a problem delivering e-mail to that user. Message-ID: Date: Wed, 14 Jul 1993 17:43:50 GMT To: MX-List@WKUVX1.BITNET Ian Vaz writes: >Hi, >MX still gives the following error when delivering e-mail to a user: > %MAIL-E-OPENOUT, error opening !AS as output >1) The user does not have a forwarding mail address. >2) Protections on the users directory and mail.mai file is: > RWE,RWE,, >3) The user receives VMS mail locally with no problems, i.e., no > "not ISAM" file errors. >4) The user has lots of disk quota. i have had this problem. user might have disk space, but i have seen this errmsg when mail directories were incredibly huge. -- -- bob pasker -- rbp@netcom.com -- ================================================================================ Archive-Date: Wed, 14 Jul 1993 13:43:40 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: Name translations Message-ID: <1993Jul14.174721.21720@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 14 Jul 1993 17:47:21 GMT To: MX-List@WKUVX1.BITNET In article <0096F618.2107B680.32174@qis.dofasco.ca>, fraser_h@qis.dofasco.ca writes: >That works fine if it's a simple site move, as would a rewrite rule in MX. >However, not all of the users on eis.dofasco.ca moved to the same place. >Some of them moved to qis.dofasco.ca, another VAX Cluster here. Others, >with PCs on their task, moved to dqc.dofasco.ca, an MSMail system connected >via SMTP. So I need a way to selectively re-address individual users >on eis.dofasco.ca to one of the two (there's actually 4) possible >destinations. Rewrite rules will do this, but I was hoping for a more >elegant solution. Nicknames only take care of the user part of the address, >and only seem to work when sending mail from VMS Mail, although the >documentation says that MX Router uses it as well. Either way, I still >need to rewrite the entire address. Louis Moore wrote a site name conversion routine, which is included in the [.CONTRIB] directory of the MX V3.3 kit. This is a site agent which converts (in both directions) a simple VMS username to a lastname.firstname format. This works to both hide the real username on the local system, and to provide an easy, consistant interface to outside users (so you need to know a person's name, not their username). ... Anyways, the datafile for this is setup with a username and a "personal name". The code is written in Macro, and it should be possible to modify the code to not only perform magic on the "user" portion of the address, but to also perform magic on the "host" portion of the address. For example, this would allow maintaining an indexed file which contained the oldusername@oldhost and would translate it to newusername@newhost. ... just a thought. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Wed, 14 Jul 1993 14:06:27 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: MXALIAS 'invalid address specification' Message-ID: <1993Jul14.182508.23063@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 14 Jul 1993 18:25:08 GMT To: MX-List@WKUVX1.BITNET In article <0096F6ED.C5BBCE20.842@m2g.gns.cri.nz>, "Andrew Carman, IGNS" writes: >If I try to enter such an address into MXALIAS, eg: >$ MXALIAS ADD user1 "'v1g::user1'@m2g.gns.cri.nz" "user1 at v1g" >MXALIAS responds with the error message: >%MXALIAS-E-INVADDR, invalid address specification: 'v1g::user1'@m2g.gns.cri.nz > >MXALIAS _will_ accept: >$ MXALIAS ADD user1 """v1g::user1""@m2g.gns.cri.nz" "user1 at v1g" >but then using that alias to send mail fails - no error messages, no bounce, >but the mail never arrives at its destination. As a workaround, you might be able to create an MXALIAS record with an address like: user1%v1g@m2g.gns.cri.nz which should be accepted by MXALIAS, and then setup an MX rewrite rule so the outgoing address is changed back into the quoted form (with the DECnet address), something like: DEFINE REWRITE_RULE "<{user}%v1g@m2g.gns.cri.nz>" - "<""v1g::{user}""@m2g.gns.cri.nz>" Not sure if it'll work, but it might.... -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Wed, 14 Jul 1993 15:45:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 13:42:49 -0700 (MST) From: "Louis B. Moore" Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Name translations To: MX-List@WKUVX1.BITNET Message-ID: <0096F7D5.3B0868E0.29782@tchden.org> Content-Transfer-Encoding: 7BIT > >... Anyways, the datafile for this is setup with a username and a "personal >name". The code is written in Macro, and it should be possible to modify >the code to not only perform magic on the "user" portion of the address, >but to also perform magic on the "host" portion of the address. The code just does an indexed lookup on the username (key 0)and converts it to whatever it finds in the file as a nickname (key 1). In our case last.first. The reverse is also done. BTW, this can cause some excitement with mail lists that are not W:W until you get the list member addresses updated. Guess how I learned this :-) >For example, this would allow maintaining an indexed file which contained the >oldusername@oldhost and would translate it to newusername@newhost. > >... just a thought. You might need to make some minor code changes for this, but it should work. >-Dan Wing, Systems Administrator, University Hospital, Denver > dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet Louis B. Moore Internet: MOORE.LOUIS@tchden.org Systems Programmer Phone: +1.303.837.2513 The Children's Hospital of Denver Denver, Colorado USA 80218 ================================================================================ Archive-Date: Wed, 14 Jul 1993 15:48:13 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 16:15:11 EDT From: Ian Vaz Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096F7EA.845D18A0.27548@mars.senecac.on.ca> Subject: Problem sending e-mail to user-->FIXED! Hi, I would like to thank Hunter Goately, Jamie Jones, Dan WIng, Larry Horn and Bob Pasker for their excellent suggestions and sharing of past experiences in solving our rather strange problem where one specific user was not receiving mx mail, although mail was arriving for him, but, getting stuck in the queue. The fix, a suggestion from Jamie Jones (mucho THANX), was: (a) User deleted as much existing, unnecessary e-mail as possible. (b) MAIL> purge/reclaim (c) compress This has fixed the problem (I hope it sticks). Thanks once again. Ian Vaz, Seneca College, Ph:(416) 491-5050, Ext. 7252 e-mail: ian@mars.senecac.on.ca OR ian@phobos.senecac.on.ca ================================================================================ Archive-Date: Wed, 14 Jul 1993 15:48:38 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 15:11:20 EDT From: fraser_h@qis.dofasco.ca Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F7E1.98C75160.32596@qis.dofasco.ca> Subject: RE: Name translations There are two modules within MX... the nickname and the sitename conversion routines. Nickname (the one I believe you're referring to) is passed the username part of an address, not the site. The site name conversion routine, generally used to convert bitnet addresses back and forth, only receives the site name part of an address. I did try using the nickname to do a nickname->full email address conversion, and then clean it up with a rewrite. The results looked something like this: MX receives fraser_h@eis.dofasco.ca Nickname translates to fraser_h@qis.dofasco.ca@eis.dofasco.ca rewrite strips it to fraser_h@qis.dofasco.ca That works, except the nickname module only saw fraser_h, and would have no way of uniquely recognizing which fraser_h I'm talking about if we happened to have more than one at different sites. Additionally, the nickname module doesn't seem to be called by router (the docs say it is), so it's only useful for sending messages from VMS mail to a nickname. By the way, I modified nickname to log calls to init, convert and cleanup in a file. mx_router calls init, but never attempts to translate anything, while VMS mail calls convert for the sender and recipient addresses. ================================================================================ Archive-Date: Wed, 14 Jul 1993 15:57:59 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 13:52:10 EDT From: kish@DRWHO.IAC.HONEYWELL.COM Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F7D6.89698C0C.3522@DRWHO.IAC.HONEYWELL.COM> Subject: MX ALIAS Can the MXALIAS command take comand file inputs? or is ther a way to get the same effect? I have 5762 ALiases I would like to load. :) Karl KISH@drwho.iac.honeywell.com ================================================================================ Archive-Date: Wed, 14 Jul 1993 16:01:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 16:01:01 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F7E8.89807DFB.6355@WKUVX1.BITNET> Subject: RE: MX ALIAS kish@DRWHO.IAC.HONEYWELL.COM writes: > >Can the MXALIAS command take comand file inputs? >or is ther a way to get the same effect? > No. You could write a command procedure to do it, though: $ MXALIAS add xxxxx "xxx@xxxx" "xxxxxxxx" add yyyyy "yyy@yyyy" "yyyyyyyy" add zzzzz "zzz@zzzz" "zzzzzzzz" exit $ exit >I have 5762 ALiases I would like to load. :) > Whew!! Let me know if you have any problems! Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 14 Jul 1993 16:30:11 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 14:21:47 EDT From: kish@DRWHO.IAC.HONEYWELL.COM Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F7DA.AC89DD69.3540@DRWHO.IAC.HONEYWELL.COM> Subject: RE: MX ALIAS RE... kish@DRWHO.IAC.HONEYWELL.COM writes: > >Can the MXALIAS command take comand file inputs? >or is ther a way to get the same effect? > No. You could write a command procedure to do it, though: $ MXALIAS add xxxxx "xxx@xxxx" "xxxxxxxx" add yyyyy "yyy@yyyy" "yyyyyyyy" add zzzzz "zzz@zzzz" "zzzzzzzz" exit $ exit Nope you appear to be using SMG input routines.... they dont like to do that... anyting special about the file? perhaps I can just do a FDL load? Karl ================================================================================ Archive-Date: Wed, 14 Jul 1993 16:53:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 16:47:03 EDT From: kenm@adhe.arknet.edu Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096F7EE.F7D66B20.508@adhe.arknet.edu> Subject: REWRITE RULES Arkansas Department of Higher Education I N T E R O F F I C E M E M O R A N D U M Date: 07-14-1993 04:44pm GMT From: KEN MCCOY KENM Dept: Information Services Tel No: 501-324-9300 FAX 501-324-9308 TO: Remote Addressee ( _MX-LIST@WKUVX1.BITNET ) Subject: REWRITE RULES Hello All-In-1 fans, How do you specify a rewrite rule in MX so that when the message is received into All-In-1 the return address (FROM: line) would look like _MX-List@WKUVX1.BITNET instead of MX%"MX-ListWKUVX1.BITNET". I've included the header that I see in All-In-1? Thanks in advance!!! Ken McCoy Arkansas Dept. of Higher Ed. ====================================================================== ====================================================================== Arkansas Department of Higher Education I N T E R O F F I C E M E M O R A N D U M Date: 06-30-1993 06:22pm GMT From: MX%"MX-List@WKUVX1.BITNET" MX%"MX-List@WKUVX1.BITNET"@MRGATE@SPEEDY Dept: Tel No: TO: kenm@A1 Subject: Rewrite Rules Return-Path: <@ULKYVM.LOUISVILLE.EDU:list-mgr@WKUVX1.BITNET> Received: from ULKYVM.LOUISVILLE.EDU by speedy.adhe.arknet.edu (MX V3.3 VAX) with SMTP; Wed, 30 Jun 1993 18:18:01 EDT Received: from ULKYVM.LOUISVILLE.EDU by ULKYVM.LOUISVILLE.EDU (IBM VM SMTP V2R1) with BSMTP id 5681; Wed, 30 Jun 93 19:18:34 EDT Received: from WKUVX1.BITNET by ULKYVM.LOUISVILLE.EDU (Mailer R2.08 R208004) with BSMTP id 7512; Wed, 30 Jun 93 19:18:32 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: list-mgr@WKUVX1.BITNET Sender: list-mgr@WKUVX1.BITNET Date: Thu, 01 Jul 1993 01:13:12 +0100 From: Per Hogstedt Reply-To: MX-List@WKUVX1.BITNET Subject: Rewrite Rules To: MX-List@WKUVX1.BITNET Message-ID: <0096ED35.5AEC8CE0.9960@plab.se> ================================================================================ Archive-Date: Wed, 14 Jul 1993 18:59:23 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Can't find MX records... Message-ID: <1993Jul14.171148.1961@dmc.com> Date: 14 Jul 93 17:11:48 EDT To: MX-List@WKUVX1.BITNET I'm seeing problem getting to Everything sent do them gets bounced with: Note: this message was generated automatically. A problem occurred during SMTP delivery of your message. Error occurred sending to the following user(s): (via nt1l.krl.com): %MX-F-RETRYEXCD, retry count exceeded -MX-F-NOHOST, no such host If I do a NSLOOKUP, type=any, from my local host, I get: set type=any > nt1l.krl.com Server: LOCALHOST Address: 127.0.0.1 *** LOCALHOST can't find nt1l.krl.com: Non-existent domain > but if I back off to krl.com I get: > krl.com Server: LOCALHOST Address: 127.0.0.1 Non-authoritative answer: krl.com nameserver = PRIMERD.CV.COM krl.com nameserver = RELAY.CV.COM krl.com origin = primerd.cv.com mail addr = aardvark.nt1l.krl.com serial = 920316 refresh = 10800 (3 hours) retry = 1800 (30 mins) expire = 360000 (4 days 4 hours) minimum ttl = 86400 (1 day) krl.com preference = 1, mail exchanger = cvrd.cv.com krl.com origin = Relay.CV.COM mail addr = aardvark.nt1l.krl.com serial = 930626 refresh = 3600 (1 hour) retry = 600 (10 mins) expire = 3600000 (41 days 16 hours) minimum ttl = 14400 (4 hours) Authoritative answers can be found from: KRL.COM nameserver = PRIMERD.CV.COM KRL.COM nameserver = RELAY.CV.COM PRIMERD.CV.COM internet address = 130.21.207.144 RELAY.CV.COM internet address = 130.21.96.1 The MX SMTP client give forth with: 14-JUL-1993 17:01:39.38 Processing queue entry number 26136 on node HULK 14-JUL-1993 17:01:40.06 Recipient: , route=nt1l.krl.com 14-JUL-1993 17:01:40.07 SMTP_SEND: looking up host name nt1l.krl.com 14-JUL-1993 17:03:11.94 SMTP_SEND: Failed, sts=00000870 14-JUL-1993 17:03:11.94 SMTP send failed, sts=0C278024, sts2=00000870 14-JUL-1993 17:03:11.94 Recipient status=0C278024 for 14-JUL-1993 17:03:12.85 1 rcpts need retry, next try 14-JUL-1993 17:33:12.85 14-JUL-1993 17:03:12.91 *** End of processing pass *** $ write sys$output f$message(%x870) %SYSTEM-W-ENDOFFILE, end of file Why can't the MX SMTP client find the MX record for krl.com and dtrt for nt1l??? If it matters, apparently krl.com can't get mail to dmc.com either. I'm running MX 3.3, Multinet 3.2B, and VMS A5.5-2. Dick -- Dick Munroe Internet: munroe@dmc.com Doyle, Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. 01749 USA FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Wed, 14 Jul 1993 20:08:52 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Can't find MX records... Message-ID: <1993Jul15.000213.3337@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.BITNET Date: Thu, 15 Jul 1993 00:02:13 GMT To: MX-List@WKUVX1.BITNET In article <1993Jul14.171148.1961@dmc.com>, munroe@dmc.com (Dick Munroe) writes: >I'm seeing problem getting to Because there is no domain name NT1L.KRL.COM, as you found out. [...] >but if I back off to krl.com I get: > >> krl.com >Server: LOCALHOST >Address: 127.0.0.1 > >Non-authoritative answer: >krl.com nameserver = PRIMERD.CV.COM >krl.com nameserver = RELAY.CV.COM >krl.com [...] Yes, OK. But so what? >Why can't the MX SMTP client find the MX record for krl.com and dtrt for >nt1l??? If it matters, apparently krl.com can't get mail to dmc.com either. >I'm running MX 3.3, Multinet 3.2B, and VMS A5.5-2. It won't because that's not the way it's supposed to work. If the people at KRL.COM want mail for NT1L.KRL.COM to be delivered to KRL.COM, they must enter an MX record in the DNS to tell mailers to do so. -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Wed, 14 Jul 1993 21:17:33 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 14 Jul 1993 21:17:15 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F814.B6753992.6421@WKUVX1.BITNET> Subject: RE: MX ALIAS kish@DRWHO.IAC.HONEYWELL.COM writes: > >>>Can the MXALIAS command take comand file inputs? >>>or is ther a way to get the same effect? >>> >>No. You could write a command procedure to do it, though: >> >>$ MXALIAS >>add xxxxx "xxx@xxxx" "xxxxxxxx" [...] > >Nope you appear to be using SMG input routines.... Yes. >they dont like to do that... > Sure they do: $ ty x.x $!Test command procedure $ mxalias add test "test@here" "test" exit $ exit $!Now execute it $ @x.x Added alias TEST to MX alias database $ >anyting special about the file? perhaps I can just do a FDL load? > You could do that too. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 15 Jul 1993 03:42:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 15 Jul 1993 11:40:05 EDT From: "ARAS.GOR. U. HAKAN ERES" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F88D.400D77A0.3656@trboun.bitnet> Subject: about BILF.EXE Hi, I need BILF.EXE file to extract the latest version of MX with UNZIP.EXE. How can I find it? Any help will be appr. Hakan Eres (NAD of Bogazici University) ************************************************************************* * **************************** ************************ * * * o o oo o o oo o o * *********** U. HAKAN ERES * * * * o o o o o o o o oo o * * * Address: * * * * oooo oooo oo oooo o oo * * ERES2@TRBOUN.BITNET * * * * o o o o o o o o o o * * * BOGAZICI UNIVERSITY * * * * o o o o o o o o o o * *********** ISTANBUL, TURKIYE * * * **************************** ************************ * ************************************************************************* ================================================================================ Archive-Date: Thu, 15 Jul 1993 05:47:34 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: MX ALIAS Message-ID: <1993Jul15.055141.1963@dmc.com> Date: 15 Jul 93 05:51:41 EDT To: MX-List@WKUVX1.BITNET In article <0096F7DA.AC89DD69.3540@DRWHO.IAC.HONEYWELL.COM>, kish@DRWHO.IAC.HONEYWELL.COM writes: > No. You could write a command procedure to do it, though: > > $ MXALIAS > add xxxxx "xxx@xxxx" "xxxxxxxx" > add yyyyy "yyy@yyyy" "yyyyyyyy" > add zzzzz "zzz@zzzz" "zzzzzzzz" > exit > $ exit What I did for my 200 or so was to generate a command procedure of the form: $ MXALIAS add ... Worked just fine for me. Dick -- Dick Munroe Internet: munroe@dmc.com Doyle, Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. 01749 USA FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Thu, 15 Jul 1993 05:48:38 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Can't find MX records... Message-ID: <1993Jul15.054935.1962@dmc.com> Date: 15 Jul 93 05:49:35 EDT To: MX-List@WKUVX1.BITNET In article <1993Jul15.000213.3337@news.arc.nasa.gov>, madison@tgv.com (Matt Madison) writes: > In article <1993Jul14.171148.1961@dmc.com>, munroe@dmc.com (Dick Munroe) writes: >>Why can't the MX SMTP client find the MX record for krl.com and dtrt for >>nt1l??? If it matters, apparently krl.com can't get mail to dmc.com either. >>I'm running MX 3.3, Multinet 3.2B, and VMS A5.5-2. > > It won't because that's not the way it's supposed to work. If the people > at KRL.COM want mail for NT1L.KRL.COM to be delivered to KRL.COM, they must > enter an MX record in the DNS to tell mailers to do so. Duhhh. I can't believe I didn't see that. I must have been more tired than I thought. Thanks for the response and my apologies for the wasted bandwidth. Dick -- Dick Munroe Internet: munroe@dmc.com Doyle, Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. 01749 USA FAX: (508) 562-1133 GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection. ================================================================================ Archive-Date: Thu, 15 Jul 1993 06:32:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 15 Jul 1993 06:32:38 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F862.4CFD5C94.6625@WKUVX1.BITNET> Subject: RE: about BILF.EXE "ARAS.GOR. U. HAKAN ERES" writes: > > Hi, > > I need BILF.EXE file to extract the latest version of MX >with UNZIP.EXE. How can I find it? Any help will be appr. > You should not need BILF---it sounds like you are trying to use an old version of UnZip. How did you get MX? If it was from my FILESERV, getting the package FILESERV_TOOLS will give you the current UNZIP.EXE. If you ftp'ed it from some place, I'd guess that you didn't transfer it as an ASCII file. BTW, BILF is included with ZOO210, also available from my FILESERV. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 15 Jul 1993 09:24:46 CDT Sender: list-mgr@WKUVX1.BITNET Date: 15 Jul 1993 10:16:36 -0400 (EDT) From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Can't find MX records... To: MX-List@WKUVX1.BITNET CC: hardis@garnet.nist.gov Message-ID: <0096F881.96B1C220.18324@garnet.nist.gov> Content-Transfer-Encoding: 7BIT > I'm seeing problem getting to As an aside, anyone who names a host N - T - 1 (one) - L (lower case "L") is asking for trouble, since a large number of people will read it incorrectly (including the typist on whom you may be depending). ================================================================================ Archive-Date: Thu, 15 Jul 1993 12:45:28 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 15 Jul 1993 11:47:05 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F88E.3ACDAAC0.26614@SHSU.edu> Subject: RE: about BILF.EXE On Thu, 15 Jul 1993 06:32:38 CST, "Hunter Goatley, WKU" posted: > BTW, BILF is included with ZOO210, also available from my FILESERV. This really ought to be included in the UNZIP package, too, Hunter -- in both your FILESERV_TOOLS (or wherever it resides) set as well as in the unz50p1x.* packages on quest.jpl.nasa.gov. The VMS/bilf/ area of the main distribution has this -- why not also in those which are VMS-specific distributions?? --George ================================================================================ Archive-Date: Thu, 15 Jul 1993 12:51:07 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 15 Jul 1993 12:50:49 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096F897.21AC2310.6782@WKUVX1.BITNET> Subject: RE: about BILF.EXE "George D. Greenwade" writes: > >On Thu, 15 Jul 1993 06:32:38 CST, "Hunter Goatley, WKU" > posted: >> BTW, BILF is included with ZOO210, also available from my FILESERV. > >This really ought to be included in the UNZIP package, too, Hunter -- in >both your FILESERV_TOOLS (or wherever it resides) set as well as in the >unz50p1x.* packages on quest.jpl.nasa.gov. The VMS/bilf/ area of the main >distribution has this -- why not also in those which are VMS-specific >distributions?? > Oooops. It is in my UNZIP50P1 distribution (though I forgot to include the AXP executable for it). My distribution includes *all* of the original UnZip files, plus the VMS binaries, so.... As for including BILF in FILESERV_TOOLS, and I'm posting this to MX-List because it relates to the original request: BILF should never be needed if the .ZIP files are properly transferred in the first place. I don't include it in FILESERV_TOOLS because if you get any of mine through e-mail, you're not going to need BILF. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 20 Jul 1993 02:43:06 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 15 Jul 1993 15:11:23 -400 (EDT) From: "Michael McIntyre, 508-371-1935" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096F8AA.C4CD0E20.2627@mcinc.com> Subject: Local Agent, and Fileserv questions Hi, I have a few questions about MX. I've just been using it for a week or so, but I have a mailing list and file server set up. Question #1: Why do some header like Mime-Version: and Content type show up at the top of the message when I have my local agent set up to put on from and date at the top, everything else at the bottom. As follows: Top headers: FROM,DATE Bottom headers: SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID, RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT, ENCRYPTED,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM, RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER Question #2: The file server is sending messages every 15 minutes during the send period. Since I have decus uucp set up to dial out on demand every 30 minutes, I am making a phone call for every other fileserv response. I would like the fileserver to send everything at 12:30 am. In one batch (actually the first message would probably kick off uucp, but the rest would wait 30 minutes) Can I set up the fileserver with a more restricted schedule? Here is the fileserver setup: Name: fileserv, Manager: msm@mcinc.com Root: MCVAX$DKA0:[FILESERV.] Not linked to a mailing list. Delay threshold: 0 Send period: 19:00 - 08:00 Daily limits: Server: 5000000 Host: 1000000 User: 1000000 Exerpt from log: 14-JUL-1993 09:24 SEND: FS="fileserv",FILE="MDC-SC12TG8.93-1-RTF",DEST="DI3027@c c.uab.es",DELAY="14-JUL-1993 19:00" 14-JUL-1993 09:24 SEND: FS="fileserv",FILE="MDC-SC12TG8.93-1-TXT",DEST="DI3027@c c.uab.es",DELAY="14-JUL-1993 19:15" 14-JUL-1993 09:24 SEND: FS="fileserv",FILE="MDC-SC12TG8.DESCRIPTION",DEST="DI302 7@cc.uab.es",DELAY="14-JUL-1993 19:30" 14-JUL-1993 09:24 SEND: FS="fileserv",FILE="File server fileserv: transaction lo g",DEST="DI3027@cc.uab.es",NODELAY Question #3: I am making documents available which are written using word perfect and MS-Word. The files frequenly have more than 80 characters per line when output in ASCII. I am also making available source code which can be executed on VMS, UNIX, DOS. I currently have a file for each document in ASCII text and RTF. What format should I put the files in so that most people will be able to use them? Thanks for your help! 8^) Michael McIntyre McIntyre Consulting, Inc. Tel: 508-371-1935 msm@mcinc.com 336 Baker Ave Fax: 508-369-6693 Concord, MA 01742 ================================================================================ Archive-Date: Tue, 20 Jul 1993 03:11:28 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Name translations Message-ID: <1993Jul15.203031.3298@inland.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 15 Jul 93 20:30:31 CST To: MX-List@WKUVX1.BITNET In article <0096F3ED.755371C0.32065@qis.dofasco.ca>, fraser_h@qis.dofasco.ca writes: > .... > cards. As they move from one network node to another, I have to find > some way of forwarding their mail to the new address. For example, I'm > at fraser_h@eis.dofasco.ca. That site no longer exists. I've since moved > to fraser_h@qis.dofasco.ca. Since eis.dofasco.ca physically no longer > exists, I can't set my forwarding address there to qis.dofasco.ca. I'd > like to set up a directory service in MX to translate > fraser_h@dofasco.ca into fraser_h@qis.dofasco.ca, but not everybody's on > qis.dofasco.ca either. > .... Stand by! A few weeks ago I alluded to some router changes I have been working on. One of those changes will do exactly what you want if you don't mind writing a little code. I've added FULL rewriting of the envelope address during the rewrite phase of the router. If an MCP defined rewrite rule does not get used (or there are none), and you have defined a REWRITE_ENVELOPE function in MX_SITE_ADDRESS_REWRITER, then the entire target address is passed to you as is for your pleasure and enjoyment. I'm currently testing these changes and developing the rewriter I need for my domain. My first cut test version of the rewriter does this: Given if "sub" is "lanmail1", "lanmail2", "lanmail3" or "lanmail4", rewrite as else if "sub" is a known DECnet node, rewrite the address as <"sub::mailbox"@decnet> otherwise "sub" must be an SMTP host, so rewrite it as Use these paths: Domain="DECNET", Path=Local Domain="*.INLAND.INLAND.COM", Path=SMTP, Route="[156.144.4.2]" Domain="[156.144.4.7]", Path=Local Domain="[156.144.*.*]", Path=SMTP Domain="*", Path=SMTP and I have delivery via DECnet to my DECnet hosts, SMTP to my SMTP hosts, and forwarding to my MS-Mail<->SMTP Gateway ** with no rewrite rules **. --- Tom Tom Allebrandi | Mail guru - DECUS UUCP Development Team Inland Steel Research Labs | NFS grunt - CMU/Tek-IP East Chicago, IN | Chairperson - VMSnet Working Group, DECUS VAX SIG 219 399 6306 | Internet: allebrandi@inland.com DECUServe: allebrandi | UUCP: ...!uunet!inland!allebrandi ================================================================================ Archive-Date: Tue, 20 Jul 1993 06:59:03 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Problem sending e-mail to user-->FIXED! Date: 16 Jul 1993 20:56:21 GMT Message-ID: <2274llINNev6@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096F7EA.845D18A0.27548@mars.senecac.on.ca>, Ian Vaz writes: =Hi, = =I would like to thank Hunter Goately, Jamie Jones, Dan WIng, Larry Horn and =Bob Pasker for their excellent suggestions and sharing of past experiences =in solving our rather strange problem where one specific user was not =receiving mx mail, although mail was arriving for him, but, getting stuck in =the queue. The fix, a suggestion from Jamie Jones (mucho THANX), was: = = (a) User deleted as much existing, unnecessary e-mail as possible. = = (b) MAIL> purge/reclaim = = (c) compress = =This has fixed the problem (I hope it sticks). Given that the user had sufficient disk quota and the disk wasn't full, then this sounds very much as if the user's disk was badly fragmented, and his mail directory was full. If that's the case, then the fix will probably stick only until his mail directory gets filled up again. Or until someone else with a mail directory of similar size has his mail directory fill up on him. If it's been very long since you defragmented that disk, then you might want to do so as soon as convenient. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Tue, 20 Jul 1993 09:38:11 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 20 Jul 1993 08:02:35 EDT From: fraser_h@qis.dofasco.ca Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FC5C.B1A88300.576@qis.dofasco.ca> Subject: Re: Name translations Envelope rewriting is exactly what I want to do. Your example didn't demonstrate that, but I have faith that that's what you're providing. So that will be available by noon, did you say ? -) ================================================================================ Archive-Date: Tue, 20 Jul 1993 10:38:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 20 Jul 1993 08:32:56 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: rharwood@Data.Basix.COM Message-ID: <0096FC60.EF1CCB20.1192@Data.Basix.COM> Subject: Handling DECNet forwarding references I'm still having problems with messages forwarded here through DECnet, and I think I've narrowed down the problem a bit. Before I installed MX, the "From" field (in the VMS header) of such a message would look like this: SMTP%"\'PIMACC::RELLISON\'@east.pima.edu" Now when MX receives a message from this person, the VMS header has this: MX%"'PIMACC::RELLISON'@east.pima.edu" REPLYing to the SMTP message was successful, but replying to the MX message gets me a bounced message at east.pima.edu (which is running UCX [ughhh!]). Can MX gurus give me a fix, or RFC-laywers tell me who's not playing according to Hoyle? Thanks for any help or pointers. Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Tue, 20 Jul 1993 16:56:29 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Handling DECNet forwarding references Message-ID: <1993Jul20.204022.18332@news.arc.nasa.gov> From: Date: Tue, 20 Jul 1993 20:40:22 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096FC60.EF1CCB20.1192@Data.Basix.COM>, "Ray Harwood -- Data Basix: (602)721-1988" writes: >I'm still having problems with messages forwarded here through DECnet, and I >think I've narrowed down the problem a bit. Before I installed MX, the "From" >field (in the VMS header) of such a message would look like this: > SMTP%"\'PIMACC::RELLISON\'@east.pima.edu" >Now when MX receives a message from this person, the VMS header has this: > MX%"'PIMACC::RELLISON'@east.pima.edu" >REPLYing to the SMTP message was successful, but replying to the MX message >gets me a bounced message at east.pima.edu (which is running UCX [ughhh!]). I can't think why. They should result in the exact same syntax for an address on the SMTP side of things. How about sending us some more information, like a copy of the bounce message? -Matt -- Matthew Madison | madison@tgv.com | +1 408 427 4366 TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA ================================================================================ Archive-Date: Tue, 20 Jul 1993 19:08:22 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Handling DECNet forwarding references Date: 20 Jul 1993 23:00:10 GMT Message-ID: <22htdqINNmfv@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096FC60.EF1CCB20.1192@Data.Basix.COM>, you write: =I'm still having problems with messages forwarded here through DECnet, and I =think I've narrowed down the problem a bit. Before I installed MX, the "From" =field (in the VMS header) of such a message would look like this: = SMTP%"\'PIMACC::RELLISON\'@east.pima.edu" =Now when MX receives a message from this person, the VMS header has this: = MX%"'PIMACC::RELLISON'@east.pima.edu" =REPLYing to the SMTP message was successful, but replying to the MX message =gets me a bounced message at east.pima.edu (which is running UCX [ughhh!]). = =Can MX gurus give me a fix, or RFC-laywers tell me who's not playing according =to Hoyle? For starters, you should've given us a lot more information. Like, for example, defining MX_SMTP_DEBUG then giving us the MX_SMTP_LOG.LOG file's contents: ******************************************************************************** 20-JUL-1993 14:54:39.98 Processing queue entry number 11016 on node SOL1 20-JUL-1993 14:54:40.46 Recipient: <"PIMACC::RELLISON"@east.pima.edu>, route=east.pima.edu 20-JUL-1993 14:54:40.46 SMTP_SEND: looking up host name east.pima.edu 20-JUL-1993 14:54:40.64 SMTP_SEND: Attempting to start session with east.pima.edu. [144.90.32.2] 20-JUL-1993 14:54:40.97 SMTP_SEND: Connected 20-JUL-1993 14:54:43.06 SMTP_SEND: Rcvd: 220 east.pima.edu Service ready 20-JUL-1993 14:54:43.28 SMTP_SEND: Sent: HELO SOL1.GPS.CALTECH.EDU 20-JUL-1993 14:54:43.36 SMTP_SEND: Rcvd: 250 east.pima.edu Hello sol1.gps.caltech.edu, pleased to meet you 20-JUL-1993 14:54:43.37 SMTP_SEND: Sent: MAIL FROM: 20-JUL-1993 14:54:43.57 SMTP_SEND: Rcvd: 250 ... Sender OK 20-JUL-1993 14:54:43.57 SMTP_SEND: Sent: RCPT TO:<"PIMACC::RELLISON"@east.pima.edu> 20-JUL-1993 14:54:43.80 SMTP_SEND: Rcvd: 250 <"PIMACC::RELLISON"@east.pima.edu>... Recipient ok 20-JUL-1993 14:54:43.84 SMTP_SEND: Sent: DATA 20-JUL-1993 14:54:43.93 SMTP_SEND: Rcvd: 354 Start mail input; end with . 20-JUL-1993 14:54:43.95 SMTP_SEND: Sent: Received: by SOL1.GPS.CALTECH.EDU (MX V3.3 VAX) id 11014; Tue, 20 Jul 1993 20-JUL-1993 14:54:43.95 SMTP_SEND: Sent: 14:52:09 PST 20-JUL-1993 14:54:43.95 SMTP_SEND: Sent: Date: Tue, 20 Jul 1993 14:52:07 PST 20-JUL-1993 14:54:43.99 SMTP_SEND: Sent: From: Carl J Lydick 20-JUL-1993 14:54:44.00 SMTP_SEND: Sent: To: "PIMACC::RELLISON"@east.pima.edu 20-JUL-1993 14:54:44.00 SMTP_SEND: Sent: Message-ID: <0096FC95.E78E7CC0.11014@SOL1.GPS.CALTECH.EDU> 20-JUL-1993 14:54:44.00 SMTP_SEND: Sent: Subject: Test. Please reply if you receive this 20-JUL-1993 14:54:44.01 SMTP_SEND: Sent: 20-JUL-1993 14:54:44.01 SMTP_SEND: Sent: Someone has reported having problems sending mail to you. I'm trying to help 20-JUL-1993 14:54:44.01 SMTP_SEND: Sent: him track down the problem. If you receive this message (though I suspect you 20-JUL-1993 14:54:44.01 SMTP_SEND: Sent: won't), please let me know. Thanks. 20-JUL-1993 14:54:44.04 SMTP_SEND: Sent: . 20-JUL-1993 14:54:44.04 SMTP_SEND: will wait 00:10:30.00 for reply. 20-JUL-1993 14:54:44.38 SMTP_SEND: Rcvd: 250 OK 20-JUL-1993 14:54:44.38 SMTP_SEND: Sent: QUIT 20-JUL-1993 14:54:44.56 SMTP_SEND: Rcvd: 221 east.pima.edu Service closing transmission channel 20-JUL-1993 14:54:44.63 Recipient status=00000001 for <"PIMACC::RELLISON"@east.pima.edu> 20-JUL-1993 14:54:44.78 Entry now completely processed, no retries needed. 20-JUL-1993 14:54:44.83 *** End of processing pass *** ******************************************************************************** Then you should've given us the bounce message: ******************************************************************************** From: MX%"UCX_SMTP@east.pima.edu" 1993-07-20 14:54:51.35 To: CARL CC: Subj: Return-Path: Received: from east.pima.edu by SOL1.GPS.CALTECH.EDU (MX V3.3 VAX) with SMTP; Tue, 20 Jul 1993 14:54:47 PST ---- Transcript of session follows ---- %UCX-E-SMTP_SNDERROR, Error detected while sending mail to "PIMACC::RELLISON"@east.pima.edu -RMS-E-RNF, record not found ---- Recipients of this delivery ---- "PIMACC::RELLISON"@east.pima.edu (bounced) ---- Unsent message follows ---- Received: by east.pima.edu (UCX V2.0) Tue, 20 Jul 1993 15:54:58 -0700 Received: by SOL1.GPS.CALTECH.EDU (MX V3.3 VAX) id 11014; Tue, 20 Jul 1993 14:52:09 PST Date: Tue, 20 Jul 1993 14:52:07 PST From: Carl J Lydick To: "PIMACC::RELLISON"@east.pima.edu Message-ID: <0096FC95.E78E7CC0.11014@SOL1.GPS.CALTECH.EDU> Subject: Test. Please reply if you receive this Someone has reported having problems sending mail to you. I'm trying to help him track down the problem. If you receive this message (though I suspect you won't), please let me know. Thanks. ******************************************************************************** Then someone familiar with UCX might be able to comment on why UCX doesn't like the address: "PIMAC::RELLISON"@east.pima.edu and what "record not found" means in this context. Since you actually gave us the address that was causing trouble, I've done your work for you. Perhaps now a UCX guru can comment. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 21 Jul 1993 03:55:58 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: (Solved) Re: Help on applying VMS MAIL patch Date: 20 Jul 93 23:53:51 Message-ID: To: MX-List@WKUVX1.BITNET Hi There: I have solved the problem. The reason is simple: I had re-defined a command symbol PATCH to a DIFF-PATCH package. By the way, does anyone know how to use MX alias without typing MX%, Just like now I can type user@host.domain when sending mail? Thanks in advance. -- +--------------------------------------------------------------------------+ | Hanjin Miao | E-mail: MIAOH@U.WASHINGTON.EDU | | Electrical Engineering, FT-10 | MIAOH@RETEX.EE.WASHINGTON.EDU | | University of Washington | Tel: (206)685-1605 (O) EEB 534 | | Seattle, WA 98105 | (206)528-1285 (H) | | U. S. A. | Fax: (206)543-3842 (EE/UW) | +--------------------------------------------------------------------------+ ================================================================================ Archive-Date: Wed, 21 Jul 1993 03:56:03 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Help on applying VMS MAIL patch Date: 20 Jul 93 23:22:30 Message-ID: To: MX-List@WKUVX1.BITNET Hi There: I installed MX3.3 and tried to apply the VMSMAIL_PATCH.COM which comes with MX in the user contrib directory. As follow the instruction, I used the commond PATCH @DKB0:[MX.CONTRIB]VMSMAIL_PATCH.COM But the problem is, after I issued this command, there was no result ccome out after I wait for more than ten minutes. On the terminal, the DCL command prompt did not appear, unless I enter control-c or control-z to interrupt it. There was a file called PATCH****. file in my home directory with 0 blocks, and MAILSHR.EXE does not change at all. Since this is the first time I use PATCH in VMS 5.5-2, I don't know if there are any changes I need to make in VMSMAIL_PATCH.COM, or there are any problems I have? Could any one help me out? (by the way, MX runs without problems. I use MultiNet 3.0 and VMW5.5-2) Thanks a lot. Hanjin Miao EE Dept, U of Washington, Seattle MIAOH@RETEX.EE.WASHINGTON.EDU -- +--------------------------------------------------------------------------+ | Hanjin Miao | E-mail: MIAOH@U.WASHINGTON.EDU | | Electrical Engineering, FT-10 | MIAOH@RETEX.EE.WASHINGTON.EDU | | University of Washington | Tel: (206)685-1605 (O) EEB 534 | | Seattle, WA 98105 | (206)528-1285 (H) | | U. S. A. | Fax: (206)543-3842 (EE/UW) | +--------------------------------------------------------------------------+ ================================================================================ Archive-Date: Wed, 21 Jul 1993 04:46:10 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 21 Jul 1993 11:42:47 +0200 From: "GWDGV1::MOELLER" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Subject: Re: Handling DECNet forwarding references In response to someone else's problem, writes: > Then someone familiar with UCX might be able to comment on why UCX doesn't > like the address: > "PIMAC::RELLISON"@east.pima.edu > and what "record not found" means in this context. UCX (starting at 2.0, latest level is 2.0D, btw.) wants DECnet forwarding to be explicitly enabled; by default it is not, so it looks for an user `PIMAC::RELLISON' (in the above case) in the local SYSUAF.DAT ... Check out $ UCX SET CONFIG SMTP /OPTIONS=RELAY Wolfgang J. Moeller, GWDG, D-37018 Goettingen, F.R.Germany | Disclaimer ... PSI%(0262)45050352008::MOELLER Phone: +49 551 201516 | No claim intended! Internet: moeller@gwdgv1.dnet.gwdg.de | This space intentionally left blank. ================================================================================ Archive-Date: Wed, 21 Jul 1993 07:04:56 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 21 Jul 1993 07:04:46 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FD1D.C85D64D2.8464@WKUVX1.BITNET> Subject: RE: (Solved) Re: Help on applying VMS MAIL patch writes: > >By the way, does anyone know how to use MX alias without typing MX%, >Just like now I can type user@host.domain when sending mail? > You can use the undocumented MAIL command SET TRANSPORT MX%. Instructions are given in the MXALIAS on-line help (under HELP Using_Aliases). Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 21 Jul 1993 07:36:10 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 21 Jul 1993 05:28:11 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: rharwood@Data.Basix.COM Message-ID: <0096FD10.4AC49660.1295@Data.Basix.COM> Subject: SOLVED: Handling DECNet forwarding references Writes: > > Then someone familiar with UCX might be able to comment on why UCX doesn't > > like the address: > > "PIMAC::RELLISON"@east.pima.edu > > and what "record not found" means in this context. > > UCX (starting at 2.0, latest level is 2.0D, btw.) wants DECnet forwarding > to be explicitly enabled; by default it is not, so it looks for an user > `PIMAC::RELLISON' (in the above case) in the local SYSUAF.DAT ... > > Check out $ UCX SET CONFIG SMTP /OPTIONS=RELAY Thanks! The HELP file (and I'm sure the documentation, which isn't nearby) makes a reference to the use of MAIL-11 as a forwarder, and says nothing (directly!) about using DECnet to deliver to other locally-connected sites. I mistakenly assumed the "forwarder" reference was in the MX-record sense, and since we're "at the end of the world" connectivity-speaking, I assumed we had no need to function as a "forwarder". This boils down to "RTFM*5", I guess! Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Wed, 21 Jul 1993 10:17:57 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: (Solved) Re: Help on applying VMS MAIL patch Message-ID: <22jj1o$i53@cutter.clas.ufl.edu> From: Date: 21 Jul 1993 14:15:20 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096FD1D.C85D64D2.8464@WKUVX1.BITNET>, "Hunter Goatley, WKU" writes: > writes: >> >>By the way, does anyone know how to use MX alias without typing MX%, >>Just like now I can type user@host.domain when sending mail? >> >You can use the undocumented MAIL command SET TRANSPORT MX%. >Instructions are given in the MXALIAS on-line help (under HELP >Using_Aliases). Curious, this actually worked for my account somewhat. Mail across the cluster used MX%, however mail outside the cluster still got me an invalid user speci- fication from the @blah.blah.blah part of the address. Any thoughts? (The system here uses version 5.) -Steven S. Morgan ** Front Page Sports Football? Civ? Talk to me!! ltcomdata@ufcc.ufl.edu ** M.U.L.E.?!? Where is it?!!!! ================================================================================ Archive-Date: Wed, 21 Jul 1993 10:34:08 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 21 Jul 1993 10:33:57 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FD3B.016CE6DB.8531@WKUVX1.BITNET> Subject: RE: (Solved) Re: Help on applying VMS MAIL patch writes: > >>>By the way, does anyone know how to use MX alias without typing MX%, >>>Just like now I can type user@host.domain when sending mail? >>> >>You can use the undocumented MAIL command SET TRANSPORT MX%. >>Instructions are given in the MXALIAS on-line help (under HELP >>Using_Aliases). > >Curious, this actually worked for my account somewhat. Mail across the cluster >used MX%, however mail outside the cluster still got me an invalid user speci- >fication from the @blah.blah.blah part of the address. Any thoughts? (The >system here uses version 5.) As is documented in the MXALIAS help: The MX% prefix can be omitted from MX aliases when the default transport has been set. Note that non-alias "user@domain" addresses must still be prefixed. That's true unless you *also* apply the MAILSHR patch in the [CONTRIB] directory. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 21 Jul 1993 11:34:22 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 21 Jul 1993 10:24:25 EDT From: kenm@adhe.arknet.edu Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096FD39.AC935BA0.610@adhe.arknet.edu> Subject: allin1 Arkansas Department of Higher Education I N T E R O F F I C E M E M O R A N D U M Date: 07-21-1993 10:23am GMT From: KEN MCCOY KENM Dept: Information Services Tel No: 501-324-9300 FAX 501-324-9308 TO: Remote Addressee ( _mx-list@wkuvx1.bitnet ) Subject: allin1 Hello All-In-1 fans, How do you specify a rewrite rule in MX so that when the message is received into All-In-1 the return address (FROM: line) would look like _"MX-List@WKUVX1.BITNET" instead of MX%"MX-List@WKUVX1.BITNET". I've included the header that I see in All-In-1? Thanks in advance!!! Ken McCoy Arkansas Dept. of Higher Ed. ============================================================= ============================================================= Arkansas Department of Higher Education I N T E R O F F I C E M E M O R A N D U M Date: 06-30-1993 06:22pm GMT From: MX%"MX-List@WKUVX1.BITNET" MX%"MX-List@WKUVX1.BITNET"@MRGATE@SPEEDY Dept: Tel No: TO: kenm@A1 Subject: Rewrite Rules Return-Path: <@ULKYVM.LOUISVILLE.EDU:list-mgr@WKUVX1.BITNET> Received: from ULKYVM.LOUISVILLE.EDU by speedy.adhe.arknet.edu (MX V3.3 VAX) with SMTP; Wed, 30 Jun 1993 18:18:01 EDT Received: from ULKYVM.LOUISVILLE.EDU by ULKYVM.LOUISVILLE.EDU (IBM VM SMTP V2R1) with BSMTP id 5681; Wed, 30 Jun 93 19:18:34 EDT Received: from WKUVX1.BITNET by ULKYVM.LOUISVILLE.EDU (Mailer R2.08 R208004) with BSMTP id 7512; Wed, 30 Jun 93 19:18:32 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: list-mgr@WKUVX1.BITNET Sender: list-mgr@WKUVX1.BITNET Date: Thu, 01 Jul 1993 01:13:12 +0100 From: Per Hogstedt Reply-To: MX-List@WKUVX1.BITNET Subject: Rewrite Rules To: MX-List@WKUVX1.BITNET Message-ID: <0096ED35.5AEC8CE0.9960@plab.se> ================================================================================ Archive-Date: Wed, 21 Jul 1993 15:38:18 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 21 Jul 1993 15:24:47 -0500 (CDT) From: stewart.nichols@dir.texas.gov Reply-To: MX-List@WKUVX1.BITNET Subject: Copies of "Welcome To xxxx Mailing List" needed. To: MX-List@WKUVX1.BITNET CC: NICHOLS_SA@DIR.TEXAS.GOV Message-ID: <01H0T53D3PRQGW2B0B@DIR.TEXAS.GOV> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT I need to make up "Welcome To" messages for some mailing lists that my division will be supporting. I need some examples of what people are using. I did save the MX list messages, but that is the only one that I can find. If you manage a list or have saved the welcome message for new subscriber for some list that you are on, please send me a copy. Any and all sent before 1993-Jul-28 will be greatly appreciated. Thanks, *--------------------------------*-------------------------------------* * Stewart Nichols * * * Wide Area Network Specialist * My deadline is 1993-Jul-28. * * Dept. of Info Resources, Texas * * * * * * Work Phone: 512-463-7601 * * * stewart.nichols@dir.texas.gov * * *--------------------------------*-------------------------------------* ================================================================================ Archive-Date: Wed, 21 Jul 1993 16:40:03 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 21 Jul 1993 17:32:25 EDT From: Stuart Cohnen Reply-To: MX-List@WKUVX1.BITNET To: westerm@bchm1.aclcb.purdue.edu CC: MX-List@WKUVX1.BITNET Message-ID: <0096FD75.76B25CC0.2657@RUVMS2.ROCKEFELLER.EDU> Does the patch to mail that is included inthe MX 3.3 kit work with OpenVMS 6.0? I am interested in VMSMAIL_PATCH.TXT;2 which does away with MX%" thanks -- please reply directly, I'm not on the mailing list (although I should be ;-) Stuart +-----------------------------------------------+ |Stuart Cohnen (cohnen@rockvax.rockefeller.edu)| |Manager of Engineering and Technical Services | |The Rockefeller University/Computer Services | |1230 York Avenue | |New York, NY 10021 | |(212) 327-7509 Fax: (212) 327 8712 | +-----------------------------------------------+ ================================================================================ Archive-Date: Wed, 21 Jul 1993 17:28:27 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 21 Jul 1993 17:28:12 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: cohnen@RUVMS2.ROCKEFELLER.EDU Message-ID: <0096FD74.E06153B1.8779@WKUVX1.BITNET> Subject: The MAILSHR patch for VMS V6.0 Stuart Cohnen writes: > >Does the patch to mail that is included inthe MX 3.3 kit >work with OpenVMS 6.0? I am interested in VMSMAIL_PATCH.TXT;2 >which does away with MX%" > No, it doesn't. One that I think works (I'm not running V6.0 because of the Jnet/BSC problem) is available via ftp from ftp.spc.edu as [.MX.CONTRIB]MX_MAILSHR_PATCH.ZIP. You can also get it via e-mail by sending the following command(s) in the body of a mail message to FILESERV@WKUVX1.BITNET: SEND MX_MAILSHR_PATCH SEND FILESERV_TOOLS !Needed if you don't have MFTU and UNZIP >thanks -- please reply directly, I'm not on the mailing list (although I should >be ;-) > Yes, you should if you expect replies. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 22 Jul 1993 03:57:24 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 22 Jul 1993 11:58:55 EDT From: Esra ESEN Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FE10.0A726780.22713@trboun.bitnet> Subject: RE: about BILF.EXE Hi, >On Thu, 15 Jul 1993 06:32:38 CST, "Hunter Goatley, WKU" > posted: <> BTW, BILF is included with ZOO210, also available from my FILESERV. >This really ought to be included in the UNZIP package, too, Hunter -- in >both your FILESERV_TOOLS (or wherever it resides) set as well as in the >unz50p1x.* packages on quest.jpl.nasa.gov. The VMS/bilf/ area of the main I want to do ftp on quest.jpl.nasa.gov but I need IP number for this address. Can you write me IP number? Or how can I get? Thanx in advance Esra ======================================================================== Esra ESEN System Manager Bogazici Universitesi ESEN@TRBOUN.BITNET Bilgisayar Merkezi Telf.:263 15 40 / Ext.:1246 80815 Bebek/Istanbul ========================================================================= ================================================================================ Archive-Date: Thu, 22 Jul 1993 04:25:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 22 Jul 1993 11:20:38 +0100 From: Szalacsi Zsolt Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FE0A.B15898E0.6675@bmeik.eik.bme.hu> Subject: RE: about BILF.EXE You wrote: > Hi, > > >On Thu, 15 Jul 1993 06:32:38 CST, "Hunter Goatley, WKU" > > posted: <> BTW, BILF is included with > ZOO210, also available from my FILESERV. > > >This really ought to be included in the UNZIP package, too, Hunter -- > in >both your FILESERV_TOOLS (or wherever it resides) set as well as > in the >unz50p1x.* packages on quest.jpl.nasa.gov. The VMS/bilf/ area > of the main > > I want to do ftp on quest.jpl.nasa.gov but I need IP number for this > address. Can you write me IP number? Or how can I get? Thanx in > advance 128.149.75.43 > > Esra > > ======================================================================== > Esra ESEN System Manager > Bogazici Universitesi ESEN@TRBOUN.BITNET > Bilgisayar Merkezi Telf.:263 15 40 / Ext.:1246 > 80815 Bebek/Istanbul > ========================================================================= Zsolt ------------------------------------+------------------------------------------- Szalacsi Zsolt | internet : szzsolt@bmeik.eik.bme.hu | bitnet : szzsolt@hubme51.BITNET Centre of Information Systems, | X.25 : (2161)2802358801::szzsolt Technical University of Budapest | ella pf. : 5102 ------------------------------------+------------------------------------------- ================================================================================ Archive-Date: Thu, 22 Jul 1993 08:53:59 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 22 Jul 1993 08:53:30 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0096FDF6.235E9323.8968@WKUVX1.BITNET> Subject: MAILSHR patch for V6.0 Well, the MAILSHR patch I provided that includes V6.0 changes by David Cathey doesn't work under the final release of VMS V6.0. Anybody out there with V6.0 and some time on your hands? If so, please send me the changes so I can incorporate it here. It patchces some of it, then fails with: symbol "ALTER_TO" defined as 00011000 %PATCH-E-NODECODE, cannot decode instruction Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 22 Jul 1993 14:11:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 22 Jul 1993 14:21:59 EDT From: wbradford@UDCVAX.BITNET Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: wbradford@UDCVAX.BITNET Message-ID: <0096FE24.0733A020.26879@UDCVAX.BITNET> Subject: Question about MX V3.3 Upgrade We are currently running MX V3.1 on our SYSTEM disk under VMS V5.4-3 with Jnet V3.5. I was about to upgrade to MX V3.3 until I noticed something in the installation instructions. On page 2-4, section 2.6.1 under Installing Message Exchange, the manual says if MX is already installed on the system, and you keep the same queue directory, any files already in the queue will be retained. However, we want to install MX on one our user disks so we can take some of the work load off the SYSTEM disk. My questions are If we install the new MX version on a different disk, will MX V3.3 pick up the queuing files in the old MX V3.1 queue area without any problems ? If MX V3.3 does not pick up the queuing files (say during installation), can we copy the files into the new queue directory manually without any format problems? Any suggestions are welcomed and appreciated, William Bradford WBRADFOR@UDCVAX.BITNET ================================================================================ Archive-Date: Thu, 22 Jul 1993 14:25:42 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 22 Jul 1993 14:25:25 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FE24.81D055A8.9115@WKUVX1.BITNET> Subject: RE: Question about MX V3.3 Upgrade wbradford@UDCVAX.BITNET writes: > >On page 2-4, section 2.6.1 under Installing Message Exchange, >the manual says if MX is already installed on the system, and you keep the >same queue directory, any files already in the queue will be retained. >However, we want to install MX on one our user disks so we can take some of >the work load off the SYSTEM disk. > Always a good thing to do..... > My questions are > > If we install the new MX version on a different disk, will MX V3.3 pick up >the queuing files in the old MX V3.1 queue area without any problems ? > No, it won't. > If MX V3.3 does not pick up the queuing files (say during installation), >can we copy the files into the new queue directory manually without any >format problems? > No, because the format of the entries in SYSTEM_QUEUE has been changed. There is a program in the .A saveset that converts it; you could run that by hand. However, the *easiest* thing to do would be: o Install MX V3.3 over the top on V3.1 on the system disk. o Once that's done, use BACKUP to move the entire MX directory tree from the system disk to the new disk. o Modify SYS$STARTUP:MX_STARTUP.COM to refer to the new disk name. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Thu, 22 Jul 1993 17:01:55 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 22 Jul 1993 14:56:48 EDT From: kish@DRWHO.IAC.HONEYWELL.COM Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FE28.E407ED86.4029@DRWHO.IAC.HONEYWELL.COM> Subject: RE: MX ALIAS RE >I have 5762 ALiases I would like to load. :) > Whew!! Let me know if you have any problems! : Well I had not put the quotes arround "XXX@ZZZ". All is well loaded all 5K without problem except for duplicates. It was our MS mail users database..... Works fine Thanks Karl ================================================================================ Archive-Date: Thu, 22 Jul 1993 18:47:57 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MX SITE hangs on specific message Message-ID: <1993Jul22.104712.2148@dymaxion.ns.ca> Date: 22 Jul 93 10:47:12 AST To: MX-List@WKUVX1.BITNET My "MX Site Delivery" agent (MX V3.3) got hung on the message attached below. - Last night, the MX Site Delivery agent got hung up and started chewing all of our CPU. We shutdown MX which failed to shutdown the SITE delivery agent, so we did a STOP/PROCESS on it. - After we verified that everything had been shut down, we brought MX back up again. It started processing some smaller SITE bound messages and finished them successfully. Eventually, though, the router tried passing off the offending message to the SITE agent and the SITE agent hung again. Only this time, it didn't eat any CPU. - I had turned on MX_SITE_DEBUG, so I could see logs for the messages the SITE agent had delivered correctly, but a log was never produced for the offending message, indicating that SITE_DELIVER.COM probably never even began to run. - When I did an MCP QUEUE SHOW, it showed a router entry in the queue with status INPROG, and a SITE agent entry with status INPROG which was slightly smaller in size (don't have exact numbers for you, but it was something like 11,000 vs. 9,000 characters). I found the size discrepancy rather odd since, when I DIFF'ed the [MX.QUEUE.*].MSG_TEXT with the corresponding MX_SITE_DIR:*.TMP file, the only difference was that the MX_SITE_DIR version had the header added to it. There were no characters missing so far as I could tell. - After saving a copy of that .TMP file (which is the message included below) I cancelled the router entry. Now things are back to normal, but this is the second time this has happened this week. I'm baffled. Please help. Ben. -- Ben Armstrong (INTP), Software Development, bus: (902)422-1973 Dymaxion Research Ltd., fax: (902)421-1267 Halifax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca --- Here are the two .TMP files the SITE agent failed to process: $1$DIA0:[MX.SITE]SITE_ADR_C93BB740_0096FDAA_2020011E.TMP;1 $1$DIA0:[MX.SITE]SITE_MSG_C93BB740_0096FDAA_2020011E.TMP;1 Received: from ac.dal.ca by dymaxion.ns.ca (MX V3.3 VAX) with SMTP; Wed, 21 Jul 1993 23:53:13 ADT Received: from vm.utcc.utoronto.ca (MAILER@UTORONTO) by AC.DAL.CA (PMDF V4.2-13 #2545) id <01H0TMNDUONK007OD1@AC.DAL.CA>; Wed, 21 Jul 1993 23:53:02 -0300 Received: from UTORONTO.BITNET by vm.utcc.utoronto.ca (Mailer R2.10 ptf000) with BSMTP id 1241; Wed, 21 Jul 93 22:51:22 EDT Date: Wed, 21 Jul 1993 21:55:09 -0500 From: Phil Endacott Subject: Administrivia--Ground Rules!! Sender: Total Quality Management In Higher Education To: Multiple recipients of list TQM-L Reply-To: Total Quality Management In Higher Education Message-ID: <01H0TMNDUONM007OD1@AC.DAL.CA> Organization: UNIVERSITY OF KANSAS Content-Transfer-Encoding: 7BIT In the past 48 hours, there has been considerable discussion about the format, message content, and message volume on TQM-L. This type of discussion occurrs each time the message volume approaches 30 to 35 messages per day. If you don't like getting "lots of mail" you can always set your options to DIGESTS. You will receive 1 message per day and at the most 7 messages per week. Its your choice!! The daily DIGEST is totally uncensored and contains ALL MESSAGE TRAFFIC that has occurred in the past 24 hours. So PLEASE don't complain to all 652 members of this list about the fact that you might have to drop off the list because you can't cope with the mail volume!! Pete and I really don't care to hear about it privately EITHER. Theory Vs. Practice?? If someone thinks that another list should be started THEN START ONE!! Pete and I spend literally hours each day in the administration of this list and while I can't speak for Pete, I have absolutely no interest in starting a separate list. TQM-L was created as an unmoderated, free-flow, discussion forum for topics/subjects related to TQM in Higher Education. The mission statement remains the same. After 14 months and 5500 messages it is obvious to me that there are precious few practical applications that anyone cares to share with the list membership. Without the practical applications to stimulate discussion, we continue to discuss TQM philosophy, the need for a complete culture change, and grope for a definition of our "customers"!! That is just where we are in the process. IMPROVEMENTS?? In an attempt at continuous improvement of TQM-L, the following USER GUIDE (Ground Rules!!) has been prepared. It is in 3rd draft form and has room for much refinement. When it reaches a final form, it will become part of the WELCOME message for all new subscribers and be available as a help document in the TQM-L FILELIST that can be retrieved by any list member. This GUIDE is several screens long and if you have time to read/study it a bit, please make any "improvements" and return your inputs to me by private mail. Notice that I said "make any imporvements"--by that I mean YOU CHANGE IT TO READ THE WAY YOU WOULD LIKE IT TO BE. Thanks for reading!!! ;-)) . . . Phil--- ------------------- DRAFT (930705) TQM-L USER GUIDE---------------- Our sincere thanks to Joan Korenman, Listowner of WMST-L, for allowing us to use the basic format of her Users Guide. Special thanks to Joanne Cate for her expert editing skills in customizing the guide to our needs. And, particular thanks to Pete Weiss for making sure that the guide is technically correct. This guide lists some of the most commonly asked questions about using TQM-L. They deal with the following topics: 1. Format for messages to the list 2. Where to send messages (difference between LISTSERV@UKANVM and TQM-L@UKANVM) 3. Stopping mail temporarily 4. TQM-L digest 5. Unexpected mail stoppage 6. Getting a list of subscribers 7. Copies of your postings 8. Replying privately versus to everyone on the TQM-L list 9. TQM-L Archives 10. TQM-L Files 11. Related lists Please read through the guide before sending any messages to TQM-L, and then save the guide for future reference. ---------------------------------------------------------------------- 1. "IS THERE A PREFERRED FORMAT TO USE FOR MESSAGES SENT TO THE LIST (I.E., TO TQM-L@UKANVM OR TQM-L@UKANVM.CC.UKANS.EDU)?" Yes. First of all, ALWAYS put your name and e-mail address(es) at the end of every posting. (It is important that people be able to contact you privately if they wish, and some mail systems do not identify the writer anywhere in the header.) Also, please include a meaningful subject heading, so that people will know whether your message deals with a topic of interest to them. Finally, if you are replying to someone else's posting, briefly quote or summarize that posting before you offer your reply. Doing so will make your message clearer and avoid confusion. (New subscribers are continually joining the list; they may not have read the original message. And since a number of topics are often being discussed on the list at any given moment, even long-time subscribers may not remember what prompted your remarks unless you remind them.) --------------------------------------------------------------------- 2. "WHAT IS THE DIFFERENCE BETWEEN LISTSERV@UKANVM AND TQM-L@UKANVM? HOW DO I TELL WHICH ADDRESS TO USE?" TQM-L@UKANVM (or TQM-L@UKANVM.CC.UKANS.EDU on the Internet) should be used ONLY for messages that you wish to send to *all* TQM-L subscribers. Messages concerning your TQM-L subscription should be sent to LISTSERV@UKANVM (or on Internet to LISTSERV@UKANVM.CC.UKANS.EDU). For example, send messages to LISTSERV@UKANVM, not TQM-L@UKANVM, when you wish to issue any one of the following commands: If you want to Then you must type the command --------------- ------------------------------ Cancel your subscription: UNSUB TQM-L Stop receiving mail temporarily: SET TQM-L NOMAIL Start receiving mail again: SET TQM-L MAIL See who is subscribed to TQM-L: REVIEW TQM-L Request messages in Digested format SET TQM-L DIGESTS NOTE: If you subscribed under a Bitnet address and sent your subscription request to LISTSERV's Bitnet address , you must send ALL subsequent mail to the list's Bitnet addresses (i.e., LISTSERV@UKANVM or TQM-L@UKANVM). Similarly, if you subscribed under an Internet address and sent your subscription request to LISTSERV's Internet address (LISTSERV@UKANVM.CC.UKANS.EDU), you must send ALL subsequent mail the the list's Internet addresses. If you try to set your subscription to NOMAIL or you try to signoff and are told you do not have a subscription, chances are you are sending your request to the wrong address for LISTSERV. Simply try the other address. (See also Section 3 below.) For more extensive information about LISTSERV commands, send a note to LISTSERV@UKANVM (or, LISTSERV@UKANVM.CC.UKANS.EDU) with the following two-word message: INFO GENINTRO. You will receive a file entitled LISTSERV.MEMO. (See Section 11 below for how to retrieve files sent to you in Netdata format.) If you have a question about your subscription that you want a human being to read, do NOT send it to TQM-L@UKANVM (Bitnet) or to TQM-L@UKANVM.CC.UKANS.EDU (Internet) nor to LISTSERV@UKANVM (Bitnet) or LISTSERV@UKANVM.CC.UKANS.EDU (Internet). Instead, send your note to the one of the List Co-owners, Phil Endacott or OR Peter M. Weiss or . ---------------------------------------------------------------------- 3. "I AM GOING ON VACATION FOR SEVERAL WEEKS. CAN I STOP MAIL WHILE I'M AWAY, OR DO I HAVE TO UNSUBSCRIBE?" You can stop mail temporarily by sending a note to LISTSERV@UKANVM (if you subscribed on Bitnet) or LISTSERV@UKANVM.CC.UKANS.EDU (if you subscribed on Internet) with the following message: SET TQM-L NOMAIL (Note: "NOMAIL" is one word) When you want mail to start arriving again, send the following message to the same address (as given above) SET TQM-L MAIL NOTE: Be sure to send these messages to LISTSERV, *not* to TQM-L! Also, see Section 3) above. ---------------------------------------------------------------------- 4. "DOES TQM-L EXIST IN A DIGEST FORMAT?" With the release of REVISED LISTSERV 1.7f, a digest is available to subscribers as a subscriber defined OPTION. If receiving 35+ individual mail messages works an undue hardship on you, you may elect to receive the DIGEST of all the daily mail messages in ONE MESSAGE!! This digest is UNEDITED and will contain ALL MESSAGES processed by LISTSERV to TQM-L subscribers in a 24 hour period. You may request the DIGEST by sending mail to: LISTSERV@UKANVM.Bitnet (or LISTSERV@UKANVM.CC.UKANS.EDU) containing the one line command: SET TQM-L DIGEST You may cancel your DIGEST option my sending a mail message containing the one line command: SET TQM-L MAIL NOTE: Be sure to send these messages to LISTSERV, *not* to TQM-L! Also, see Section 3) above. ---------------------------------------------------------------------- 5. "WHAT SHOULD I DO IF MAIL FROM TQM-L SUDDENLY STOPS?" Occasionally, mail sent from TQM-L may fail to reach you. If you notice that you haven't received any TQM-L mail for at least 24 hours, you should do the following: a. Send the following two-word message to LISTSERV@UKANVM (if you subscribed under a Bitnet address) or LISTSERV@UKANVM.CC.UKANS.EDU (if you subscribed under an Internet address): QUERY TQM-L If you get back a message saying that you are not subscribed to TQM-L, send the QUERY TQM-L message to the other LISTSERV address (i.e., if you sent the message to LISTSERV@UKANVM, try sending the same message to LISTSERV@UKANVM.CC.UKANS.EDU). If your message is successful, you should get back a message from LISTSERV telling you how your "options" are set. The key part will look something like this: > Query TQM-L Distribution options for Jane Doe , list TQM-L: Ack= Yes, Mail= Yes, Files= Yes, Repro= No, Header= Short, Conceal= No Your options may vary; the important part is Mail=Yes. If it says Mail=No, that means your subscription has been set to NOMAIL. The most likely explanation for its being set to NOMAIL is that mail started to bounce and so we (List Co-Owners) set your subscription to NOMAIL. If you have been receiving other mail, the problem was probably short-lived and you can set your subscription back to MAIL (for instructions, see item b. below). If the reply from LISTSERV says MAIL=YES, contact your computer support staff to find out whether they're aware of a mail problem. If they don't know of any problem, contact the list owner privately. (Do not send mail to TQM-L@UKANVM but rather to one of the Co-owners of the list, Phil Endacott, whose address is: or OR Peter M. Weiss or . b. To set your subscription back to MAIL, simply send the following message to LISTSERV@UKANVM or LISTSERV@UKANVM.CC.UKANS.EDU (if one doesn't work, try the other): SET TQM-L MAIL If you have questions or encounter problems, please write to one of the List Co-owners, Phil Endacott or Peter Weiss. (See addresses in a. above) Under NO circumstances should you send messages about your subscription to TQM-L@UKANVM.Bitnet or TQM-L@UKANVM.CC.UKANS.EDU (Internet). ---------------------------------------------------------------------- 6. "HOW CAN I GET A LIST OF SUBSCRIBERS TO TQM-L?" To get a current list of TQM-L subscribers, send the following message to LISTSERV@UKANVM (Bitnet) or LISTSERV@UKANVM.CC.UKANS.EDU (Internet): REVIEW TQM-L You will get back either a mail message with the subject heading "FILE: 'TQM-L LIST' BEING SENT TO YOU" or a message telling you that the list is being sent as a Netdata file (not a mail file); LISTSERV apparently chooses which method to use. (See Section 11 below for instructions on how to retrieve files sent in Netdata format.) Either way, the file contains a list of subscribers, arranged alphabetically by e-mail node (the part of the e-mail address after the "@" sign), not by subscriber's name. If you prefer to receive the list sorted more or less alphabetically by subscriber's last name, send the following command: REVIEW TQM-L BY NAME --------------------------------------------------------------------- 7. "HOW CAN I BEGIN RECEIVING COPIES OF *MY* MESSAGES TO THE LIST?" TQM-L is NOT set up so that people receive copies of the messages they post to the list. If you do wish to receive such copies, simply send a note to LISTSERV@UKANVM (if you subscribed under your Bitnet address) or to LISTSERV@UKANVM.CC.UKANS.EDU (if you subscribed under your Internet address) with the following message: SET TQM-L REPRO If you would like to receive a mail acknowledgement of your posting but not a copy, enter a command line that says: SET TQM-L ACK ---------------------------------------------------------------------- 8. WHEN SHOULD I REPLY PRIVATELY RATHER THAN TO TQM-L@UKANVM? You should send replies to TQM-L when the contents are likely to be of interest to a number of subscribers (most suggestions for reading lists and TQM applications fall into this category). However, if you are writing to request a copy of a paper someone has mentioned, please send your request privately, NOT to TQM-L. Similarly, comments directed at a particular person (e.g., "Right on, Pete. Good point," or "Thanks for the info," or "What a horrendous experience that must have been. I don't know why people do such things," or "Hi, Jane, I'm glad to see you've joined the list. Write to me," etc.) should be sent privately, NOT to TQM-L. Also, short general statements of approval or disapproval (e.g., "Hooray! I'm glad someone finally said that!" or "I can't imagine how anyone can believe such nonsense") should NOT be sent to TQM-L. ---------------------------------------------------------------------- 9. I'VE BEEN AWAY FOR TWO WEEKS. I'D LIKE TO SEE WHAT I'VE MISSED ON TQM-L DURING THE TIME I'VE BEEN GONE. IS IT POSSIBLE TO ACCESS PREVIOUS MESSAGES?? (Also useful for new subscribers) Yes. All TQM-L messages are automatically archived. The archives are arranged in weekly logs To find out what logs are available, you can send LISTSERV@UKANVM (Bitnet) or LISTSERV@UKANVM.CC.UKANS.EDU (Internet) the following command: INDEX TQM-L You will then receive a list of the available logs. To obtain the logs, send LISTSERV the following command: GET TQM-L |filename| where |filename| is the name of the log file you want. For example: GET TQM-L LOG9205C will get you the May '92 third week log (9205 refers to the 5th month of 1992 and C is the 3rd week of the month). --------------------------------------------------------------------- 10. HOW DO I FIND OUT WHAT FILES ARE AVAILABLE FROM TQM-L, AND HOW DO I OBTAIN THE FILES I WANT?? To find out what files are available, send to LISTSERV@UKANVM (Bitnet) or to LISTSERV@UKANVM.CC.UKANS.EDU (Internet) the same command mentioned in the previous Section: INDEX TQM-L The list you will receive from LISTSERV includes files as well as logs. To obtain the file(s) you want, send to LISTSERV@UKANVM (or LISTSERV@UKANVM.CC.UKANS.EDU) the following command: GET |filename| TQM-L where |filename| is the name of the file you want. For example: GET TQM-L WELCOME TQM-L Note that |filename| consists of two words separated by a space and not a period. (Adding TQM-L after the two-word filename is optional; it simply makes sure that if two lists have a file with the same name, you'll get the right one.) If your e-mail address is on a VAX/VMS machine, when you get a message that one or more files have arrived at your e-mail address, you should type "RECEIVE *" (do not include the quotation marks) at the $ prompt. This command will put the file(s) into your main directory. You can then type "TYPE filename" (replace "filename" with the actual name of the file) to read the file. If it's a long file, you can read it more effectively by typing "TYPE/PAGE filename." If your e-mail address is on an IBM VM/CMS machine, either use your mailer front end or type RLIST and RECEIVE the file into your FLIST. Go into your FLIST to look at the file. If your e-mail address is on a different kind of machine OR you are using PROFS or some other kind of similar mailing system, go ahead and try the above commands. If they do not work, CALL YOUR COMPUTER SERVICES OFFICE. The people there should be able to help you and/or give you a manual for your mailing system commands. ---------------------------------------------------------------------- 11. THE LIST'S "WELCOME" LETTER MAKES IT CLEAR THAT TQM-L HAS BEEN ESTABLISHED TO DEAL WITH TOTAL QUALITY MANAGEMENT ISSUES IN HIGHER EDUCATION. WHAT ELECTRONIC FORUMS EXIST FOR DISCUSSION OF OTHER ACADEMIC DISCIPLINES?? PREFATORY NOTE: Lists with LISTSERV or COMSERVE addresses are managed with automated software. To subscribe to such a list, send the following message to the address given: SUB , where is the name of the list and is your real name, not your e-mail account id (e.g., SUB GENDER Jane Doe). For lists that do not have LISTSERV or COMSERVE addresses, be sure to include your name and e-mail address at the end of your message asking to subscribe. Also, some lists have only Bitnet or only Internet addresses. If you encounter problems sending mail to these lists, ask the computer people at your institution for help. GENERAL LISTS: Network-wide ID Full address List title --------------- ------------ ---------- ASHE-L ASHE-L@MIZZOU1 Association for the Study of Higher Educatio+ ASSESS ASSESS@UKCC ASSESS "Assessment in Higher Education" BMW92 BMW92@UVMVM BMW92: Summer Institute for Women in Higher + CBEHIGH CBEHIGH@BLEKUL11 CBEHIGH list : Computer Based Education in h+ CIO-L CIO-L@WVNVM Higher Education Chief Information Officers IBM-HESC IBM-HESC@PSUORVM IBM Higher Education Consortium STAFFGOV STAFFGOV@NDSUVM1 Staff Governance in Higher Education STLHE-L STLHE-L@UNBVM1 Forum for Teaching & Learning in Higher Educ. Thank you for wading through this rather long and perhaps boring WELCOME messag and USERS GUIDE. We hope it is helpful to you and will assist in your enjoyment of your networking experiences. If we can be of further help, don't hesitate to ask us for help: TQM-L CO-OWNERS: Pete Weiss PMW1@PSUVM.PSU.EDU Phil Endacott Supervisor@SWEEP.FO.UKANS.EDU -- =-=-=-=-=-=-=-=-=-=-=-=-=-PHIL ENDACOTT (PE38)=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |*| Facilities Operations | |*| |*| Lawrence, Kansas 66045 | |*| |*| FAX: 913-864-4707 | |*| |*| WORK:913-864-3204 | Co-Owner: TQM-L, LDBASE-L, JANITORS |*| =-=-=-=-=-=-=-=-=-=-=-=-=THE UNIVERSITY OF KANSAS=-=-=-=-=-=-=-=-=-=-=-=-=-= -- Ben Armstrong (INTP), Software Development, bus: (902)422-1973 Dymaxion Research Ltd., fax: (902)421-1267 Halifax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca ================================================================================ Archive-Date: Thu, 22 Jul 1993 21:12:26 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: MLF bug? Message-ID: <1993Jul22.104725.15455@vax.oxford.ac.uk> Date: 22 Jul 93 10:47:25 BST To: MX-List@WKUVX1.BITNET Hi, I've discovered an undocumented feature (or maybe it's a bug :-) ) in MLF. I recently defined a new mailing list, and for some reason I put the ADD_MESSAGE filename in lowercase ans surrounded it with double quotes. Now this was accepted quite happily by MCP, but when anybody subscribed to the list they did not receive the file. When I altered the list definition so that the filename was in upper case, new subscribers did receive the file. As far as I can see the documentation does not say anything about whether this filename should be in upper or lower case. BTW the same thing happened with the REMOVE_MESSAGE. I'm running MX v3.3 Dave -- David Hastings | "The technical axiom that nothing is VAX Systems Programmer | impossible sinisterly conditions one to Oxford University Computing Services| the pitfall corollary that nothing is daveh@vax.oxford.ac.uk | ridiculous" ================================================================================ Archive-Date: Thu, 22 Jul 1993 21:31:49 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 22 Jul 1993 21:31:36 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FE60.0B214322.9305@WKUVX1.BITNET> Subject: RE: MLF bug? writes: > >I've discovered an undocumented feature (or maybe it's a bug :-) ) in MLF. > Yep, it is (actually, it's an MCP problem, not MLF). >I recently defined a new mailing list, and for some reason I put the ADD_MESSAGE >filename in lowercase ans surrounded it with double quotes. Now this was >accepted quite happily by MCP, but when anybody subscribed to the list they did >not receive the file. When I altered the list definition so that the filename >was in upper case, new subscribers did receive the file. > >As far as I can see the documentation does not say anything about whether this >filename should be in upper or lower case. > It's not the case, but rather the quotes around the file name. MCP stores the quotes as part of the file name. When MLF tries to open "X.X", it fails. So leave the quotes off and go upper. 8-) I'll fix that in MX V3.4. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 23 Jul 1993 09:28:31 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <930723153734> Date: Fri, 23 JUL 93 16:16 GMT From: rok.vidmar@uni-lj.si Reply-To: MX-List@WKUVX1.BITNET Subject: Wishlist: MCP STATUS To: MX-list@WKUVX1.BITNET I believe two enhancements for MCP STATUS are in place: - Agent type column should include agent name as accepted by MCP and MX_STARTUP.COM; - /NODE qualifier should be accepted to display selected cluster node(s) only. Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +38 61 186439 61000 Ljubljana fax: +38 61 186358 Slovenia ================================================================================ Archive-Date: Sat, 24 Jul 1993 13:03:47 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Handling DECNet forwarding references Message-ID: <1993Jul23.111905.28876@sparc4.ncu.edu.tw> Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 23 Jul 1993 11:19:05 GMT To: MX-List@WKUVX1.BITNET Hello there... Who can tell me where I can get the source code of mx mail in VMS And my version of VMS is VMS 5.4.. Thanks.... ================================================================================ Archive-Date: Sat, 24 Jul 1993 13:04:41 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: MLF bug? Message-ID: <1993Jul23.123801.15474@vax.oxford.ac.uk> From: Reply-To: MX-List@WKUVX1.BITNET Date: 23 Jul 93 12:38:01 BST To: MX-List@WKUVX1.BITNET In article <0096FE60.0B214322.9305@WKUVX1.BITNET>, "Hunter Goatley, WKU" writes: > writes: >> >>I've discovered an undocumented feature (or maybe it's a bug :-) ) in MLF. >> > Yep, it is (actually, it's an MCP problem, not MLF). > >>I recently defined a new mailing list, and for some reason I put the ADD_MESSAG > E >>filename in lowercase ans surrounded it with double quotes. Now this was >>accepted quite happily by MCP, but when anybody subscribed to the list they did >>not receive the file. When I altered the list definition so that the filename >>was in upper case, new subscribers did receive the file. >> >>As far as I can see the documentation does not say anything about whether this >>filename should be in upper or lower case. >> > It's not the case, but rather the quotes around the file name. MCP > stores the quotes as part of the file name. When MLF tries to open > "X.X", it fails. So leave the quotes off and go upper. 8-) > > I'll fix that in MX V3.4. > OK, thanks, Hunter. Dave -- David Hastings | "The technical axiom that nothing is VAX Systems Programmer | impossible sinisterly conditions one to Oxford University Computing Services| the pitfall corollary that nothing is daveh@vax.oxford.ac.uk | ridiculous" ================================================================================ Archive-Date: Sat, 24 Jul 1993 13:04:50 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Question about MX V3.3 Upgrade Date: 23 Jul 1993 20:01:45 GMT Message-ID: <22pg39INNh6r@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <0096FE24.0733A020.26879@UDCVAX.BITNET>, wbradford@UDCVAX.BITNET writes: =On page 2-4, section 2.6.1 under Installing Message Exchange, =the manual says if MX is already installed on the system, and you keep the =same queue directory, any files already in the queue will be retained. =However, we want to install MX on one our user disks so we can take some of =the work load off the SYSTEM disk. = = My questions are = = If we install the new MX version on a different disk, will MX V3.3 pick up =the queuing files in the old MX V3.1 queue area without any problems ? = = If MX V3.3 does not pick up the queuing files (say during installation), =can we copy the files into the new queue directory manually without any =format problems? = = Any suggestions are welcomed and appreciated, Why not backup the MX directory tree to the user disk, THEN do the upgrade? -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Sat, 24 Jul 1993 13:04:59 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: The MAILSHR patch for VMS V6.0 Message-ID: <1993Jul22.183627.17931@alpha.montagar.com> From: Reply-To: MX-List@WKUVX1.BITNET Date: 22 Jul 93 18:36:27 CDT To: MX-List@WKUVX1.BITNET In article <0096FD74.E06153B1.8779@WKUVX1.BITNET>, "Hunter Goatley, WKU" writes: > Stuart Cohnen writes: >> >>Does the patch to mail that is included inthe MX 3.3 kit >>work with OpenVMS 6.0? I am interested in VMSMAIL_PATCH.TXT;2 >>which does away with MX%" >> > No, it doesn't. One that I think works (I'm not running V6.0 because > of the Jnet/BSC problem) is available via ftp from ftp.spc.edu as > [.MX.CONTRIB]MX_MAILSHR_PATCH.ZIP. You can also get it via e-mail by > sending the following command(s) in the body of a mail message to > FILESERV@WKUVX1.BITNET: > > SEND MX_MAILSHR_PATCH > SEND FILESERV_TOOLS !Needed if you don't have MFTU and UNZIP If this is the one that I created, it doesn't work. It was done on V6.0-FT3, and they have changed MAILSHR (again) for the actual V6.0 release. For the V6.0 patch, you might try my file server at: FILESERV@montagar.com In the body of the message, include the command: SEND VMSMAIL_PATCH You might want to get another copy, too, Hunter! > Hunter > ------ > Hunter Goatley, VMS Systems Programmer, Western Kentucky University > goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - David L. Cathey |INET: davidc@montagar.com Montagar Software Concepts |UUCP: ...!montagar!davidc P. O. Box 260772, Plano TX 75026-0772 |Fone: (214)-618-2117 ================================================================================ Archive-Date: Sat, 24 Jul 1993 16:40:10 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 24 Jul 1993 16:39:59 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0096FFC9.A2E8202B.9810@WKUVX1.BITNET> Subject: Re: Handling DECNet forwarding references writes: > >Hello there... > > Who can tell me where I can get the source code of mx mail in VMS > And my version of VMS is VMS 5.4.. > Thanks.... > The binaries and sources for MX V3.3 are available via anonymous ftp from ftp.spc.edu in [.MX.MX033]. You can get them via e-mail by sending the following commands in the body of a mail message to FILESERV@WKUVX1.BITNET: SEND MX033 SEND MX033_SRC SEND FILESERV_TOOLS Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sat, 24 Jul 1993 23:58:49 CDT Sender: list-mgr@WKUVX1.BITNET Date: Sat, 24 Jul 1993 23:58:34 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <00970006.E82C553E.9854@WKUVX1.BITNET> Subject: New MAILSHR patch for VMS V6.0 Thanks to David Cathey, the *correct* VMS Mail MAILSHR patch for VMS V6.0 (the patch allows you to omit MX%"") has been added to ftp.spc.edu and FILESERV@WKUVX1.BITNET. Via FTP, it's [.MX.CONTRIB]MX_MAILSHR_PATCH.ZIP. From FILESERV, it's MX_MAILSHR_PATCH. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Sun, 25 Jul 1993 15:40:59 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <2952698185.0.p00128@psilink.com> Date: Sun, 25 Jul 93 10:57:30 -0500 To: mx-list@WKUVX1.BITNET From: "Barry Raveendran Greene" Reply-To: MX-List@WKUVX1.BITNET Subject: Could someone please remove me from MX-List? To the Listmanager, Could you please drop my old E-mail address from the MX List? I have tried sending message to the listserver and the list-mgr with no success. My subscription address was either greenebl@peocu1.navy.mil or greenebl@peocu1.peocu.navy.mil. I've got a USENet feed so I no longer need the E-mail subscription. Thanks, ********************************************************************** | Barry Raveendran Greene Tel: +1 (703) 273-1734 | | System & Network Engineer | | | | Internet: p00128@psilink.com | | X.400: C=CH ADMD=arcom PRMD=switch O=com OU=psilink PN=p00128 | | | | "All effort and exertion put forth by man from the fullness | | of his heart is worship, if it is prompted by the highest | | motives and the will to do service to humanity." | | - Abdu'l-Baha | | The Baha'i Faith | ********************************************************************** ------- End of Forwarded Message ********************************************************************** | Barry Raveendran Greene Tel: +1 (703) 273-1734 | | System & Network Engineer | | | | Internet: p00128@psilink.com | | X.400: C=CH ADMD=arcom PRMD=switch O=com OU=psilink PN=p00128 | | | | "All effort and exertion put forth by man from the fullness | | of his heart is worship, if it is prompted by the highest | | motives and the will to do service to humanity." | | - Abdu'l-Baha | | The Baha'i Faith | ********************************************************************** ================================================================================ Archive-Date: Mon, 26 Jul 1993 10:07:32 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 26 Jul 1993 17:01:13 EDT From: Jo Lejeune Reply-To: MX-List@WKUVX1.BITNET To: MX-List%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU Message-ID: <0097015E.EF352460.115@licr.ucl.ac.be> Subject: RE: MX-LIST Administrivia: Monthly Post SIGNOFF MX-List ================================================================================ Archive-Date: Tue, 27 Jul 1993 10:26:11 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: MX SITE hangs on specific message Message-ID: <1993Jul27.112304.2154@dymaxion.ns.ca> Date: 27 Jul 93 11:23:04 AST To: MX-List@WKUVX1.BITNET I'm still having problems with MX->SITE getting hung up. This is the fourth time recently. I haven't a clue what is going on. I thought it might be because the message is being delivered during an ANU-NEWS add run of the gatewayed mail batches, but the time of creation of the queue entries don't coincide with the newsskim runs. Someone please help. Ben. P.S. In the subsequent MX->SITE failures, there was no size discrepancy in the queue entries, so I've dropped that point from my trouble report below. ---- In article <1993Jul22.104712.2148@dymaxion.ns.ca>, bg@dymaxion.ns.ca (Ben Armstrong) writes: > My "MX Site Delivery" agent (MX V3.3) got hung on the message attached > below. > > - Last night, the MX Site Delivery agent got hung up and started > chewing all of our CPU. We shutdown MX which failed to shutdown the > SITE delivery agent, so we did a STOP/PROCESS on it. > - After we verified that everything had been shut down, we brought MX > back up again. It started processing some smaller SITE bound > messages and finished them successfully. Eventually, though, the > router tried passing off the offending message to the SITE agent and > the SITE agent hung again. Only this time, it didn't eat any CPU. > - I had turned on MX_SITE_DEBUG, so I could see logs for the messages > the SITE agent had delivered correctly, but a log was never produced > for the offending message, indicating that SITE_DELIVER.COM probably > never even began to run. > - After saving a copy of the .TMP files (which are the files included > below) I cancelled the router entry. > > Now things are back to normal, but this is the second time this has > happened this week. I'm baffled. Please help. > > Ben. Ben Armstrong (INTP), Software Development, bus: (902)422-1973 Dymaxion Research Ltd., fax: (902)421-1267 Halifax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca ================================================================================ Archive-Date: Tue, 27 Jul 1993 10:35:51 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 27 Jul 1993 10:35:36 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009701F2.3ABCC445.10394@WKUVX1.BITNET> Subject: Re: MX SITE hangs on specific message writes: > >I'm still having problems with MX->SITE getting hung up. This is the >fourth time recently. I haven't a clue what is going on. I thought >it might be because the message is being delivered during an ANU-NEWS >add run of the gatewayed mail batches, but the time of creation of the >queue entries don't coincide with the newsskim runs. > I found your original note again last night and realized that I never followed it up---sorry. (FYI: My wife and I are now expecting our second child, due sometime in March; she's been feeling pretty blah lately, so I've been home more than usual, which is why I haven't replied (yet) to several posts here....) >> My "MX Site Delivery" agent (MX V3.3) got hung on the message attached >> below. [...] >> - I had turned on MX_SITE_DEBUG, so I could see logs for the messages >> the SITE agent had delivered correctly, but a log was never produced >> for the offending message, indicating that SITE_DELIVER.COM probably >> never even began to run. Have you tried turning on router debug too just to see what it says about the message? I saw nothing obviously wrong with the message itself. The only thing I can think of is that there may be a bug in the SITE_DELIVER.COM (or a program it's running). Since MX->SITE was the process hanging, it had to have been processing the message, so I don't know why you didn't get a debug log for it. If it happens again, use F$GETJPI(MX->SITE's PID,"IMAGNAME") to see what image it's running (which might just be DCL). Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 27 Jul 1993 10:48:32 CDT Sender: list-mgr@WKUVX1.BITNET Date: 27 Jul 1993 11:40:45 -0500 (EST) From: Teresa Feck Reply-To: MX-List@WKUVX1.BITNET Subject: unzip.exe To: mx-list@WKUVX1.BITNET Message-ID: <01H11AQJKNEA9S5R26@TOE.TOWSON.EDU> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Date sent: 27-JUL-1993 11:41:25 I looking for the unzip utility on a ftp site that will unzip the latest version of MX [033]. Thanks in Advance Teresa _______________________________ Teresa J. Feck Internet: feck@fre.fsu.umd.edu Academic Computing Bitnet: feck@towson.edu Frostburg State University Phonemail: (301) 689-7090 Frostburg, Maryland 21532 ================================================================================ Archive-Date: Tue, 27 Jul 1993 10:54:17 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 27 Jul 1993 10:54:02 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009701F4.CE1B0FC4.10402@WKUVX1.BITNET> Subject: RE: unzip.exe Teresa Feck writes: > >Date sent: 27-JUL-1993 11:41:25 > >I looking for the unzip utility on a ftp site that will unzip the latest >version of MX [033]. > There's an UNZIP.EXE in [.MX] on ftp.spc.edu. The sources and binaries for UnZip (and Zip) are on ftp.spc.edu in: [.MACRO32.SAVESETS]ZIP19P1.ZIP [.MACRO32.SAVESETS]UNZIP50P1.ZIP Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 27 Jul 1993 11:01:45 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 27 Jul 1993 08:55:35 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: rharwood@Data.Basix.COM Message-ID: <009701E4.41FA4100.1765@Data.Basix.COM> Subject: RE: unzip.exe > I looking for the unzip utility on a ftp site that will unzip the latest > version of MX [033]. If you got MX from ftp.spc.edu, you probably went right by it. Look in the [.MX] directory for UNZIP.EXE. Remember to TENEX before retrieving. Note: It's been my experience that you should NOT use TENEX before retrieving any MXnnn.ZIP file, though I dont' remember reading that anywhere. Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Tue, 27 Jul 1993 13:56:26 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 26 Jul 1993 16:44:47 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0097015C.A3B3D600.11539@swdev.si.com> Subject: Upgrading the underlying TCP/IP Does one need to re-install MX if one upgrades from UCX 1.3A to DEC TCP/IP V2.0D? ================================================================================ Archive-Date: Tue, 27 Jul 1993 13:57:19 CDT Sender: list-mgr@WKUVX1.BITNET Date: Mon, 26 Jul 1993 14:54:30 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <0097014D.3B3752A0.11411@swdev.si.com> Subject: Floating periods I realize that SMTP mail uses a period on a line by itself to terminate a message, but does this mean that messages in which someone has embedded a period on a line by itself should be truncated at that point. Today someone sent a message via MX to some people on our VMS system. They had inadvertently separated the period in the abbreviation "etc." from the "etc" part and had placed it on the next line. The message the VMS people received was truncated at the "etc" line. Shouldn't this condition be handled somehow? I had the impression that at least some other SMTP mailers were able to handle this. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Tue, 27 Jul 1993 14:02:48 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 27 Jul 1993 14:02:28 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097020F.20DD45D7.10438@WKUVX1.BITNET> Subject: RE: Upgrading the underlying TCP/IP "Brian Tillman" writes: > >Does one need to re-install MX if one upgrades from UCX 1.3A to DEC TCP/IP >V2.0D? No, it's not necessary. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 27 Jul 1993 14:12:00 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 27 Jul 1993 14:11:39 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00970210.6969CAAE.10446@WKUVX1.BITNET> Subject: RE: Floating periods "Brian Tillman" writes: > >I realize that SMTP mail uses a period on a line by itself to terminate a >message, but does this mean that messages in which someone has embedded a period >on a line by itself should be truncated at that point. Today someone sent a >message via MX to some people on our VMS system. They had inadvertently >separated the period in the abbreviation "etc." from the "etc" part and had >placed it on the next line. The message the VMS people received was truncated >at the "etc" line. > >Shouldn't this condition be handled somehow? I had the impression that at >least >some other SMTP mailers were able to handle this. It's not up to the incoming SMTP mailer, but rather the "client" side. If you send mail from VMS Mail through MX, any period at the beginning of the line is doubled by the SMTP agent. The SMTP server on the remote system is supposed to strip off the extra "." when processing the message. Sounds like the SMTP mailer on the origin system didn't double the ".". Here are some to show that it works: . . . Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Tue, 27 Jul 1993 17:25:15 CDT Sender: list-mgr@WKUVX1.BITNET Date: Tue, 27 Jul 1993 15:20:45 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: rharwood@Data.Basix.COM Message-ID: <0097021A.1122AF00.1834@Data.Basix.COM> Subject: Can MX handle DNS MX records? I loved MX so much at Basix.COM, I'm about to install MX at East.Pima.EDU. Will MX handle MX-record routing? UCX (currently installed at East.Pima.EDU) choked severely when designated as a "backup" receiver for Basix.COM, and I'm hoping MX will easily allow East.Pima.EDU to be a "Preference 500" MX record. If so, how does one configure MX to properly do that? (My "guess": a re-write rule of *.basix.com via SMTP routed to Basix.COM... am I close?) Thanks! Ray ================================================================================ Archive-Date: Tue, 27 Jul 1993 17:30:22 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: Floating periods Message-ID: <1993Jul27.213114.16102@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Tue, 27 Jul 1993 21:31:14 GMT To: MX-List@WKUVX1.BITNET In article <00970210.6969CAAE.10446@WKUVX1.BITNET>, "Hunter Goatley, WKU" writes: >Here are some to show that it works: >.. >.. >.. But, if you're reading from news, you see two periods! -d -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Tue, 27 Jul 1993 21:26:34 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Suspending mail receipt? Date: 28 Jul 1993 01:20:35 GMT Message-ID: <234k93$or@cutter.clas.ufl.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Our system here has problems with users subscribing to mailing lists and then ignoring their accounts. As a result, disk space gets eaten up by all these mailings -- even more so since MX ignores the user's quota limit. We have seen many instances of entire disks running out of quota and throwing many users out of their current tasks as a result. Does anyone know how to suspend receipt of mailings from the internet in in- stances of disk quota trouble? Or is there maybe a way for MX to recognize the user's quota? Any help would be appreciated. -Steve Morgan ltcomdata@ufcc.ufl.edu -Steven S. Morgan ** Front Page Sports Football? Civ? Talk to me!! ltcomdata@ufcc.ufl.edu ** M.U.L.E.?!? Where is it?!!!! ================================================================================ Archive-Date: Wed, 28 Jul 1993 01:50:35 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 28 Jul 1993 09:51:32 EDT From: Esra ESEN Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <009702B5.3D60CFC0.5965@trboun.bitnet> Subject: RE: Upgrading the underlying TCP/IP > >Does one need to re-install MX if one upgrades from UCX 1.3A to DEC TCP/IP >V2.0D? Does DEC TCP/IP support wide area network. As far as I know UCX doesn't. Esra ======================================================================== Esra ESEN System Manager Bogazici Universitesi ESEN@TRBOUN.BITNET Bilgisayar Merkezi Telf.:263 15 40 / Ext.:1246 80815 Bebek/Istanbul ========================================================================= ================================================================================ Archive-Date: Wed, 28 Jul 1993 02:37:53 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 28 Jul 1993 00:05:02 BST From: "Jamie Jones, HICOM Software Development" Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Message-ID: <00970263.4E80F0C0.5213@hicom.lut.ac.uk> Subject: Regarding the problem with RESET not working properly Sorry if this is lame, but just a thought : I remember some messages about MCP> RESET not always working correctly for some people after they've made alterations to the MX configuration. (Sorry, I've lost the original thread) Is it a possibility that the changes are being made, then the "RESET" command is typed *BEFORE* typing "SAVE" ? When you then exit, MCP automatically save the new configuration, but the RESET command was issued on the old configuration files... Just a though. Jamie. ================================================================================ Archive-Date: Wed, 28 Jul 1993 05:36:36 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 28 Jul 1993 15:04 GMT From: SAEED KHADEMI Reply-To: MX-List@WKUVX1.BITNET Subject: Question. To: mx-list@WKUVX1.BITNET Hi All, I have one question about programing MX mailer. My question is : - Is it possible to write a program, that MX calls it whenever - there is some flags on? - Suppose that one end-user wants to go somewhere, let say holidays. - And he/she wants to SET one flag in VMS mail to say to MX that - everytime one new mail recieved, answer it by a specified text file, - something like MX SIGNATURE. - I need this because some of our users want automatic answering service - during their holidays, or when they are participating in some congress - in another countries. Any help would be appreciated, and many thanks in advance. Regards, S.Khademi P.S: You can send your E-mails directly to my own address: E-mail : saeed@irearn.bitnet ================================================================================ Archive-Date: Wed, 28 Jul 1993 06:45:37 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: AXP VMS supprt for UCX Message-ID: <1993Jul28.121943.7253@dct.ac.uk> Date: 28 Jul 93 12:19:43 +0100 To: MX-List@WKUVX1.BITNET Does the current MX alpha support include TCP/IP services (UCX)? Yes I know it's still in field test. -- Alan Greig Janet: A.Greig@uk.ac.dct Dundee Institute of Technology Internet: A.Greig@dct.ac.uk Tel: (0382) 308810 (Int +44 382 308810) ** Never underestimate the power of human stupidity ** ================================================================================ Archive-Date: Wed, 28 Jul 1993 06:45:42 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: RE: Floating periods Message-ID: <1993Jul28.121742.7252@dct.ac.uk> Date: 28 Jul 93 12:17:42 +0100 To: MX-List@WKUVX1.BITNET In article <1993Jul27.213114.16102@colorado.edu>, dwing@uh01.colorado.edu (Dan Wing) writes: > In article <00970210.6969CAAE.10446@WKUVX1.BITNET>, "Hunter Goatley, WKU" > writes: > >>Here are some to show that it works: >>.. >>.. >>.. > > But, if you're reading from news, you see two periods! Huh? I'm reading from NEWS and see only one. ======== Relay-Version: VMS News - V6.1 24/02/92 VAX/VMS V5.4-2; site dct.ac.uk Path: dct.ac.uk!uknet!pipex!uunet!europa.eng.gtefsd.com!howland.reston.ans.net!usc!ne ws.service.uci.edu!unogate!mvb.saic.com!mx-list Newsgroups: vmsnet.mail.mx Subject: RE: Floating periods Message-ID: <00970210.6969CAAE.10446@WKUVX1.BITNET> From: "Hunter Goatley, WKU" Date: Tue, 27 Jul 1993 14:11:39 CST Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway X-Gateway-Source-Info: Mailing List Lines: 33 Here are some to show that it works: . . . Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ======== -- Alan Greig Janet: A.Greig@uk.ac.dct Dundee Institute of Technology Internet: A.Greig@dct.ac.uk Tel: (0382) 308810 (Int +44 382 308810) ** Never underestimate the power of human stupidity ** ================================================================================ Archive-Date: Wed, 28 Jul 1993 06:48:58 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 28 Jul 1993 06:48:46 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097029B.B4F92FC4.10612@WKUVX1.BITNET> Subject: RE: AXP VMS supprt for UCX writes: > >Does the current MX alpha support include TCP/IP services (UCX)? >Yes I know it's still in field test. > MX V3.3 AXP does support UCX, though I don't know how much it's actually been tested---I don't have any figures for how many AXPs are running MX. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 28 Jul 1993 06:59:40 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 28 Jul 1993 06:59:27 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097029D.3323AFF4.10614@WKUVX1.BITNET> Subject: RE: Question. SAEED KHADEMI writes: > >Hi All, > I have one question about programing MX mailer. > My question is : > - Is it possible to write a program, that MX calls it whenever > - there is some flags on? > - Suppose that one end-user wants to go somewhere, let say holidays. > - And he/she wants to SET one flag in VMS mail to say to MX that > - everytime one new mail recieved, answer it by a specified text file, > - something like MX SIGNATURE. > - I need this because some of our users want automatic answering service > - during their holidays, or when they are participating in some congress > - in another countries. > You can use the DELIVER package to do this. It's available via anonymous ftp from ftp.spc.edu in [.MACRO32.SAVESETS]DELIVER.ZIP. You can find UNZIP.EXE in [.MACRO32]. This version does not yet support AXP. You can also get it via e-mail by sending the following commands in the body of a mail message to FILESERV@WKUVX1.BITNET: SEND DELIVER SEND FILESERV_TOOLS Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Wed, 28 Jul 1993 11:21:54 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Suspending mail receipt? Message-ID: <1993Jul28.153031.27949@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 28 Jul 1993 15:30:31 GMT To: MX-List@WKUVX1.BITNET In article <234k93$or@cutter.clas.ufl.edu>, ltcomdata@maple.circa.ufl.edu (son of soong!) writes: >Does anyone know how to suspend receipt of mailings from the internet in in- >stances of disk quota trouble? Or is there maybe a way for MX to recognize the >user's quota? Any help would be appreciated. A possible workaround, which requires that the user subscribe to a real LISTSERV (not something that is called LISTSERV but works like a piece of @* and sends out the wrong hearders), is to disable the EXQUOTA privilege for the MX Local processes. This will cause the users' mail to bounce, but it could possibly bounce back *into* the list, depending on if the list owner setup the list's headers correctly. Not a fantastic idea. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Wed, 28 Jul 1993 11:22:35 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Can MX handle DNS MX records? Message-ID: <1993Jul28.152210.27647@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Wed, 28 Jul 1993 15:22:10 GMT To: MX-List@WKUVX1.BITNET In article <0097021A.1122AF00.1834@Data.Basix.COM>, "Ray Harwood -- Data Basix: (602)721-1988" writes: >I loved MX so much at Basix.COM, I'm about to install MX at East.Pima.EDU. >Will MX handle MX-record routing? Yes. My return address is uh01.colorado.edu, which doesn't have an A record; it is only an MX record pointing to buckie.hsc.colorado.edu. I can receive mail sent to me by systems running MX. >UCX (currently installed at East.Pima.EDU) >choked severely when designated as a "backup" receiver for Basix.COM, and I'm >hoping MX will easily allow East.Pima.EDU to be a "Preference 500" MX record. > >If so, how does one configure MX to properly do that? (My "guess": a re-write >rule of *.basix.com via SMTP routed to Basix.COM... am I close?) MX uses MX records by default - there is no configuration necessary. If MX can't find an MX record for a host, I believe it tries to find an A record. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Wed, 28 Jul 1993 14:07:28 CDT Sender: list-mgr@WKUVX1.BITNET Date: Wed, 28 Jul 1993 11:41:58 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET CC: rharwood@Data.Basix.COM Message-ID: <009702C4.AAFF1B40.1963@Data.Basix.COM> Subject: BBOARD-like feature in MX? Is there a feature in MX similar to the BBOARD feature of BULLETIN? Is that a possible "wish-list" item, Hunter? ;)} I'm trying to set up a one-way BBoard to receive the daily Whitehouse briefing notes... a PoliSci teacher wants her students to read them. I'm trying to set up one "public" username (like WHITEHOUSE) as a captive account that will permit reading of any of these postings by anyone without a "real" account. (The list is "one-way" outbound, so no posting capability is desired.) Thanks for any suggestions! Ray ----- Ray Harwood | Data Basix | Adjunct Faculty, East Campus, Voice: (602)721-1988 | PO Box 18324 | Pima Community College FAX: (602)721-7240 | Tucson, AZ 85731 | Instructor in Ada and Pascal rharwood@Data.Basix.COM | Info@Data.Basix.COM | rharwood@east.pima.edu ================================================================================ Archive-Date: Thu, 29 Jul 1993 06:12:08 CDT Sender: list-mgr@WKUVX1.BITNET Return-Path: Message-ID: <9307291028.AA18042@psk2.am.lod.edu.pl> From: Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Date: Thu, 29 Jul 93 11:28:29 CET subscribe ================================================================================ Archive-Date: Thu, 29 Jul 1993 07:21:19 CDT Sender: list-mgr@WKUVX1.BITNET Return-Path: Message-ID: <9307291317.AA18221@psk2.am.lod.edu.pl> From: Reply-To: MX-List@WKUVX1.BITNET To: mx-list@WKUVX1.BITNET Date: Thu, 29 Jul 93 14:17:00 CET list ================================================================================ Archive-Date: Thu, 29 Jul 1993 14:32:05 CDT Sender: list-mgr@WKUVX1.BITNET Date: Thu, 29 Jul 1993 15:00:14 EST From: "Jerry L Storrs, SYS MGR" Reply-To: MX-List@WKUVX1.BITNET To: mx-list%wkuvx1.bitnet@ulkyvm.louisville.edu CC: storrs@che.ncsu.edu Message-ID: <009703A9.87F8E0A0.9147@che.ncsu.edu> Subject: SIGNOFF MX-List SIGNOFF MX-List ================================================================================ Archive-Date: Fri, 30 Jul 1993 00:02:28 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: Floating periods Date: 28 Jul 1993 22:01:47 GMT Message-ID: <236t0bINN48f@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993Jul27.213114.16102@colorado.edu>, dwing@uh01.colorado.edu (Dan Wing) writes: =In article <00970210.6969CAAE.10446@WKUVX1.BITNET>, "Hunter Goatley, WKU" = writes: = =>Here are some to show that it works: =>.. =>.. =>.. = =But, if you're reading from news, you see two periods! I didn't. I'm using NEWSRDR. Which news reader are you using? -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Fri, 30 Jul 1993 00:38:15 CDT Sender: list-mgr@WKUVX1.BITNET From: bleau@umdsp.umd.edu Subject: Re: Suspending mail receipt? Date: 29 Jul 1993 16:43:39 GMT Message-ID: <238unr$t7l@umd5.umd.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Another possibility is to set the DISMAIL flag on the user's account. This will bounce all incoming mail. Though you still have the problem of it possibly bouncing back into the list and being sent all over. A third way is to log onto SYSTEM, get into MAIL, and do a SET FORWARD/USER= to change the forwarding address on the account to some other account that has enough room to receive the mail. Lastly, if you know the list the user has subscribed to, you can create a short .COm file like the one below and do a SUBMIT/USER=offending-user $ MAIL SEND/NOSELF MX%"nameoflist-request@system.name" UNSUBSCRIBE nameoflist $ EXIT This may raise the user's ire somewhat, though. Oh yes, don't forget the /SUBJECT="anything"/NOCC qualifiers on the SEND command above. Larry Bleau University of Maryland bleau@umdsp.umd.edu 301-405-6223 ================================================================================ Archive-Date: Fri, 30 Jul 1993 00:51:30 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Floating periods Date: 29 Jul 1993 22:10:07 +0400 Message-ID: <2393pv$ed1@lpuds.oea.ihep.su> To: MX-List@WKUVX1.BITNET Dan Wing (dwing@uh01.colorado.edu) wrote: : In article <00970210.6969CAAE.10446@WKUVX1.BITNET>, "Hunter Goatley, WKU" : writes: : >Here are some to show that it works: : >.. : >.. : >.. : But, if you're reading from news, you see two periods! Piece of Hunter's message as I see it: -------------------------------------------------------------------- : :Here are some to show that it works: :. :. :. -------------------------------------------------------------------- No double dots ! -- Igor Mandrichenko ================================================================================ Archive-Date: Fri, 30 Jul 1993 00:51:47 CDT Sender: list-mgr@WKUVX1.BITNET From: Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Can MX handle DNS MX records? Date: 29 Jul 1993 22:16:15 +0400 Message-ID: <23945f$ed9@lpuds.oea.ihep.su> To: MX-List@WKUVX1.BITNET Ray Harwood -- Data Basix: (602)721-1988 (rharwood@Data.Basix.COM) wrote: : I loved MX so much at Basix.COM, I'm about to install MX at East.Pima.EDU. : Will MX handle MX-record routing? UCX (currently installed at East.Pima.EDU) : choked severely when designated as a "backup" receiver for Basix.COM, and I'm : hoping MX will easily allow East.Pima.EDU to be a "Preference 500" MX record. If your host will be least-prefered host in MX RRs list, you'll have no problems with MX. : If so, how does one configure MX to properly do that? : (My "guess": a re-write : rule of *.basix.com via SMTP routed to Basix.COM... am I close?) Why "rewrite rule" ? Use "set path" instead. -- Igor Mandrichenko ================================================================================ Archive-Date: Fri, 30 Jul 1993 01:44:33 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <930728171636> Date: Fri, 30 JUL 93 08:22 GMT From: rok.vidmar@uni-lj.si Reply-To: MX-List@WKUVX1.BITNET Subject: How to turn MM support *off*? To: MX-List@WKUVX1.BITNET MX V3.3 VAX seems to deliver message to Multinet's MM if MAIL.TXT is found in SYS$LOGIN: strange things happen if MAIL.TXT is not MM's file (maximum record length becomes 1). Is there any way to turn MM support off? Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +38 61 186439 61000 Ljubljana fax: +38 61 186358 Slovenia ================================================================================ Archive-Date: Fri, 30 Jul 1993 06:37:33 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 30 Jul 1993 06:37:11 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097042C.6B791273.11425@WKUVX1.BITNET> Subject: RE: How to turn MM support *off*? rok.vidmar@uni-lj.si writes: > > MX V3.3 VAX seems to deliver message to Multinet's MM if MAIL.TXT is found >in SYS$LOGIN: strange things happen if MAIL.TXT is not MM's file (maximum >record length becomes 1). > > Is there any way to turn MM support off? > Completely, by the system manager? Currently, no. I assume you're running MultiNet on the system? If it's V3.2 or later, the user can create an MM.INIT file in their main directory with the following line: DELIVERY-TO-MM 0 If I'm not mistaken, earlier versions of MultiNet's SMTP would also make the same delivery mistake. If the MM.INIT file is not a practical option, let me know. I may be able to come up with a patch that disables it. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 30 Jul 1993 08:50:44 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 30 Jul 1993 09:01:30 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.BITNET To: WKUVX1.BITNET!MX-list@esseye.si.com Message-ID: <00970440.94B95120.14883@swdev.si.com> Subject: RE: Floating periods So far, only Dan Wing's (I don't know what it is) and mine (Mark London's BULLETIN) see two the periods that SMTP substitutes for single periods. I'd really like to know whether this fault lies with the news reader (the NNTP client) or the NNTP server, which should, in my opinion, convert the double period back to a single period prior to storing the message on disk (i.e. when it is received). How do the rest of you who read this group via news see the periods in Hunter's message - one period or two? ================================================================================ Archive-Date: Fri, 30 Jul 1993 10:29:02 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <930730161306> Date: Fri, 30 JUL 93 16:45 GMT From: rok.vidmar@uni-lj.si Reply-To: MX-List@WKUVX1.BITNET Subject: RE: RE: Floating periods To: MX-list@WKUVX1.BITNET > So far, only Dan Wing's (I don't know what it is) and mine (Mark London's > BULLETIN) see two the periods that SMTP substitutes for single periods. I'd > really like to know whether this fault lies with the news reader (the NNTP > client) or the NNTP server, which should, in my opinion, convert the double > period back to a single period prior to storing the message on disk (i.e. when > it is received). How do the rest of you who read this group via news see the > periods in Hunter's message - one period or two? I receive MX-list into X.400 (EAN V2.0) mailbox, so no news reader. I see two periods. I believe mail uses BITNET from WKUVX1 to GARR in Italy. I do not know whitch protocol is used between Italy an Germany, but from Germany message uses X.400 to reach me. Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +38 61 186439 61000 Ljubljana fax: +38 61 186358 Slovenia ================================================================================ Archive-Date: Fri, 30 Jul 1993 11:45:12 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: RE: Floating periods Message-ID: <1993Jul29.221057.17840@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Thu, 29 Jul 1993 22:10:57 GMT To: MX-List@WKUVX1.BITNET In article <236t0bINN48f@gap.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: >=But, if you're reading from news, you see two periods! > >I didn't. I'm using NEWSRDR. Which news reader are you using? I'm using NEWSRDR (version A4.3). I don't know if the NNTP client or server is supposed to handle that, though.... (my news server seems to be "NNTP" version 1.5.11 running on a Unix box). -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Fri, 30 Jul 1993 11:45:25 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Suspending mail receipt? Message-ID: <1993Jul30.001612.22989@colorado.edu> From: Date: Fri, 30 Jul 1993 00:16:12 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <238unr$t7l@umd5.umd.edu>, bleau@umdsp.umd.edu writes: >Lastly, if you know the list the user has subscribed to, you can create a >short .COm file like the one below and do a SUBMIT/USER=offending-user > $ MAIL > SEND/NOSELF > MX%"nameoflist-request@system.name" > UNSUBSCRIBE nameoflist > $ EXIT The MLFAKE utility will do this sortof thing for you (it's included with the MX distribution). But, if you do use something like the above, keep in mind that some user settings, like automatic CC prompting, can cause your MAIL script to be 'off'. It is better to use something similar to: $ $ MAIL/noSELF SYS$INPUT: MX%"""nameoflist-request@site""" UNSUBSCRIBE $ which isn't affected by user's settings within Mail (they added CC prompting in V5.0, and who knows what they're going to add in V7.0!). -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Fri, 30 Jul 1993 12:02:44 CDT Sender: list-mgr@WKUVX1.BITNET Message-ID: <930730180023> Date: Fri, 30 JUL 93 18:47 GMT From: rok.vidmar@uni-lj.si Reply-To: MX-List@WKUVX1.BITNET Subject: RE: RE: How to turn MM support *off*? To: MX-list@WKUVX1.BITNET > I assume you're running MultiNet on the system? If it's V3.2 or > later, the user can create an MM.INIT file in their main directory > with the following line: > > DELIVERY-TO-MM 0 Bad news: : $ mm : DSK$:[USR]mm.init: Syntax error at line 1, keyword DELIVERY-TO-MM : : Your current MM profile file contains errors. It was probably created by an : older version of MM. It will now be updated to remove the lines in error. : : DSK$:[USR]mm.init updated. : MM>VERSION : uek.uni-lj.si VAX-MM Version 5.1(312) : TOPSLIB 3.1(155) : Created by Kashtan@TGV.COM : Last edited by L. Stuart Vance on Sat May 2 18:11:00 1992 : MM>^Z : $ and DELIVERY-TO-MM 0 is gone. Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +38 61 186439 61000 Ljubljana fax: +38 61 186358 Slovenia ================================================================================ Archive-Date: Fri, 30 Jul 1993 13:58:02 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Suspending mail receipt? Message-ID: <23aghi$hhd@lpuds.oea.ihep.su> From: Reply-To: MX-List@WKUVX1.BITNET Date: 30 Jul 1993 10:53:38 +0400 To: MX-List@WKUVX1.BITNET son of soong! (ltcomdata@maple.circa.ufl.edu) wrote: : Our system here has problems with users subscribing to mailing lists and then : ignoring their accounts. As a result, disk space gets eaten up by all these : mailings -- even more so since MX ignores the user's quota limit. We have : seen many instances of entire disks running out of quota and throwing many : users out of their current tasks as a result. : Does anyone know how to suspend receipt of mailings from the internet in in- : stances of disk quota trouble? Or is there maybe a way for MX to recognize the : user's quota? Any help would be appreciated. Did you try to run MX LOCAL delivery agent without the privilege, allowing to ignore quota ? I never did it but it seems to be a legal solution. By default MX LOCAL (as other MX components) runs under SYSTEM account and have the privilege. Matt or Hunter may confirm if it's possible to run MX LOCAL under another less privileged account or to run all MX components under account without this privilege. -- Igor Mandrichenko ================================================================================ Archive-Date: Fri, 30 Jul 1993 15:26:37 CDT Sender: list-mgr@WKUVX1.BITNET Date: 30 Jul 1993 16:21:15 -0500 (EST) From: Teresa Feck Reply-To: MX-List@WKUVX1.BITNET Subject: Upgrading to MX3.3 To: mx-list@WKUVX1.BITNET Message-ID: <01H15PWJTKXU9S6JBF@TOE.TOWSON.EDU> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Date sent: 30-JUL-1993 15:39:04 We are running VMS 5.5-2 and UCX 2.0. I've just upgraded from MX 3.0 to MX 3.3. What happens with the entries that were in the queue prior to the upgrade? It looks as if they are not being processed by the new MX 3.3 queue. How can these entries be converted so they will be processed by the MX 3.3 queue? Thanks in advance, Teresa _______________________________ Teresa J. Feck Internet: feck@fre.fsu.umd.edu Academic Computing Bitnet: feck@towson.edu Frostburg State University Phonemail: (301) 689-7090 Frostburg, Maryland 21532 ================================================================================ Archive-Date: Fri, 30 Jul 1993 15:29:32 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 30 Jul 1993 15:29:12 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <00970476.BE2C6F4D.11669@WKUVX1.BITNET> Subject: RE: Upgrading to MX3.3 Teresa Feck writes: > >Date sent: 30-JUL-1993 15:39:04 > >We are running VMS 5.5-2 and UCX 2.0. I've just upgraded from MX 3.0 to MX 3.3. >What happens with the entries that were in the queue prior to the upgrade? It >looks as if they are not being processed by the new MX 3.3 queue. How can >these entries be converted so they will be processed by the MX 3.3 queue? > They should have been converted automatically. Have you tried using MCP QUEUE READY to re-ready them? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 30 Jul 1993 15:58:50 CDT Sender: list-mgr@WKUVX1.BITNET Date: 30 Jul 1993 16:50:21 -0500 (EST) From: Teresa Feck Reply-To: MX-List@WKUVX1.BITNET Subject: Re: Upgrading to MX3.3 To: MX-List@WKUVX1.BITNET Message-ID: <01H15S6YV63M9X5RFF@TOE.TOWSON.EDU> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Date sent: 30-JUL-1993 16:42:47 >Teresa Feck writes: >> >>Date sent: 30-JUL-1993 15:39:04 >> >>We are running VMS 5.5-2 and UCX 2.0. I've just upgraded from MX 3.0 to MX 3. 3 >. >>What happens with the entries that were in the queue prior to the upgrade? It >>looks as if they are not being processed by the new MX 3.3 queue. How can >>these entries be converted so they will be processed by the MX 3.3 queue? >> >Hunter Goatley writes: > >They should have been converted automatically. Have you tried using >MCP QUEUE READY to re-ready them? > Yes I did. When I use the MCP QUEUE READY, it gives me the following error message: ERROR READING QUEUE ENTRY NUMBER #, RECORD NOT FOUND. The new queue entries are at 115 and the old queue entries are at 20070. When I do a MCP QUEUE SHOW /BRIEF, the old entries are not listed. The old entries are in the MX_FLQ_DIR directory and the new entries are in a subdirectory of 1 through 9 under the MX_FLQ_DIR directory. _______________________________ Teresa J. Feck Internet: feck@fre.fsu.umd.edu Academic Computing Bitnet: feck@towson.edu Frostburg State University Phonemail: (301) 689-7090 Frostburg, Maryland 21532 ================================================================================ Archive-Date: Fri, 30 Jul 1993 16:03:30 CDT Sender: list-mgr@WKUVX1.BITNET Date: Fri, 30 Jul 1993 16:03:12 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Message-ID: <0097047B.7E198F67.11702@WKUVX1.BITNET> Subject: Re: Upgrading to MX3.3 Teresa Feck writes: > >>>We are running VMS 5.5-2 and UCX 2.0. I've just upgraded from MX 3.0 to MX 3. > 3 >>. [...] >Yes I did. When I use the MCP QUEUE READY, it gives me the following error >message: ERROR READING QUEUE ENTRY NUMBER #, RECORD NOT FOUND. The new queue >entries are at 115 and the old queue entries are at 20070. When I do a >MCP QUEUE SHOW /BRIEF, the old entries are not listed. Then they were somehow eliminated from the SYSTEM_QUEUE.FLQ_CTL file. >The old entries are >in the MX_FLQ_DIR directory and the new entries are in a subdirectory of >1 through 9 under the MX_FLQ_DIR directory. > The installation *should* have caught this and moved them, but it wouldn't if they weren't in the SYSTEM_QUEUE file. You're sure the old entries haven't already been processed? Sounds to me like you're SOL for now. There's nothing in MX yet to let you create entries on the fly like that. And the installation didn't report any errors? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@WKUVX1.BITNET (or goathunter%wkuvx1.bitnet@ULKYVM.LOUISVILLE.EDU) ================================================================================ Archive-Date: Fri, 30 Jul 1993 16:40:24 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Mail notification on homogenous clusters? Message-ID: <1993Jul30.155809.1@tesla.njit.edu> From: syssfk@tesla.njit.edu Reply-To: MX-List@WKUVX1.BITNET Date: 30 Jul 93 19:58:09 GMT To: MX-List@WKUVX1.BITNET Currently, although both systems in my VAXcluster share the same sysuaf.dat file, MAIL will only broadcast a notification to a user on the same system that is processing the incomming mail. This makes sense because MAIL doesn't know about the uaf. If I set up a cluster alias will notifications go to all systems sharing the alias when the alias name is used in the mail address? How about if the message is addressed to an individual node name (which also holds the alias name)? Or perhaps some parameter other than (or in addition to) the existence of an alias name and enabling alias connects in the DECnet MAIL object controls the notifications. They're production systems so I have to schedule an hour of downtime a week or more in advance so I don't get many opportunities to experiment. I haven't been able to find this topic mentioned in the docs but of course that doesn't mean it isn't there. Can anyone point me in the right direction? Thanks, - Steve - ----------------------------------------------- Stephen F. Keeton syssfk@tesla.njit.edu Senior System Programmer Computing Services Department New Jersey Institute of Technology Newark, NJ 07102 (201) 596-2907 ================================================================================ Archive-Date: Fri, 30 Jul 1993 16:40:41 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Mail notification on homogenous clusters? Message-ID: <1993Jul30.201747.9593@colorado.edu> From: Date: Fri, 30 Jul 1993 20:17:47 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993Jul30.155809.1@tesla.njit.edu>, syssfk@tesla.njit.edu writes: > Currently, although both systems in my VAXcluster share the same sysuaf.dat >file, MAIL will only broadcast a notification to a user on the same system that >is processing the incomming mail. This makes sense because MAIL doesn't know >about the uaf. Mail certainly does know about the SYSUAF. Mail checks the SYSUAF to determine the user's default directory and device to find their MAIL.MAI file (combined with the user-specified subdirectory, if any), and Mail checks DisMail to ensure that mail is allowed to be delivered to a user. If you define the system logical name MAIL$SYSTEM_FLAGS to 3 (define it /SYSTEM/EXECUTIVE), you will get cluster-wide notification. MAIL$SYSTEM_FLAGS: bit 0 (1) = this node is part of a cluster bit 1 (2) = send cluster-wide broadcast for new mail bit 2 (4) = include timestamp on broadcast Remote nodes should send mail to your VAXcluster alias, and your nodes should be setup to send mail with a VAXcluster alias. Not that setting bit 0, you will speed up how quickly mail is handled within your VAXcluster because DECnet won't be involved for Email transfer between VAXcluster nodes. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Fri, 30 Jul 1993 19:15:04 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Suspending mail receipt? Message-ID: <1993Jul30.153120.25492@colorado.edu> Reply-To: MX-List@WKUVX1.BITNET Date: Fri, 30 Jul 1993 15:31:20 GMT To: MX-List@WKUVX1.BITNET In article <23aghi$hhd@lpuds.oea.ihep.su>, igor@lpuds.oea.ihep.su (Igor Mandrichenko) writes: > Did you try to run MX LOCAL delivery agent without the privilege, >allowing to ignore quota ? I never did it but it seems to be a legal solution. >By default MX LOCAL (as other MX components) runs under SYSTEM account and >have the privilege. Matt or Hunter may confirm if it's possible to >run MX LOCAL under another less privileged account or to run all MX components >under account without this privilege. Just change the line in MX_EXE:MX_START.COM from: "/PAGE_FILE=15000/QUEUE=50/TIME_LIMIT=0/DETACH/PRIV=ALL/PRIO=4" to: "/PAGE_FILE=15000/QUEUE=50/TIME_LIMIT=0/DETACH/PRIV=(ALL,noEXQUOTA)/PRIO=4" and see if the behavior changes. Of course, this will remove EXQUOTA from *all* MX processes, so be sure that [1,4] (or whoever owns the files in MX_FLQ_DIR) has enough quota on your MX_DEVICE disk! -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Fri, 30 Jul 1993 19:29:57 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: Floating periods Message-ID: <23br80$s1a@umd5.umd.edu> From: bleau@umdsp.umd.edu Date: 30 Jul 1993 19:02:24 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET I'm using NEWSRDR (I forget which version), and I'm getting double periods. Here's a double period line I'll post to see what happens. .. Hope this helps. Larry Bleau University of Maryland bleau@umdsp.umd.edu 301-405-6223 ================================================================================ Archive-Date: Fri, 30 Jul 1993 19:30:03 CDT Sender: list-mgr@WKUVX1.BITNET Subject: RE: Floating periods Message-ID: <1993Jul30.192747.7571@colorado.edu> From: Date: Fri, 30 Jul 1993 19:27:47 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <23br80$s1a@umd5.umd.edu>, bleau@umdsp.umd.edu writes: >I'm using NEWSRDR (I forget which version), and I'm getting double periods. >Here's a double period line I'll post to see what happens. >... >Hope this helps. If anyone cares, I see three periods! :-) Back to our regularly scheduled discussion of MX (MX does it right, so I'm sure Matt's NEWSRDR does it right, and it is being handled improperly by some of our news servers.) -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Fri, 30 Jul 1993 22:52:25 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Does MX strip trailing white space??? Message-ID: From: Date: Fri, 30 Jul 1993 20:42:38 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET Has anyone else noticed that MX seems to strip white space (blanks and tabs) off the end of messages it gets? This stripping is really messing up transfers of files. I am using MX v3.1C on a cluster running VMS v5.5-1. I have v3.3 ready to install. Would this fix this problem? Thanks for any help you can provide! Rick Dyson -- Richard L. Dyson INTERNET: dyson@sunfish.Physics.UIowa.EDU _ _ _____ Graduate Research Assistant O: 319/335--1879 | | | | |_ _| Department of Physics & Astronomy H: 319/338--6117 | | | | of | | Van Allen Hall SPAN: IOWASP::DYSON | \_/ | _| |_ University of Iowa or : 7231::DYSON \___/ |_____| Iowa City, IA 52242 ================================================================================ Archive-Date: Fri, 30 Jul 1993 22:52:30 CDT Sender: list-mgr@WKUVX1.BITNET Subject: Re: Does MX strip trailing white space??? Message-ID: <1993Jul30.235234.17034@colorado.edu> From: Date: Fri, 30 Jul 1993 23:52:34 GMT Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article , dyson@sunfish.physics.uiowa.edu (Richard L. Dyson) writes: >Has anyone else noticed that MX seems to strip white space (blanks and >tabs) off the end of messages it gets? This stripping is really messing >up transfers of files. > >I am using MX v3.1C on a cluster running VMS v5.5-1. I have v3.3 ready >to install. Would this fix this problem? From the MX V3.3 release notes: 5 The MX UUCP interface and the SMTP servers (SMTP, DNSMTP, and XSMTP) stripped trailing blanks off of lines on incoming messages from MX. The blanks are no longer removed. However, you should *not* really rely on this -- other mailers between you and your destination may strip trailing blanks. Using UUENCODE, MIME (BAS64) encoding, or VMS_SHARE is better than relying on the MTAs between hither and yon. -Dan Wing, Systems Administrator, University Hospital, Denver dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet ================================================================================ Archive-Date: Fri, 30 Jul 1993 23:39:05 CDT Sender: list-mgr@WKUVX1.BITNET From: Subject: Re: Mail notification on homogenous clusters? Date: 31 Jul 1993 04:05:21 GMT Message-ID: <23cr21INN7g2@gap.caltech.edu> Reply-To: MX-List@WKUVX1.BITNET To: MX-List@WKUVX1.BITNET In article <1993Jul30.155809.1@tesla.njit.edu>, syssfk@tesla.njit.edu writes: = = Currently, although both systems in my VAXcluster share the same sysuaf.dat =file, MAIL will only broadcast a notification to a user on the same system that =is processing the incomming mail. This makes sense because MAIL doesn't know =about the uaf. If I set up a cluster alias will notifications go to all =systems sharing the alias when the alias name is used in the mail address? No. =How about if the message is addressed to an individual node name (which also holds =the alias name)? No. =Or perhaps some parameter other than (or in addition to) the =existence of an alias name and enabling alias connects in the DECnet MAIL =object controls the notifications. Yes. You need to define the logical name MAIL$SYSTEM_FLAGS on all members of your cluster. If memory serves, then in order to get cluster-wide notification of new mail, you should: $ DEFINE/SYS/EXEC MAIL$SYSTEM_+ FLAGS 2 -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it.