Hi Ward,

On 2021-05-04 18:12:18, you wrote to All:

Odd things in the messages which I get in this echo ... we take as an example the below message from Janis ...

***************************************************************************
** From: Janis Kracht To: Rob Swindell

MSGID: 1:261/38.0 ed385693

P@TH: 320/219 80/1 301/1 292/854 203/0 230/0 150 261/38 396/45
P@TH: 280/464 292/854 ***************************************************************************
** For starters, as good as every msg I get in this echo starts with pathline..

P@TH: 320/219 ... ???

To my mind, a message written by Janis should start with ...

P@TH: 261/38 ...

There was a huge message dump of old mail this morning in this area.
All with the same path line when they arrived here:

@PATH: 320/219 80/1 301/1

So my guess is that 80/1 did a rescan of this area at 320/219. I've already notified both sysops, but haven't got a response yet.

Therefore the question ... Andrew Leary ... Wazzup? Why are you in the first spot? Who's your uplink?

Second, my nodenumber is clearly visible. The message loops again to Z1, transits Janis's system undetected and eventually lands back on my system coming from Wilfred ... but Wilfred already received it from me and his system would, as the French say, "neveurrr do zis"... Unless someone stripped the seen-by's ... which is exactly what happened because 80/1 is gone.

Janis, Bjorn, Marc and Wilfred can be ruled-out ... but hello Gert Andersen. My money's on him, the last 20 years he could always be counted upon for stupid things. He's probably the most incompetent sysop in the whole nodelist ... there are only 2 Danes in Fidonet and both are challenged.

I'm not the moderator here, but ... Janis, could you please disconnect yourself from Gert in this echo ... Only Turing knows how many echoes Gert has recently messed again with ...

In this case it's not Gerts fault. He uses an old HPT (1.4) that has hardcoded seenby stripping, but that is on arrival from a different zone, and he got it from Bjorn in this case. In this case, my guess, the problem is at Janis. BBBS Also has a form of hardcoded seenby stripping (tiny seenby's), where it strips seenby's from not connected systems when the echomail arrives from another zone (in this case from Gert). I've discussed this with Janis last year, she was going to contact Kim about this, but I think he has been AWOL for a while now. So no fix for BBBS yet...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Odd things in the messages which I get in this echo ... we take as an example the below message from Janis ...

***************************************************************************** From: Janis Kracht
To: Rob Swindell

MSGID: 1:261/38.0 ed385693

P@TH: 320/219 80/1 301/1 292/854 203/0 230/0 150 261/38 396/45
P@TH: 280/464 292/854 ***************************************************************************** For starters, as good as every msg I get in this echo starts with pathline..

P@TH: 320/219 ... ???

To my mind, a message written by Janis should start with ...

P@TH: 261/38 ...

Therefore the question ... Andrew Leary ... Wazzup? Why are you in the first spot? Who's your uplink?

Second, my nodenumber is clearly visible. The message loops again to Z1, transits Janis's system undetected and eventually lands back on my system coming from Wilfred ... but Wilfred already received it from me and his system would, as the French say, "neveurrr do zis"... Unless someone stripped the seen-by's ... which is exactly what happened because 80/1 is gone.

Janis, Bjorn, Marc and Wilfred can be ruled-out ... but hello Gert Andersen. My money's on him, the last 20 years he could always be counted upon for stupid things. He's probably the most incompetent sysop in the whole nodelist ... there are only 2 Danes in Fidonet and both are challenged.

I'm not the moderator here, but ... Janis, could you please disconnect yourself from Gert in this echo ... Only Turing knows how many echoes Gert has recently messed again with ...

\%/@rd

--- DB4 - May.03 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Hi Ward,

On 2021-05-04 18:23:08, I wrote to you:

P@TH: 320/219 80/1 301/1 292/854 203/0 230/0 150 261/38 396/45
P@TH: 280/464 292/854

