Subj : Possible bug using mbfido no To : Vincent Coen From : Andrew Leary Date : Sat Feb 15 2025 01:13:42 Hello Vincent! 14 Feb 25 17:35, you wrote to all: VC> Just did a notify using mbfido no 2:263/1 VC> Node reports that the netmails come from 2:263/0 VC> Now my AKAs are as set up : VC> 1 2:250/1@fidonet 11 VC> 2 2:25/21@fidonet 12 VC> 3 2:250/0@fidonet 13 VC> 4 2:25/0@fidonet 14 VC> 5 2:263/0@fidonet 15 VC> This is because I am the Host for region 2:25 and therefore 2:250 and VC> 2:263 VC> My primary node is 2:250/1 and 2:25/21 is used for the Elist software. VC> As region 25 is the UK including Northern Ireland but Southern Ireland VC> is an independent country it has its own net as 2:263 and there are 2 VC> nodes present .1 and .5. and I am the host at 2:263/0 as that has to VC> be defined in the nodelist. VC> I have had a look at the source code at mbfido / notify.c and I cannot VC> see where it obtains system AKA from but at a guess it is the last one VC> so how do I tell mbfido no to use the first entry (2:250/1) ? VC> I did a mbfido no 2:250/1 but that did not produce anything, then did VC> a mbfido no 2:25/21 then unpacked the archive being sent to that VC> address as the system reported all AKA's are locked - reasonably as it VC> was trying to send to itself. So moved over the pkt and let mbse deal VC> with it into my netmail inbox area for 250/1 (I have 2 more one for VC> 25/21 and one for 25/0 & 25/21 and no I have no idea who two different VC> akas are being used as : NETMAIL is set Fido Aka 2:250/1 all traffic VC> to/from me at 250/1. NETMAIL2 is set Fido Aka 2:25/0 for Z2 netmail VC> traffic. NETMAIL3 is set Fido Aka 2:25/21 for the Elist AKA 25/21. VC> The only conclusion I can draw is that the problem netmail sent from VC> MBFIDO NO uses the Last AKA but I cannot define what one is used so VC> the question is how do I fix it without breaking the other two Netmail VC> msg areas. VC> Hope I have made this clear but if you have a query regarding all VC> this, fire away. VC> Vincent MBSE defaults to using the closest AKA to the destination. For 2:263/1, that would be 2:263/0. There currently isn't a way to override which AKA is used. I am considering adding support for this, but it'll take a while to get that done and debugged. I do recommend that you setup a NetMail area for every AKA your system has. This insures that MBFIDO has a place to put incoming netmail for any of your system's AKA addresses. Andrew --- GoldED+/LNX 1.1.5-b20240209 * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219) .