1. Forum
  2. FidoNet
  3. MAKENL NG

  • Bug or User Error? :)

    From Paul Hayton@3:770/100 to All on Tue Feb 9 20:27:03 2021
    In my CTL file I have a

    netaddress 21:1/1

    Later I have under files these lines

    Net 3 z21n3 21:3/100
    Net 4 z21n4 21:4/100

    when testing for segments being sent in MakeNL processes them and generates *.msg files to send back to the submitters..

    But it seems to create them addressed to Zone 3 addresses not Zone 21 as when
    I run HPT to pack those netmails I see this

    7 Feb:09:2021:20:19:04 Msg packed with flavour 'crash': 3:1/1 -> 3:3/100
    L Feb:09:2021:20:19:04 Msg #1 from 3:1/1 to 3:3/100 deleted
    7 Feb:09:2021:20:19:04 Msg packed with flavour 'crash': 3:1/1 -> 3:4/100
    L Feb:09:2021:20:19:04 Msg #1 from 3:1/1 to 3:4/100 deleted


    Any thoughts?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Andrew Leary@1:320/219 to Paul Hayton on Tue Feb 9 05:01:01 2021
    Hello Paul!

    09 Feb 21 20:27, you wrote to all:

    @TID: Mystic BBS 1.12 A46
    @MSGID: 3:770/100 25b3f259
    @TZUTC: 1300
    In my CTL file I have a

    netaddress 21:1/1

    Later I have under files these lines

    Net 3 z21n3 21:3/100
    Net 4 z21n4 21:4/100

    when testing for segments being sent in MakeNL processes them and generates *.msg files to send back to the submitters..

    But it seems to create them addressed to Zone 3 addresses not Zone 21
    as when I run HPT to pack those netmails I see this

    7 Feb:09:2021:20:19:04 Msg packed with flavour 'crash': 3:1/1 ->
    3:3/100 L Feb:09:2021:20:19:04 Msg #1 from 3:1/1 to 3:3/100 deleted 7 Feb:09:2021:20:19:04 Msg packed with flavour 'crash': 3:1/1 ->
    3:4/100 L Feb:09:2021:20:19:04 Msg #1 from 3:1/1 to 3:4/100 deleted

    Any thoughts?

    Add the INTL flag to your notify keywords to force MakeNL to include an INTL kludge line even if the netmail is addressed to the same zone. ie:

    Notify Self INTL
    Notify Errors CRASH INTL
    Notify Receipt INTL

    Regards,

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Paul Hayton@3:770/100 to Andrew Leary on Wed Feb 10 12:02:20 2021
    On 09 Feb 2021 at 05:01a, Andrew Leary pondered and said...

    Add the INTL flag to your notify keywords to force MakeNL to include an INTL kludge line even if the netmail is addressed to the same zone. ie:

    Thanks Andrew, that seems to have fixed this issue. :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Nick Andre@1:229/426 to Paul Hayton on Tue Feb 9 22:36:52 2021
    On 10 Feb 21 12:02:20, Paul Hayton said the following to Andrew Leary:

    Add the INTL flag to your notify keywords to force MakeNL to include a INTL kludge line even if the netmail is addressed to the same zone. i

    Thanks Andrew, that seems to have fixed this issue. :)

    What you may or may not find helpful... is you have a working MakeNL directory that "calls" your master text files, programs etc. as part of a batch that sweeps your inbound every half hour.

    I wrote custom software I am willing to share with you that examines every segment received from RC's and if there is a "problem" it will reject the segment but it reverts back to the last-known-good segment. That way, nothing is being rejected outright out of the nodelist because of problems... there is never a missing Region or Net segment.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Paul Hayton@3:770/100 to Nick Andre on Wed Feb 10 19:57:47 2021
    On 09 Feb 2021 at 10:36p, Nick Andre pondered and said...

    What you may or may not find helpful... is you have a working MakeNL directory that "calls" your master text files, programs etc. as part of
    a batch that sweeps your inbound every half hour.

    I wrote custom software I am willing to share with you that examines
    every segment received from RC's and if there is a "problem" it will reject the segment but it reverts back to the last-known-good segment.

    Thanks Nick, really appreciate the offer. I'll get in touch with you via Netmail.

    For starters I am just going to get the thing running using the out of the
    box settings and options. This is because I have not been using it to accept segments from nets in Zone 21... To date it's been just me maintaining the
    lot, but thats not a great plan so the new plan is to start accepting segments in the not too distant future. It's a brave new world for this fellow :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)