Tillbaka till svenska Fidonet
English   Information   Debug  
ENET.SYSOP   33888
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   24094
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   16442/30874
FIDONEWS_OLD4   23049/37224
FIDO_SYSOP   12852
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4393
FN_SYSOP   41678
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13598
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16069
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22090
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   924
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4786
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1121
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   3205
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13258
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2056
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4288
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   32677
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2053
DOS_INTERNET   0/196
duplikat   6002
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
Möte FIDONEWS_OLD4, 37224 texter
 lista första sista föregående nästa
Text 22254, 331 rader
Skriven 2015-03-30 00:35:42 av FidoNews Robot (2:2/2.0)
Ärende: FidoNews 32:13 [02/08]: Ftsc Information
================================================
=================================================================
                        FTSC INFORMATION
=================================================================

Publication:    FTS-5005

Revision:       2
Title:          Advanced BinkleyTerm Style Outbound flow and control
                files.
Authors:        Igor Romanovsky
                Administrator and FTSC members

Date:           2015-03-29
----------------------------------------------------------------------
Contents:       0. Status of this document.
                1. Introduction.
                2. Definitions.
                3. Flow files.
                4. File Requests
                5. Control files.
                A. References.
                B. Contact Info.
                C. History
----------------------------------------------------------------------

0. Status of this document
--------------------------


  This document is a Fidonet Technical Standard (FTS) - it specifies
  the current technical requirements and recommendations for FTN
  software developers, coordinators and sysops of the Fidonet network
  and other networks using FTN technology.

  This document is released to the public domain, and may be used,
  copied or modified for any purpose whatever.

  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
  NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
  in this document are to be interpreted as described in FTA-1006.


1. Introduction
---------------

  BinkleyTerm Style Outbound (BSO) flow and control files have been
  used for a long time but still are not fully documented. This has
  led to software developers using different approaches that make
  changing the mailer on a FTN station rather sophisticated.
  This document combines the original ideas, introduced by Vince
  Perriello and Bob Hartman (BinkleyTerm), and Andy Elkin (T-Mail).


