• Weekly nodelist report on noteworthy changes (288)

    From Nodelist Police Commissioner@2:280/464 to All on Fri Oct 15 12:24:46 2021

    Hi All,

    The prolog has been updated:
    "R25 UK Ireland" -> "R25 Ireland" ?

    Test node 2:292/1111 has become Pvt.

    New host for net 451: Host,451,Grodno_Net,Mogilev_Belarus,Alexey_Korotkov,375-222-634894,9600,CM,V90C,V42B,IBN,INA:82.209.239.18,INA:unnamed.by
    Connect with binkd/1.1a-49/Linux.
    This is the RC and Host of 3 other nets in R45.


    Regards, NPC

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Nodelist Police Commissioner on Fri Oct 15 12:45:11 2021
    Hello Nodelist,

    On Friday October 15 2021 12:24, you wrote to All:

    The prolog has been updated:
    "R25 UK Ireland" -> "R25 Ireland" ?

    The presentation is a bit confusing. After brexit, the GDPR is no longer in force in the UK. But in Ireland it still is. We have the odd situation of a Fidonet region crossing the EU border.

    Perhaps the Republic of Ireland should have its own Fidonet Region (26?) back.

    Test node 2:292/1111 has become Pvt.

    New host for net 451: Host,451,Grodno_Net,Mogilev_Belarus,Alexey_Korotkov,375-222-634894,960 0,CM,V90C,V42B,IBN,INA:82.209.239.18,INA:unnamed.by Connect with binkd/1.1a-49/Linux. This is the RC and Host of 3 other nets in R45.

    It is a mess there in Belarus. Too many small nets with the RC as Host. Time for the Big Cleanup!


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nodelist Police Station (2:280/5555)
  • From Nodelist Police Commissioner@2:280/464 to Michiel van der Vlist on Fri Oct 15 13:15:32 2021
    Hello Michiel,

    On 2021-10-15 12:45:11, you wrote to me:

    The prolog has been updated:
    "R25 UK Ireland" -> "R25 Ireland" ?

    MvdV> The presentation is a bit confusing. After brexit, the GDPR is no longer in
    MvdV> force in the UK. But in Ireland it still is. We have the odd situation of a
    MvdV> Fidonet region crossing the EU border.

    Aha, ok, I didn't notice the context...

    MvdV> Perhaps the Republic of Ireland should have its own Fidonet Region
    MvdV> (26?) back.

    That's in conflict with what you say below about R45 nets. ;-)

    Test node 2:292/1111 has become Pvt.

    New host for net 451:
    Host,451,Grodno_Net,Mogilev_Belarus,Alexey_Korotkov,375-222-634894,960
    0,CM,V90C,V42B,IBN,INA:82.209.239.18,INA:unnamed.by Connect with
    binkd/1.1a-49/Linux. This is the RC and Host of 3 other nets in R45.

    MvdV> It is a mess there in Belarus. Too many small nets with the RC as Host.
    MvdV> Time for the Big Cleanup!

    It would be a good thing if they did that, but it's up to them...


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Nodelist Police Commissioner on Fri Oct 15 13:39:41 2021
    Hello Nodelist,

    On Friday October 15 2021 13:15, you wrote to me:

    MvdV>> Perhaps the Republic of Ireland should have its own Fidonet
    MvdV>> Region (26?) back.

    That's in conflict with what you say below about R45 nets. ;-)

    How so? Contrary to Belarus, The Irish Republic is just one net.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nodelist Police Station (2:280/5555)
  • From Nodelist Police Commissioner@2:280/464 to Michiel van der Vlist on Fri Oct 15 15:08:21 2021
    Hello Michiel,

    On 2021-10-15 13:39:41, you wrote to me:

    MvdV>>> Perhaps the Republic of Ireland should have its own Fidonet
    MvdV>>> Region (26?) back.

    That's in conflict with what you say below about R45 nets. ;-)

    MvdV> How so? Contrary to Belarus, The Irish Republic is just one net.

    In the first paragraph you wanted to split things up, in the second you wanted to join them together... (I wasn't looking at the details, and there was a smiley!) ;-)

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Wilfred van Velzen@2:280/464 to All on Fri Oct 14 12:34:15 2022

    Hi All,

    Net 221 concatenated the IBN,INA: entries to IBN:, and corrected the order of the Ixx flags for node 360. Kudos to Tommi! ;)

    No longer down in net 230:
    ,150,The_KOFO_BBS,Broendby_DK,Gert_Andersen,...
    Connect with: VER binkd/1.1a-27/Linux (Old!)
    When I connect with a point number: Error: No AKAs in common domains or all AKAs are busy.
    With my node number the response is ok.

    "New" node in net 712: ,101,jumpleft.com,Sydney_NSW,Jared_Quinn,-Unpublished-,300,CM,IBN:jumpleft.com Connect with: BinkIT/2.41,JSBinkP/4,sbbs3.19c/Linux
    (Jared already was a node a couple of times since 1993)

    Regards, Wilfred

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Tommi Koivula@2:221/1 to Wilfred van Velzen on Fri Oct 14 13:53:22 2022
    Hi Wilfred.

    14 Oct 22 12:34, you wrote to All:

    Net 221 concatenated the IBN,INA: entries to IBN:,

    It indeed did!

    and corrected the order of the Ixx flags for node 360.

    I'm not sure if there was anything to 'correct', but changed the order...

    Kudos to Tommi! ;)

    Thanks anyways.. ;)

    'Tommi

    --- GoldED+/LNX 1.1.5-b20220504
    * Origin: rbb.fidonet.fi (2:221/1)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri Oct 14 13:14:03 2022
    Hi Tommi,

    On 2022-10-14 13:53:22, you wrote to me:

    and corrected the order of the Ixx flags for node 360.

    I'm not sure if there was anything to 'correct', but changed the order...

    When you have multiple INA and other Ixx flags, it could be unclear which INA applies to which other Ixx flag. So the prefered order is to put the INA in front of the other Ixx flags it applies to.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Tommi Koivula@2:221/1.1 to Wilfred van Velzen on Fri Oct 14 14:37:08 2022
    Hi Wilfred.

    14 Oct 22 13:14:02, you wrote to me:

    and corrected the order of the Ixx flags for node 360.

    I'm not sure if there was anything to 'correct', but changed the order...

    When you have multiple INA and other Ixx flags, it could be unclear which INA applies to which other Ixx
    flag. So the prefered order is to put the INA in front of the other Ixx flags it applies to.

    I know what you mean, but still I don't know if it makes any difference to any mailer. If there is INA, it applies to every Ixx.

    I was thinking about removing INA from 2:221/360 and putting multiple IBN:'s and ITN:'s instead. So that ITN has A address and IBN has A and AAAA. :)

    'Tommi

    ---
    * Origin: Point One (2:221/1.1)
  • From Tommi Koivula@2:221/1 to Wilfred van Velzen on Fri Oct 14 14:57:58 2022

    14 Oct 22 14:37, Tommi Koivula wrote to Wilfred van Velzen:

    When you have multiple INA and other Ixx flags, it could be unclear which INA applies to which other Ixx
    flag. So the prefered order is to put the INA in front of the other Ixx flags it applies to.

    I know what you mean, but still I don't know if it makes any difference to any mailer. If there is INA, it applies
    to every Ixx.

    === Cut ===
    ;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 |
    === Cut ===

    - _the default_
    - _that does not specify its own_

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/1)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri Oct 14 14:42:21 2022
    Hi Tommi,

    On 2022-10-14 14:37:08, you wrote to me:

    When you have multiple INA and other Ixx flags, it could be unclear
    which INA applies to which other Ixx flag. So the prefered order is
    to put the INA in front of the other Ixx flags it applies to.

    I know what you mean, but still I don't know if it makes any difference to any mailer. If there is INA, it applies to every Ixx.

    Maybe, but all examples in ftsc documents always list the INA first. And I think that makes sense.

    I was thinking about removing INA from 2:221/360 and putting multiple IBN:'s and ITN:'s instead. So that ITN has A address and IBN has A and AAAA. :)

    Not using an INA, makes it absolutely clear what is intended.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri Oct 14 14:42:39 2022
    Hi Tommi,

    On 2022-10-14 14:57:58, you wrote to me:

    I know what you mean, but still I don't know if it makes any
    difference to any mailer. If there is INA, it applies to every Ixx.

    === Cut ===
    ;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 |
    === Cut ===

    - _the default_

    That seems to agree with fts-5001.006

    Flag Description
    -------------------------

    INA This flag sets a default server address used
    for any Internet Protocol Flag that does not
    specify its own.

    - _that does not specify its own_

    But in the examples of fts-5004.001, we read this:

    ; 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

    ; 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

    ; IBN:fido.example.net,IFC:fido.example.com:12345
    ; no INA flag means there's no common address

    So these 2 document contradict


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)