home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   BINKD      Support for the Internet BinKD mailer      8,958 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 6,139 of 8,958   
   binkd Team to All   
   binkd FAQ [2/4]   
   02 Feb 19 01:15:02   
   
         31 Mar 16:48:44 [40423] Connection rejected by proxy (HTTP/1.0 403   
   Forbidden)   
       ? 31 Mar 16:48:44 [40423] unable to connect: {13} Permission denied   
      
       In such a case you may try to use http tunnelling for instance with the   
   help of httport, HTTPTunnel (http://http-tunnel.sourceforge.net/), stunnel   
   (https://www.stunnel.org/) or you may find a node receiving binkp    
   connections at port 443.   
      
      
   ----------------------------------------------------------------------------   
      
      
           07. How Can binkd Work via SOCKS-proxy?   
      
       It is not a rare case when users go out to the internet from their   
   corporate LAN exclusively via the proxy server based at the only computer   
   connected to the internet. Thus binkd cannot make a direct connection to   
   the remote node and one must use the proxy server. Proxy servers support   
   was included in version 0.9.4 and the later ones.   
      
       binkd works with a SOCKS proxy version 4 and 5. The first one does not   
   demand an authorization (no login and password), the second one demands it   
   as a rule.   
      
       Suppose the connected to the Internet computer has the IP address   
   192.168.0.1 in its LAN and the SOCKS server at the computer responds on   
   port 1080. Here is the line in binkd configuration file necessary for   
   working via the SOCKS proxy.   
      
       1. A SOCKS server without user authorization (no login and password are   
   demanded):   
      
       socks 192.168.0.1:1080   
      
       2. A proxy server with user authorization (it is necessary to type login   
   and password, e.g. login "user", password "password"):   
      
       socks 192.168.0.1:1080/user/password   
      
      
   ----------------------------------------------------------------------------   
      
      
           08. IP-Point: How Can I Make binkd to Get My Mail From My Bossnode   
   (Uplink)?   
      
       Make a poll using the command line option -P:   
      
       binkd -P1:2/3 binkd.cfg   
      
       Usually they want binkd to exit after the session is finished. One can   
   use the command line option -p:   
      
       binkd -p -P1:2/3 binkd.cfg   
      
       If binkd does not exit for a long time after the session has been   
   finished then decrease the value of rescan-delay (and sometimes the value   
   of timeout).   
      
       If binkd works permanently (e.g. as a Windows service) and you want to   
   get your mail regularly then you need some additional program or a script.   
   As an example in DOS, Windows or OS/2 it is enough to execute the command:   
      
       cd . >> %outbound%\NNNNMMMM.ilo   
      
       where NNNN is the hex net number,   
             MMMM is the hex node number,   
             %outbound% is the path to the necessary zone outbound.   
      
      
   ----------------------------------------------------------------------------   
      
      
           09. "start_file_transfer: .: Permission denied" Error   
      
       You get the message when binkd cannot open a file for sending indicated   
   in some *.?lo file. Most likely the file has a line containing only "."   
   because the poll has been made by a command of the type   
      
       echo . >> xxxxyyyy.flo   
      
       you should change it to "cd . >> xxxxyyyy.flo"   
      
      
   ----------------------------------------------------------------------------   
      
      
           10. binkd/win and Dial-up: Dialing-up and Disconnecting Automatically   
      
       The problem is to configure the fidonet box in such a way that binkd   
   would initiate a telephone call to your Internet provider, get your mail   
   and disconnect.   
      
       The solutions:   
      
       1st Solution   
      
       Configure automatic connection and timeout in the dial-up connection   
   properties (idle time before hanging up). It is convinient to use a   
   non-standard software for dialing-up (Advanced Dialer and others). You   
   should start binkd with a command line option -p periodically (and possibly   
   -Paddress for binkd to make a poll to the address).   
      
       binkd -p -P1:2/3.4  binkd.cfg   
      
      
       2nd Solution   
      
       Use the command line option -p and the batch file where first Remote   
   Access Service (RAS) is started then binkd is started and after binkd exits   
   RAS is stopped.   
      
       Two variants, for Windows NT and for Windows 2000:   
       === binkdpoll1.cmd   
       rasdial Connection   
       binkd -p binkd.cfg   
       rasdial Connection /disconnect   
       ===   
      
       === binkdpoll2.cmd   
       net start "remote access service"   
       net start "remote access auto service"   
       binkd -p binkd.cfg   
       net stop "remote access auto service"   
       net stop "remote access service"   
       ===   
      
       3rd Solution (The Best One For Win9x)   
      
       Use the command line options -p and -Paddress and control connection   
   with a non-standard dial-up software (for example dialerp).  This solution   
   is the most reliable one (especially if the modem connection to your   
   Internet provider is bad) due to the fact that dialerp can start some   
   indicated programs at setting the connection.  Here is the batch file you   
   should start in the 'Execute' parameter of the dialerp configuration file:   
      
       ====   
       binkd -p -P1:2/3.4  binkd.cfg   
       dialerp BREAK *   
       ====   
      
       The question you may now ask: Where can I take dialerp? The answer is:   
   Ask the author (Alexander Vedjakin, 2:5020/540) or look for it in fileecho   
   archives and in ftp/http.   
      
      
       In any case you should set a small value for 'rescan-delay' parameter in   
   the binkd configuration file. binkd would exit faster.   
      
       === binkd.cfg   
       # Outbound rescans period (sec)   
       rescan-delay 2   
       ===   
      
      
   ----------------------------------------------------------------------------   
      
      
           11. I Have Changed binkd Configuration File On-The-Fly. When Will It   
   Be Reloaded?   
      
       Starting with the version 0.9.1 binkd could feel that its configuration   
   file changed. It exited with code 3 if it had been started with option -C.   
   Modification time was checked after each ingoing session. Here is the batch   
   file for starting binkd versions 0.9.1-0.9.3 and 0.9.4-0.9.6/w32:   
      
       ====   
       :aaa   
       binkd -C binkd.cfg   
       if errorlevel 4 goto end   
       if errorlevel 3 goto aaa   
       :end   
       ====   
      
       In the versions 0.9.4/unix and /os2-emx (and in these ones only) binkd   
   restarts automatically if it is started with -C command line option.   
   Besides that starting with version 0.9.4 the files included into the   
   configuration file with the help of 'include' keyword are tested not only   
   on incoming sessions but also in every 'rescan-delay' seconds.   
      
       If you install binkd 0.9.4/w32 as a Windows NT service you should use it   
   with -C command line option.  Then binkd re-reads its configuration file.   
      
       Before version 0.9.4 changes in the configuration file were not tested if   
   binkd was started in client-only mode (-c command line option).   
      
       In the unix versions configuration file is re-read on SIGHUP signal   
   by the command   
       kill -HUP `cat /var/run/binkd.pid`   
      
       In the version 1.0 configuration file is re-read automatically if   
   changed. binkd tests on changes at every 'rescan-delay' seconds.   
      
      
   ----------------------------------------------------------------------------   
      
      
           12. How Can binkd Work With T-mail/IP?   
      
       There is no way to do it. The protocols differ in essence: binkd uses   
   binkp protocol whereas T-mail/IP uses EMSI etc.   
      
      
   ----------------------------------------------------------------------------   
      
      
           13. Is There At Least One Log Analyzer Under Unix?   
      
       There exist many Perl scripts and several win32 binaries. For example here:   
      
       binkdstat 0.1 beta4 Christmas version 6.01.2002   
       Statistics generator for binkd   
       (c) Dmitry Sergienko, 2:464/910@fidonet, dmitry@trifle.net 14.08.2000   
       http://binkd.grumbler.org/loganalisers/binkdstat-ds.0.1_beta4_Christmas   
      
       There also exists BndStat program:   
       BNDST101.ZIP   34812 14-Aug-01 (AREA:AFTNMISC)   
       BndStat 1.01. With sources. binkd statistics generator. Compiled for all   
       platforms. Included win32 binaries. (C) Dmitry Rusov, 2:5090/94   
      
       Log analyzer by val khokhlov (perl):   
       http://www.vk.kiev.ua/create/soft.html#bnkds   
       http://binkd.grumbler.org/loganalisers/stat-binkd.pl.gz   
      
       binkdstat (c) val khokhlov, Dmitry Kolvakh, updated at April 2006   
       http://binkd.grumbler.org/loganalisers/binkdstat.zip   
      
       T-Hist (c) Michael Markowsky, 2:5020/378 (KLUG's BBS)   
       Binary log file analyzer for various mailers including binkd.   
       Works in DOS, Windows NT (2000, XP, 2003) and OS/2.   
       ftp://ftp.grumbler.org/pub/binkd/hist30a7.zip   
      
       Kleine Statistiker/BINKD for DOS v0.60a, Russian version   
       A small statistics generator for posting statistics to an echo conference.   
       ftp://ftp.grumbler.org/pub/binkd/statddos.rar   
      
      
   ----------------------------------------------------------------------------   
      
      
           14. binkd Connects Too Slowly (~20 Seconds) Though I Have a High-Speed   
   LAN   
      
       It is possible that 'backresolv' parameter is on (for logging the remote   
   host domain name) and DNS is not configured.   
      
       The simplest solution is to comment the 'backresolv' out in the   
   configuration file.  Configuring DNS is a more complex solution.   
      
      
   ----------------------------------------------------------------------------   
      
      
           15. Why Does binkd Not Understand Command Line Options When I Start It   
   From inetd?   
      
       You should use the program name as the first parameter in inetd.conf (it   
   may be any string for binkd), the second and the following parameters   
   are the command line options (-iqs etc.) and the last parameter is the   
   configuration file full path:   
      
       binkp stream tcp nowait root /usr/fido/binkd binkd -isq /usr/fido/binkd.cfg   
      
       If you do not use -q option then you should switch console output off   
   (comment 'printq', 'percents', 'conlog' out).   
      
      
   ----------------------------------------------------------------------------   
      
      
           16. Can One Make a File Request From binkd?   
      
       It's a piece of cake! binkd supports WAZOO FREQ with an external helper.   
      
       To request files from a remote system it is necessary to create a file   
   of type nnnnmmmm.REQ and to put it in the outbound directory next to *.?ut   
   and *.?lo files. But *.REQ files do not initiate binkd to call a link so    
   to make a FREQ it is necessary to make a poll. The contents of a .REQ file   
   is described in the "!SRIF.TXT" file which is a copy of FSC-0086.001 from   
   http://ftsc.org   
      
      
   ----------------------------------------------------------------------------   
      
      
           17. How Can my binkd Respond to a File Request?   
      
       One can configure binkd for calling an external file request processor   
   supporting SRIF (FSC-0086) for receiving and handling FREQs in binkd. Please   
   read the "!SRIF.TXT" file and the comment to 'exec' in the configuration   
   file.   
      
       Here are the examples of lines in configuration file for DOS-based OS   
   and for *nix (you should use regular expressions in the latter case for   
   binkd to match both upper-case and lower-case letters, e.g. both *.REQ and   
   *.req):   
      
       exec "\\ftn\\allfix\\allfix.exe RP -SRIF *S" *.req   
      
       exec "/ftn/bin/tmafreq-srif *S" *.[rR][eE][qQ]   
      
       A bash script "srifreq" is delivered with binkd starting with version    
   1.1a19.   
       The following file request processors are also compatible with binkd    
   (but they are not the only ones, any other one supporting SRIF will do):   
      
       Allfix by Harms Software Engineering: it is a fileecho processor with   
   built-in file request processor and it has versions for DOS and OS/2;   
      
       ViReq by Michael Haase (2:2432/280): a specialized FREQ processor for   
   Windows, it is distributed by Michael Massenberg (2:2411/505) via modem,   
   ISDN and Fido-over-IP.   
      
       tmafreq by Maxim Timofeyev : the FREQ processor   
   is created for a unix-like OS and ported into Windows. One may obtain tmafreq   
   from different BBS and FTP with fileecho archives, or may get tmafreq sources   
   from anonymous CVS :pserver:anoncvs@tma.spb.ru:/cvsroot, module "tmafreq".   
      
       VIREQ/x by Volker Imre  (2:246/2098): the FREQ   
   processor is created for a unix-like OS but can be compiled in the OS/2,    
   Windows and maybe other operating systems. Now it is included into "ftnapps"    
   project on Sourceforge and may be downloaded from    
   http://ftnapps.sourceforge.net/vireq.html.   
   Binaries built for Win32 and OS/2 may be downloaded from   
   http://download.binkd.org  and   
   http://sites.google.com/site/vasilyevmax/fido   
      
      
   ----------------------------------------------------------------------------   
      
      
           18. How Can I Add binkd To a Fidonet Box Working With a Modem?   
      
       You must configure your modem mailer and tosser for BSO (binkley-style   
   outbound) mode so that all of them including binkd would have the same   
   inbound directories (and also the same outbound directories). For example,   
   one may put the following line to T-Mail mailer configuration file:   
      
       BinkStyle_Pack_For All   
      
       If your mailer can work with AMA (arcmail-attach) only you may try to   
   use fileboxes and/or find programs that can convert your mailer's queue to   
   BSO or fileboxes. For example, Mail2dir utility allows using fileboxes with   
   FrontDoor. Such a means disables a possibility of sending your mail to the   
   same link both by IP and by modem (for instance, when one of the channels   
   failed). There is another more radical but more flexible way: you may change   
   your mailer.   
       See also question 35.   
      
      
   ----------------------------------------------------------------------------   
      
      
           19. Flags Are Not Created On Receiving a File, Programs Do Not Start   
      
       For sure you have a wrong template in the configuration file. You have to   
   use it this way (the first two lines are for Windows and OS/2, the rest are   
   for the Unix-like OS):   
      
       flag m:\\ftn\\flg\\pntseg.flg m:\\\\ftn\\\\inbound\\\\sec\\\\pntstr*.*   
       flag m:\\ftn\\flg\\toss.flg *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.pkt   
      
       exec "/usr/local/bin/ftrack -c /fido/conf/ftrack" *.[Pp][Kk][Tt]   
       flag "/ftn/flg/echo-in" /ftn/inboundsec/*.[Ss][Uu][0-9A-Za-z]   
       flag "/ftn/flg/echo-in" /ftn/inboundsec/*.[Mm][Oo][0-9A-Za-z]   
       flag "/ftn/flg/echo-in" /ftn/inboundsec/*.[Tt][Uu][0-9A-Za-z]   
       flag "/ftn/flg/echo-in" /ftn/inboundsec/*.[Ww][Ee][0-9A-Za-z]   
       flag "/ftn/flg/echo-in" /ftn/inboundsec/*.[Tt][Hh][0-9A-Za-z]   
       flag "/ftn/flg/echo-in" /ftn/inboundsec/*.[Ff][Rr][0-9A-Za-z]   
       flag "/ftn/flg/echo-in" /ftn/inboundsec/*.[Ss][Aa][0-9A-Za-z]   
       flag "/ftn/flg/fech-in" /ftn/inboundsec/*.[Tt][Ii][Cc]   
      
       You must use the full path with four slashes for the file to receive or   
   the template should start with an asterisk character. You must use two   
   slashes for the flag file.   
      
       You must use the full path because using a filename without path means   
   the event of receiving the file in the current directory and not in the   
   inbound directory. If a template begins with "*" then it means "any   
   directory" (and since all the files are received in one of the inbound   
   directories it works for both password protected and for unprotected   
   sessions).   
      
       In a UNIX-like OS you should take into account that filenames are case   
   sensitive. Please use regular expressions in templates.   
      
      
   ----------------------------------------------------------------------------   
      
      
           20. 'skipmask' Keyword Does Not Work   
      
       A filename is compared without path and the comparison is case   
   sensitive when 'skipmask' is used.   
      
      
   ----------------------------------------------------------------------------   
      
      
           21. binkd Under Windows 3.x   
      
       Sergey Zharsky (zharik@usa.net) ported binkd 0.9.2 and binkd 0.9.5 for   
   Windows 3.x. They work using IP stacks Trumpet Winsock ver. 3.0 revision D   
   and Novell TCP/IP Client for Win 3.11 (see the answer to the question   
   'binkd Under DOS', the section "The DOS version has the feature...").   
      
      
   ----------------------------------------------------------------------------   
      
      
           22. Different FTN Domains in binkd And a Tosser Without 5D Support   
      
       Suppose there are two domains (with different zone numbers though it   
   does not matter).  Mail can be successfully sent to the first domain but   
   not to the second one. This situation may arise if the tosser, the tracker   
   and the other your FTN programs do not support 5D BSO.   
      
       This is a typical binkd configuration for two FTN domains and 5D   
   outbound:   
      
       domain fidonet c:\\ftn\\outbound\\fidonet 2   
       domain omeganet c:\\ftn\\outbound\\omeganet 11   
       address 2:5070/222@fidonet 11:58/6@omeganet   
      
       One must configure not the zone of your own address for 'domain'   
   keyword as one might think but the zone that should not be appended to the   
   outbound name (i.e. the outbound subdirectory extensions are not processed   
   for the zone denoted in the 'domain' line).   
      
       If your tosser would create bundles for omeganet in the omeganet   
   directory then you should write as indicated above. But since it does not   
   work with 5D and it creates the bundles in fidonet.00b then you should   
   write this way:   
      
       domain fidonet c:\\ftn\\outbound\\fidonet 2   
   --- hpt/lnx 1.9.0-cur 21-02-18   
    * Origin: Moscow, Russia (2:5020/1042)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca