= Сообщение: 2652 из 7125 ====================================== FTSC_PUBLIC = От : TequilaMockingbird Online 1:266/404 13 Jan 17 23:59:03 Кому : All 13 Jan 17 23:59:03 Тема : New Files Received FGHI : area://FTSC_PUBLIC?msgid=51076.2ftscpubl@1:266/404+1cdfad9b = Кодировка сообщения определена как: ASCII ================================== ============================================================================== System name: TequilaMockingbird Online Sysop: Bill McGarrity (1@tequilamockingbirdonline.net) Location: Toms River, New Jersey USA Networks: 1:266/404@fidonet 316:973/2@whispnet 618:100/24@micronet 24:24/0@sportnet 46:1/159@agoranet Telnet: bbs.tequilamockingbirdonline.net:23 Web: bbs.tequilamockingbirdonline.net:81 Running: Synchronet 3.16a Win/32 - Windows Server 2008 Enterprise Mailer: binkd/1.1a-89/win32 IPv6 Native -------------------------------------------------------------------------------
>Area : FILES2HQ : Oddball Files to HQ ----------------------------------------------------------------------------- sportnet.zip 20925 SportNet InfoPak for day 13, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 20925 bytes in 1 file(s)
>Area : INFOPACK : Fidonet: League Info Packs ----------------------------------------------------------------------------- SPORTNET.ZIP 20916 The Official Sportnet Infopak Contains the following: sportapp.txt - SportNet application sportnet.xxx - Current nodelist sportnet.na - Message echo list sporgate.zxx - File echo list sportnet.txt - Binkd Style nodelist sportnet.old - Retired Echo areas Orig: 1:340/400 ----------------------------------------------------------------------------- 20916 bytes in 1 file(s)
>Area : MIN_INFO : MicroNet: Information ----------------------------------------------------------------------------- MICRONET.ZIP 17445 Micronet Information Network nodelist for Friday, January 13, 2017 (day 013). For more information about Micronet, please FREQ MININFO or MINLIST from 1:18/200@Fidonet or 618:618/1@Micronet. Info also available at http://outpostbbs.net/micronet.html. ZC: Sean Dennis (618:618/1@Micronet) Orig: 618:618/1 MININFO.ZIP 4046 Micronet Information Network Infopack for Sunday, 8 January 2017 (day 008). All the information you need to join Micronet, an active and friendly BBS mail network. We offer FTN, QWK and NNTP networking. For more info, please read this infopack, visit a participating BBS, or visit our webpage for more info. http://outpostbbs.net/micronet.html FREQ MININFO from 1:18/200 Micronet Information Network nodelist for Friday, 13 January 2017 (day 013). For more information about Micronet, please FREQ MININFO or MINLIST from 1:18/200@Fidonet or 618:618/1@Micronet. Info also available at http://outpostbbs.net/micronet.html. ZC: Sean Dennis (618:618/1@Micronet) Micronet Information Network Infopack for Friday, 13 January 2017 (day 013). All the information you need to join Orig: 618:618/1 ----------------------------------------------------------------------------- 21491 bytes in 2 file(s)
>Area : MIN_MISC : MicroNet: Misc. ----------------------------------------------------------------------------- IBBS0117.ZIP 621467 = The Telnet & Dial-Up BBS Guide - 1/17 = = January 2017 Edition = The largest active Telnettable BBS listing! Detailed listings on nearly 400 Telnet BBS listings. Also includes US/Canada Dial-Up BBS list. NetRunner Freeware Telnet Client included. Maintained by The BBS Corner at: http://telnetbbsguide.com Orig: 618:618/1 ----------------------------------------------------------------------------- 621467 bytes in 1 file(s)
>Area : PASPOINT : PAS Pascal-Net Pointlist ----------------------------------------------------------------------------- PASPOINT.Z13 8616 Weekly Pascal-Net PointList file Orig: 115:115/15 ppoint.z13 8325 Pascal-Net Zone 115 Weekly New Fakenet Pointlist By new 5 digits numbers. Orig: 115:115/15 pzpoint.z13 10800 Weekly Pascal-Net PointList in new Boss format. Orig: 115:115/15 pzpoint.z13 5531 Weekly Pascal-Net PointList in new Boss format. Orig: 115:115/15 ----------------------------------------------------------------------------- 33272 bytes in 4 file(s)
>Area : SPORINFO : SportNet InfoPak ----------------------------------------------------------------------------- sportnet.zip 20925 SportNet InfoPak for day 13, 2017 Orig: 24:24/1 ----------------------------------------------------------------------------- 20925 bytes in 1 file(s)
>Area : SPORNODE : SportNet Nodelists ----------------------------------------------------------------------------- spordiff.z13 351 SportNet nodediff for day 13, 2017 Orig: 24:24/1 sportnet.txt 20798 SportNet BinkD style nodelist for day 13, 2017 Orig: 24:24/1 sportnet.z13 8187 SportNet nodelist for day 13, 2017 Orig: 24:24/1 ----------------------------------------------------------------------------- 29336 bytes in 3 file(s)
2. Rename the file using the hex of my net and node... each must be padded with leading zeros to make four places... Net: 266 Node: 404
266 == 010a 404 == 0194
ren WPUSA.REQ 010a0194.req
3. Move the REQ file to your proper outbound directory for zone 1 since I'm in zone 1... in my case, this is just the .../outbound folder you have configured in binkd... for others it would be .../outbound.001 if zone 1 is not their primary zone...
move 010a0194.req .../outbound/010a0194.req
4. Create a poll file of the same name in the same directory to trigger binkd to connect to the remote system... a REQ file by itself will not trigger the poll... a ?LO file is required...
echo.>> .../outbound/010a0194.clo
5. sit back and watch binkd send the request and pick up the files and/or response messages...
[/FIRST METHOD]
[SECOND METHOD]
1. Create a file containing the magic or actual file name(s) of the desired file(s)... i'll use my master files list and the fido history archive in this example... both of these are magic names on my system...
2. Move the REQ file to your proper outbound directory for zone 1 since i'm in zone 1... in my case, this is just the /outbound folder you have configured in binkd... for others it would be /outbound.001 if zone 1 is not their primary zone...
move WPUSA.REQ /.../outbound/wpusa.req
[ yes i renamed the REQ file to all lower case in the move to show that one can move and rename at the same time ;) ]
3. Create a poll file containing a pointer to the REQ file in the outbound directory... the poll file must be the hex net and node as shown in the example above... a REQ file by itself will not trigger the poll... a ?LO file is required...
The '^' in the above tells binkd to delete the req file after it has been sent... the full path to the REQ file is needed... it may reside anywhere and is not required to be in the outbound with using this method...
4. Sit back and watch binkd send the request and pick up the files and/or response messages...
[/SECOND METHOD]
I just tested both of these and they worked properly If one is using fileboxes for a system they want to FREQ from, i would imagine that just placing the REQ file in the filebox would work without the need to create the ?LO file or mess with the hex format naming stuff... as long as the file has the REQ extension it should work...
