1. Forum
  2. FidoNet
  3. Z2REGION25

  • Warning about using 2:25/21 for ECHOLIST file area

    From Vincent Coen@2:250/1 to All on Thu Feb 3 01:10:25 2022
    Hello All!

    Received this today from a downlink :

    --
    Hi Vincent,

    Just to let you know I received a file ELST2202.ZIP but it was from your 2:25/21 address and not your 2:250/1 address so ended up in my unsecure area.

    I thought all files would come from 2:250/1?

    Terry
    --

    When sending ECHOLIST archives starting with ELSTyymm.ZIP I am using AKA 2:25/21 as that is the formal address of the elistmaint network name aka.

    If your system can handle multi AKS's for a uplink then just make sure both 2:250/1 and 2:25/21 are listed for my system.

    Can EVERYONE who gets this area check that you are processing it OK and it is not sitting in your inbound or badarea folders and this, is from my system of list of downlinks for this area :

    --
    1. S-- 1:153/7715@fidonet
    2. S-- 2:263/5@fidonet
    3. S-- 2:250/5@fidonet
    4. S- 1:3634/12@fidonet
    5. S-- 2:250/8@fidonet
    6. S-- 2:341/66@fidonet
    7. S-- 2:5020/1042@fidonet
    8. S-- 1:153/757@fidonet
    9. S-- 3:640/1321@fidonet
    --

    If this is a problem for your system let me know ASAP,

    Thanks,

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Alan Ianson@1:153/757 to Vincent Coen on Thu Feb 3 02:23:30 2022
    Just to let you know I received a file ELST2202.ZIP but it was from your 2:25/21 address and not your 2:250/1 address so ended up in my unsecure area.

    I thought all files would come from 2:250/1?

    The same thing happened here. I adjusted the from address to 2:250/1 in the tic and retossed it to get the file moving.

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Ray Quinn@1:214/23 to Vincent Coen on Sat Feb 5 11:48:54 2022
    Hello Vincent!

    03 Feb 22 01:10, you wrote to all:


    When sending ECHOLIST archives starting with ELSTyymm.ZIP I am using
    AKA
    2:25/21 as that is the formal address of the elistmaint network name
    aka.

    If your system can handle multi AKS's for a uplink then just make sure both
    2:250/1 and 2:25/21 are listed for my system.

    With Synchronet/Tickit (I was using HTICK just last week) I can put as many addresses as required. This should be fine as long as any AKA's are in the SEEN-BY section.

    Can EVERYONE who gets this area check that you are processing it OK
    and it is not sitting in your inbound or badarea folders and this, is
    from my system of list of downlinks for this area :

    --
    1. S-- 1:153/7715@fidonet
    2. S-- 2:263/5@fidonet
    3. S-- 2:250/5@fidonet
    4. S- 1:3634/12@fidonet
    5. S-- 2:250/8@fidonet
    6. S-- 2:341/66@fidonet
    7. S-- 2:5020/1042@fidonet
    8. S-- 1:153/757@fidonet
    9. S-- 3:640/1321@fidonet
    --

    If this is a problem for your system let me know ASAP,

    This is one area that slipped by. I just added it today.

    Regarding the multiple addresses you mentioned above: will this also include binkd connections? Should I add 2:25/21 with the same password information or will we only be using the one address. For example: Me, my 1:214/22 to your 2:250/1 and nothing else? I, like you, have multiple Fidonet addresses, 1:214/0 1 22. This one 1:214/23 is a portable one ran from a micro-SD card.


    Ray


    --- GoldED+/W64-MSVC 1.1.5-b20180707
    * Origin: Ham Radio operators do it with frequency! (1:214/23)
  • From Vincent Coen@2:250/1 to Ray Quinn on Mon Feb 7 13:47:29 2022
    Hello Ray!

    Saturday February 05 2022 11:48, you wrote to me:

    03 Feb 22 01:10, you wrote to all:


    When sending ECHOLIST archives starting with ELSTyymm.ZIP I am
    using AKA
    2:25/21 as that is the formal address of the elistmaint network
    name aka.

    If your system can handle multi AKS's for a uplink then just make
    sure both
    2:250/1 and 2:25/21 are listed for my system.

    With Synchronet/Tickit (I was using HTICK just last week) I can put as
    many addresses as required. This should be fine as long as any AKA's
    are in the SEEN-BY section.

    Can EVERYONE who gets this area check that you are processing it
    OK and it is not sitting in your inbound or badarea folders and
    this, is from my system of list of downlinks for this area :

    --
    1. S-- 1:153/7715@fidonet
    2. S-- 2:263/5@fidonet
    3. S-- 2:250/5@fidonet
    4. S- 1:3634/12@fidonet
    5. S-- 2:250/8@fidonet
    6. S-- 2:341/66@fidonet
    7. S-- 2:5020/1042@fidonet
    8. S-- 1:153/757@fidonet
    9. S-- 3:640/1321@fidonet
    --

    If this is a problem for your system let me know ASAP,

    This is one area that slipped by. I just added it today.

    Regarding the multiple addresses you mentioned above: will this also
    include binkd connections? Should I add 2:25/21 with the same password information or will we only be using the one address. For example: Me,
    my 1:214/22 to your 2:250/1 and nothing else? I, like you, have
    multiple Fidonet addresses, 1:214/0 1 22. This one 1:214/23 is a
    portable one ran from a micro-SD card.


    I have now changed the aka I use for this one area to use 2:250/1 - the same as
    all the others but it will not harm you also recording the secondary one as 2:25/21 - JIC :)



    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)