• rouge areafix?

    From Rick Smith@1:105/81 to All on Sat Feb 5 12:14:36 2022
    Hello All!

    For months now I am been recieving at the hub areafix responses about a request that cannot be found. It comes from a different node in my hub each time and sometimes the hubs addy as well? I have contacted all my nodes and they all say that they did not make this request, anyone ever see this before? He is an example of message I receive and this one the request supposedly came from my bbs which I know it didnt..

    Area Status
    -------------------------------------------------- -------------------------
    Eric ............................................. not found

    Following is the original message text
    --------------------------------------
    -Eric


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

    -+- hpt/lnx 1.9.0-cur 2021-04-18 areafix
    + Origin: Areafix robot (1:105/10)

    Regards,

    Rick

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)
  • From Alan Ianson@1:153/757 to Rick Smith on Sat Feb 5 14:29:04 2022
    Hello All!

    For months now I am been recieving at the hub areafix responses about a request that cannot be found. It comes from a different node in my hub each time and sometimes the hubs addy as well? I have contacted all my nodes and they all say that they did not make this request, anyone ever see this before? He is an example of message I receive and this one the request supposedly came from my bbs which I know it didnt..

    Have a look at the time and date that message was created and then have a look in your log for that time and date for an areafix reply.

    Hopefully the log will shed a little light an what is happening.

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From mark lewis@1:3634/12.73 to Rick Smith on Sun Feb 6 06:16:10 2022

    On 2022 Feb 05 12:14:36, you wrote to All:

    Area Status
    -------------------------------------------------- ------------------------- Eric ............................................. not found

    Following is the original message text --------------------------------------
    -Eric

    ProTip: when you do an areafix or filefix request, be sure the last thing below the actual areafix/filefix commands is three dashes ("---") for a tear line... this way the areafix/filefix software will know to stop processing at that point and it will not attempt to process any signature lines that your software may automatically add...

    eg:

    to: areafix, 1:123/0
    fr: me, 1:123/xx
    re: mypassword
    =====================
    %help
    %list
    ---
    these are my autoadded signature
    lines that areafix always complains
    about until i add the tear line above


    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
    ... Maybe if I go lay down the feeling will go away.
    ---
    * Origin: (1:3634/12.73)
  • From Rick Smith@1:105/81 to mark lewis on Sun Feb 6 10:31:34 2022
    Hello mark!

    Sunday February 06 2022 06:16, you wrote to me:

    * Forwarded from area 'FN_SYSOP'
    On 2022 Feb 05 12:14:36, you wrote to All:

    Area Status
    --------------------------------------------------
    --------------------------------------
    -Eric

    ProTip: when you do an areafix or filefix request, be sure the last
    thing below the actual areafix/filefix commands is three dashes
    ("---") for a tear line... this way the areafix/filefix software will
    know to stop processing at that point and it will not attempt to
    process any signature lines that your software may automatically
    add...
    Mark that just gave me a thought, one of my nodes sysops first name is Eric, maybe he did not use a ---? and it read his name as a request? In any even any idea how to stop this perpetual request???

    Regards,

    Rick
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)
  • From Rick Smith@1:105/81 to Alan Ianson on Sun Feb 6 10:32:00 2022
    Hello Alan!

    Saturday February 05 2022 14:29, you wrote to me:

    * Forwarded from area 'FN_SYSOP'
    Hello All!

    For months now I am been recieving at the hub areafix responses
    about a request that cannot be found. It comes from a different
    node in my hub each time and sometimes the hubs addy as well? I
    have contacted all my nodes and they all say that they did not make
    this request, anyone ever see this before? He is an example of
    message I receive and this one the request supposedly came from my
    bbs which I know it didnt..

    Have a look at the time and date that message was created and then
    have a look in your log for that time and date for an areafix reply.

    Thanks for the tip, I see I can find anything

    Regards,

    Rick
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)
  • From mark lewis@1:3634/12.73 to Rick Smith on Mon Feb 7 03:04:42 2022

    On 2022 Feb 06 10:31:34, you wrote to me:

    ProTip: when you do an areafix or filefix request, be sure the last
    thing below the actual areafix/filefix commands is three dashes
    ("---") for a tear line... this way the areafix/filefix software will
    know to stop processing at that point and it will not attempt to
    process any signature lines that your software may automatically
    add...

    Mark that just gave me a thought, one of my nodes sysops first name is Eric, maybe he did not use a ---? and it read his name as a request?

    most likely... a lot of people don't think about it... especially if the software they use automatically adds a signature to their messages...

    In any even any idea how to stop this perpetual request???

    what do you mean "perpetual request"?? do you mean it happens on everyone one of their areafix requests or something else?

    if it happens on every one of their areafix messages, there's nothing you can do other than maybe pointing out to them what is happening due to their signature... if you can get them to manually add the three dashes tearline after their areafix commands, as i wrote above, it should stop...

    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
    ... "War against Terror!" - Means no more Hollywood horror movies?
    ---
    * Origin: (1:3634/12.73)
  • From Rick Smith@1:105/81 to mark lewis on Tue Feb 8 07:00:04 2022
    Hello mark!

    Monday February 07 2022 03:04, you wrote to me:

    * Forwarded from area 'FN_SYSOP'

    On 2022 Feb 06 10:31:34, you wrote to me:


    In any even any idea how to stop this perpetual request???

    what do you mean "perpetual request"?? do you mean it happens on
    everyone one of their areafix requests or something else?

    What I mean is I have got this message on the hub estimated hundred times for months, it rotates through all my hosted nodes. even my own. So one week it will come from say 105/10 then it will come from /11 the next and so on, then it will come from the hub to the hub at some point... Its crazy

    Regards,

    Rick

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)
  • From deon@3:633/509 to Rick Smith on Wed Feb 9 10:11:05 2022
    Re: rouge areafix?
    By: Rick Smith to mark lewis on Tue Feb 08 2022 07:00 am

    What I mean is I have got this message on the hub estimated hundred times for months, it rotates through all my hosted nodes. even my own. So one week it will come from say 105/10 then it will come from /11 the next and so on, then it will come from the hub to the hub at some point... Its crazy

    Have you traced which system that gives you the packet that areafix process and generates that reply?

    Everything should be in your log - you may need to turn up the logging to trace it better, but the approach I would take is:

    * Find the packet that causes your areafix to reply with this error (ie: tosser log)
    * Find the system that gave you that packet. (ie: binkp log)
    * Talk with the system owner, and see if they can see why they gave you that packet.


    ...δεσ∩
    --- SBBSecho 3.14-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)