= Сообщение: 2673 из 7125 ====================================== FTSC_PUBLIC = От : TequilaMockingbird Online 1:266/404 03 Feb 17 23:59:04 Кому : All 03 Feb 17 23:59:04 Тема : New Files Received FGHI : area://FTSC_PUBLIC?msgid=51624.2ftscpubl@1:266/404+1cfb5f40 = Кодировка сообщения определена как: 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 20889 SportNet InfoPak for day 34, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 20889 bytes in 1 file(s)
>Area : FWCOMM : Fidonet: OS/2 Miscellaneous ----------------------------------------------------------------------------- links214.zip 4449861 Links browser version 2.14 Orig: 1:261/38 weasel23.zip 623553 Weasel: a POP3 and SMTP daemon for OS/2. Includes controls on who may send relay mail, and includes a way of blocking mail from specified hosts. Orig: 1:261/38 wslsrc23.zip 1183546 Weasel: a POP3 and SMTP daemon for OS/2. Source Orig: 1:261/38 ----------------------------------------------------------------------------- 6256960 bytes in 3 file(s)
>Area : INFOPACK : Fidonet: League Info Packs ----------------------------------------------------------------------------- CSCNET.ZIP 5460 Colorado Springs Central Net InfoPack Application And Other Info for Joining UpDate with New Zone Number Orig: 1:340/400 SPORTNET.ZIP 20886 The Official Sportnet Infopak Contains the following: sportapp.txt - SportNet application sportnet.??? - 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 ----------------------------------------------------------------------------- 26346 bytes in 2 file(s)
>Area : NASA : Fidonet: Earth & Space Science Material ----------------------------------------------------------------------------- AP170203.ZIP 897677 NASA Astronomy Picture of the Day (plus published Report; antwrp.gsfc.nasa.gov) Orig: 1:393/68 ----------------------------------------------------------------------------- 897677 bytes in 1 file(s)
>Area : PASPOINT : PAS Pascal-Net Pointlist ----------------------------------------------------------------------------- PASPOINT.Z34 8618 Weekly Pascal-Net PointList file Orig: 115:115/15 ppoint.z34 8325 Pascal-Net Zone 115 Weekly New Fakenet Pointlist By new 5 digits numbers. Orig: 115:115/15 pzpoint.z34 10801 Weekly Pascal-Net PointList in new Boss format. Orig: 115:115/15 pzpoint.z34 5532 Weekly Pascal-Net PointList in new Boss format. Orig: 115:115/15 ----------------------------------------------------------------------------- 33276 bytes in 4 file(s)
>Area : SPORINFO : SportNet InfoPak ----------------------------------------------------------------------------- sportnet.zip 20889 SportNet InfoPak for day 34, 2017 Orig: 24:24/1 ----------------------------------------------------------------------------- 20889 bytes in 1 file(s)
>Area : SPORNODE : SportNet Nodelists ----------------------------------------------------------------------------- spordiff.z34 622 SportNet nodediff for day 34, 2017 Orig: 24:24/1 sportnet.txt 20751 SportNet BinkD style nodelist for day 34, 2017 Orig: 24:24/1 sportnet.z34 8164 SportNet nodelist for day 34, 2017 Orig: 24:24/1 ----------------------------------------------------------------------------- 29537 bytes in 3 file(s)
>Area : WEATHER : Fidonet: Daily Graphic Forecasts ----------------------------------------------------------------------------- DAILYWET.ZIP 732206 Daily Weather Graphics Forecasts for North America from NOAA and wisc.edu Orig: 1:393/68 ----------------------------------------------------------------------------- 732206 bytes in 1 file(s)
============================================================================= >Total 8282332 bytes in 26 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...
