TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Paul Edwards
from: Bob Lawrence
date: 1997-05-19 14:56:00
subject: UUCP!!!

BL> fx.rSystem: scorpio Any g "" ATZ OK ATD9436-1785 CONNECT \m\c
 BL> in:--in: Ubobl: password

 BL> I am using BobL as my "machine name in the uucp world"
 BL> (whatever

 PE> You might find that you need to put Ubobl there instead, since
 PE> I know nothing about a BobL. 

  You could be right... I really don't have a clue what it means.

  I changed it to boblaw because Ubobl is not satisfactory.
"You-bobble" is a dick of a name! My SPCUG Internet address is
boblawrence{at}sydpcug.org.au and boblaw is a 6-char version of that. If
you want a meaningless name in the tradition of the Internet, similar
to your scorpio and Jeff's grntrs (or whatever it was) then I would
prefer nonsens.

  Is my Internet address... boblaw{at}scorpio.rosebay.matra.com.au ? 

 PE> Well, that "in:--in:" somehow means "look for the last bit of
 PE> the word 'Login:'".

  I worked it out this morning (Sunday), and I've been waiting
all bloody day to see if it works.

... later!!! It WORKS... WHOOPEE!

  You sent me all sorts of shit and the two little files in my spool 
file were uploaded to you. I got Jeff's tml stuff too. This looks like 
it might work! A small catch was that it sent my own replies too...

  But there is a problem for me...

  You sent those cunbatch files as gd0005.d and my compress program
expects a .*z extension. My DOS version of compress skips the cunbatch
lines which makes it a lot faster to process, and if you send .d 
extensions I'll have to rename them to .z files before I process... or
rewrite compress.

  Each of the .d files has a .x equivalent. What does this mean? Does
the x-file identify the d-file, and can I rely on the .x extension on
the X File? I know the truth is out there somewhere...

  Or to put it another way... why the FUCK don't you use .z!

  How do I identify actual mail? The mad "#! cunbatch" line is not on
all mail... or are those plain-text "Fred" messages your own creation?
Can I rely on the .d extension? Can I rely on the #! cunbatch line?
Has the whole world gone mad?

  How would you like my replies sent? Do you have any particular
letter in mind as an extension or would you prefer me to change them
daily? Would you mind if I changed the first line to "#! cunthook"?

  The mail transfer seems to work okay but it's bloody slow with so
many separate small files each from a different person. Doesn't UUCP
have a packet standard so you can send them all at once?

  We're getting there... now you need an Areafix so I can leave all
that C-programming crap and get a bit more AVT. This seems to be 
incredibly easy at this end...

  I've started writing my mail processor... what language would annoy 
you more, VB or Pascal?

... later...

  I'm confused by the various types of file in your download.

  The 0001 message is in plain text (Fred) and the X-file shows:
  U news scorpio
  C rnews Ubobl Ubobl.uucp

  The 0005 message is compressed international packet and #1 cunbatch;
  U news scorpio
  C rnews

  The 000c message is compressed local locuser and locsysop and shows:
  U root scorpio
  C rnews

  I am in full agreement with U root scorpio, but is there any way I
can tell if the packet is compressed ahead of time, or do I have to
open every file, and let compress fail?

    THESE SMARTARSE UNIX-WANKERS GIVE ME THE SHITS!!!!!!

  First, they put a #1 cunthook header their compress doesn't handle,
they have no way to tell if the file is compressed *inside* the file
(PKZIP uses "PK" as the first two characters), and then they use
nonstandard file suffixes! Does it mean that I have to try *every*
file? 


Regards,
Bob

___ Blue Wave/QWK v2.12
@EOT:

---
* Origin: Precision Nonsense, Sydney (3:711/934.12)
SEEN-BY: 711/934 712/610
@PATH: 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.