TIP: Click on subject to list as thread! ANSI
echo: binkd
to: MICHIEL VAN DER VLIST
from: MARK LEWIS
date: 2015-02-23 10:40:00
subject: File requesting with bink

 On Mon, 23 Feb 2015, Michiel van der Vlist wrote to Paul Quinn:

 PQ> Did you ever try a 'crash' filebox for the .REQ file against the 
 PQ> target system?

 MvdV> That may not give the desired result. Binkd renames the *.req 
 MvdV> file from net/node to a random? number when sending:

 MvdV> + 23 Jan 01:02:03 [172] sending d:\fido\outbound.001\009902cb.req
 MvdV> as 54c1d79e.req (20)

 MvdV> It may act different when it is placed in a file box.

it would send the file named as is... the name doesn't cause any specific
behavior on the other end... the .req extension does, though...

it is possible that changing the name on transmission is a hack to work around
the possibility of another .req file of the same name residing in the remote
systems inbound, though...

)\/(ark

* Origin: (1:3634/12)

SOURCE: echomail via QWK@docsplace.org

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™.