Just discovered something strange going on at my hub. Got a new node running Synchronet 3.17 having issues getting netmail working. On investigation, I disvocered something strange going on. Here's the log from MIS2.

+ 15:31:02 BINKP 1-Addr: ::FFFF:4DBB:AE57
+ 15:31:02 BINKP 1-Host: x4dbbae57.dyn.telefonica.de
+ 15:31:04 BINKP 1-System: anybox
+ 15:31:04 BINKP 1-SysOp: DC6AP
+ 15:31:04 BINKP 1-Authenticating 432:1/115@vkradio by CRAM-MD5
+ 15:31:04 BINKP 1-Queued 0 files for 432:1/115@vkradio
+ 15:31:05 BINKP 1-Renaming file 00010064.out to 00010064.3.out <-- here
+ 15:31:05 BINKP 1-Receiving: 00010064.3.out (395 bytes)
+ 15:31:06 BINKP 1-Session complete (0 sent, 1 rcvd, 0 skip)

Notice that the received file wasn't renamed to *.pkt as normally happens. Because of this, mutil couldn't toss the file. Manually renaming it to *.pkt resulted in a successful import of the netmail contained within.

Anyone else seeing this? I am running MIS2, which hasn't missed a beat until now.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

On 11/03/16, Tony Langdon pondered and said...

+ 15:31:04 BINKP 1-SysOp: DC6AP
+ 15:31:04 BINKP 1-Authenticating 432:1/115@vkradio by CRAM-MD5
+ 15:31:04 BINKP 1-Queued 0 files for 432:1/115@vkradio
+ 15:31:05 BINKP 1-Renaming file 00010064.out to 00010064.3.out <-- here + 15:31:05 BINKP 1-Receiving: 00010064.3.out (395 bytes)
+ 15:31:06 BINKP 1-Session complete (0 sent, 1 rcvd, 0 skip)

Notice that the received file wasn't renamed to *.pkt as normally

I am also seeing out files from a fsxNet node. I wonder if it's the same system?

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Avon wrote to Tony Langdon <=-

@MSGID: <581AB0A3.1156.fsx_mys@freeway.apana.org.au>
@REPLY: <581A9E5D.1155.fsx_mys@freeway.apana.org.au>
@TZ: 030c
On 11/03/16, Tony Langdon pondered and said...

+ 15:31:04 BINKP 1-SysOp: DC6AP
+ 15:31:04 BINKP 1-Authenticating 432:1/115@vkradio by CRAM-MD5
+ 15:31:04 BINKP 1-Queued 0 files for 432:1/115@vkradio
+ 15:31:05 BINKP 1-Renaming file 00010064.out to 00010064.3.out <-- here + 15:31:05 BINKP 1-Receiving: 00010064.3.out (395 bytes)
+ 15:31:06 BINKP 1-Session complete (0 sent, 1 rcvd, 0 skip)

Notice that the received file wasn't renamed to *.pkt as normally

I am also seeing out files from a fsxNet node. I wonder if it's the
same system?

The node in question is in Germany, running Synchronet v3.17 (the development version, analogous to Mystic 1.12A versions).


... We are star-stuff. We are the universe made manifest.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 11/03/16, Vk3jed pondered and said...

The node in question is in Germany, running Synchronet v3.17 (the development version, analogous to Mystic 1.12A versions).

Are .OUT files a Synchronet thing Tony? Does the software create them as part of the tossing process etc.?

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Are .OUT files a Synchronet thing Tony? Does the software create them as part of the tossing process etc.?

.OUT files are netmail messages normally, all fidonet tossers create them if they follow FTN hirearchy

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)

Avon wrote to Vk3jed <=-

Are .OUT files a Synchronet thing Tony? Does the software create them
as part of the tossing process etc.?

.out is a BSO style uncompressed .pkt with normal flavour.

As opposed to:

.dut (Direct)
.hut (Hold)
.cut (Crash)


... Better to live with one spider than many bugs.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 11/03/16, Night Stalker pondered and said...

Are .OUT files a Synchronet thing Tony? Does the software create them part of the tossing process etc.?

.OUT files are netmail messages normally, all fidonet tossers create
them if they follow FTN hirearchy

Ah... well these are not netmail just echomail being sent back to the HUB
after it has sent it to the node... loopy stuff :)

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 11/03/16, Vk3jed pondered and said...

.out is a BSO style uncompressed .pkt with normal flavour.

Thanks :)

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Ah... well these are not netmail just echomail being sent back to the HUB after it has sent it to the node... loopy stuff :)

Ahh so someone is not routing properly and messages are getting bounced
around until they find a system that can process them lol.. viral mail :D

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)

Avon wrote to Vk3jed <=-

.out is a BSO style uncompressed .pkt with normal flavour.

Thanks :)

You're welcome. It's weird, the renaming is not working with this particular node. He is using binkd with me, which should work. It works perfecty between Mystic and my other node, which also runs binkd.


... Don't be sexist. Broads hate that.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Avon wrote to Night Stalker <=-

Ah... well these are not netmail just echomail being sent back to the
HUB after it has sent it to the node... loopy stuff :)

Different issue. The .out files I'm receiving are netmails. Just weird that the renaming to .pkt is not occurring as it should.


... The Lab called... Your brain is ready!
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)