HTML Image
Forum: 1 Lucky Nerd

  • FidoNews 42:19 [00/07]: The Front Page

    From FidoNews Robot@2:2/2 to All on Monday, May 12, 2025 02:58:48
    The F I D O N E W S Volume 42, Number 19 12 May 2025 +--------------------------+-----------------------------------------+
    | |The newsletter of the | | |
    | | FidoNet community. | | Netmail attach to (POTS): |
    | | Est. 1984 | | Editor @ 2:2/2 (+46-31-960447) |
    | | ____________| | |
    | | / __ | Netmail attach to (BinkP): |
    | | / / \ | Editor @ 2:203/0 |
    | | WOOF! ( /|oo \ | |
    | \_______\(_| /_) | Email attach to: |
    | _ @/_ \ _ | b @ felten dot se |
    | | | \ \\ | |
    | | (*) | \ ))| |
    | |__U__| / \// | Publisher: Bj”rn Felten |
    | ______ _//|| _\ / | |
    | / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
    | (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+


    Table of Contents
    1. GENERAL ARTICLES ......................................... 1
    Configuring my own fiberglass modem/router part 2 ........ 1
    2. LIST OF FIDONET IPV6 NODES ............................... 5
    List of IPv6 nodes ....................................... 5
    3. JAMNNTPD SERVERS LIST .................................... 8
    The Johan Billing JamNNTPd project ....................... 8
    4. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 9
    5. SPECIAL INTEREST ......................................... 17
    Nodelist Stats ........................................... 17
    6. FIDONEWS INFORMATION ..................................... 19
    How to Submit an Article ................................. 19
    Credits, Legal Information, Availability ................. 21

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, May 12, 2025 02:58:48
    =================================================================
    GENERAL ARTICLES =================================================================

    Configuring my own fiberglass modem/router part 2
    By Michiel van der Vlist, 2:280/5555

    Part 1 was about installing and registering my own Optical Network
    Terminator (ONT). This part will be about installing and configuring
    my own router.

    My choice fell on the Mikrotik hEX. It is a no nonsence router, No
    fancy enclosure, no flashing GUI. But it is very powerfull. It is
    aimed at the professional user. Almost anything is configurable and
    it is relatively cheap. While the ONT has the potential for 10 Gbps
    and the fiber company has an option for 8 Gbps, the Mikrotek hEX is
    limited to 1 Gpbs. So I won't use the full potential of the fiber
    connection. No problem, my LAN is designed for 1 Gbps and my contract
    with the provider is 500/500 Mbps. So for now the router will not be
    the bottleneck. Who needs more than 1 Gbps? Not me anyway, not for
    now.

    The price for all these goodies is a steep learning curve. Its OS,
    RouterOS is based on Linux. For Windows users most of the configura-
    tion is counter intuitive. And much of it for Linux users as well I
    guess. Getting started is quit a challenge. Mikrotik is European which
    in these times of world-wide turmoil has its merits for a European
    like me...

    So I connected the ethernet port of the ONT to the WAN port of the
    Mikrotik and my laptop to the router's first LAN port and I tried to
    access its GUI to start the configuration. I was unable to. The GUI
    should be accesable at 192.168.88.1 but no respons. The laoptop did
    not even get an address in the range 192.168.88.xx. Hmm... So maybe
    it does nothing without an "upstream" connection. For an upstream
    connection via the ONT it needs VLAN 100 and to configure that I need
    access to the router's GUI. So let me connect it to the LAN of my
    cable connection. I connected the WAN interface of the Mikrotik - or
    what I thought was the WAN port - to a LAN port of the modem/router of
    my cable connection. Still nothing on 192.168.88.xx. But.. my laptop
    got an IP in the range from the cable connections's LAN. Hmmm...
    So let's look into the config of the cable modem/router to see if the
    Mikrotik got an address in that range. And it had! So I tried to
    access the Mikrotik's GUI at that address and Bingo! I was in.

    I got a log in screen and to my surprise I did not need a password.
    The second surprise came with the first screen after log in. The
    device has two modes. Router and switch. It was in switch mode! That
    explains a lot. What remains unexplained is how it got there in the
    first place.
    Nevermind, let's move on. I put it in router mode and configured
    192.168.88.xx as the addresses to use for the LAN. After a restart I
    could address it at 192.168.88.1. While exploring the device I found
    how to update the firmware. It was delivered with RouterOs 6.xx
    which by default did not support IPv6. For IPv6 one had to add a
    "package". Hmmm.. Looking a bit further revealed that there was
    RouterOs 7,xx and that included IPv6 by default. So I upgraded to
    RouterOs 7.18.2, the latest version.

    I configured VLAN 100 and reconnected to the ONT. Still no IP from
    Delta, the fiberglass provider. I checked and checked again but could
    find nothing that could explain why I did not get an IP from the
    provider. Further trial and error revealed that the GUI was accesable
    via the LAN port. THAT I diddn't like. Ik could find nothing in the
    config to block that and I found it strange that the default
    configuration allowed it. All that made me decide to follow the
    procedure for resetting the device to the default configuration.
    Remove the power, press the reset button and hold it while restoring
    the power until one of the green lights starts flashing. Sounds easy
    but you need three hands for that. It took more that one attempt to
    get it right. After the first attempts the VLAN did not disappear but
    at the fourth attempt the VLAN was gone and I could no longer access
    the GUI from the WAN port. So I figured this time I really had the
    default configurtation. I reconfigured the VLAN but still no IP from
    the provider. It was at this point that I actually configred VLAN 100
    on my laptop, directly connected it to the ONT and got an IP from the
    provider.

    Now we get to the steep learning curve of RouterOs. In Windows it is
    enough to configure a VLAN. Windows presumes that if you configure a
    VLAN for an interface that you actually want to use it to make a
    connection with it. Not so with Mikrotik. After getting some help on
    a Mikrotik forum I found out that in addition to just configuring a
    VLAN for the port used as WAN, you also have to configure a DHCP
    client and add the interface created for the VLAN to the WAN list.
    ANd THEN finally I got an IPv4 address from the provider. Wauw!

    So now I had outgoing IPv4 on the devices connected to the LAN. I
    could make outgoing binkp connections. Configuring a port forward
    seemed easy. But that didn't work. I wasn't really surprised, almost
    nothing with Mikrotik seems to work at the first go.

    OK, let's try somethimg else. Let's activate IPv6. Contrary to what I encountered so far that was releatively easy. Or maybe I already got
    used to the peculartities of RouterOs. First we have to configure a
    DHCPv6 client for the VLAN interface. Specify what you want to
    request, address, prefix or info. I specified both address and prefix.
    The address turned out to be not needed, but it didn't hurt for now.
    For the prefix size specify the prefix size that the provider issues,
    56 in my case. Specify a pool name, any name will do but something
    logical like the name of the provider can be handy. Specify nothing
    for the address hint and voila, you get a pefix from the provider.
    So we now have a prefix, what is next ask for an address range for the
    subnet where our LAN will be. So we go ask fo an addrees for the
    interface "bridge" that is our local LAN. Ask for a ::/64 from the
    pool that we defined in the previous step and leave the rest as
    default. And the first /64 from the /56 that we got before is assigned
    to the LAN. IPv6 capable devices on the LAN now automatically get a
    global IPv6 address. So far so good. But.. no access to the IPv6 part
    of the InterNet. And there it is: another Mikrotik thing. It turned
    out that one needs to click on "add default route" when configuring
    the DHCPv6 client for the VLAN interface. No ideau why this isn't set
    by default like "Use peer DNS" and "Rapid Commit", but that's
    Mikrotik. Anyway, we now have outgoing IPv6.

    OK, back to IPv4. Why does the port forwarding not work? Not only does
    the port fowarding not work, I could not even reach the binkp server
    from the local LAN using the local IPv4 addresses. It seems to be
    totally isolated for incoming, even locally. I asked for suggestions
    in a Mikrotek forum and posted my config there. None of Mikrotik gurus
    could find anything wrong with it. But I got a few suggestions. One of
    them was the Windows firewall of the PC running the servers. My first
    reaction was: "of course not. This system has been running for a very
    long time and so has the port forwarding." But I checked anyway. Yes,
    binkp was in the rules of the Windows firewall. So I decided on some
    more tests. I could not access my binkp server from my laptop that was
    on the same LAN. What about it being connected on the same port of the
    router via an extra switch? It was also unaccessable. That seemed
    impossible because in that case it it didn't even go through the
    router, So what about the client running on the same PC as my binkp
    system? I still had 280/5556 installed on the same system. So I fired
    that up. And low and behold, 280/5556 could connect to 280/5555. Now
    I wasn't so sure anymore that the problem was not in the Windows'
    firewall. So I turned it around. Let me see if I can make a connection
    when I configure my point 1 on the laptop as the server. And, yes I
    could.

    At this point I should mention that I kept my connection with the
    cable company and that I installed a second network card for the
    connection with the fiber boys. I already mentioned this in part 1 but
    the reader may have forgotten. As I did. Sort of...

    So I looked at configuation of the Windows firewall once more and then
    it suddenly hit me. While there is only one setting for the list of
    programs that are allowed access, there are actually two networks. One associated with each interface. For each network there is a setting
    that defines it as a home network or a public network. And the second
    network, the one for the fiber connection was configured as a public
    network. I have no idea how this happened an how long it had been that
    way. Well, I was moaning about RouterOs having it pecularities, we all
    know that Windows has some strange ideas of its own too. Anyway, when
    I changed the setting from public network to home network the problem
    was solved and port forwarding worked as expected.

    The IPv6 pinhole for port 24554 was not a poblem. Except for the fact
    that a rule added with the Mikrotik's GUI puts it on the bottom of the
    list of rules and the order is relevant. The original last line was a
    rule that rejects "all else that doen not come from the LAN" and so
    the new rule had no effect. But there is no way to influence where in
    the list the new rule comes when entering it wiyh the GUI. That
    problem was solved when I discovered that when displayng the list one
    can grab a line with the mouse and drag it to another place in the
    list. So I moved that last line one place up and that activated the
    pinhole for port 24554.

    Now there was one thing left. The internet communication between the
    router and the ONT goes via interface VLAN 100. The physical interface
    ether1 is configured by default to have a DHCP client and it is added
    to the WAN list. That is not needed in this setup. But there still is
    one little thing that I wanted to add. I mentioned in part 1 that the
    ONT has a GUI that can be accessed by connecting a PC or laptop
    configured with a fixed IP of 192.168.100.xx to the ethernet port. But
    that ethernet port is now connected to the WAN port of the router.
    What I wanted was to make the ONT accessable via the router. That
    turned out to be easy. I added a fixed address of 192.168.100.10 to
    the interface "ether1". It was already on the WAN list. The DHCP
    client associated with it was no longer needed, so I disabled that.
    After that I could indeed access the ONT's GUI by browsing to
    192.168.100.1 from any PC on the LAN. That was easy. It seems I am
    getting a little bit familiar with RouterOs.

    My Fidonet system is now reachable via both providers. IPv4 and IPv6.
    The IPv4 address starting with 83 and the IPv6 address starting with
    2001.1c02 are from the cable provider. (Ziggo) The IPv4 address
    starting with 81 and the IPv6 address starting with 2001.4c3c are from
    the fiberglass provider. (Delta) Feel free to try it.

    That completes the installation and configuration of my own ONT and
    router for my fiberglass connection. For now of course. On a Fidonet
    system there is always room for further tuning and experiments. But
    for now I will leave it as is.

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, May 12, 2025 02:58:48
    =================================================================
    LIST OF FIDONET IPV6 NODES =================================================================

    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 11 May 2025


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Freedom f
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo/Delta f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 1:154/10 Nicholas Boel Native Spectrum f
    9 2:203/2 Bjorn Felten T-6in4 he.net 6DWN HOLD
    10 2:280/5006 Kees van Eeten Native KPN f INO4
    11 3:712/848 Scott Little T-6in4 he.net f
    12 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    13 1:103/17 Stephen Hurd T-6in4 he.net
    14 2:5020/9696 Alexander Skovpen T-6in4 IP4Market
    15 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    16 2:222/2 Kim Heino Native TeliaSonera
    17 3:633/280 Stephen Walsh Native AusNetServers f
    18 1:19/10 Matt Bedynek T-6in4 he.net
    19 3:770/1 Paul Hayton Native VETTA
    20 3:770/100 Paul Hayton Native VETTA
    21 2:5053/58 Alexander Kruglikov Native ER-Telecom f
    22 1:103/1 Stephen Hurd Native Choopa
    23 3:633/281 Stephen Walsh Native Internode
    24 2:310/31 Richard Menedetter Native DE-NETCUP f
    25 3:633/410 Tony Langdon Native IINET
    26 2:5020/329 Oleg Lukashin Native Comfortel f
    27 2:331/51 Marco d'Itri Native BOFH-IT
    28 1:154/30 Mike Miller Native LINODE
    29 2:5001/100 Dmitry Protasoff Native Layer7 Networks
    30 2:5059/38 Andrey Mundirov T-6in4 he.net
    31 2:5083/444 Peter Khanin Native OVH
    32 2:240/5413 Ingo Juergensmann Native RRBONE-COLO f
    33 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    34 1:103/13 Stephen Hurd Native Choopa
    35 2:5020/1042 Stas Mishchenkov T-6-in4 he.net f
    36 2:5019/400 Konstantin Kuzov Native LT-LT
    37 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    38 2:5010/275 Evgeny Chevtaev T-6in4 IP4Market f
    39 2:280/2000 Michael Trip Native KPN
    40 2:230/38 Benny Pedersen Native Linode
    41 2:460/58 Stas Mishchenkov T-6in4 he.net f
    42 2:5101/1 Andrey Ignatov Native HETZNER
    43 2:5005/49 Victor Sudakov T-6in4 he.net f
    44 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    45 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    46 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    47 2:292/854 Ward Dossche Native Proximus
    48 2:469/122 Sergey Zabolotny T-6in4 he.net f
    49 2:5053/400 Alexander Kruglikov Native FirstVDS f
    50 2:5030/1997 Alexey Fayans T-6in4 he.net
    51 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    52 2:240/502 Ludwig Bernhartzeder Native DTAG
    53 2:423/39 Karel Kral Native WEDOS
    54 2:280/1049 Simon Voortman Native Solcon
    55 2:335/364 Fabio Bizzi Native OVH
    56 1:124/5016 Nigel Reed Native DAL1-US f
    57 2:5030/1520 Andrey Geyko T-6in4 he.net f
    58 1:229/664 Jay Harris Native Rogers f
    59 2:280/2030 Martien Korenblom Native Transip
    60 3:633/509 Deon George Native Telstra
    61 2:5020/4441 Yuri Myakotin Native SOVINTEL
    62 1:320/319 Andrew Leary Native Comcast f
    63 2:240/5824 Anna Christina Nass Native DTAG f
    64 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    65 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    66 2:301/812 Benoit Panizon Native WOODYV6
    67 1:229/616 Vasily Losev Native GIGEPORT
    68 2:301/113 Alisha Stutz T-6in4 he.ne
    69 1:153/7715 Dallas Hinton Native Shaw Comms
    70 1:218/840 Morgan Collins Native Linode
    71 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    72 2:240/1634 Hugo Andriessen Native Vodafone
    73 2:280/2040 Leo Barnhoorn Native KPN f
    74 2:5020/736 Egor Glukhov Native RUWEB f
    75 2:221/10 Tommi Koivula Native Hetzner f INO4
    76 1:218/850 John Nicpon Native LINODE-US
    77 2:301/1 Alisha Stutz Native CH-DATAWIRE
    78 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    79 2:5020/290 Andrew Kolchoogin T-6in4 he.net
    80 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
    81 1:218/820 Ryan Fantus Native DIGITALOCEAN
    82 1:103/705 Rob Swindell Native Spectrum f
    83 1:135/395 Charles Blackburn Native Charter Comms
    84 1:134/303 Travis Mehrer Native Shaw Comms
    85 2:5057/19 Max Vasilyev Native ER-Telecom f
    86 2:5075/35 Eugene Subbotin Native RUWEB f
    87 2:5075/37 Andrew Komardin Native IHC
    88 2:5075/128 Eugene Subbotin T-6in4 IP4Market f
    89 2:550/278 Vladislav Muschinskikh Native FirstByte
    90 2:5010/278 Vladislav Muschinskikh T-6in4 he.net f
    91 2:240/5411 Stephan Gebbers Native DTAG
    92 2:5020/715 Alex Barinov T-6in4 he.net f
    93 1:16/201 Sergey Myasoedov Native Amazon
    94 1:104/117 Vitaliy Aksyonov Native LLC
    95 2:5030/1340 Dmitry Afanasiev T-6in4 TUNNEL-BROKER-NET
    96 2:221/360 Tommi Koivula Native Elisa f
    97 2:5031/25 Alex Kazankov Native VDSINA
    98 4:902/26 Fernando Toledo Native Claro
    99 2:280/2050 Floris van Unen Native Azure
    100 2:280/2060 Dennis Slagers Native Ziggo f
    101 2:467/4 Ruslan Suleimanov T-6in4 he.net
    102 2:467/888 Ruslan Suleimanov T-6in4 he.net f
    103 1:266/625 Scott Street Native Verizon
    104 2:5020/5452 Alex Barinov T-6in4 he.net
    105 2:5030/723 Alexey Khromov Native RU-AI-20240222
    106 3:633/2744 Deon George Native EXETEL-AU
    107 4:930/1 David Gonzalez Native EPMNET
    108 3:633/267 Andrew Clarke Native widebandnetv6 OO


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    Example: ::f1d0:2:280:5555 (for node 2:280/5555)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    Submitted on day 131


    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, May 12, 2025 02:58:48
    =================================================================
    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 newsreader 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 2023-09-06


    URL news://eljaco.se:4119
    Join http://fidonews.eu
    NETMAIL Yes, 2:203/2

    URL nntp://rbb.fidonet.fi
    Join https://news.fidonet.fi
    NETMAIL Yes, 2:221/360

    URL nntp://fidonews.mine.nu
    URL nntps://fidonews.mine.nu
    Join http://fidonews.mine.nu
    NETMAIL Yes, 2:221/6

    URL nntp://news.bytemuseum.org
    nntps://news.bytemuseum.org (secure)
    Join Info in group +ACCCESS&SUPPORT+
    NETMAIL Yes, 1:19/10

    URL nntp://news.pharcyde.org
    Join Info in group, +GETACCESS+
    NETMAIL Yes, 1:154/10


    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, May 12, 2025 02:58:48
    =================================================================
    FIDONEWS'S FIDONET SOFTWARE LISTING =================================================================



    =================================================================
    FIDONET SOFTWARE LISTING
    =================================================================

    BBS Software List

    Updated 2025-03-27

    Maintained by Andrew Leary (1:320/219)
    Editors Emeritus: Robert Couture, Janis Kracht,
    Sean Dennis

    M=Mailer T=Tosser B=BBS D=Door C=Comm/Terminal
    P=Points E=Editor I=Internet U=Utility #=Info
    F=TIC/SRIF Processor

    *=Software is available and may be registerable,
    but no longer supported or updated.

    @=Website is operating but is no longer updated.

    ?=Software's updating/support status is unknown.

    O=Software is open source.

    This list contains BBS-related software that is available
    for registration (not necessarily supported), open source
    software and actively developed/supported software by its
    author. Software listed may be available for DOS, Linux,
    OS/2 (eComStation), Windows (16 or 32 bit) and OSX.

    .- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.
    |Software: Author |Type |URL, Contact, Ver, Notes Help Node|
    `- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -'

    ==> FRONT-END/INTERNET MAILERS

    Argus |MI*? |http://www.ritlabs.com/en/products
    | | /argus/
    | | v3.210 on 2001-03-29

    Binkleyforce |MI |https://prj.zxalexis.ru/gitea
    | | /zx/bforce 2:5030/723
    Alexey Khromov | | zx@zxalexis.ru
    | | v0.25.3 on 2024-07-05


    BinkleyTerm XE |MO* |http://btxe.sourceforge.net
    | | 2.60XE Beta-XH7 on 2000-10-22

    BinkD |MI? |http://binkd.grumbler.org
    | | gul@gul.kiev.ua 2:463/68
    | | v.1.0.4
    | | v.1.1a-115 (alpha)
    | | ftp://cvs.happy.kiev.ua/pub/fidosoft
    | | /mailer/binkd/
    | |http://www.filegate.net/r50/aftnbinkd/

    D'Bridge |MTCPE|http://www.dbridgemailer.com
    |I | support@dbridgemailer.com 1:1/130
    Nick Andre | | v4.00 on 2024-11-12

    FIDO-Deluxe IP |MPUI |http://www.datenbahn.dd-dns.de/
    | | cdp/fp_deluxe/
    | | v2.4 on 2003-09-26

    FrontDoor |MITPC|https://defsol.com 2:201/4609
    Definite Solutions |E | defsol@defsol.se
    Joaquim Homrighausen| | FrontDoor v24.01 on 2024-12-20
    | | FrontDoor/2 v24.01 on 2024-12-22

    InterMail |MCPE |http://www.Intermail.net 1:106/201
    Dale Barnes | | dalebarnes42@majik.net
    | | IM v2.60 on 2017-08-28

    Husky Project |MTPUI|http://husky.sourceforge.net/
    |EO? | v1.9 RC2 on 2010-04-20

    Taurus |MI |http://www.fidotel.com/public/forums/
    (based on Radius) |? | taurus/index.htm
    | | v5.0 on 2006-06-12
    | |

    T-Mail |MI |http://www.tmail.spb.ru (Russian only)
    |? | v2608 on 2001-12-12

    AfterShock |MTEI |https://play.google.com/store/apps/
    Asvcorp | | details?id=com.asvcorp.aftershock
    Anatoly Vdovichev | | rudi.timmermans@mailfence.com
    Rudi Timmermans | | v1.7.1 on 2022-11-30 2:292/140

    HotDogEd |E |https://play.google.com/store/apps/
    Sergey Pushkin | | details?id=com.pushkin.hotdoged
    | | v2.13.5 on 2017-03-13 2:5020/2141

    HotDogEd FidoNet |MTI |https://play.google.com/store/apps/
    Provider | | details?id=com.pushkin.hotdoged.fido
    Sergey Pushkin | | v2.13.5 on 2017-03-13 2:5020/2141

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    MAIL TOSSERS

    Crashmail II |TO |http://ftnapps.sourceforge.net/
    | | crashmail.html

    FastEcho |T |http://www.softeq.de/old/Products
    | | /FastEcho/fastecho.html
    | | v1.46.1 on 2007-11-13
    | | Registration keys are free & available
    | | by request from the author

    Fidogate |TUI? |http://www.fidogate.org
    | | v4.4.10 on 2004-08-27
    | |

    FMail |TO |https://sourceforge.net/projects/fmail/
    | | v2.3.1.0 on 2024-03-30 2:280/464

    InterEcho |T |http://www.Intermail.net 1:220/60
    Dale Barnes | | dalebarnes42@majik.net
    | | IE 1.20 on 2017-08-28

    JetMail: JetSys |TU |
    (ATARI ST only) | | v1.01 on 2000-01-01

    Squish |T* |http://www.filegate.net/maximus_bbs/
    | | v1.11R2 on 2009-01-01
    | | Source code available in Maximus BBS
    | | archive: http://maximus.sourceforge.net


    WWIVToss |T |http://www.weather-station.org/wwiv/
    | | v1.51 on 2015-05-23

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    BBS SOFTWARE

    BBBS |BICTM|http://www.bbbs.net 2:222/2
    | | b@bbbs.net
    | | v4.01 on 2007-01-28

    EleBBS |BO*? |http://www.elebbs.com
    | | v0.10.RC1 on 2002-06-09

    Enthral BBS |B |http://enthralbbs.com
    Linux/BSD/OSX | | v0.429/Alpha on 2010-10-14
    | | Fidonet filebone SCENEENT

    Ezycom BBS |BT* |http://www.ezycom-bbs.com
    | | v2.15g2 on 2009-11-16

    GT Power |B |http://www.gtpowerbbs.com/
    | | v19.00

    Hermes II Project |BT |http://www.hermesbbs.com/
    Macintosh-based | | malyn@strangegizmo.com
    | | v3.5.10b3

    Maximus BBS |BO* |http://www.filegate.net/maximus_bbs/
    | | v3.03
    | | Source code available at:
    | | http://maximus.sourceforge.net/

    MBSE BBS |BMTFI|https://sourceforge.net 1:1/119
    |PO | /projects/mbsebbs
    | | ajleary@sourceforge.net
    | | v1.1.1 on 2025-03-27

    Meltdown BBS |UIO |http://meltdown-bbs.sourceforge.net/
    | | v1.0b on 2004-04-26

    Mystic BBS |BMTCE|http://www.mysticbbs.com
    |I | v1.12 A48 on 2023-01-15

    NiKom BBS (Amiga) |BO |http://www.nikom.org
    | | v2.3.1 on 2017-07-01

    RemoteAccess BBS |B? |http://www.rapro.com 1:1/120
    | | bfmorse@rapro.com
    | | v2.62.2SW on 2000-10-25

    Renegade BBS |B |http://renegadebbs.info 1:129/305
    | | v1.33/DOS on 2023-05-05

    Spitfire BBS |B? |http://www.buffalocrk.com/
    | | mdwoltz@buffalocrk.com
    | | v3.7 on 2010-01-01

    Synchronet BBS |BMTIO|https://www.synchro.net 1:103/705
    Rob Swindell | |https://wiki.synchro.net
    | | v3.20d on 2025-03-03

    Telegard BBS |B* |
    | | v3.09g2-sp4/mL on 1999-12-19

    WildCat! Interactive |MTBEI|http://www.santronics.com
    Net Server, Platinum| | sales@santronics.com
    Xpress: Santronics | |
    Software, Inc. | | v8.0 AUP 454.12 on 2021-05-14

    WWIV BBS |B |http://www.wwivbbs.org
    | | v5.6.1 on 2021-04-23

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    TIC PROCESSORS/FILEFIX/SRIF

    Allfix |FIUT |http://www.allfix.com/ 1:218/720
    Ken Johnson | | v6.1.0 on 2019-02-02

    NEF/pk |F |http://nefpk.8m.com/
    | | v2.45b2 on 2000-03-05

    TinyTIC |FO |http://ftnapps.sourceforge.net
    | | /tinytic.html

    VIReq |FO |http://ftnapps.sourceforge.net
    | | /vireq.html

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    BBS DOORS/UTILITIES

    Cheepware |DU |http://outpostbbs.net/cheepware.html
    Sean Dennis | | sysop@outpostbbs.net 1:18/200
    | | Fidonet filebone CH-WARE

    DDS (Doorware |D@ |http://www.doorgames.org
    Distribution System)| | ruth@doorgames.org
    Ruth Argust | |

    Jibben Software |D* |http://www.jibbensoftware.com/
    | | bbs-door-games.cfm
    | | scott@jibben.com
    | | 1995-99 Release dates

    John Dailey Software |DU |http://www.johndaileysoftware.com

    Shining Star |D* |http://www.shiningstar.net/bbsdoors/
    | | nannette@shiningstar.net
    | | Doors are registerable via website

    Sunrise Doors: |D |http://www.sunrisedoors.com
    Al Lawrence | | al@sunrisedoors.com
    | | Tel: (404) 256-9518

    T1ny's Software |DU |http://www.tinysbbs.com/files/tsoft/
    Shawn Highfield | | shighfield@gmail.com 1:229/452
    | | Fidonet filebone CH-WARE

    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 |DU* |http://vbsoft.dhakota.org
    | | d@dhakota.org
    | | Last update: 2008-04-11

    WWIVEdit |DE |http://www.weather-station.org/wwiv/
    | | v3.0 on 2011-06-27

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    +- - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - - - -+

    ==> POINT SOFTWARE

    APoint |PI |https://stargate.org.uk/apoint/
    | | v1.25 on 2001-12-12 (Win32)
    | | Needs the binkD Toolkit for Fido-over-IP
    | | which is available from the above URL.

    CrossPoint |P |http://www.crosspoint.de
    | | pm@crosspoint.de
    | | v3.12d on 1999-12-22 (DOS, Shareware)

    FreeXP |PO |http://www.freexp.de
    | | support@freexp.de
    | | v3.42 on 2020-09-25 (DOS)

    OpenXP |PIO |https://sourceforge.net/projects/openxp5/
    | | v5.0.64 on 2025-02-17
    | | (Win32, Linux(64-Bit})

    WinPoint |PI |http://www.winpoint.org/
    | | Tim Schattkowsky 2:240/1120.29
    | | v415.0 on 2023-02-17 (Win32)

    +- - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - - - -+

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    SYSOP MAIL EDITORS

    GoldEd+ |EO |http://golded-plus.sourceforge.net/
    | | v1.1.5 (Snapshot) on 2023-02-14
    | | NOTE: Unstable versions released often

    gossipEd |EO |https://github.com/askovpen/gossiped
    | | v2.1.0 on 2025-02-05

    SqEd32 |E |http://www.sqed.de 2:2476/493
    | | v1.15 on 1999-12-15
    | | Website is in German and English

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    INTERNET UTILITIES

    Ifmail |UIO |http://ifmail.sourceforge.net
    | | crosser@average.org

    Internet Rex |UI? |http://members.shaw.ca/InternetRex/
    | | telnet://xanadubbs.ca 1:342/806
    | | v2.29 on 2001-10-21

    JamNNTPd |UIO |http://ftnapps.sourceforge.net
    | | /jamnntpd.html

    Luckygate |UO | ftp://happy.kiev.ua/pub/fidosoft/gate
    | | /lgate
    | | gul@gul.kiev.ua

    MakeNL |UO |http://makenl.sourceforge.net
    | | v3.5.0 on 2019-05-06

    PLMake |UOP |https://sourceforge.net/projects
    | | /plmake 2:280/464
    | | v2.1 beta on 2024-11-01

    ErrFlags |UO |http://sourceforge.net/projects
    | | /errflags 2:280/464
    | | v3.0.0 on 2023-02-21

    RNtrack |U |http://sourceforge.net/projects
    | | /ftrack-as 2:5080/102
    | |stas_degteff@users.sourceforge.net
    | | v2.1.10 on 2020-04-30

    TransNet |UIO? |http://www-personal.umich.edu/~mressl/
    | | transnet/index.html
    | | transnet@ressl.com.ar
    | | v2.11 on 2007-09-13

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    INFORMATIONAL WEBSITES/BBS LISTS

    Telnet/Dialup BBS |# |http://www.telnetbbsguide.com 1:275/89
    Guide | | Maintained by Dave Perrussel
    | | This is probably the most updated BBS
    | | list on the Internet for a general
    | | BBS list.

    Synchronet BBS List |# |http://www.synchro.net/sbbslist.html
    | | Maintained automatically
    | | This list is specifically for
    | | Synchronet-based BBS systems and is
    | | automatically updated nightly.

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, May 12, 2025 02:58:48
    The BBS Corner |# |http://www.bbscorner.com
    | | This website is more than just files,
    | | it's an encyclopedia of knowledge for
    | | BBS sysops and people who want to
    | | become sysops. This site is run by
    | | the same person who does the Telnet
    | | BBS Guide.

    BBS Nexus |# |https://bbsnexus.com
    | | This website offers a searchable list
    | | of Telnet BBS's.

    +- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+

    File Archives:

    http://www.filegate.net/ (FTP access via port 60721)
    https://hobbesarchive.com (New home of the Hobbes OS/2 Archive)

    Note: Most also provide FTP access (use ftp instead of http above)
    The BBS Software List is published weekly in the FidoNews.

    If you have corrections, suggestions or additions to the information
    above, please contact Andrew Leary with your information via the
    FIDONEWS echo or netmail at 1:320/219.

    --------------------------------------------------------------------

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, May 12, 2025 02:58:48
    =================================================================
    SPECIAL INTEREST =================================================================

    Nodelist Stats

    Input nodelist nodelist.129
    size 154.9kb
    date 2025-05-09

    The nodelist has 805 nodes in it
    and a total of 1199 non-comment entries

    including 4 zones
    30 regions
    157 hosts
    59 hubs
    admin overhead 250 ( 31.06 %)

    and 83 private nodes
    19 nodes down
    42 nodes on hold
    off line overhead 144 ( 17.89 %)


    Speed summary:

    >9600 = 19 ( 2.36 %)
    9600 = 88 ( 10.93 %)
    (HST = 2 or 2.27 %)
    (CSP = 0 or 0.00 %)
    (PEP = 0 or 0.00 %)
    (MAX = 0 or 0.00 %)
    (HAY = 0 or 0.00 %)
    (V32 = 51 or 57.95 %)
    (V32B = 0 or 0.00 %)
    (V34 = 52 or 59.09 %)
    (V42 = 45 or 51.14 %)
    (V42B = 0 or 0.00 %)
    2400 = 1 ( 0.12 %)
    1200 = 0 ( 0.00 %)
    300 = 697 ( 86.58 %)

    ISDN = 18 ( 2.24 %)

    -----------------------------------------------------
    IP Flags Protocol Number of systems -----------------------------------------------------
    IBN Binkp 690 ( 85.71 %) ----------------------------------
    IFC Raw ifcico 61 ( 7.58 %) ----------------------------------
    IFT FTP 33 ( 4.10 %) ----------------------------------
    ITN Telnet 91 ( 11.30 %) ----------------------------------
    IVM Vmodem 11 ( 1.37 %) ----------------------------------
    IP Other 1 ( 0.12 %) ----------------------------------
    INO4 IPv6 only 5 ( 0.62 %) ----------------------------------

    CrashMail capable = 741 ( 92.05 %)
    MailOnly nodes = 241 ( 29.94 %)
    Listed-only nodes = 19 ( 2.36 %)



    [Report produced by NETSTATS - A PD pgm]
    [ Revised by B Felten, 2:203/2]
    [ NetStats 3.8 2014-11-23]

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Monday, May 12, 2025 02:58:48
    =================================================================
    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 text. If you could type it on your keyboard, it's probably
    quite OK. TABs (ASCII 09) are not allowed -- there's no knowing
    how long you've set your tab markings. 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.


    In case a) and b) above is not crystal clear, here's an excellent
    summary by Ward Dossche, a major article contributor:

    Piece of cake:

    1) Ascii text
    2) Line length of 70
    3) Put this at the very top:

    *The title of your text
    The title of your text
    Your Name - Your Nodenumber

    The title is there twice, the line with the * is how it will be
    visible in the table of content.


    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.

    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 b @ felten dot se
    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.


    -----------------------------------------------------------------
    Credits, Legal Information, Availability

    + -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- +
    | |
    | Editor: Bj”rn Felten, 2:2/2 |
    | |
    | The IPv6 list: Michiel van der Vlist, 2:280/5555 |
    | The S/W list: Andrew Leary, 1:320/219 |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

    + -- -- -- -- -- -- -- - 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 |
    | or FNEWTvii.ZIP |
    | articles, vol.no nn, issue ii INPUnnii.ZIP |
    | |
    | On the web: |
    | http://eljaco.se/FILES/fnews/ |
    | |
    | The FIDONEWS echo in your newsreader: |
    | news://eljaco.se/FIDONEWS |
    | |
    + -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +

    -----------------------------------------------------------------


    ** Prepared for FIDONEWS by Azure/NewsPrep 3.0
    (c) Copyright 1996-1999 Peter Karlsson

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Monday, May 12, 2025 09:15:42
    Hi Michiel,

    On 2025-05-12 02:58:48, FidoNews Robot wrote to All:

    My Fidonet system is now reachable via both providers. IPv4 and IPv6.
    The IPv4 address starting with 83 and the IPv6 address starting with 2001.1c02 are from the cable provider. (Ziggo) The IPv4 address
    starting with 81 and the IPv6 address starting with 2001.4c3c are from
    the fiberglass provider. (Delta) Feel free to try it.

    All is still good:

    fido.vlist.eu, 24554
    Calling 2:280/5555 (2001:1c02:1100:f00:f1d0:2:280:5555:24554)
    2001:1c02:1100:f00:f1d0:2:280:5555 - Ok.

    Calling 2:280/5555 (2001:4c3c:7d02:ff00:f1d0:2:280:5555:24554)
    2001:4c3c:7d02:ff00:f1d0:2:280:5555 - Ok.

    Calling 2:280/5555 (83.80.251.71:24554)
    83.80.251.71 - Ok.

    Calling 2:280/5555 (81.172.216.197:24554)
    81.172.216.197 - Ok.

    fido4to6.vlist.eu, 24554
    Calling 2:280/5555 (185.248.148.18:24554)
    185.248.148.18 - Ok.

    ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Monday, May 12, 2025 09:50:20
    Hello Wilfred,

    On Monday May 12 2025 09:15, you wrote to me:

    All is still good:

    fido.vlist.eu, 24554
    Calling 2:280/5555 (2001:1c02:1100:f00:f1d0:2:280:5555:24554)
    2001:1c02:1100:f00:f1d0:2:280:5555 - Ok.

    Calling 2:280/5555 (2001:4c3c:7d02:ff00:f1d0:2:280:5555:24554)
    2001:4c3c:7d02:ff00:f1d0:2:280:5555 - Ok.

    Calling 2:280/5555 (83.80.251.71:24554)
    83.80.251.71 - Ok.

    Calling 2:280/5555 (81.172.216.197:24554)
    81.172.216.197 - Ok.

    fido4to6.vlist.eu, 24554
    Calling 2:280/5555 (185.248.148.18:24554)
    185.248.148.18 - Ok.

    Tnx for testing.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Björn Felten@2:203/2 to Wilfred van Velzen on Monday, May 12, 2025 12:39:33
    Wilfred van Velzen -> Michiel van der Vlist skrev 2025-05-12 09:15:
    Hi Michiel,

    On 2025-05-12 02:58:48, FidoNews Robot wrote to All:

    Just checking to see if outgoing netmail still works, after my big overhaul. It's easy to forget som changes...

    --

    Everything happens for a reason. Sometimes the reason is you're stupid and make bad decisions.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 6.1; sv-SE; rv:1.9.1.5) Gecko/20091121
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Wilfred van Velzen@2:280/464 to Björn Felten on Monday, May 12, 2025 12:56:07
    Hi Bj”rn,

    On 2025-05-12 12:39:33, you wrote to me:

    Just checking to see if outgoing netmail still works, after my big overhaul. It's easy to forget som changes...

    It works... ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Björn Felten@2:203/2 to Björn Felten on Monday, May 12, 2025 12:55:50
    Bj”rn Felten -> Wilfred van Velzen skrev 2025-05-12 12:39:
    Just checking to see if outgoing netmail still works, after my big overhaul. It's easy to forget som changes...

    Sigh. An of course I forgot to change groupe from FIDONEWS to NETMAIL. Sorry about that.

    --

    Everything happens for a reason. Sometimes the reason is you're stupid and make bad decisions.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 6.1; sv-SE; rv:1.9.1.5) Gecko/20091121
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Monday, May 12, 2025 13:16:37
    Hello Bj”rn,

    On Monday May 12 2025 12:39, you wrote to Wilfred van Velzen:

    On 2025-05-12 02:58:48, FidoNews Robot wrote to All:

    Just checking to see if outgoing netmail still works, after my big overhaul. It's easy to forget som changes...

    You check if NETMAIL still works by posting ECHOMAil? ;-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Ward Dossche@2:292/854 to Michiel van der Vlist on Monday, May 12, 2025 16:16:50
    You check if NETMAIL still works by posting ECHOMAil? ;-)

    Well, after all echomail is just another flavor of netmail ... not my words.

    \%/@rd

    {Yeah yeah yeah .... I know what you're going to reply}

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

I recommend using



to connect to the BBS