BL> I've had a cognition. I don't know what TIC is, and I don't care.
BL> All I need is a letter-drop system: a name/address, a password, a
BL> holding directory, a way to update the FILES list online, and FREQ can
BL> do the rest. The problem with file attach is that someone else pays
BL> the bill. With a letter-drop, only the users pay.

file-attach is a problem for me to solve in Tobruk.  I don't currently
support that under OS/2, so nothing will change going to Linux.

BL> 1.  Look in inbound for POST/files, check for files and password.

I don't see why you can't call it .TIC instead of POST.

BL> 2.  Move files to specialr, add name/desc to list, erase POST.
BL> 3.  Send reply message on error or confirm.

This is all fine.

BL> 4.  Sort specialr list, update FILES list.

As I said, I think you should separate this out into a separate utility.

BL> Where can I get your utility? Does my packet have to have a packet
BL> header, or just the message header? And what do I call it?

All packets need a packet header.  If you require that I supply my own, and
prepend that, and post-append a couple of NULs, then that can be done too,
although obviously with more hassle!

BL> As it stands now, Binkley does its thing and answers the phone, puts
BL> all the inbound in the inbound directory... checks what's waiting and
BL> sends that back, and then... TIC gets to sort out what it has in the
BL> inbound. There's no way to slip TIC in between? Bummer.

TIC only gets run (currently) after the caller has hung up.

BL> Jeesuz! All that? And it looks like you do need a packet header, so
BL> all I need to know is... what do I call it? Won't
"temp.pkt" get lost
BL> in the syustem?

If you call it temp.pkt, that is fine, I can get tobruk to toss it, and
tobruk will create a new pkt, call it 00044629.pkt (etc) and then squish
will compress it into an outbound archive.  Alternatively you could create
the 00044629.pkt file yourself.  I suggest you use the number of seconds
since 1970 to name the .pkt.  There's no standard other than the .pkt needs
to have a name with hex digits, but that only applies to stuff you send
out.  Internally, tobruk will accept *.pkt, but only put out proper names. 
BFN.  Paul.
@EOT:

---