In this case it's not Gerts fault. He uses an old HPT (1.4) that has hardcoded seenby stripping, but that is on arrival from a different
zone, and he got it from Bjorn in this case.

Sorry that should be Benny, not Bjorn. But that doesn't change my point, that Gert got it from within the same zone, so no seenby stripping took place on his system...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Odd things in the messages which I get in this echo ... we take as an example the below message from Janis ...

My bad. I was re-organizing the feeds and did this mess.
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Fidonet Brasil - R80 Internet Gateway (4:80/1)

Hi Andrew,

On 2021-05-04 13:13:43, you wrote to me:

So my guess is that 80/1 did a rescan of this area at 320/219. I've
already notified both sysops, but haven't got a response yet.

I checked the log; Flavio Bessa at 4:80/1 rescanned FN_SYSOP this morning, for 15001 messages.

I got 1432 of them:

---------- Tue 2021-05-04 13:33:50, FMail-lnx64-2.1.0.18-Beta20170815 - Toss Summary

Board Area name #Msgs Dupes
----- -------------------------------------------------- ----- -----
200 Bad messages 1014
JAM FN_SYSOP 17 401
----- -------------------------------------------------- ----- -----
2 1031 401

So most were detected as too old or as dupes...

I haven't received a message from you regarding it; did you send it routed?

I delivered 2 crashmails:

+ 04 May 13:40:52 [12394] call to 1:320/219@fidonet
- 04 May 13:40:53 [12394] SYS Phoenix BBS
- 04 May 13:40:53 [12394] ZYZ Andrew Leary
+ 04 May 13:40:53 [12394] addr: 1:320/219@fidonet
+ 04 May 13:40:53 [12394] sent: /home/fido/outbound.001/09132c10.pkt (1148, 1148.00 CPS, 1:320/219@fidonet)

+ 04 May 13:44:34 [12496] call to 1:320/219@fidonet
- 04 May 13:44:34 [12496] SYS Phoenix BBS
- 04 May 13:44:34 [12496] ZYZ Andrew Leary
+ 04 May 13:44:34 [12496] addr: 1:320/219@fidonet
+ 04 May 13:44:35 [12496] sent: /home/fido/outbound.001/09133a10.pkt (1420, 1420.00 CPS, 1:320/219@fidonet)

Maybe they are in your insecure inbound?

