;A FidoNet Nodelist for Friday, October 28, 2016 -- Day number 302 : 50241 D1 A26 ;A FidoNet Nodelist for Friday, November 4, 2016 -- Day number 309 : 55965 ;A ;A MakeNL 3.4.5 (Win32) ;A ;A The FidoNet NodeList, a listing of the systems within FidoNet. ;A ;A This is the nodelist produced at 2:2/0 ;A ;A .. All rights reserved except for the following: ;A ;A .. The FidoNet NodeList is compiled so that computer systems within ;A FidoNet may communicate with each other. Use and intra-FidoNet ;A distribution rights are granted to all FidoNet system operators ;A for the purposes of communication within FidoNet or applying for ;A a FidoNet node number. ;A ;A .. This is a compilation of individual nodelist segments contributed ;A by the drafters and compilers of those segments. Contribution of ;A these segments to this compilation does not diminish the rights ;A of the contributors. ;A ;A .. Please address all issues relating to the status of this document ;A to the Z2C (ZONE2 Coordinator) of Fidonet at the Fido-address ;A 2:292/854, the email-address wd-at-skynet-dot-be or write snailmail ;A to: Ward Dossche - Drabstraat 142 - 2640 Mortsel - Belgium ;A D25 C2 D12 A16 ;S | PROLOG-DATE : 29 OCT 2016 | ;S +-------------------------------+ ;S ;S +------------------------------------------------------------+ ;S * THIS LIST HAS BEEN COMPILED IN AND FOR ZONE-2 * ;S +------------------------------------------------------------+ ;S ;S +------------------------------------------------------------+ ;S | INFORMATION RE: THE WEEKLY NODELIST.jjj AND NODEDIFF.jjj | ;S +------------------------------------------------------------+ ;S | SYSOPS FROM OUTSIDE ZONE-2 PLEASE CHECK THAT YOU UPDATE | ;S | IT WITH THE CORRESPONDING DIFF ORIGINATING IN ZONE-2. | ;S | | ;S | SYSOPS INSIDE ZONE-2 PLEASE MAKE CERTAIN YOU TRY NOT TO | ;S | UPDATE WITH A DIFF ORIGINATING IN ANOTHER ZONE. | ;S +------------------------------------------------------------+ C39 D1 A1 ;S | Heartbeat of 2:292/854 AKA 2:2/0 | C54 D1 A1 ;S | FTP - HTTP | C70 D1 A1 Zone,2,Eur_(309),B,Ward_Dossche,-Unpublished-,300,MO,CM,XX,IEM:mg@dossche.org,INA:many-glacier.dtdns.net,IBN,IFT,IMI,IUC,ITX,PING C280 D1 A1 Region,28,Belgie+Nederland(308),Driebergen_NL,Michiel_van_der_Vlist,-Unpublished-,300,MN,MO,CM,XW,IBN:fido.vlist.eu,PING,U,ENC C10 D1 A1 Hold,2020,Starlight_BBS,Beek_en_Donk,Lars_van_Dijk,-Unpublished-,300,CM,IBN:starlight.altimit.nl C189 D1 A1 Region,46,Ukraine_and_Moldova[309],Nikolaev_Ukraine,Yury_Roschupkin,380-512-374472,9600,V42B,IBN,IFC,XX,MO,ICM,INA:fido.mksat.net,TSG,U,DO4:binkp.net C131 D1 A1 Host,463,Ukraine_Capital_[302],Kiev,Alexander_Yakusha,380-44-4952708,33600,X2C,V90C,VFC,XX,CM,IBN,INA:fido.porteq.com.ua,MO C412 D1 A1 Host,5020,NET_Moscow_Russia_(02/11/2016),Moscow_Russia,Andrey_Frolov,7-498-483-3338,33600,CM,XX,HST,V34,IBN,INA:94.79.47.242 C23 D1 A1 Hold,313,fido.lleo.aha.ru,Moscow,Leonid_Kaganov,-Unpublished-,300,MO,IEM:fido@lleo.aha.ru,IMI,CM C10 D1 A1 Hold,961,fido.cemehob.ru,Moscow,Denis_Semenov,-Unpublished-,300,CM,IBN,INA:fido.cemehob.ru C1 D1 A1 Hold,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru C8 D1 A1 Hold,2230,Pilona,Moscow,Sergey_Goltsov,-Unpublished-,300,CM,IMI:pilotnet@list.ru C12 D2 A2 Hold,785,f785.25u.com,Moscow,Max_Larionov,-Unpublished-,300,MO,CM,IBN,INA:f785.25u.com Hold,814,Misantropolis,Lubertsy,Gregory_Leonov,-Unpublished-,300,MO,IBN,INA:f814.no-ip.org C16 D1 A1 Hold,2038,DKsoft,Moscow,Dmitry_Kanidev,-Unpublished-,300,CM,MO,IFC,INA:2038.no-ip.org C2 D1 A1 Hold,10192,dzv,Moscow,Mike_Shishkov,-Unpublished-,300,MO,CM,IBN,INA:f10192.hopto.org C2 D2 A2 Hold,14,Hell-hole,Moscow,Sasha_Gromov,-Unpublished-,300,CM,MO,IMI,EMA:skrester@gmail.com Hold,77,MS-DOS,Moscow,Mihail_Vinogradov,-Unpublished-,300,CM,IBN,INA:fido.rn3aig.ru C6 D1 A1 Hold,850,FoxFire_Station,Moscow,Alex_Lazarev,-Unpublished-,300,MO,LO,CM,IBN,INA:dartfox.ru C2 D1 A1 Hold,1754,DREAMWEB_Station,Moscow,Vitaly_Kremnev,-Unpublished-,300,MO,CM,IBN,INA:fido1754.no-ip.org C2 D1 A1 Hold,4040,Blackfire,Moscow,Valerij_Kozhevnikoff,-Unpublished-,300,CM,XX,MO,V90C,EMA:jason2000@yandex.ru C329 A1 ,43,Forester_XIII_station,Murmansk,Anatoly_Vesnin,-Unpublished-,300,CM,IMI,IEM:fido@avesnin.ru C128 D1 A1 ,40,Aurora,Simbirsk_Russia,Alexander_Kuznecov,-Unpublished-,300,IBN,INA:89.250.161.43 C237 D1 A1 ,28,Nostalgie,Togliatti,Dmitry_Pshenisnov,-Unpublished-,300,CM,IMI:2507528@gmail.com C30 A1 ,85,Jazz_Station,Almaty_Kazakhstan,Eugene_Erokhin,-Unpublished-,300,MO,ICM,IBN,INA:uncleeugene.dlinkddns.com C456 D1 A1 Down,757,The_Rusty_MailBox,Penticton_BC,Alan_Ianson,-Unpublished-,300,CM,INA:trmb.ca,IBN C101 D1 A1 Host,3634,North_Carolina_USA_(2016/309),central_NC_USA,mark_lewis,1-919-774-5930,33600,XA,V34,CM,ITN,INA:ftn.wpusa.dynip.com,IBN,IVM,PING C124 D1 C10 A1 ,146,AltBBS,Sorocaba_SP,Eduardo_Marcal,000-0-0-0-0,300,ICM,IBN,INA:bbs.altbbs.net C2 D1 A1 ,189,Brain_Storm_BBS,Recife_PE,Ioram_Sette,000-0-0-0-0,300,ICM,IBN,INA:bsbbs.com.br C27 D423 A421 ;S *************************************************************** ;S *** BEGIN EPILOG-SECTION FOR A ZONE2 NODELIST = OCT 29 2016 *** ;S *************************************************************** ;S ;S The following flags define special operating conditions: ;S ;S Flag Meaning ;S ;S CM Node accepts mail 24 hours a day ;S MO Node does not accept human callers ;S LO Node accepts calls Only from Listed ;S FidoNet addresses ;S ICM Node accepts 24/7 IP-mail but has limited ;S "open" hours only via PSTN and/or ISDN ;S ;S The following flags define modem capabilities supported: ;S ;S Flag Meaning ;S ;S V22 ITU-T V22 1200 bps full duplex ;S V29 ITU-T V29 9600 bps half duplex ;S V32 ITU-T V32 9600 bps full duplex ;S V32B ITU-T V32bis 14400 bps full duplex ;S V34 ITU-T V34 33600 bps full duplex ;S V42 LAP-M error correction w/fallback to MNP 1-4 ;S V42B LAP-M error correction w/fallback to MNP 1-5 ;S MNP Microcom Networking Protocol error correction ;S H96 Hayes V9600 ;S HST USR Courier HST ;S H14 USR Courier HST up to 14.4Kbps ;S H16 USR Courier HST up to 16.8Kbps ;S MAX Microcom AX/96xx series ;S PEP Packet Ensemble Protocol ;S CSP Compucom Speedmodem ;S V32T V.32 Terbo mode (implies V.32Bis) ;S VFC Rockwell's V.Fast Class ;S ZYX Zyxel 16.8 Kbps (implies V.32Bis & V.42Bis) ;S V90C ITU-T V.90 modem Client. A modem having this capability ;S can connect to a V90S-capable modem and potentially ;S achieve 56 kbit/s throughput in the direction server to ;S client and normal V.34-type througput in the opposite ;S direction. ;S V90S ITU-T V.90 Server. A device having this capability ;S is mandatorily connected to the telephone network using ;S a digital interface (probably ISDN) and can connect with ;S any other V90-capable device. ;S V90S <-> V90S: symmetrical 64kb link can be established. ;S V90S <-> V90C: see V90C user-flag ;S X2C US Robotics x2 client. A modem having this capability ;S can connect to an X2S-capable modem and potentially ;S achieve 56 kbit/s throughput in the direction X2S to X2C ;S and normal V.34-type througput in the opposite ;S direction. ;S X2S US Robotics x2 server. A device having this capability ;S is mandatorily connected to the telephone network using ;S a digital interface (probably ISDN) and can connect ;S either to another X2S-capable device or to an ;S X2C-capable device. In the former case, a symmetrical ;S 64kbit/s link can be established. The latter case is the ;S reverse of what is described under the X2C flag. ;S Z19 Zyxel 19.2 Kbps (implies V.32Bis & V.42Bis & ZYX) ;S Can be used in combination with the V34-flag indicating ;S V34 with ZyXEL-proprietary-protocol support ;S ;S NOTE: Many V22 modems also support Bell 212A. ;S ;S If no modem flag is given, ITU-T V.22 is assumed within zone 2 ;S for 1200bps, while Bell 212A is assumed for 1200 bps systems in ;S other zones, ITU-T V22bis is assumed for 2400 bps systems. ;S ;S A separate modem capability flag should not be used when it can be ;S determined by the modem flag. For instance, a modem flag of HST ;S implies MNP. V32B implies V32 and V42B implies V42. MNP,HST and ;S V32,V32B and V42,V42B flag pairs are unnecessary. H14 implies HST ;S and H16 implies H14 as well as V42.Bis . ;S ;S The following flags define the type(s) of compression of mail ;S packets supported. ;S ;S Flag Meaning ;S ;S MN No compression supported ;S ;S NOTE: The only compression method standard in ;S FidoNet is archiving, using the standard SEA ARC ;S format, with archive names defined by the ;S specification for ARCMail 0.6. The absence of the ;S MN flag indicates that ARCMail 0.6 compression is ;S supported by this node. Additional compression ;S algorithms may be supported. ;S ;S The following flags indicate the types of file/update requests supported: ;S ;S +------+-------------------------+-------------------------+ ;S | | Bark | WaZOO | ;S | +------------+------------+-------------------------+ ;S | | File | Update | File | Update | ;S | Flag | Requests | Requests | Requests | Requests | ;S +------+------------+------------+------------+------------+ ;S | XA | Yes | Yes | Yes | Yes | ;S | XB | Yes | Yes | Yes | No | ;S | XC | Yes | No | Yes | Yes | ;S | XP | Yes | Yes | No | No | ;S | XR | Yes | No | Yes | No | ;S | XW | No | No | Yes | No | ;S | XX | No | No | Yes | Yes | ;S +------+------------+------------+------------+------------+ ;S ;S The following software is qualified to use the appropriate file request flag: ;S ;S +---------------------------------------+ ;S | File Req Flag Software Package | ;S +---------------------------------------+ ;S | XA Frontdoor <1.99b | ;S | Frontdoor 2.01+ | ;S | Dutchie 2.90c | ;S | Binkleyterm >2.1 | ;S | D'Bridge <1.3 | ;S | TIMS | ;S | Xenia | ;S +---------------------------------------+ ;S | XB Binkleyterm 2.0 | ;S | Dutchie 2.90b | ;S +---------------------------------------+ ;S | XC Opus 1.1 | ;S +---------------------------------------+ ;S | XP Seadog | ;S +---------------------------------------+ ;S | XR Opus 1.03 | ;S +---------------------------------------+ ;S | XW Fido >12M | ;S | Tabby | ;S +---------------------------------------+ ;S | XX D'Bridge > 1.30 | ;S | Frontdoor 1.99b | ;S | InterMail 2.01 | ;S | T-Mail | ;S +---------------------------------------+ ;S | None QMM | ;S +---------------------------------------+ ;S ;S The following flag defines gateways to other domains (mail networks): ;S ;S Flag Meaning ;S ;S Gx..x Gateway to domain 'x..x', where 'x..x` is a string ;S of alphanumeric characters. ;S ;S NOTE: Valid values for 'x..x' are assigned by the FidoNet ;S International Coordinator or the person appointed as ;S Internetworking Coordinator by the FidoNet ;S International Coordinator. Current valid values of ;S 'x..x' may usually be found in the notes at the end ;S of the current FidoNet nodelist. The most common ;S gateway flag is "GUUCP", to denote a gateway to the ;S Internet mail system that gates on behalf of the ;S fidonet.org internet domain. ;S ;S Registered domain gateways include: ;S ;S UUCP to be used only for nodes with an MX-entry ;S in the internet dns-table of the z2.fidonet.org ;S domain. It implies a willingness to act as a ;S gateway both inbound and outbound. ;S ;S The following flags define the dedicated mail periods supported. ;S They have the form "#nn" or !nn where nn is the UTC hour the mail ;S period begins, # indicates Bell 212A compatibility, and ! ;S indicates incompatibility with Bell 212A. ;S ;S Flag Meaning ;S ;S #02 Zone 2 mail hour (02:30 - 03:30 UTC) (do not use in zone-2) ;S #08 Zone 4 mail hour (08:00 - 09:00 UTC) ;S #09 Zone 1 mail hour (09:00 - 10:00 UTC) ;S #17 Zone 3 mail hour (17:00 - 18:00 UTC) ;S ;S NOTE: When applicable, the mail period flags may ;S be strung together with no intervening commas, eg. ;S "#08#09". Only mail hours other than what is standard ;S for one's own zone should be given. Since ;S observance of mail hour within one's zone is ;S mandatory, it obviously must not be indicated. ;S ;S +--------------------------------------------------------------------------+ ;S | IP Flags | ;S +--------------------------------------------------------------------------+ ;S | The IP-flag consists of two parts: | ;S | | ;S | A basic transport and an optional non-standard port, separated by | ;S | a colon. | ;S | | ;S | IBN[:24554] ......... BinkP protocol | ;S | | ;S | IFC[:60179] ......... Raw protocol as used by ifcico | ;S | | ;S | IFT[:port] .......... Denotes a system that allows FTP | ;S | | ;S | ITN[:23] ............ Telnet protocol. | ;S | | ;S | IVM[:3141] .......... Vmodem protocol | ;S | | ;S | Note: the optional non-standard port for IBN, IFC, IFT, ITN and IVN can | ;S | ===== be substituted by an IP-address, in which case the syntax is as | ;S | follows: | ;S | | ;S | IBN[:IP-addres] ......... BinkP protocol | ;S | IFC[:IP-addres] ......... Raw protocol as used by ifcico | ;S | IFT[:IP-addres] ......... Denotes a system that allows FTP | ;S | ITN[:IP-addres] ......... Telnet protocol. | ;S | IVM[:IP-addres] ......... Vmodem protocol | ;S | | ;S | IP .................. General flag for special protocol specifications, | ;S | if the other IP-flags are not relevant. | ;S | | ;S | INA[:IP-addres] ..... Flag sets the default Internet address used for | ;S | any non-email based IP-flag that does not specify | ;S | its own. | ;S | | ;S | INO4 Indicates that an otherwise IP capable node is unable to | ;S | accept incoming connections over IPv4. (FSP-1038) | ;S +--------------------------------------------------------------------------+ ;S ;S +--------------------------------------------------------------------------+ ;S | Additional Capabilities | ;S |+========================================================================+| ;S || SMTP-based transport media || ;S |+========================================================================+| ;S || IMI Mime encoded || ;S || ISE SEAT encoded || ;S || ITX TransX compatible || ;S || IUC UUencoded || ;S || The node accepts and processes e-mail messages which contain || ;S || UUencoded inbound Fidonet mail packets (one per message) || ;S || || ;S || "mail packet" = a type-2 packet file (.PKT extension) or an || ;S || archive style file (SU?, MO?..SA? extension) || ;S || that contains one or more .PKT files. || ;S || IEM Everything not defined by the aforementioned individual flags || ;S |+========================================================================+| ;S | These flags describe additional capabilities and are preliminary appro- | ;S | ved for Zone 2, but may still be updated: | ;S |+========================================================================+| ;S || E-mail-based transport media (rev. 18/9/2002) || ;S |+========================================================================+| ;S || EVY Voyager-compatible || ;S || EMA Everything not defined by the aforementioned individual flags || ;S |**************************************************************************| ;S |! The flags described above need an e-mail address for resolving, it !| ;S |! should be provided immediately following the flag but separated by a !| ;S |! colon, example: !| ;S |! <[flag]:xxx@zzz> !| ;S |! !| ;S |! If several flags share a single e-mail address then the IEM-, resp. !| ;S |! EMA-flag will be the advised location for the primary email address, !| ;S |! if technically possible. !| ;S |**************************************************************************| ;S +--------------------------------------------------------------------------+ ;S ;S ISDN nodelist flags as per FTS-5001 : ;S ------------------------------------- ;S ;S Nodelist Specification of minimal support required for this flag; ;S flag any additional support to be arranged via agreement between users ;S ======== ================================================================= ;S V110L ITU-T V.110 19k2 async ('low'). ;S V110H ITU-T V.110 38k4 async ('high'). ;S V120L ITU-T V.120 56k async, layer 2 framesize 259, window 7, modulo 8. ;S V120H ITU-T V.120 64k async, layer 2 framesize 259, window 7, modulo 8. ;S X75 ITU-T X.75 SLP (single link procedure) with 64kbit/s B channel; ;S layer 2 max.framesize 2048, window 2, non-ext.mode (modulo 8); ;S layer 3 transparent (no packet layer). ;S ISDN Other configurations. Use *only* if none of the above fits. ;S =========================================================================== ;S NOTE: No flag implies another. Each capability MUST be specifically listed. ;S If no modem connects are supported, the nodelist speed field should be 300. ;S =========================================================================== ;S ;S The final field may be used for user-specific values. If present, ;S this field MUST be the last field present in the nodelist entry. The ;S user field is separated from the rest of the nodelist entry by a ;S comma (,) and the first character is an upper case "U". Flags ;S within this field are separated from each other with a single ;S comma. ;S ;S Field Meaning ;S ;S Ux..x A user-specified string, which may contain any ;S alphanumeric character except blanks. This string ;S may contain one to thirty-two characters of ;S information that may be used to add user-defined ;S data to a specific nodelist entry. The string "U," ;S should NOT be repeated, eg, "U,XXX,YYY" not "UXXX,UYYY". ;S ;S For maximum compatibility with FTN software, it is ;S recommended that the initial "U" is immediately followed ;S by a comma and then any user flags required, as in the ;S above example. ;S ;S This string is NOT to be used for advertisements, or ;S non-essential information. If you have questions ;S concerning the use of this string, please contact your ;S Network, Regional or Zone Coordinator. ;S ;S In zone 2 this string can only contain elements ;S which have been authorised by ZC/2. They are weekly ;S published in this nodelist-epilog. ;S ;S ;S Special flag: "PING" without any argument ;S ;S Meaning: ;S ;S Nodes flying this flag will adhere to the following functionality: ;S ;S 1) PING-function: ;S """"""""""""""""" ;S If a message destined to "PING" arrives at its final destination ;S and this final destination flies the "PING"-flag, then the ;S receiving node will bounce the message back to the original ;S sender clearly displaying all the original via-lines. ;S ;S If a message destined to "PING" arrives at its final destination ;S but this final destination does _not_ fly the "PING"-flag then the ;S message may be deleted from the inbound-queue without further ;S follow-up. ;S ;S 2) TRACE-function: ;S """""""""""""""""" ;S If a message destined to "PING" arrives at a node which flies ;S the PING-flag but is merely passing-through to another destination ;S then the in-transit node will notify the sender of this occurence ;S and will forward the original mail unaltered towards its final ;S destination. ;S ;S System open hours: ;S ;S Txx Availability flag for non-CM nodes indicating the ;S hours during which the node is available in addition ;S to ZMH. This must be in accordance with the directives ;S in FTS-5001 5.7 and the reference table reproduced ;S below. ;S ;S ATTENTION : All times are UTC! ;S ;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+ ;S |Letter|Time| |Letter|Time| |Letter|Time| |Letter|Time| |Letter|Time| ;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+ ;S | A |0000| | F |0500| | K |1000| | P |1500| | U |2000| ;S | a |0030| | f |0530| | k |1030| | p |1530| | u |2030| ;S | B |0100| | G |0600| | L |1100| | Q |1600| | V |2100| ;S | b |0130| | g |0630| | l |1130| | q |1630| | v |2130| ;S | C |0200| | H |0700| | M |1200| | R |1700| | W |2200| ;S | c |0230| | h |0730| | m |1230| | r |1730| | w |2230| ;S | D |0300| | I |0800| | N |1300| | S |1800| | X |2300| ;S | d |0330| | i |0830| | n |1330| | s |1830| | x |2330| ;S | E |0400| | J |0900| | O |1400| | T |1900| | | | ;S | e |0430| | j |0930| | o |1430| | t |1930| | | | ;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+ ;S ;S Zone 2 authorised 'user' flags: ;S ;S NetWork Coordination ;S ;S NC Network Coordinator. This flag is ONLY to be used by ;S the Network Coordinator of a net which has split the ;S duties of NC and Host and the NC does NOT occupy the ;S Net/0 position in the nodelist. ;S ;S EchoMail Coordination: ;S ;S REC Regional EchoMail Coordinator. Not more than one ;S entry in any region may carry this flag and that must ;S be the current Regional EchoMail Coordinator. ;S ;S NEC Network EchoMail coordinator. Not more than one entry ;S in any net may carry this flag and that must be the ;S current Network EchoMail Coordinator of that Net. This ;S flag will be authorised by the relevant Regional EchoMail ;S Coordinator. ;S ;S Note: * Redundant AKAs used to indicate EchoMail ;S Coordination functions are no longer permitted. ;S * One *EC-flag is valid for all AKA's of a given ;S sysop ;S ;S Pointlists ;S ;S RPK Regional Pointlist Keeper. ;S ;S This user-flag identifies the person who compiles the ;S region-pointlist (only 1 entry per region allowed) ;S ;S NPK Net Pointlist Keeper. ;S ;S This user-flag identifies the person who compiles the ;S net-pointlist (only 1 entry per net allowed) ;S ;S Special userflags: ;S ;S ENC The node accepts inbound encrypted mail ;S ;S CDP CD-Point capable (i.e. automatic point creation) ;S ;S SDS Software Distribution System ;S ;S SMH Secure Mail Hub ;S ;S Special technical nodenumbers: ;S ;S z:z/z Fidonews-editor (Bjorn Felten) ;S ;S z:z/1000 IC ;S ;S 2:2/1002 Postmaster of "z2.fidonet.org". Internet-gates as well ;S as use of the GUUCP must be approved by this person. ;S ;S 2:2/1003 Zone Pointlist Keeper (ZPK) ;S ;S ************************************************************************** ;S *** END EPILOG-SECTION FOR A ZONE2 NODELIST *** C1