2. Definitions
--------------

  Filename case sensitivity - the case of the BSO filenames depends on
  the OS file system. Lower case filenames are prefered if supported
  by the file system. If the OS file system supports lower and upper
  case filenames, the software should be able to handle both for
  maximum compatibility. That behaviour might be controlled by a
  configuration option.

  Outbound directory (outbound) - directory where flow and control
  files are stored. Outbound directory names will have the format
  <path>[.zzz], for example F:\Mailer\Out.002\ for the zone 2
  outbound.

  Default Outbound - The Outbound directory for your zone. In this
  case a directory generic name without a quasi extension is
  functionally equal to a directory with a quasi extension equal to
  your own zone number. If we consider node 1:234/5, the default
  zone is 1, thus "outbound" and "outbound.001" are both valid
  directories for storing flow and control files and it is recommended
  to check both of them but create flow and control files only in
  first, "outbound".

  For supporting point systems an outbound sub-directory is created
  with name "<nff>.pnt", where <nff> - name of flow file as described
  below. In this directory flow and control files are created with
  name formed from point number as 8 hexadecimal digits zero-padded
  on the left. Thus information concerning to point 104/36.45 is
  stored in subdirectory "outbound\00680024.pnt" in flow and control
  files with the name"0000002d.*".

  For supporting communications with systems from a different zone, a
  number of directories are created with the same generic name chosen
  for the default directory, plus a quasi extension equal to the zone
  number expressed as 3 hexadecimal digits zero-padded on the left.
  If the zone number > 4095 then 4 hexadecimal digits are used in
  quasi extension. The last can be implemented *only* with a modern
  OS. Thus information concerning node 2:104/36 is stored in directory
  "outbound.002" in flow and control files with name "00680024.*".
  "outbound" is assumed to be a generic name.

  Domain Addressing - is an extended method of designating various
  FTNs as compared with the zone-only method previously used. Domain
  addressing adds an additional "layer" to address designation that
  represents a particular FTN. Within that FTN, zones and nets can be
  specified without conflicting with identical zones and nets in other
  FTNs. Domain Addressing is only needed if you operate in two or more
  Fido Technology Networks (FTNs) using the same Zone numbers, or you
  wish to keep different Domains' compiled nodelists separate.

  How should Outbound Areas be named when domains are used?
  As always, the outbound area for your primary address (including
  domain) is the default outbound.

  Separate Outbound Areas are needed for each Zone in each Domain.
  These take an identical stem path to the primary outbound, except
  that the name of the last sub-directory is changed to the
  <abbreviation> parameter, plus the zone extension.
  For example, if your default outbound is C:\BINKLEY\OUTBOUND
  for the outbound holding area (and you are in FidoNet), Alternet
  (zone 7) outbound mail would be held in the C:\BINKLEY\ALTERNET.007
  directory instead. Note that outbound areas for domains other than
  your primary will ALWAYS have a zone extension, and that zone
  extensions are always specified in Hexadecimal, up to .FFF (4095).

  The outbound holding areas (for Zone 1 FidoNet) would then be as
  follows:

  c:\bink\outbound        (Default Outbound)
  c:\bink\outbound.002    (FidoNet Zone 2)
  c:\bink\outbound.003    (FidoNet Zone 3)
  c:\bink\outbound.004    (FidoNet Zone 4)
  c:\bink\outbound.005    (FidoNet Zone 5)
  c:\bink\outbound.006    (FidoNet Zone 6)
  c:\bink\alternet.007    (Alternet Zone 7)
  c:\bink\alternet.059    (Alternet Zone 89)
  c:\bink\eggnet.063      (Eggnet Zone 99)

  Flow file - a file with specific name and various extension that
  contains extension specific information to be sent to remote side.

  The name of flow file is formed from network and node number of the
  remote system, expressed as 4 hexadecimal digits each, zero-padded
  on the left. Thus information concerning node 104/36 is stored in
  flow and control files with name "00680024" but with different
  extension.

  Control file - same as flow for file but usually does not contain
  any information inside. Its purpose is to control behavior all
  software dealing with BSO. A reduced flow file (file does not
  contain any information inside or is of zero length) also may be
  considered as a control file.

  Restrictions - time intervals when it is not desirable to call the
  remote system. Restrictions may be external, introduced, for example
  by nodelist's information or internal due to economical or
  organizational reasons.


