The F I D O N E W S Volume 30, Number 01 07 Jan 2013 +--------------------------+-----------------------------------------+ | |The newsletter of the | | | | | FidoNet community. | | Netmail attach to (POTS): | | | | | Editor @ 2:2/2 (+46-31-960447) | | | ____________| | | | | / __ | Netmail attach to (BinkP): | | | / / \ | Editor @ 2:203/0 | | | WOOF! ( /|oo \ | | | \_______\(_| /_) | Email attach to: | | _ @/_ \ _ | bfelten @ telia dot com | | | | \ \\ | | | | (*) | \ ))| | | |__U__| / \// | Editor: Bj”rn Felten | | ______ _//|| _\ / | | | / Fido \ (_/(_|(____/ | Newspapers should have no friends. | | (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+ Table of Contents 1. FOOD FOR THOUGHT ......................................... 1 2. FTSC INFORMATION ......................................... 2 FRL-1036.001 ............................................. 2 FTS-5004.001 ............................................. 5 3. GETTING FIDONET TECHNICAL ................................ 10 BBS name field ........................................... 10 4. FROM THE *CS ............................................. 13 Has anyone seen or heard from Zone-4 lately ? ............ 13 5. GENERAL ARTICLES ......................................... 14 Annuncio vobis gaudeum magnum ............................ 14 6. FIDONET'S INTERNATIONAL KITCHEN .......................... 15 Cooking with Ward ........................................ 15 7. JAMNNTPD SERVERS LIST .................................... 17 The Johan Billing JamNNTPd project ....................... 17 8. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 18 FidoNet Software References .............................. 18 9. SPECIAL INTEREST ......................................... 23 Nodelist Stats ........................................... 23 10. FIDONEWS INFORMATION .................................... 25 How to Submit an Article ................................. 25 Credits, Legal Infomation, Availability .................. 27 FIDONEWS 30-01 Page 1 7 Jan 2013 ================================================================= FOOD FOR THOUGHT ================================================================= More computing sins are commited in the name of efficiency (without necessarily achieving it) than for any other single reason -- including blind stupidity. -- W.A. Wulf ----------------------------------------------------------------- FIDONEWS 30-01 Page 2 7 Jan 2013 ================================================================= FTSC INFORMATION ================================================================= FRL-1036.001 Publication: FRL-1036 Revision: 1 Title: IPv6 numbers in the nodelist. Author(s): Michiel van der Vlist Date: 6 Jauary 2013 ---------------------------------------------------------------------- Contents: 1. Introduction. 2. The problem. 3. The solution. ---------------------------------------------------------------------- Status of this document ----------------------- This document is a Fidonet Reference Library Document (FRL) This document preserves FSP-1036 which is integrated in FTS-5000 and FTS-5001. This document is released to the public domain, and may be used, copied or modified for any purpose whatever. 1. Introduction --------------- In addition to the classic modem connection over telephone lines, FidoNet increasingly makes use of the InterNet for its links. This means InterNet contact information needs to be in the nodelist. Up to now, this has been in the form of IP quads and fqdn's. (Fully Qualified Domain Names). In the future the need to have IPv6 addresses in the nodelist may very well arise. There is a problem however. 2. The Problem -------------- The format of an IPv6 address is: Eight hexadecimal values in the range 0-FFFF separated by a colon. One or more successive zero values may once be represented by two successive colons. F.e. 1234::6789:abcd expands to 1234:0:0:0:0:0:6789:abcd. The problem is that the colon is already in use to separate a node- FIDONEWS 30-01 Page 3 7 Jan 2013 list flag from its parameter(s), that some flags may carry a varia- ble number of parameters and that the colon is also used to sepa- rate parameters from each other. E.g. a flag carrying both a host name and a port number: FLAG:fido.vlist.eu:24555 Having the same character for separating parameters as for separa- ting individual items within a multidimensional parameter creates a parsing problem. Does 1234::6789:abcd:5678 resolve to address 1234:0:0:0:0:0:6789:abcd with a port number of 5678 or does it resolve to just an address of 1234:0:0:0:0:6789:abcd:5678 and no port number specified? 3. The Solution --------------- Whenever an IPv6 address is to appear as a parameter in the nodelist the address shall be encased in square brackets. This follows the practise described in RFC 2732 paragraph 2 and RFC 3986 paragraph 3.2.2 for literal IPv6 addresses in URL's and URI's. Example: FLAG:[2002:4f87:44d5::1]:443 References ---------- [FTS-5] "The distribution nodelist", Ben Baker, Rick Moore. February 1989. Obsoleted by FTS-5000. [FTS-5000] "The distribution nodelist". FTSC Members, Administrator and Honoured Guests Jan 2005. [FTS-5001] "Nodelist flags and userflags". FTSC Members, Administrator and Honoured Guests Jan 2005. [RFC1883] S. Deering, R. Hinden. Internet Protocol, version 6 (IPv6) Dec 1995 [RFC1884] S. Deering, R. Hinden. IP Version 6 Addressing Architecture. Dec 1995 [RFC2732] R. Hinden, B. Carpenter, L. Masisnter. Format for Literal IPv6 Addresses in URL's Dec 1999. FIDONEWS 30-01 Page 4 7 Jan 2013 [RFC3986] T. Berners Lee, R. Fielding, L. Masinter. Uniform Resource Identifier (URI): Generic Syntax Jan 2005. Contact Data ------------ Michiel van der Vlist Fidonet: 2:280/5555 E-mail: pa0mmv at vrza dot org E-mail: administrator at ftsc dot org History ------- Rev.1, 20100309: Initial Release. Principal author Michiel van der Vlist. 20130106: Preserved in FRL-1036. ********************************************************************** ----------------------------------------------------------------- FIDONEWS 30-01 Page 5 7 Jan 2013 FTS-5004.001 Publication: FTS-5004 Revision: 1 Title: DNS Distributed Nodelist Author(s): Alexey Vissarionov, 2:5020/545 FTSC members and administrator Issue Date: 6 January 2013 ===================================================================== Contents: 0. Introduction 1. Translation of a Fidonet address into a host name 2. Service port location 3. Resolving algorithm 4. NS zone generation 5. Examples 6. References 0. Introduction Abstract: This document describes the method of distributing Fidonet nodelist data through the DNS infrastructure for use by IP-capable Fidonet mailers. Status: This document is a Fidonet Technical Standard (FTS) - it specifies the best current practices for the Fidonet community. It is hereby released to the public domain, and may be used, copied or modified for any purpose whatever. This document supersedes and replaces FSP-1035. FSP-1035 is preserved in the FTSC reference library as FRL-1035. 1. Translation of a Fidonet address into a host name. The format of Fidonet address is: Z:N/F.P@W Where the fields are: Z - Zone Number: The zone the node is part of. N - Net Number: The network the node is a member of. F - Node Number: The actual node number. FIDONEWS 30-01 Page 6 7 Jan 2013 P - Point Number: If the system is a point rather than a node then this is their point number at that node. Optional. If ".P" is missing then assume 0 (node itself). W - Network name: The name of the "Fidonet Technology Network". Optional. Fidonet address should be translated into host name as: [pP.]fF.nN.zZ.RD. where the fields refer to... P - Point Number, as in Fidonet address (FA) Optional. F - Node Number, as in FA Must be present. N - Net Number, as in FA Must be present. Z - Zone Number, as in FA Must be present. RD - Root Domain assigned to DDN. Must be present. In the past, when a node carried IP protocol flags, but no IP connec- tion information, it was often assumed to partake in the fidonet.net project and that the information could be found there. The fidonet.net domain however was lost for the Fidonet community in 2011 when the keeper allowed it to expire. Dependence on an individual to maintain the domain registration is a weakness of the DDN system, therefore it is strongly recommended that implementations that make use of a DDN service allow the user to easily configure the root domain and to configure overrides for often used stationary links so that these links won't be lost when the DDN service is interrupted or discontinued. Please note the trailing dot - it should exist in "host name" parameter when making the DNS query to avoid resolving hosts like "f545.n5020.z2.ddn.example.tld.office.local. instead of "f545.n5020.z2.ddn.example.tld." As points normally don't accept incoming connections, the rest of this document uses node addresses for any and all examples. However, the techniques described here may be used for points as well. 2. Service port location. FIDONEWS 30-01 Page 7 7 Jan 2013 If a node accepts connections on a non-standard port, NS zone should contain a SRV record for every protocol flag. Format of SRV record is: _service._proto.name IN SRV priority weight port host Where the fields are: service: service name - "binkp" or "ifcico"; other names may be added in the future proto: protocol family - only "tcp" is used for now name: record name priority: host priority, lower value means more preferred; if record contains only one host, this value should be set to zero weight: relative weight for records with the same priority, used for load-balancing; if no load-balancing is performed, this value should be set to one port: decimal number of the TCP or UDP port host: the hostname of the machine providing the service. 3. Resolving algorithm. * Query DDN for SRV record. If it exists - perform connection using resolved hostname:port pair. * Query DDN for AAAA and A records. On success, perform connection using resolved address and default port. * If both failed, return the "server not found" error. Note: CNAME targets MUST NOT be queried for SRV records. 4. NS zone generation. The only valid source for DDN records is FTS-5000 world nodelist. Data from partial (network etc.) segments SHOULD NOT appear in DDN until they get into world nodelist. Data from any sources other than nodelist MUST NOT appear in DDN NS zones. To be published in DDN, the node MUST have at least one Internet address published in the nodelist. The IP protocol flags or the INA flag SHOULD be used for that purpose, but some nodes use the system name instead, so the implementations SHOULD look for a hostname in the protocol flag, the INA flag and the system name field in that order. Multiple INA flags MAY be used if they carry different addresses. Multiple IP protocol flags MAY be used for different port numbers; if the default port is listed among others, the SRV record for it MUST be added to resulting NS zone. If the INA flag (or any of the protocol flags) of any node carries host name built from the FTN address using DDN or any other method, FIDONEWS 30-01 Page 8 7 Jan 2013 that node MUST be skipped and MUST NOT appear in resulting NS zone. In general, such names SHOULD NOT appear in the nodelist. 5. Examples. This section contains some examples of valid records which may appear in DDN. ; INA:fido.example.net,IBN ; no SRV record required f9999 IN CNAME fido.example.net. ; INA:192.0.2.123,INA:[2001:0DB8:F1D0::2:5020:9999],IBN ; both A and AAAA records are created _binkp._tcp.f9999 IN SRV 0 1 24554 f9999 f9999 IN A 192.0.2.123 IN AAAA 2001:0DB8:F1D0::2:5020:9999 ; INA:fido.example.net,IBN:12345 _binkp._tcp.f9999 IN SRV 0 1 12345 fido.example.net. ; INA:192.0.2.123,IBN:12345 _binkp._tcp.f9999 IN SRV 0 1 12345 f9999 f9999 IN A 192.0.2.123 ; INA:fido.example.net,IBN,IBN:12345 ; here the default port is supported, so we use CNAME to provide ; backward compatibility for old mailers ; also, some sort of (equal) load-balancing is performed here _binkp._tcp.f9999 IN SRV 0 1 24554 fido.example.net. IN SRV 0 1 12345 fido.example.net. f9999 IN CNAME fido.example.net. ; IBN:192.0.2.123,IBN:fido.example.net:12345 ; only first record (numeric IP) will be available to old mailers _binkp._tcp.f9999 IN SRV 0 1 12345 fido.example.net. IN SRV 0 1 24554 f9999 f9999 IN A 192.0.2.123 ; INA:fido.example.net,IBN:fido.example.com,IFC:12345 ; both mailers listen at fido.example.net, but only binkp-capable ; mailer listens at fido.example.com ; ifcico-capable mailer uses non-standard port ; also, CNAME record is created to provide backward compatibility ; for old binkp-capable mailers _binkp._tcp.f9999 IN SRV 0 1 24554 fido.example.net. IN SRV 0 1 24554 fido.example.com. _ifcico._tcp.f9999 IN SRV 0 1 12345 fido.example.net. f9999 IN CNAME fido.example.net. ; INA:fido.example.net,IBN,IFC:fido.example.com:12345 ; both mailers listen at fido.example.net, but only ifcico-capable ; mailer listens at non-standard port on fido.example.com _binkp._tcp.f9999 IN SRV 0 1 24554 fido.example.net. _ifcico._tcp.f9999 IN SRV 0 1 12345 fido.example.com. IN SRV 0 1 12345 fido.example.net. FIDONEWS 30-01 Page 9 7 Jan 2013 f9999 IN CNAME fido.example.net. ; IBN:fido.example.net,IFC:fido.example.com:12345 ; no INA flag means there's no common address _binkp._tcp.f9999 IN SRV 0 1 24554 fido.example.net. _ifcico._tcp.f9999 IN SRV 0 1 12345 fido.example.com. f9999 IN CNAME fido.example.net. 6. References. FTA-1006 "Key words to indicate requirement levels" FTS-5000 "The Distribution Nodelist" FTS-5001 "Nodelist flags and userflags" FTS-1026 "Binkp/1.0 Protocol specification" FTS-1024 "Raw ifcico mail transfer protocol" FRL-1035 "DNS Distributed Nodelist". RFC-2872 "A DNS RR for specifying the location of services (DNS SRV)" History ======= Rev.1, 20130106 - Alexey Vissarionov (2:5020/545), first release. ********************************************************************* ----------------------------------------------------------------- FIDONEWS 30-01 Page 10 7 Jan 2013 ================================================================= GETTING FIDONET TECHNICAL ================================================================= BBS name field Stas Degteff 2:5080/102@fidonet Nodelist issue: What (and who) binkp-capable nodes uses BBS name field for the indication of actual host name or IP address. Preamble. Between members of the Fidonet Standard Technical Comittee discuttion is conducted about usage a 3th field of the node line in the nodelist (BBS name field). This discuttion induced me to make small research: I selected all nodes with records contain somewhere like host name or IP address in the nodelist, next I checked these values for validity and another. Method of research. I use unixtools (grep/egrep, cut, sort, wc, string), networktools (telnet) and nmap program in the GNU/Linux enviroment. I take 1st fidonet nodelist of the 2013 produced by Ward Dossche for Zone 2: nodelist.001 at 1 jan 2013. I use following commands to select data from nodelist: grep -v '^;' nodelist.001 - for drops all comment lines; cut -d , -f 3 - for take 3th field from node lines; egrep '([A-Z].+)?,[0-9]+,[0-9]+\.[0-9.]+,' - for select nodes with IPv4 address in the 3th field; egrep -i '([A-Z].+)?,[0-9]+,\[[0-9a-f]+:[0-9a-f:]+\],' - for select nodes with IPv6 address in the 3th field; egrep -i '([A-Z].+)?,[0-9]+,[[:alnum:]]+\.[[:alnum:].-]+[a-z]{2},' - for select nodes with some like host name in the 3th field; egrep 'IBN:[0-9]+(,|.$)' - for select nodes with port specified in the IBN flag; cut -d , -f 3 | egrep -v '(_|fidonet\.net)' - for exclude ahead invalid values in the 3th field ("_" are invalid char for the host name according RFC 1035, "fidonet.net" are lost domain name for fidonet community); egrep -v ',INA:' - for exclude nodes with hostname or IP address specified in the INA flag; egrep -i ",IBN:[0-9a-z-]+\.[0-9a-z.-]+(,|.$)" - for select nodes with hostname or IP address specified in the IBN flag; egrep ",IBN:[0-9]+(,|.$)" - for select nodes with port specified in the IBN flag; sort -u | wc -l - for count unique values; nmap -sT -p24554 (hosts list) - for mass-testing binkp port on many hosts. FIDONEWS 30-01 Page 11 7 Jan 2013 In the several cases I use manual operations for node alive testing. I look an alternate port in the "IBN:portnumber" field and I used "telnet" program to connect to his port of host presented in the 3th field. If telnet returned binkp handshake sequence, I tried to extract (FTN) address of the node using a "string" utility. Results of research. 1. Nodes with IPv6 address in the BBS name field: none. 2. Nodes with IPv4 address in the BBS name field: 9 all, 7 unique IP addresses. 3. Nodes with hostname-like value in the BBS name field: 291 all, 274 unique, 81 with fidonet.net hierarhy (80 unique). 194 approaches to real host names. 4. Nodes with IPv4 address in the BBS name field and nor "INA:host_or_address" nor "IBN:host_or_address" flags: 5 unique IP. 5. Nodes with hostnames in the BBS name field and nor "INA:host_or_address" nor "IBN:host_or_address" flags (part of 194 nodes): 146 unique (and tested later). 6. Tested nodes with IPv4 address in the BBS name field and nor "INA:" nor "IBN:host_or_address" flags (5 unique IP addresses): 2 hosts up, but only one host replies with binkp. 7. Tested nodes with approaches to real host name in the BBS name field and nor "INA:host_or_address" nor "IBN:host_or_address" flags (make test for standard binkp port 24554): 144 unique hosts, 113 IP addresses resolved, 75 hosts up and only 52 nodes replied on binkp. 8. Special case - test nodes with approaches to real host name in the BBS name field and nor "INA:host_or_address" nor "IBN:host_or_address" flags but with port number in "IBN:port": - 2:222/42 replies on specified 200/TCP with binkp; - 2:2432/344 AKA 2:2432/348 replies on specified 24555/TCP with binkp, and repries on standard 24554/TCP with binkp with AKA 2:2432/349 (third node of same sysop), separate node with alternate port is not needed for this case. 9. Nodes wih IP address in 3rd field and nonstandard port is not exist in nodelist. Some selective control tests. A. Tested nodes with IPv4 address in the BBS name field and presented "INA:": - 2:5020/214 - IP in the 3rd field same as in "INA:"; - 2:5020/4441 - IP in the 3rd field different with hostname in "INA:" and node replies only on hostname specified in "INA:" flag (3rd field contain invalid IP address or not an IP address but only similar to IP address). B. Nodes with different information in the "INA:" and 3rd field: - 2:5011/92 - "izverg.no-ip.info" in the 3rd field and invalid (outdated) "INA:f92.n5011.z2.fidonet.net", node don't reply on binkp; - 2:5000/54 - "f54.n5000.z2.fidonet.net" in the 3rd field are invalid and connect to "fido.olmisoft.com" (taken from "INA:fido.olmisoft.com") rejected; - 2:464/95 - "pedal.isd.dp.ua" in the 3rd field are invalid because resolved to nonroutable (intranet) IP address 10.98.3.58 (see RFC1918); FIDONEWS 30-01 Page 12 7 Jan 2013 - 2:2437/224 - "travelbit.dyndns.org" in the 3rd field and "INA:travelbit.servebeer.com" resolved to same IP; - 2:2/1002 - "fidonet.org" in the 3rd field is not node's hostname but address of mail server, host name looks in "INA:many-glacier.mine.nu". Corollaries. BBS name field uses for present actual information about connectivity very few nodes (53 from 3100 non-technical nodes) and this method may be recognized the outdated now and should be obsoleted in the official documents. Respectively I will delete this way from my DDN-script and DDN generating on my node - nodelist.grumbler.org. (See FTS-5004 or FSP-1035 "DNS Distributed Nodelist" for information about DDN.) Done. If you want to discuss with me, you may write message to "FIDONEWS" echo but please type "Stas Degteff" into "TO:" field that I saw this message in carboncopies area. Or you may write netmail to me. ----------------------------------------------------------------- FIDONEWS 30-01 Page 13 7 Jan 2013 ================================================================= FROM THE *CS ================================================================= Has anyone seen or heard from Zone-4 lately ? By Ward Dossche 2:292/854 Open Letter to Manuel Adorni, Z4C ... at least that's what the nodelist says he is. Manuel, 2 months ago, around Nov.15 2012, you requested access to the zone-2 sysop conference ENET.SYSOP in order for you to make your case for the continuation of Z4. Your request was immediately granted. On my turn I then asked access to LATIN.SYSOP which according to the prolog in your ZONE-segment is the official Zone-4 sysop conference "where everything is discussed". Not only did you not reply me in netmail, not in echomail, not in email nor in the closed ZCC-conference ... there simply has been no sign of life coming from you anymore. I went searching for this conference LATIN.SYSOP, but nowhere is it available. Not a single system carries it. The question is painfully clear: what's up? If there still is a zone-4 please show yourself and just not hide until a ZCC-vote is needed somewhere and someone will miraculously strangle a vote from you. If you're not up to the job, please get someone else to do it. If there's no-one else ... pls disband this phalacy and join Z1 for the same time-zone or R34 here for the Spanish language. If zone-4 does not exist nor shows a sign of life, there is no reason to further include it in the nodelist. Please respond. Take care, \%/@rd ----------------------------------------------------------------- FIDONEWS 30-01 Page 14 7 Jan 2013 ================================================================= GENERAL ARTICLES ================================================================= Annuncio vobis gaudeum magnum : Conferentiae regulus LATIN Ward Dossche 2:292/854 Conferentiae regulas LATIN -- III I MMXIII I. In EchoMail area LATIN creata est propositum SysOp communicationem in FidoNet in lingua Latina. II. Hoc colloquio sit amet participes descripserunt in album participantium FidoNet. Duis locis legimus, ut fiat users Sysops de aliis networks coniungantur ad discrecionem recipiendi nodorum, in tantum legere, basis. Tem, ut singulis invitatos ad participant. III. Manubria "possunt" utendum, dummodo nuntius est "signati." aut "de" agrum vel subscriptio oportet continent sysop genuinum nomen sicut est definitur in album participantium Fidonet. IV. Messages esse debet ex summam rem ad alia FidoNet sysops sed parum limitation ponitur super content: Oppugnationibus individuum sunt SEMPER off-topic, ut sunt sacrilegiorum ac vendo. V. Si conloquio statuendum est contra regulas aut aliquis fluminis ratio regit, accipiat quisque indicium. Si confractione prosequitur est, duo monitis erit edenda ante terminabitur individui, tempus colloquii aditus ut stabiliatur tempore talis terminatio fit. In casu extremae delinquendi, immediatum terminatio accesso potest individui, petenda est a turpis. Ward Dossche moderatrix LATIN ----------------------------------------------------------------- FIDONEWS 30-01 Page 15 7 Jan 2013 ================================================================= FIDONET'S INTERNATIONAL KITCHEN ================================================================= Cooking with Ward By Ward Dossche 2:292/854 There must be something better than re-hashed internet-recipes, I figured, so here's one of my favourites: Red cabbage, sausages and potatoes. This serves 4. Ingredients * 4 fresh sausages (pork+veal) * 1/2 red cabbage * 3 large apples to stew * 2 tablespoons real butter * 2 tablespoon brown sugar * 1 cup red wine * 1 dash of vinegar * fresh thyme * fresh bay * 4 juniper berries * 2 cloves * half a kilo potatoes to boil * pepper * salt * mild mustard Preparation * Remove the sausages from the refrigerator and let the meat come to room temperature. They will be less likely to burst while frying * Remove the outer leaves from the red cabage. Cut in half, save the other half for whatever. Remove the white center and grate it into small pieces * Slowly melt the butter on a low temperature in a large casserole and add the shredded red cabbage * Peel the apples and grate the flesh. Also add it to the pot with cabbage and stir everything thoroughly. * Crush the juniper berries so they'll release more taste. Put them together with the cloves into a tea infuser. Later easy to remove. * Tie with kitchen twine a few sprigs of fresh thyme and a few bay leaves together, drop that bouquet in the pot as well. * After a few minutes turn the heat up and add the red wine. Allow the moisture to evaporate, stirring a bit and then turn the heat back down. * Add the brown sugar, stir and let the dish simmer for an hour. Stir oncein a while. * Sprinkle a tablespoon of vinegar or two and stir. Remove the tea infuser and herb bundle. * Peel the potatoes and boil in salted water. * Prick a few holes in each sausage (three is enough) and season to taste with salt and pepper from the mill. FIDONEWS 30-01 Page 16 7 Jan 2013 * Heat a frying pan with a knob of butter in it. Choose a pan in which all the sausages fit in one effort. * Fry the sausages on one side in the hot butter and then turn them gently. (no pricking anymore) * Place a lid on the pan, and let the sausages continue cooking over medium heat. * Serve the sausages with potatoes and fresh red cabbage with a spoon of mild mustard. ----------------------------------------------------------------- FIDONEWS 30-01 Page 17 7 Jan 2013 ================================================================= JAMNNTPD SERVERS LIST ================================================================= The Johan Billing JamNNTPd project This is a list of known JamNNTPd servers working. They are essentially the modern version of Bulletin Board Systems. You connect to them using the email client of your choice and you don't need any other software installed on your computer -- regardless of operating system -- but that favourite mail client of yours. Even smart phones can handle this, giving you the opportunity to get your daily doses of fidonet on the bus, tram or train on the way to your job, school or whatever. Updated 2012-03-11 URL news://felten.yi.org Join http://felten.yi.org/join.html NETMAIL Yes, 2:203/2 URL news://the-estar.com:1119 Join http://www.easternstar.info NETMAIL Yes, 1:123/789 URL news://quinnspost.dyndns.org:60119 Join mailto:eskimo261@bigfoot.com NETMAIL No URL news://nntp.rbb.bbs.fi Join Info in group +GETACCESS+ NETMAIL Yes, 2:221/361 URL news://news.wpusa.dynip.com Join Info in group +GETACCESS+ NETMAIL Yes, 1:3634/12 ----------------------------------------------------------------- FIDONEWS 30-01 Page 18 7 Jan 2013 ================================================================= FIDONEWS'S FIDONET SOFTWARE LISTING ================================================================= -=:{ FidoNet Software Reference }:=- Type: M=Mailer T=Tosser B=BBS D=Door C=Comm/Terminal P=Points E=Editor I=Internet U=Utility ?=Info .- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -. |Software: Author |Type |URL, Contact, Ver, Notes Help Node| `- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -' Argus |MI |http://www.ritlabs.com/argus/ 2:469/84 | | argus@ritlabs.com Tel: 373-2-246889 | | v3.210 on Mar 20th 2001 BinkleyTerm XE |M |http://btxe.sourceforge.net 1:1/102 | | v2.60XE/Gamma-6 on Nov 11th 1998 BinkD |MI |http://binkd.grumbler.org/ 2:463/69 | | v0.9.10 on Oct 2nd 2008 D'Bridge |MTCPE|http://www.net229.org/dbridge.htm 1:1/130 Nick Andre |I | v3.8 on July 10 2012 FIDO-Deluxe IP |MPUI |http://www.fido-deluxe.de.vu 2:2432/280 Michael Haase | | m.haase@gmx.net | | v2.4 on Sep 26th 2003 FrontDoor, FD/APX: |MTPC |http://www.defsol.se 2:201/330 Definite Solutions | | sales@defsol.se 1:1/101 | | v2.26SW & v2.33ml FD, v1.15 APX Husky Project |MTPUI|http://sf.net/projects/husky/ | | v1.4 RC5 on Apr 24th 2006 Radius |MI |http://radius.pp.ru 2:5012/38 (based on Argus) | | fido5012@zaural.net Tel: 7-3522-469463 | | Last Release: v4.010 on Jan 3nd 2005 Taurus |MI |http://taurus.rinet.ru (Russian) 2:461/70 | |http://www.fidotel.com/taurus (English) (based on Radius) | | E-mail: taurus@rinet.ru | | v5.000 alpha on Oct 11th 2004 Tmail |MI |http://www.tmail.spb.ru v2608 | | Website is in Russian only WildCat! Interactive |MTBEI|http://www.santronics.com Net Server, Platinum| | sales@santronics.com Xpress: Santronics | | Tel: (305) 248-3204 Software, Inc. | | AUP 451.1 on April 26th 2004 +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+ Fidogate |TUI |http://www.fidogate.org FIDONEWS 30-01 Page 19 7 Jan 2013 | | Martin_Junius@m-j-s.net v4.4.10 FMail |T |http://sourceforge.net/projects/fmail/ | | v1.60.GPL JetMail: JetSys |TU |http://www.jetsys.de js@jetsys.de (ATARI ST only) | | v1.01 on Jan 1st 2000 Squish |T |http://maximus.sourceforge.net/ | | Lanuis site redirects to above | | Squish is part of Maximus. +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+ BBBS |BI |http://www.bbbs.net b@bbbs.net | | v4.00MP on Oct 25th 1999 2:22/222 ELEBBS: The Elevator |B |http://www.elebbs.com Software Production | | elebbs@elebbs.com | | v0.10.RC1 on Jun 9th 2002 Ezycom BBS |BT |http://www.ezycom-bbs.com | | ezycom@amnet.net.au or | | ezycom_hq@ezycom-bbs.com 3:690/682 | | v2.15g2 on 16 Nov 2009 Hermes II Project |B |http://www.hermesii.org | | info@HermesII.org v3.5.9 Beta Final Maximus BBS |B |http://maximus.sourceforge.net/ | | v3.03 | |Archives back online at: | |http://maximus.outpostbbs.net/ MBSE BBS: |BI |http://mbse.sourceforge.net 2:280/2802 Michiel Broek | | mbroek@users.sourceforge.net | | v0.60.0 on June 5th 2004 Mystic BBS |B |http://www.mysticbbs.com | | v1.07.3 on May 13th 2001 Nexus BBS |B |http://www.nexusbbs.net | | groberts@nexusbbs.net | | v0.99.41-Beta on Oct 16th 2002 | | [Note: No Longer under active | | development.] Proboard BBS |B |http://www.proboard.be | | v2.17 on Jun 9th 2002 RemoteAccess BBS: |B |http://www.rapro.com 1:1/120 Bruce Morse | | bfmorse@rapro.com | | v2.62.2SW Spitfire BBS: Buffalo|B |http://www.angelfire.com/ia/buffalo/ Creek Software | | MDWoltz@aol.com 1:1/150 FIDONEWS 30-01 Page 20 7 Jan 2013 | | v3.6 on Aug 20th 1999 Synchronet BBS |BT |http://www.synchro.net | | sysop(at)vert(dot)synchro(dot)net | | v3.10L Beta Telegard BBS |B |http://www.telegard.net | | support@telegard.net | | v3.09g2 SP4 +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+ Atlantis Software |D |http://www.jimmyrose.com/atlantis/ | | Last Update: August 2004 Cheepware |DU |http://outpostbbs.net Sean Dennis | | sean@outpostbbs.net 1:18/200 DDS (Doorware |D |http://www.doorgames.org 1:2404/201 Distribution System)| | ruth@doorgames.org Ruth Argust | | DoorMUD |D |http://doormud.com | | v0.98 Jun 1st 2002 | | Website is down after | | past the splash page. Jibben Software |D |http://www.jibbensoftware.com | | scott@jibben.com | | 1995-99 Release dates John Dailey Software |D |http://www.johndaileysoftware.com | | support@johndaileysoftware.com Shining Star |D |http://www.shiningstar.net/bbsdoors/ | | nannette@shiningstar.net Sunrise Doors: |D |http://www.sunrisedoors.com Al Lawrence | | al@sunrisedoors.com | | Tel: (404) 256-9518 The Brainex System |D |http://www.brainex.com/brainex_system/ | | stanley@brainex.com 1994-99 Releases Trade Wars |D |http://www.eisonline.com/tradewars/ | | jpritch@eisonline.com | | v3.09 (DOS-32) in 2002 Vagabond Software: |D |http://www.vbsoft.org 1:124/7013 Bryan Turner | | vagabond@vbsoft.org | | last update: Jul 17th 2002 +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+ APoint |PI |http://www.apoint-mail.de 2:2426/1210.13 | |http://www.apoint-mail.de/indexe.htm | | (English Version) FIDONEWS 30-01 Page 21 7 Jan 2013 | | dirk.pokorny@apoint-mail.de | | v1.25 CrossPoint (XP) |P |http://www.crosspoint.de (German Only) | | pm@crosspoint.de v3.12d Dec 22nd 1999 FreeXP |P |http://www.freexp.de 2:2433/460 | | support@freexp.de | | v3.40 RC3 Aug 31st 2003 (Snapshot) OpenXP/32 |PI |http://www.openxp.com 2:248/2004 | | (Site is in German Only) | | mk@openxp.de v3.8.15 Beta Feb 10th 2004 | | Download Page comes back 404 not found. +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+ GoldEd+ |E |http://golded-plus.sourceforge.net/ | | 2:5080/102 | | stas_degteff@users.sourceforge.net | | v1.1.5 Snapshot on Feb 28th 2003 SqEd32 |E |http://www.sqed.de | | v1.15 on Dec 15th 1999 TimEd |E |http://blizzard.dnsalias.org/fidonet | | mail@ozzmosis.com /timed | | v1.11.a5 in March 2003 3:633/267 +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+ FidoIP |MTPEIU|http://sourceforge.net/projects/fidoip | | Maxim Sokolsky 2:5020/828.777 | | v.0.5_1 on Jan 11 2010 GiGo |UI |http://www.gigo.com | | v0109 on Jan 9th 1997 Ifmail |UI |http://ifmail.sourceforge.net | | crosser@average.org 2:5020/230 | | Ifmail is a FTN <-> E-Mail/News Gateway | | Program. Internet Rex: |UI |http://members.shaw.ca/InternetRex/ Charles Cruden | | telnet://xanadubbs.ca 1:342/806 (Khan Software) | | v2.29 on Oct 21st 2001 MakeNL |U | http://hub2000.darktech.org/makenl | | fidonet.hub2000 [at] gmail [dot] com | | Fido: 1:229/2000 | | FidoNet Nodelist Processor Meltdown-BBS |UI |http://meltdown-bbs.sourceforge.net/ | | meltdown-bbs.project.petkan | | @spamgourmet.com | | Fido: 2:350/5 FIDONEWS 30-01 Page 22 7 Jan 2013 | | Meltdown-BBS is an FTN <-> | | Web/PHP/MySQL BBS forum system. RNtrack |U |http://sourceforge.net/projects/ftrack-as | |2:5080/102 | |stas_degteff@users.sourceforge.net | | v1.1.4 Snapshot on Oct 09 2009 TransNet |UI |http://www.ressl.com.ar/transnet/ | | transnet@ressl.com.ar | | v2.11 on Jul 18th 1998 TransX: Multiboard |UI |http://www.start.ca/software/multiboard Communications, Inc.| | Unsure about support now but Free Keys | | are now available. Donations accepted. | | v3.5 (Note: KeyGen is a Windows Program) Turquoise SuperStat |U |http://www.softwolves.pp.se/sw/ | | software/turquoise | | peter@softwolves.pp.se | | Version: 3.0 on 2008-01-21 +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+ National BBS List |? | http://www.usbbs.org Hispanic FIDO/BBS's |? | http://www.conecta2.org/pucela_bbs/ (in Spanish only) | | (Extensive software & BBS Listings) +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+ File Archives: http://archives.thebbs.org http://www.filegate.net http://sysopscorner.thebbs.org http://www.juge.com http://www.dmine.com/bbscorner/ http://garbo.uwasa.fi http://www.simtel.net http://wuarchive.wustl.edu http://www.bbsfiles.com http://hobbes.nmsu.edu Note: most also provide FTP access (use ftp:// instead of http:// above) *=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=* Please send corrections & additions to: Fidonews Editor Emeritus: Robert Couture, Ben Ritchey, Todd Cochrane, Frank Vest, Peter Popovich ----------------------------------------------------------------- FIDONEWS 30-01 Page 23 7 Jan 2013 ================================================================= SPECIAL INTEREST ================================================================= Nodelist Stats Input nodelist nodelist.004 size 330.5kb date 2013-01-04 The nodelist has 2309 nodes in it and a total of 3371 non-comment entries including 4 zones 35 regions 236 hosts 197 hubs admin overhead 472 ( 20.44 %) and 308 private nodes 121 nodes down 161 nodes on hold off line overhead 590 ( 25.55 %) Speed summary: >9600 = 169 ( 7.32 %) 9600 = 1489 ( 64.49 %) (HST = 21 or 1.41 %) (CSP = 0 or 0.00 %) (PEP = 1 or 0.07 %) (MAX = 0 or 0.00 %) (HAY = 1 or 0.07 %) (V32 = 710 or 47.68 %) (V32B = 48 or 3.22 %) (V34 = 979 or 65.75 %) (V42 = 833 or 55.94 %) (V42B = 51 or 3.43 %) 2400 = 11 ( 0.48 %) 1200 = 2 ( 0.09 %) 300 = 638 ( 27.63 %) ISDN = 163 ( 7.06 %) ---------------------------------------------------------- File Req Flag Applicable software Number of systems ---------------------------------------------------------- XA Frontdoor <1.99b 671 Frontdoor 2.02+ Dutchie 2.90c Binkleyterm >2.1 D'Bridge <1.3 TIMS Xenia -------------------------------------- FIDONEWS 30-01 Page 24 7 Jan 2013 XB Binkleyterm 2.0 0 Dutchie 2.90b -------------------------------------- XC Opus 1.1 1 -------------------------------------- XP Seadog 0 -------------------------------------- XR Opus 1.03 16 -------------------------------------- XW Fido >12M 66 Tabby KittenMail -------------------------------------- XX D'Bridge 1.30 718 Frontdoor 1.99b Intermail 2.01 T-Mail -------------------------------------- None QMM 837 -------------------------------------- CrashMail capable = 1167 ( 50.54 %) MailOnly nodes = 1138 ( 49.29 %) Listed-only nodes = 183 ( 7.93 %) Other = -179 ( -7.75 %) [Report produced by NETSTATS - A PD pgm] [ Revised by B Felten, 2:203/208] ----------------------------------------------------------------- FIDONEWS 30-01 Page 25 7 Jan 2013 ================================================================= FIDONEWS INFORMATION ================================================================= How to Submit an Article If you wish to submit an article for inclusion in the Fidonews, here are some guidelines, if you send it as an attached file; the preferred method if you want reasonable control over how the published article will appear in the Fidonews: a) Plain ASCII text. If you could type it on your keyboard, it's probably quite OK. No line may be longer than 70 characters. b) Put a title to the article. Put the title in two times. The first time, on the first line, with an * before it. The second time, on the second line, without the * and centered. This will help in the format since the title with the * is removed and used in the index, the second line will become the headline. On the third line, put your name and FidoNet address, present or former. If former, you may want to add some other address where you can be reached for personal comments. c) Deadline for article submission is Sunday, 22:00 UTC. Help the Editor by following the above guides. Below are some subjects and the file extension for the article as set in the configuration file for the making of the Fidonews. Please help by putting the file extension of the correct subject on the file name if known. Ideas for Subject areas: Subject File | Subject File ----------------------------------|---------------------------------- From the *C's *.css | Rebuttals to articles *.reb Fidonet Regional News *.reg | Fidonet Net News *.net Retractions *.rtx | General Fidonet Articles *.art Guest Editorial *.gue | Fidonet Current Events *.cur Fidonet Interviews *.inv | Fidonet Software Reviews *.rev Fidonet Web Page Reviews *.web | Fidonet Notices *.not Getting Fidonet Technical *.ftc | Question Of The Week *.que Humor in a Fido Vein *.hfv | Comix in ASCII *.cmx Fidonet's Int. Kitchen *.rec | Poet's Corner *.poe Clean Humor & Jokes *.jok | Other Stuff *.oth Fidonet Classified Ads *.ads | Corrections *.cor Best of Fidonet *.bof | Letters to the Editor *.let If you don't know or are not sure, send the article anyway. Put a .TXT on it and I'll try to figure out where it should be in the Fidonews. If you follow these simple guidelines, there should be little problem in getting your article published. If your submission is too far out of specs for the Fidonews, it will be returned to you and/or a message sent informing you of the problem. This DOES NOT mean that your article is not accepted. It means that there is something in it that I can not fix and I need your help on it. FIDONEWS 30-01 Page 26 7 Jan 2013 Send articles via e-mail or netmail, file attach or message to: Bj”rn Felten Fidonet 2:2/2 or 2:203/0 E-Mail bfelten @ telia dot com Skype file bfelten IMPORTANT! If you send the article via e-mail, make sure you put the word "fidonews" somewhere in the subject line! That way it will always pass the spam filter, ending up in the proper folder. Please include a message, telling me that you have sent an article. That way I will know to look for it. ----------------------------------------------------------------- FIDONEWS 30-01 Page 27 7 Jan 2013 Credits, Legal Infomation, Availability + -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- + | | | Editor: Bj”rn Felten, 2:2/2 | | | + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- + + -- -- -- -- -- -- -- - EDITORS EMERITI - -- -- -- -- -- -- -- + | | | Tom Jennings, Thom Henderson, Dale Lovell, Vince | | Perriello, Tim Pozar, Sylvia Maxwell, Donald Tees, | | Christopher Baker, Zorch Frezberg, Henk Wolsink, | | Doug Meyers, Warren D. Bonner, Frank L. Vest | | | + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- + Fidonews is published weekly by and for the members of Fidonet. There is no copyright attached to Fidonews, though authors retain rights to their contributed articles. Opinions expressed by the authors are strictly their own. Noncommercial duplication and distribution within Fidonet is encouraged. Authors are encouraged to send their articles in ASCII text to the Editor at one of the addresses above. The weekly edition of Fidonews is distributed through the file area FIDONEWS, and is published as echomail in the echo FIDONEWS. The different articles are distributed in the file area SNOOZE. A service to various projects for making Fidonews available on the web with a more pleasing lay-out. These sources are normally available through your Network Coordinator. The current and past issues are also available from the following sources: + -- -- -- -- -- -- - FIDONEWS AVAILABILITY - -- -- -- -- -- -- + | | | File request from 2:2/2 or 2:203/0: | | current issue FIDONEWS | | back issue, volume v, issue ii FNEWSvii.ZIP | | articles, vol.no nn, issue ii INPUnnii.ZIP | | | | On the web: | | http://felten.yi.org/fidonews | | http://fidonews.eu | | | | The Snooze *and* the FIDONEWS echo in your newsreader: | | news://felten.yi.org/FIDONEWS | | | + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- + -----------------------------------------------------------------