In this case it's not Gerts fault. He uses an old HPT (1.4) that has
hardcoded seenby stripping, but that is on arrival from a different
zone, and he got it from Bjorn in this case. In this case, my guess,
the problem is at Janis. BBBS Also has a form of hardcoded seenby
stripping (tiny seenby's), where it strips seenby's from not connected
systems when the echomail arrives from another zone (in this case from
Gert). I've discussed this with Janis last year, she was going to
contact Kim about this, but I think he has been AWOL for a while now.
So no fix for BBBS yet...

Interesting. It appears that BBBS and HPT 1.4 can join FastEcho on the list as not suitable for use on interzone FidoWeb connections.

They were on that list already of course, but not as well known, certainly BBBS wasn't...

Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

04 May 21 20:44, you wrote to me:

I delivered 2 crashmails:

Maybe they are in your insecure inbound?

Correct. I've been meaning to change mbfido to automatically process uncompressed packets from the insecure inbound. ARCmail from the insecure inbound is not processed until I manually do so.

Interesting. It appears that BBBS and HPT 1.4 can join FastEcho
on the list as not suitable for use on interzone FidoWeb
connections.

They were on that list already of course, but not as well known,
certainly BBBS wasn't...

I find it interesting that BBBS forces tiny seen-bys, instead of stripping them completely. To be fair, stripping seen-bys when crossing Zone boundaries used to be necessary, back in the days when there were duplicate net numbers between Zones. The last of those has been gone for over 7 years now, when Net 1:250 was removed in March, 2014.

Andrew

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Odd things in the messages which I get in this echo ... we take as an example the below message from Janis ...

***************************************************************************** From: Janis Kracht
To: Rob Swindell

MSGID: 1:261/38.0 ed385693

P@TH: 320/219 80/1 301/1 292/854 203/0 230/0 150 261/38 396/45
P@TH: 280/464 292/854 ***************************************************************************** For starters, as good as every msg I get in this echo starts with pathline..

P@TH: 320/219 ... ???

To my mind, a message written by Janis should start with ...

P@TH: 261/38 ...

Therefore the question ... Andrew Leary ... Wazzup? Why are you in the first spot? Who's your uplink?

Second, my nodenumber is clearly visible. The message loops again to Z1, transits Janis's system undetected and eventually lands back on my system
coming from Wilfred ... but Wilfred already received it from me and his system
would, as the French say, "neveurrr do zis"... Unless someone stripped the seen-by's ... which is exactly what happened because 80/1 is gone.

Janis, Bjorn, Marc and Wilfred can be ruled-out ... but hello Gert Andersen. M
money's on him, the last 20 years he could always be counted upon for stupid things. He's probably the most incompetent sysop in the whole nodelist ... there are only 2 Danes in Fidonet and both are challenged.

<sigh>

I'm not the moderator here, but ... Janis, could you please disconnect yoursel >from Gert in this echo ... Only Turing knows how many echoes Gert has recently
messed again with ...

Yeah, I can do that...I'll take care of it tonight...we'll see what happens then.

Take care,
Janis

--- BBBS/Li6 v4.10 Toy-5
* Origin: Prism bbs (1:261/38)

Hi Andrew,

On 2021-05-04 16:54:57, you wrote to me:

I delivered 2 crashmails:

Maybe they are in your insecure inbound?

Correct. I've been meaning to change mbfido to automatically process uncompressed packets from the insecure inbound. ARCmail from the insecure inbound is not processed until I manually do so.

That's good practice, I do that too...

Interesting. It appears that BBBS and HPT 1.4 can join FastEcho
on the list as not suitable for use on interzone FidoWeb
connections.

They were on that list already of course, but not as well known,
certainly BBBS wasn't...

I find it interesting that BBBS forces tiny seen-bys, instead of
stripping them completely. To be fair, stripping seen-bys when
crossing Zone boundaries used to be necessary, back in the days when
there were duplicate net numbers between Zones.

Of course, that's why it was "invented".

The last of those has been gone for over 7 years now, when Net 1:250
was removed in March, 2014.

And still there is software in use that has this hardcoded... :-(


Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi Janis,

On 2021-05-04 19:29:30, you wrote to Ward Dossche:

Janis, Bjorn, Marc and Wilfred can be ruled-out ... but hello Gert
Andersen. M money's on him, the last 20 years he could always be
counted upon for stupid things. He's probably the most incompetent
sysop in the whole nodelist ... there are only 2 Danes in Fidonet and
both are challenged.

<sigh>

I'm not the moderator here, but ... Janis, could you please disconnect
yoursel from Gert in this echo ... Only Turing knows how many echoes Gert
has recently messed again with ...

Yeah, I can do that...I'll take care of it tonight...we'll see what happens
then.

You might want to read the rest of the messages in this area about this subject. If anything you need to disconnect all your links in other zones from all areas...

Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

05 May 21 08:59, you wrote to me:

Correct. I've been meaning to change mbfido to automatically
process uncompressed packets from the insecure inbound. ARCmail
from the insecure inbound is not processed until I manually do
so.

That's good practice, I do that too...

I was bored at work last night, so I finally got around to adding automatic processing of uncompressed .PKTs from the insecure inbound. I tested it this morning and it appears to be working properly.

And still there is software in use that has this hardcoded... :-(

That's why I try to use open source software whenever I can. If something like this is a problem, I can fix it myself, as I did with MBSE.

Andrew

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)