3. Flow files
-------------

  Flow files contain references to information to be sent to remote
  system. The address of remote system and name of this file has
  one-to-one correspondence. Flow files are divided by type and
  flavour.

  3.1. Types of flow file

       There are 2 types of flow files: netmail, file reference.

       Netmail flow files are an FTS-0001 packet containing packed
       netmail as described in FTS-0001. This flow file has
       signature "ut" as 2nd and 3rd letters in extension. During a
       session this file must be dynamically renamed at the moment
       of sending to a remote system with a unique name and extension
       "pkt". The method of creating unique names is implementation
       dependent.

       This file must be transferred to the remote system at any
       successful session. If the session is terminated accidentally
       during sending, this file must be resent in the next session
       from the beginning. After successful transmission this file
       must be deleted from the outbound directory.

       Reference files consist of a number of lines (terminated by
       0x0a or 0x0d,0x0a) each consisting of the name of the file
       to transfer to the remote system. It has signature "lo" as
       2nd and 3rd letters in the extension.

       The file name is optionally prefixed with a one character
       directive that indicates what to do with the file after a
       succesful transfer.

       The following directives are documented as a standard:

       "#" - Indicates that the files should be truncated to zero-
       length after successfully sending the file to the remote
       system. This is normally only employed when sending compressed
       mail (archived mail) to the remote.

       "^" - delete the file after successfully sending the file to
       the remote system.

       "~" - skip the line from treatment. It may be useful to mark
       an already processed line.

       <none> - indicates that the file should be sent and neither be
       truncated nor deleted after sending. Listing the file with the
       full path circumvents problems with files that have a name
       starting with a character that is a known directive.


       Software may optionally recognise the following directives:

       "-" As an alternate for "^"

       "!" As an alternate for "~"

       "@" Send file, do not truncate or delete.

       It is recommended that for maximum compatibility new implemen-
       tations recognise the above directives as documented, but do
       not use them when creating reference files.

       If an indicated file does not show a path, the result depends
       on the implementation. The implementation may assume that it
       resides in the same directory as the flow file, the working
       directory or some other directory. Also, programs running in
       different tasks may make different assumptions about what is
       the default directory. Therefore it is highly recommended to
       always use the full path in reference files.

       If a file is not found, software must ignore the line and
       continue processing.

       Whether the mailer does or does not send the files listed in
       the reference file during the successful session depends on the
       flavour of the reference file.

       After successful transmission of the listed files the flow file
       must be deleted from the outbound. (But see below.) Should the
       session be terminated accidentally while sending the listed
       files, the flow file must be processed in the next session from
       the beginning.


  3.2. Flavours of flow file

       The flavour of a flow file controls mailer's behavior. It can
       initiate a poll to a remote system. Especially it is useful
       with a reduced flow file. Creating such a flow file may force
       the mailer to execute actions that are not specified in normal
       mode of operation.

       It is recommended to use only reference files for reduced flow
       files and to use the method of "touch"ing a file; creating a
       new file if there isn't one already, or changing the file date
       to current if there is a file already. The difference in mailer
       behaviour for flow and reduced flow files is described later.


       There are 5 flavours.

       Immediate has "i" as the first char in the extension. Thus the
       full extension of a netmail file is "iut" and for a reference
       file is "ilo". If a flow file with such a flavour exists the
       mailer must try to poll a remote system without taking in
       consideration any external and internal restrictions. During a
       successful session files listed in "ilo" file must be sent to
       the remote system. It is assumed that information mentioned in
       "iut" and "ilo" will be sent to the specific system. Very often
       a reduced form is used only for making a poll.

       Continuous has "c" as the first char in the extension. Thus
       the full extension of netmail file is "cut" and for a reference
       file is "clo". If a flow file with such flavour exists the
       mailer must try to poll a remote system taking in consideration
       internal restrictions but not external ones (assuming that the
       remote system carries a CM flag). During a successful session
       files listed in "clo" file must be sent to the remote system.
       It is assumed that information mentioned in "cut" and "clo"
       will be sent to the specific system. Very often a reduced form
       is used for making a poll.

       Direct has "d" as the first char in the extension. Thus the
       full extension of a netmail file is "dut" and for a reference
       file is "dlo". If a flow file with such flavour exists the
       mailer must try to poll a remote system taking into considera-
       tion both external and internal restrictions. During a success-
       ful session files listed in "dlo" file must be sent to the
       remote system. It is assumed that information mentioned in
       "dut" and "dlo" will be sent to the specific system. Very often
       a reduced form is used for making a poll.

       Normal has "o" as the first char in extension for netmail and
       "f" for a reference file (using of "n" is considered as
       outdated). Thus the full extension of netmail file is "out" and
       for a reference file is "flo". If a flow file with such flavour
       exists the mailer must try to poll a remote system taking in
       consideration both external and internal restrictions. During a
       successful session files listed in "flo" file must be sent to
       the remote system. It is assumed that information mentioned in
       "out" and "flo" may be rerouted by specific programs (such as
       a netmail tracker) to another system.

       Hold has "h" as the first char in extension. Thus the full
       extension of a netmail file is "hut" and for a reference file
       is "hlo". A flow file with such flavour instructs the mailer
       to wait for a poll from the remote system. During a successful
       session files listed in "hlo" file must be sent if the remote
       system is the initiator of the session. If the remote system is
       not the initator of the session, it is implementation dependant
       whether the files are send or not. It is assumed that informa-
       tion mentioned in "hut" and "hlo" may be rerouted by specific
       programs (such as a netmail tracker) to another system.

       When flow files of more than one flavour are present for a
       particular AKA of a remote system, they should be processed in
       the following order:

       Immediate   ("iut" or "ilo")
       Continuous  ("cut" or "clo")
       Direct      ("dut" or "dlo")
       Normal      ("out" or "flo")
       Hold        ("hut" or "hlo")


  3.3. Simple time chart.

       Suppose our node has working hours from 21:00 till 09:00, and
       the remote system has working hours from 17:00 till 07:00. This
       time chart indicates when a poll would be produced for
       different flavours:

--- Azure/NewsPrep 3.0
 * Origin: Home of the Fidonews (2:2/2.0)