Howdy,

So my little project has been to revive my BBS from 1995 - which I've succeeded. It's happily running and I am slowing putting it back to the way
it was (doors and all)...

I wanted to get mail flowing to it, and while I've got MBSE talking to it via EMSI, I sent a netmail that is failing to transfer. :(

The receiving side (which is RLFOSSIL and Portal of Power) is complaining
about Z Receive CRC32 - CRC Error receiving the packet (which is 431 bytes in size).

Anybody successfully got MBSE talking to a DOS mailer via RLFOSSIL? I'm
stumped where to look now...

...deon

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)

Hello Deon!

Tuesday September 18 2018 10:43, you wrote to All:

Howdy,

So my little project has been to revive my BBS from 1995 - which I've succeeded. It's happily running and I am slowing putting it back to
the way it was (doors and all)...

I wanted to get mail flowing to it, and while I've got MBSE talking to
it via EMSI, I sent a netmail that is failing to transfer. :(

The receiving side (which is RLFOSSIL and Portal of Power) is
complaining about Z Receive CRC32 - CRC Error receiving the packet
(which is 431 bytes in size).

Anybody successfully got MBSE talking to a DOS mailer via RLFOSSIL?
I'm stumped where to look now...

I have not found any mailer that does not work when mbse calls it providing it has been set up correctly.

Even to OS/2 running Max via a fossil - mind you that was over 15 years ago.

Fossils must be set up and use a buffered 1650 or similar otherwise they can loss data.

Some areas to look at - Check the log files in debug (you will need to set up mbse it maximise reporting) and error.

Don't forget to reduce debug reporting ASAP after testing as the log files can get large. Make sure you have set up logrotate for mbse log files as specified in the mbse manual.



Vince

--- Mageia Linux v6/Mbse v1.0.7.8/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

On 09/18/18, Vince Coen said the following...

Some areas to look at - Check the log files in debug (you will need to
set up mbse it maximise reporting) and error.

Thanks Vince,

This had me stumped for a while - I had full verbose logging on and I was trying to read the source to see what it was trying to do.

I did get it working, I changed it from fido:// to telnet:// and it worked a treat. I was suspecting that MBSE was not calculating the checksum - possibly because fido:// over TCP is by definition reliable? Anyway, using EMSI over telnet was the thing.

MBSE didnt like the packets it got back:
? 19-Sep-2018 19:53:38 mbfido[45] Could not read header (46F05668.PKT)
? 19-Sep-2018 19:53:38 mbfido[45] bad packet header, aborting

But that will be the next thing to look at :)

Cheers

...deon

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)

Hello Deon!

Wednesday September 19 2018 09:57, you wrote to me:

On 09/18/18, Vince Coen said the following...

Some areas to look at - Check the log files in debug (you will
need to set up mbse it maximise reporting) and error.

Thanks Vince,

This had me stumped for a while - I had full verbose logging on and I
was trying to read the source to see what it was trying to do.

I did get it working, I changed it from fido:// to telnet:// and it
worked a treat. I was suspecting that MBSE was not calculating the
checksum - possibly because fido:// over TCP is by definition
reliable? Anyway, using EMSI over telnet was the thing.

You have lost me on this one :(
Do not understand the usage of fido - telnet etc but I do not have telnet installed any more only use ssh - Security issues with telnet as it has no security.

MBSE didnt like the packets it got back:
? 19-Sep-2018 19:53:38 mbfido[45] Could not read header (46F05668.PKT)
? 19-Sep-2018 19:53:38 mbfido[45] bad packet header, aborting

Now this I can relate to as I get bad packets from my up link almost weekly.

I just delete them.

But that will be the next thing to look at :)

Let me know the results of your examinations as it might relate.



Vince

--- Mageia Linux v6/Mbse v1.0.7.9/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Vince!

21 Sep 18 15:38, you wrote to me:

I did get it working, I changed it from fido:// to telnet:// and it
worked a treat. I was suspecting that MBSE was not calculating the
checksum - possibly because fido:// over TCP is by definition
reliable? Anyway, using EMSI over telnet was the thing.

You have lost me on this one :(
Do not understand the usage of fido - telnet etc but I do not have
telnet installed any more only use ssh - Security issues with telnet
as it has no security.

I dont have telnet installed - it is an alternative to BINKD. Binkd sessions are over 24554. fido:// ones are 60177 and the telnet:// ones are 60179. I think the later two are modem emulated IP connections(?) - IE: I needed EMSI to the old board, and it expires the "connector" to transmit some special chars to destingish between a mailer calling and human (wanting to go into the BBS)...

Now this I can relate to as I get bad packets from my up link almost weekly.

I just delete them.

Let me know the results of your examinations as it might relate.

I'm guessing, that these were "dummy packets" from my old BBS - there was a zmodem option enabled to send a dummy zmodem transfer. Those dummy packets were zero bytes in size - and they stopped once I turned that option off...

...deon


--- GoldED+/LNX 1.1.5--b20180707
* Origin: Chinwag | MBSE in Docker on Pi (3:633/509)