PE> I think a file-attach with the "hold" attribute would be
PE> appropriate, but I don't know enough about it.

BL> Ahh... so there is! The method exists already. That's 
BL> letter-drop I was talking about. I wonder why it isn't more 
BL> popular?

AWL> Most Sysops are incompetant morons, NFSE.

AWL> Many of them don't know what a hold is, let alone a TOPT 
AWL> kludge line.

 PE> Then perhaps you could explain what combinations of 
 PE> attributes are required to be set by Bob in order for him 
 PE> to send a file to my BBS and have my BBS hold it for pickup 
 PE> by a remote point (who is not known to my system), when all 
 PE> of my mail is normally routed through to Dave, and I have 
 PE> stripattributes in squish to stop people sending me files 
 PE> marked "crash".  Because I sure don't know.  And one of the 
 PE> hold combinations requires the setting of TWO flags (or so I 
 PE> recall from SQDEV200 I think).  BFN.  Paul.

I think you will find that the Hold for collect must be done at your end, I
think if Bob does it the message/file will sit in his outbound area until
he gets a call or his system does a force - some apparently allow you to
force stuff that is being held for collection to travel on an outbound call
(I think that's at the scheduler layer)

To make it all work, you should setup to force all files from elsewhere to
hold, and Bob just attaches them to you. The HOLD (at least in BINKLEY) is
done by a file that encodes the recipients address, so when they poll it
will identify them as having mail/files on hold... 

Of course they could be stuffed if you decline connections from unlisted
systems. (I wonder if stuff with a HOLD attribute would override that? (If
you password lock them out it wouldn't))

...Alex.
(Pagan & Proud)

---