Subj : Possible bug using mbfido no
To   : Andrew Leary
From : Vincent Coen
Date : Fri Feb 28 2025 20:43:32


Hello Andrew!

15 Feb 25 15:29, I wrote to you:


As a follow on from previous msg regarding issues when using mbfido no  on a
secondary fido address at 2:263/1  where the infor sent is - well broken such
as :

 Dear Sean Rima:

 The following is a flow report of all message areas

 Group @G @J (@I)
                                         P O S T E D         R E C E I V
 E D Message area                   Last week  Last month  Last week
 Last Month - ------------------------------ ---------- ----------
 ---------- ----------


With the rest blank I suspect that it relates to the address of the node is 
not
in 2:25 or 2:250.

I am going to try and allocate a new node address 2:0/101 as an aka to 263/1
and see if that fixes it - just have to remember to route such to 2:263/1
though.

Will advise.

Vincent


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

.