From wang!elf.wang.com!ucsd.edu!tcp-digest-relay Mon Feb 4 15:11:33 1991 remote from tosspot Received: by tosspot (1.63/waf) via UUCP; Mon, 04 Feb 91 20:23:48 EST for lee Received: from somewhere by elf.wang.com id aa03995; Mon, 4 Feb 91 15:11:32 GMT Received: from ucsd.edu by uunet.UU.NET (5.61/1.14) with SMTP id AA28027; Mon, 4 Feb 91 09:36:10 -0500 Received: by ucsd.edu; id AA04677 sendmail 5.64/UCSD-2.1-sun Mon, 4 Feb 91 04:30:21 -0800 for jbloom Received: by ucsd.edu; id AA04668 sendmail 5.64/UCSD-2.1-sun Mon, 4 Feb 91 04:30:17 -0800 for /usr/lib/sendmail -oc -odb -oQ/var/spool/lqueue -oi -ftcp-digest-relay tcp-digest-list Message-Id: <9102041230.AA04668@ucsd.edu> Date: Mon, 4 Feb 91 04:30:15 PST From: Advanced Amateur Radio Networking Group Reply-To: TCP-Group@ucsd.edu Subject: TCP-Group Digest V91 #33 To: tcp-group-digest@ucsd.edu TCP-Group Digest Mon, 4 Feb 91 Volume 91 : Issue 33 Today's Topics: FCC Citation NOS/MSYS Forwarding Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Sun, 03 Feb 91 14:36:59 EST From: jbloom%arrlhq.UUCP@uhasun.hartford.edu (Jon Bloom) Subject: FCC Citation To: tcp-group@ucsd.edu >I think I've just thought of the first good reason to get rid of the >Received header lines in mail... if the FCC is going to use them to cite >intermediate stations for carrying verboten traffic, then why should we make >their jobs easier for them? :-) > >A bit more seriously, I am concerned that the FCC would use evidence as >indirect as a Received line to cite a station for a rules violation. They >assume that because a station appears in the list, it must have transmitted >it at one time over amateur frequencies. But I know of at least some links >within the BBS "network" that are phone lines, not amateur channels. > >Phil The stations in the middle of the list only got letters asking them to explain the apparent violation. Obviously, if they explain that they transmitted the message via landline the FCC won't cite them. Likewise, the stations who were fined received (assuming normal FCC practice was followed) a "notice of apparent liability." If they can explain the apparent violation to the FCC's satisfaction, they'll be OK. Jon ------------------------------ Date: Sun, 03 Feb 91 14:12:28 EST From: gatech!usenet.INS.CWRU.Edu!ncoast!n8hsp!tbell Subject: NOS/MSYS Forwarding To: tcp-group First, I lost my "tcp-group" feed this month, so if this has been discussed please bear with me. I have recently been deludged with reports of NOS to MSYS forwarding failures. Heres what I have found so far: (ie: AX.25) When forwarding a *SINGLE* message, no sweat, all works just fine. When forwarding more than *ONE* message at a time, KAPOOF,BANG,BOOM! The first message gets forwarded just fine, the *SECOND* message starts out with a bang! The command NOS sends to initiate the forwarding of the second message is FUBAR. Here is what I was able to trace. N8HSP-2 is a TheNet 2.06 node interconnecting N8HSP-4 my NOS node to WA8BXN MSYS PBBS. The following is *AFTER* successfully forwarding the first message. AX25: N8HSP-2->N8HSP-4 I NR=6 NS=5 pid=Text 0000 >. AX25: N8HSP-4->N8HSP-2 I NR=6 NS=6 pid=Text 0000 SP tle?. < n8hsp . Well, any takers on this one? I looked at the /spool/mail/wa8bxn.txt file before forwarding and I couldn't find anything there that looked outta place. Please reply by E-mail as I said I lost my "tcp-group" feed this month. PERSONAL NOTE: Hey all you NOS/MSYS people this is TCP/IP! MSYS Sysop's activate your SMTP server! NOS User's activate your SMTP server! Flame out! Speaking of flame outs, Support *OUR* troops overseas!!!! 73,Terry !usenet.ins.cwru.edu!ncoast!n8hsp!tbell or ab617@cleveland.freenet.edu Terry Bell [44.70.4.10] INTERNET: ab617@cleveland.freenet.edu AmPR: N8HSP@WA8BXN.OH UUCP: uunet!usenet.ins.cwru.edu!ncoast!n8hsp!tbell ------------------------------ End of TCP-Group Digest ******************************