* Copied (from: MYMAIL) by Marc Lewis using timEd/2 1.10.y2k+.

All:

This is a copy of an ongoing conversation with Wilfred van Velsen about a .pkt I transmitted to his system (I transmit uncompressed to him) that was missing the packet password and contained 2 routed NetMails to someone in Zone 2. Normally there are no problems between our two systems with either my NetMail or EchoMail to him. This time the two messages seem to have circumvented *everything*.

Needless to day, I'm running the last (latest) version of Squish/2.

Any ideas on how or why and how to prevent this will be appreciated.

Best,
Marc

-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

Hello Wilfred!

<On 23Jul2020 09:14 Wilfred van Velzen wrote a message regarding Re: Follow-up on: .pkt received without a pkt password? >

[snip]

This pkt file contained 2 routed netmails. I never see this on pkt
files coming from your system, containing echomail...?

Strange. I've looked at my "saved" directory of routed NetMails and
I found nothing going to 2:280/464. To whom are they addressed or
what do they contain? I simply can't see how anyone could get the
stuff into your system without knowing our somewhat lengthy session
password. Any clue in the .pkts as to the tosser? I am at a loss.
I am going to try and get squish to give me a log of outbound .pkt
files via the log analyser, but at the moment I am mystified.

Okay - I do see where that .pkt was transmitted to you on 21 JUL 20@21:31:25 US Central time. It will take me a while to run the squish analyser to try and find out what that packet contained

See my other netmail.

and how squish could have sent it without the .pkt password prepended
to the .pkt body... I don't know how that would be possible. (!?)

Your own netmails, like this one get processes fine. So the pkt
file must be containing the correct password. ;)

Maybe it's somehow just related to routed netmails?

Perhaps I have uncovered a squish bug. *Normally* a routed NetMail shows up in my "saved" NetMail folder (which of course is private and I don't normally read anything in there.) Somehow, these two messages managed to circumvent *everything* including the packet level password my system is supposed to place on every .pkt going to you. The squish analyzer I have is quite old and repeatedly returns an error when I ask it for full details - returning nothing but the error... so I am a bit in the dark on this one. I think I will post this in the TUB echo and see if someone comes up with an explanation for this anomaly of packets coming from me to you containing a routed NetMail ending up in your unsecured area. I am at a loss.

Best regards,
Marc

Internet recipients: Your reply in plain-text will be appreciated.
-+- timEd/2 1.10.y2k+
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Hello Marc,

Thursday July 23 2020 14:37, you wrote to All:

Any ideas on how or why and how to prevent this will be appreciated.

What's your set up to him in ROUTE.CFG?

For everyone that I send direct, I use Send Normal File. For all other netmail which I send routed, I use Route Normal File.

It sounds like there was a problem in the netmail headers, maybe?

Later,
Sean

--- GoldED/2 3.0.1
* Origin: Outpost BBS * bbs.outpostbbs.net:10123 (1:18/200)

Hello Sean.

<On 23Jul2020 19:28 Sean Dennis (1:18/200) wrote a message to Marc Lewis regarding Follow-up on: .pkt received without a pkt password? >

Thursday July 23 2020 14:37, you wrote to All:

Any ideas on how or why and how to prevent this will be appreciated.

What's your set up to him in ROUTE.CFG?

For everyone that I send direct, I use Send Normal File. For all
other netmail which I send routed, I use Route Normal File.

It sounds like there was a problem in the netmail headers, maybe?

Here's a small segment of my ROUTE.CFG:

-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
Send Hold 1:261/38
>> Send Hold NoArc 2:280/464
Send Hold 2:25/21 2:250/1
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

His line is highlighted. I am wondering, if like you mentioned, there was some anomaly with the in-transit NetMail that was sent to me to forward on... I can honestly say I have never run into this quirk before. Absolutely nothing stands out to me to have caused this problem.

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

His line is highlighted. I am wondering, if like you
mentioned, there was some anomaly with the in-transit
NetMail that was sent to me to forward on... I can
honestly say I have never run into this quirk before.
Absolutely nothing stands out to me to have caused this
problem.

I can't see anything wrong either with that line. I do the same thing with the nodes I connect directly to and then for my main Fidonet feed, I use "Route Crash" for him. For all of my hubs in Micronet, I use "Route Crash" also to make sure that netmail flows correctly throughout the network properly.

Well, "Route Crash File" since Micronet is so small that routing an occasional file doesn't hurt anything.

From what you've told me, I'd agree with your that the netmail was somehow malformed.

If you allow netmail to be routed through your system, do you have the "Tracking" keyword in Squish?

--Sean


--- Maximus/2 3.01
* Origin: Outpost BBS * bbs.outpostbbs.net:10123 (1:18/200)