PE> If mail is on hold waiting for another node, the other node
 PE> doesn't need to FREQ it, he just has to connect, and he 
 PE> gets the file whether he likes it or not.

 BL> Yair... I understand this now, but that's not ideal. A huge 
 BL> file could end up getting moved all around Australia.

No Bob, the file sits at the system that did *not* forward it, waiting for
the intended recipient to poll. It then goes out (unless there are
restrictions in the BINKLEY.EVT file) automatically.

 BL> 1.  Send netmail to recipient anywhere, with attribute set 
 BL> and file. 

File Attach set, Hold not set (otherwise it would wait in *your* outbound
area for the recipient to poll)...

 BL> 2.  File is held at first BBS, listed for the recipient (or 
 BL> password) 

Held at the first system in the path that sets files for that address to
hold. It may be that the Sysop sends files to your intended recipient, and
doesn't care much if you (as a trusted point) piggyback one or two... 

 BL> 3.  Recipient gets netmail, freqs original board (uses 
 BL> password?). 

Not Freq, poll. File is waiting in the nnnnnnnn.HLO file in the outbound
area for nnnnnnnn to poll...

 BL> 4.  File is deleted.

Should normally happen...

 BL> This is what I mean by a letter drop. The file is intended 
 BL> *only* for the recipient, and is deleted after it is sent. 
 BL> Perhaps the file would be deleted after a while, like a dead 
 BL> letter.

Easy enough to do, if it is the only entry in the .HLO, otherwise you will
need to scan the log, (or include a comment in the HLO for each file with
the arrival date...)

 BL> The point sending the file would need a password to enter 
 BL> the system, but the recipient could use his name, since he 
 BL> woukld be the only one who knew a file was waiting for him.

Password would only be needed if there was a session password already in
place (always a good idea). Otherwise the first system presenting
z:nnn/fff.ppp as an AKA would get it... Hmmm... Interesting idea...

 BL> FileAttach wouldn't work because he is not your point, and 
 BL> whoever took the file would have to bear the cost (not to
 BL> mention my private file going all over the system).

Most systems don't enable file passthrough at all, so it would die partway...

 BL> I was wondering if it might be possible to do this with 
 BL> existing attributes, but it seems not.

I think you are a bit off the beam here Bob. It depends on what the Sysops
have set up as to whether the file is held, forwarded, or goes into the
bit-bucket...

...Alex.
(Pagan & Proud)

---