Routing more information from original poster BUG Found
From Vincent Coen@2:250/1 to All on Mon May 2 17:19:37 2022
An update from previous post :
I have now received a email showing what he sent :
* Area: NetMail
* From: Ping TRACE service, 2:250/1 (02 May 2022 14:59)
* To: John Dovey
* Subject: Re: Your PING Request ============================================================
Dear John Dovey,
You sent a PING request to 2:250/21.
This is a TRACE response from "Air Applewood BBS" (AKA 2:250/1@fidonet).
The time of arrival is Mon, 02 May 2022 14:59:45 +0100.
Here are all the detected VIA lines from your message:
Via 4:92/1 @20220502.043835.UTC SBBSecho 3.15-Linux master/04cec7e18
Via 2:30/0@fidonet @20220502.063908.UTC FlexToss 2.00B01/1
Via 2:250/1@fidonet @20220502.043916.UTC mbfido 1.0.8
Chopped lots of the last line
Yss his system should have bounced the direct posting as address does not exist
BUT looking at the mbse manual the routing if sent from here by using
mbfido te f21.n250.z2 (This does not exist in the Nodelist) is :
BFIDO: MBSE BBS 1.0.8 - Fidonet File and Mail Processor
Copyright (C) 1997-2022 MBSE Development Team, All Rights Reserved
Route 2:250/21 => 2:250/0@fidonet, route result: Route to
MBFIDO finished in 0.00s
This seems to me to indicate that mbse is NOT rejected and bouncing back the netmail request.
So even if the poster get his mail to me my system is helping to create the loop.
This is clearly looking like a bug in mbse.
There is a comment from Michael that he was going to fix this documented in the
section about the Netmail routing behaviour under Tracking and bouncing.
Looks like this was never done and needs to be.
--- Mageia Linux v8 X64/Mbse v1.0.8/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
Fri Sep 29 13:02:31 2023
Fri Sep 29 11:29:13 2023
Fri Sep 29 10:40:11 2023
Fri Sep 29 09:19:43 2023