1. Forum
  2. Fidonet
  3. FIDOSOFT.HUSKY

  • htick and robots

    From Deon George@3:633/509 to Michael Dukelsky on Thu Nov 5 16:02:30 2020
    Hey Michael,

    I see you doing lots of updates to husky (awesome), so wondered if you could also fix a problem that I see.

    (Or let me know what I'm doing wrong.)

    I have multiple networks, and use multiple netmailareas. (I needed to use multiple, so that makenl posts of nodelist updates go out correctly.)

    So, to handle areafix requests, I also have a netmail area for areafix and filefix messages:

    netmailarea robots /fido/msgbase/robots -b Jam -p 30 robotsarea robots

    While requests to htick (from any network) work and are processed correctly, messages to filefix do not.

    I'm working from memory, but I think the problem is that incoming messages to a robot (eg: filefix), get put in the network netmail area, not the robot netmail area, and thus they dont get processed.

    My work around at the moment is via perl, I copy messages to filefix back into the robots area, so they get processed.

    Happy to provide more debugging or detail if this is something you can fix...

    ...

    ... Heresy is only another word for freedom of thought.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Kai Richter@2:240/77 to Deon George on Thu Nov 5 07:08:10 2020
    Hello Deon!

    05 Nov 20, Deon George wrote to Michael Dukelsky:

    My work around at the moment is via perl, I copy messages to filefix
    back into the robots area, so they get processed.

    Why perl? There is carbon copy in hpt:

    * CarbonAddr:: make carbonCopy using from address of msg
    * CarbonAndQuit:: carbon message only one time
    * CarbonCopy:: specify the area where the carbon copies go into
    * CarbonDelete:: specify that the carbon msg should be deleted
    * CarbonExcludeFwdFrom:: exclude " * Forward from area " string
    * CarbonExtern:: specify the external program to pass msg text to
    * CarbonFrom:: make carbonCopy using from-field of msg
    * CarbonFromArea:: carbon messages from area
    * CarbonGroups:: make carbonbonCopy from this groups
    * CarbonKeepSb:: keep seen-by's and path
    * CarbonKludge:: make carbonCopy using kludge lines of msg

    * CarbonMove:: specify the area where the carbon msg get moved

    * CarbonOut:: carbon outgoing messages
    * CarbonReason:: string of carbon copy reason
    * CarbonRule:: how to combine Carbon expressions
    * CarbonSubj:: make carbonCopy using subject-field of msg
    * CarbonText:: make carbonCopy using text-field of msg
    * CarbonTo:: make carbonCopy using to-field of msg
    * ExcludePassthroughCarbon:: don't carbon in passthrough areas
    * NetmailExtern:: specify the external Program to pass netmail

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Michael Dukelsky@2:5020/1042 to Deon George on Thu Nov 5 13:34:14 2020
    Hello Deon,

    Thursday November 05 2020, Deon George wrote to Michael Dukelsky:

    I have multiple networks, and use multiple netmailareas. (I needed to
    use multiple, so that makenl posts of nodelist updates go out
    correctly.)

    So, to handle areafix requests, I also have a netmail area for areafix
    and filefix messages:

    netmailarea robots /fido/msgbase/robots -b Jam -p 30
    robotsarea robots

    While requests to htick (from any network) work and are processed correctly, messages to filefix do not.

    I'm working from memory, but I think the problem is that incoming
    messages to a robot (eg: filefix), get put in the network netmail
    area, not the robot netmail area, and thus they dont get processed.

    My work around at the moment is via perl, I copy messages to filefix
    back into the robots area, so they get processed.

    Filefix processes messages from RobotsArea, or from the first netmail area if RobotsArea is not defined. Since you have many netmail areas, the only option for you is moving the messages to filefix to RobotsArea. So I think what you do is not a workaround, it is normal.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Moscow, Russia (2:5020/1042)
  • From Deon George@3:633/509 to Kai Richter on Thu Nov 5 22:08:58 2020
    Re: htick and robots
    By: Kai Richter to Deon George on Thu Nov 05 2020 07:08 am

    Howdy,

    My work around at the moment is via perl, I copy messages to filefix
    back into the robots area, so they get processed.

    Why perl? There is carbon copy in hpt:

    Yeah, I actually knew of Carbon Copy, but I had perl doing other things - responding to test messages, ping, etc, so I just had it copy the mail into the robots area...

    ...

    ... Deny thy father and forget thy tagline.
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Deon George@3:633/509 to Michael Dukelsky on Thu Nov 5 22:10:45 2020
    Re: htick and robots
    By: Michael Dukelsky to Deon George on Thu Nov 05 2020 01:34 pm

    Howdy,

    Filefix processes messages from RobotsArea, or from the first netmail area if RobotsArea is not defined. Since you have many netmail
    areas, the only option for you is moving the messages to filefix to RobotsArea. So I think what you do is not a workaround, it is
    normal.

    Ahh, OK. Thanks.

    I was thinking that it would recognise robot messages and put them in the Robot area automatically - but if that isnt intended, and my workaround is the right way - good enough...

    ...

    ... Psychologists only do it if they feel good about it
    --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)