Hey folks,

I configured a fake fidonet node for myself to be able to send netmail to a
hub (per their application process) and did so successfully. I used 1:10/999
as my fake address.

I've since changed this to my actual node, 10:218/820, but I notice that connecting to my binkp service is still showing 1:10/999. This is hampering someone's ability to netmail me successfully.

Anyone have any idea why this might be?

Thanks

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: monterey bbs (21:1/168)

I've since changed this to my actual node, 10:218/820, but I notice that connecting to my binkp service is still showing 1:10/999. This is hampering someone's ability to netmail me successfully.

I fixed this by stopping the mis daemon and restarting it.

@g00r00 - it looks like all other aspects of Mystic's binkp worked as
expected, it was just reporting the aka incorrectly during initial parts of connections on the binkp port.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: monterey bbs (21:1/168)

I've since changed this to my actual node, 10:218/820, but I notice that connecting to my binkp service is still showing 1:10/999. This is hampering someone's ability to netmail me successfully.

I'm assuming your node number is 1:218/820 as 10: is not a fidonet zone.

Is it just in your binkp header that it is coming up with 1:10/999?

|15frank |08// |15netsurge
|07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)

I'm assuming your node number is 1:218/820 as 10: is not a fidonet zone.

Is it just in your binkp header that it is coming up with 1:10/999?

Correct on your assumption. Yeah, the binkp header was still saying 1:10/999 after everything was changed appropriately. I noticed that bouncing 'mis'
fixed this.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: monterey bbs (21:1/168)

Correct on your assumption. Yeah, the binkp header was still saying 1:10/999 after everything was changed appropriately. I noticed that bouncing 'mis' fixed this.

That was going to be my next suggestion. Have you tried turning it off and on again, lol.

|15frank |08// |15netsurge
|07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)

Correct on your assumption. Yeah, the binkp header was still saying 1:10/999 after everything was changed appropriately. I noticed that bouncing 'mis' fixed this.

Yep you always have to bounce the server when changing the base configuration because the server keeps that in memory.

I could have it periodically check to see if its changed and refresh, but
what happens then is someone changes something like a path in the middle of
MIS running that completely screws up everything.

Forcing people to shutdown and restart it allows MIS to put itself through
its own checks and balances before starting up.

--- Mystic BBS v1.12 A46 2020/03/05 (Windows/64)
* Origin: Sector 7 (21:1/108)

Forcing people to shutdown and restart it allows MIS to put itself
through its own checks and balances before starting up.

All good. I should have figured as much :)

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: monterey bbs (21:1/168)