Subj : Re: makenl sbbsecho and netmail and routing issue
To   : Digital Man
From : Ragnarok
Date : Tue Oct 05 2021 22:03:37

El 5/10/21 a las 16:54, Digital Man escribió:
>    Re: Re: makenl sbbsecho and netmail and routing issue
>    By: Wilfred van Velzen to Digital Man on Tue Oct 05 2021 09:45 am
> 
>   > Hi Digital,
>   >
>   > On 2021-10-04 19:06:36, you wrote to Ragnarok:
>   >
>   >  >> I notice that the sbbsecho log weird address (4:943) instead of 39:943,
>   >  >> so this was ruoted via 4:* (zone was rewrite)
>   >  >>
>   >  >> 2021-10-03 22:42:03 Packing NetMail (1.msg) from MakeNL 3.5.1 (4:943/0)
>   >  >> to Coordinator (4:943/100), attr: 0191, subject:
>   >  >> /sbbs/fido/makenl/out/net.943
>   >
>   >  DM> Looks like Fuzzy Zone operation is enabled.
>   >
>   >  DM> Fuzzy Zone Operation when set to Yes, if SBBSecho receives an inbound
>   >  DM>      netmail with NO international zone information, it will compare
>   >  DM> the
>   >  DM>      net/node of the destination to the net/node information in your
>   >  DM> AKAs
>   >  DM>      and assume the (source and destination) zone of a matching AKA.
>   >  DM>      This setting defaults to No.
>   >
>   > I checked a stored message that makenl generates. It has the complete 4D
>   > address of the source and destination in the header (and also the source
>   > address in the MSGID kludge). A tosser should put those in the INTL kludge
>   > of the packed message in the .pkt file it generates. The Fuzzy Zone setting
>   > shouldn't overrule the information in an INTL kludge if present. So where
>   > does this go wrong?
> 
> The Fuzzy Zone setting instructs SBBSecho to ignore the zone information in the netmail message header. If the netmail itself had an INTL kludge, it would use the zone information from that, but makenl isn't adding it. So, with Fuzzy Zone behavior, SBBSecho will "guess" the zone information based on the destination net/node/point. It's an arcane feature for old pre-historic "stored messages" and probably should just be removed.
> 
Yeah this is!!.. i found that notify option on makenl have a INTL 
parameter, if i add this, the @INTL kludge was added to the netmail

"notify all intl"

root@scarlet:/sbbs/fido/makenl/msgout# fmsgdump -c -b 1.msg
fmsgdump rev 3.6 - Dump FidoNet Stored Messages

Opening 1.msg
Subj: /sbbs/fido/makenl/out/net.943
Attr: 0x0191 (PRIVATE, FILE, KILLSENT, LOCAL)
To  : Coordinator (39:943/100.0)
From: MakeNL 3.5.1 (39:943/0.0)
Time: 05 Oct 21  21:52:18

-start of message text-
@INTL 39:943/100 39:943/0
MSGID: 39:943/0 615908bd
-end of message text-

Now, sbbs sent perfect to the z39 node!


2021-10-05 21:53:34 Packing NetMail (1.msg) from MakeNL 3.5.1 (39:943/0) 
to Coordinator (39:943/100), attr: 0191, subject: 
/sbbs/fido/makenl/out/net.943
2021-10-05 21:53:34 Node (39:943/100) successfully locked via: 
/sbbs/fido/outbound.027/03af0064.bsy
2021-10-05 21:53:34 File (/sbbs/fido/makenl/out/net.943, 0.7KB) for 
39:943/100 added to BSO/FLO file: /sbbs/fido/outbound.027/03af0064.flo
2021-10-05 21:53:34 Adding NetMail (1.msg) to new packet for 39:943/100: 
/sbbs/fido/outbound.027/03af0064.out

This was the correct solution, I had deactivated fuzzy zone, but it 
still did not work until I changed the INTL parameter in the makenl config

DM and Wilfred! I am very grateful to learn from you!
You are the best!

Thanks!

---
 ￭ Synchronet ￭ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.