Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.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:09:03 GMT Sender: ANU-NEWS Discussion Reply-To: root@NSFNET-RELAY.AC.UK Lines: 97 Via: 000040010180.FTP.MAIL; 2 JAN 90 8:12:31 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 ab00636; 2 Jan 90 8:04 GMT Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK via Janet with NIFTP id aa00599; 2 Jan 90 7:53 GMT Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 4106; Tue, 02 Jan 90 08:00:35 GM Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id 0365; Tue, 02 Jan 90 08:00:35 G Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id 6404; Tue, 02 Jan 90 01:59:10 C Date: Tue, 2 Jan 90 07:52:02 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 ab00229; 1 Jan 90 7:22 GMT Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK via Janet with NIFTP id aa00389; 1 Jan 90 7:12 GMT Received: from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 9676; Mon, 01 Jan 90 07:18:32 GM Received: from NDSUVM1.BITNET by UKACRL.BITNET (Mailer X1.25) with BSMTP id 6612; Mon, 01 Jan 90 07:18:32 G Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id 2474; Mon, 01 Jan 90 01:18:19 C Date: Sun, 31 Dec 89 20:59:35 GMT Reply-To: jeh@com.simpact Original-Sender: ANU-NEWS Discussion From: jeh@com.simpact Subject: 5.9C , reject of crossposted item though one group s/b okay? To: Multiple recipients of list ANU-NEWS Sender: ANU-NEWS%earn.ndsuvm1@uk.ac.earn-relay Running NEWS 5.9C (thanks, Geoff!), VMS 5.2. While reviewing last night's RNEWS log files [RNEWS is a DECUS uucp thing that takes news batches received via uucp and feeds them to NEWS via ADD BATCH commands] I noticed a message that was rejected due to my sys filter. The message was posted to alt.flame and to news.groups (in that order), and followups were directed to alt.flame. My sys filter says (among other things) news,!alt Is this the intended behavior? I thought that the posting to news.groups should be alllowed. --- Jamie Hanrahan, Simpact Associates, San Diego CA Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG Internet: jeh@simpact.com, or if that fails, jeh@crash.cts.com Uucp: ...Ecrash,scubed,decwrlL!simpact!jeh