Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!kuhub.cc.ukans.edu!anu-news!list From: root@NSFNET-RELAY.AC.UK Newsgroups: news.software.anu-news Subject: Mail Delivery Failure to uk.ac.king - Rejected Message-ID: Date: 2 Jan 90 08:30:55 GMT Sender: ANU-NEWS Discussion Reply-To: root@NSFNET-RELAY.AC.UK Lines: 219 Via: 000040010180.FTP.MAIL; 2 JAN 90 8:37:16 GMT The NIFTP process was unable to deliver your mail to host uk.ac.king over janet. The reason given by the remote host was: Invalid value in command: invalid attribute - filename "FTP$NETWELL:MAILTMP.TMP". File open failure reason - device full (insufficient space for allocation). Secondary reason - device full - allocation failure. Username ignored. VAX/VMS FTP (80) Version 5.0. Your message was not delivered to the following addresses: GPKING@uk.ac.kingston Your message begins as follows: Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK Via Ethernet with SMTP id ab00745; 2 Jan 90 8:24 GMT Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK via Janet with NIFTP id aa00781; 2 Jan 90 8:13 GMT Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4398; Tue, 02 Jan 90 08:20:41 GM Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id 0547; Tue, 02 Jan 90 08:20:40 G Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id 7010; Tue, 02 Jan 90 02:12:14 C Date: Tue, 2 Jan 90 07:58:04 GMT Reply-To: root@uk.ac.nsfnet-relay Original-Sender: ANU-NEWS Discussion From: root@uk.ac.nsfnet-relay Subject: Mail Delivery Failure to uk.ac.king - Rejected To: Multiple recipients of list ANU-NEWS Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay The NIFTP process was unable to deliver your mail to host uk.ac.king over janet. The reason given by the remote host was: Invalid value in command: invalid attribute - filename "FTP$NETWELL:MAILTMP.TMP". File open failure reason - device full (insufficient space for allocation). Secondary reason - device full - allocation failure. Username ignored. VAX/VMS FTP (80) Version 5.0. Your message was not delivered to the following addresses: GPKING@uk.ac.kingston Your message begins as follows: Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK Via Ethernet with SMTP id ab00538; 2 Jan 90 7:53 GMT Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK via Janet with NIFTP id aa00539; 2 Jan 90 7:43 GMT Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4058; Tue, 02 Jan 90 07:50:58 GM Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id 0329; Tue, 02 Jan 90 07:50:58 G Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id 6168; Tue, 02 Jan 90 01:38:51 C Date: Tue, 2 Jan 90 07:21:05 GMT Reply-To: root@uk.ac.nsfnet-relay Original-Sender: ANU-NEWS Discussion From: root@uk.ac.nsfnet-relay Subject: Mail Delivery Failure to uk.ac.king - Rejected To: Multiple recipients of list ANU-NEWS Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay The NIFTP process was unable to deliver your mail to host uk.ac.king over janet. The reason given by the remote host was: Invalid value in command: invalid attribute - filename "FTP$NETWELL:MAILTMP.TMP". File open failure reason - device full (insufficient space for allocation). Secondary reason - device full - allocation failure. Username ignored. VAX/VMS FTP (80) Version 5.0. Your message was not delivered to the following addresses: GPKING@uk.ac.kingston Your message begins as follows: Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK Via Ethernet with SMTP id aa00267; 2 Jan 90 7:17 GMT Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK via Janet with NIFTP id aa00373; 2 Jan 90 7:08 GMT Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 3738; Tue, 02 Jan 90 07:00:05 GM Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id 0098; Tue, 02 Jan 90 07:00:04 G Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id 5181; Tue, 02 Jan 90 00:56:29 C Date: Tue, 2 Jan 90 06:29:14 GMT Reply-To: root@uk.ac.nsfnet-relay Original-Sender: ANU-NEWS Discussion From: root@uk.ac.nsfnet-relay Subject: Mail Delivery Failure to uk.ac.king - Rejected To: Multiple recipients of list ANU-NEWS Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay The NIFTP process was unable to deliver your mail to host uk.ac.king over janet. The reason given by the remote host was: Invalid value in command: invalid attribute - filename "FTP$NETWELL:MAILTMP.TMP". File open failure reason - device full (insufficient space for allocation). Secondary reason - device full - allocation failure. Username ignored. VAX/VMS FTP (80) Version 5.0. Your message was not delivered to the following addresses: GPKING@uk.ac.kingston Your message begins as follows: Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK Via Ethernet with SMTP id ac12347; 30 Dec 89 6:08 GMT Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK via Janet with NIFTP id aa09015; 30 Dec 89 6:02 GMT Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 0975; Sat, 30 Dec 89 06:07:38 GM Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id 8513; Sat, 30 Dec 89 06:07:38 G Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id 5421; Sat, 30 Dec 89 00:06:40 C Date: Sat, 30 Dec 89 05:56:06 GMT Reply-To: root@uk.ac.nsfnet-relay Original-Sender: ANU-NEWS Discussion From: root@uk.ac.nsfnet-relay Subject: Mail Delivery Failure to uk.ac.king - Timeout To: Multiple recipients of list ANU-NEWS Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay The NIFTP process was unable to deliver your mail to host uk.ac.king over janet. The reason given by the local host was: The NIFTP process gave up after 91 attempts over 172 hours Your message was not delivered to the following addresses: GPKING@uk.ac.kingston Your message begins as follows: Received: from vax.nsfnet-relay.ac.uk by sun.NSFnet-Relay.AC.UK Via Ethernet with SMTP id ad14251; 23 Dec 89 0:53 GMT Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK via Janet with NIFTP id aa13513; 23 Dec 89 0:49 GMT Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 7997; Sat, 23 Dec 89 00:50:31 GM Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id 4992; Sat, 23 Dec 89 00:50:31 G Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id 8819; Fri, 22 Dec 89 11:52:22 C Date: Thu, 21 Dec 89 19:55:39 GMT Reply-To: brodie@edu.mcw.fps Original-Sender: ANU-NEWS Discussion From: brodie@edu.mcw.fps Subject: Re: RE: rot13 utility in DCL. (and TPU suggestion) To: Multiple recipients of list ANU-NEWS Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay In article <8912200842.AA22375@uunet.uu.net>, munnari!csc.anu.oz.au!gih900@UUNET .UU.NET (Geoff Huston) writes: [stuff deleted about my dcl rot13 utility) > I'm impressed!!! thanks, geoff!! >>READ/ROT13, so it shouldn't be TOO tough....) > > Wouldn't it be better to have a TPU edit procedure called rot13 to allow you > to rot the necessary bits?? > (said he trying to avoid having to add the code) > > Geoff hey, now THERE's a neat idea. The tricky part is to tell TPU to do the ROT13 stuff when WRITING the file upon exit. Sounds neat, and I'm sure it's pretty easy to do. Unfortunately, I don't know tpu programming at ALL... never had time do learn it (I really should... maybe this would be a good project?) unless someone ELSE wants to do it..... ------------------------------------------------------------------------------- Kent C. Brodie - Systems Manager brodie@mcw.edu Medical College of Wisconsin +1 414 778 4500 "Gee, I hope these are the right coordinates..." -Chief O'Brian; STTNG