I don't think you're getting out. Try deleting your .XLR files in the msgs directory (those are your export last read pointers). Not sure what else to try but I will test the QWKnet bases to see if I can get them to generate
that error message.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 06 Mar 2019 &4, g00r00 said the following...

I don't think you're getting out. Try deleting your .XLR files in the msgs directory (those are your export last read pointers). Not sure
what else to try but I will test the QWKnet bases to see if I can get
them to generate that error message.

Well, I know I *am* getting out, because I've had responses to my test posts.

But having said that, I did delete the .XLR files in my fsx msg directory. I separate all the msg files into folder by network.

I upgraded to the a43 from yesterday's prealpha, and I'm seeing a new
addition to the mail scan log.

ERROR: Unable to find echonode 0 while bundling (._file_id.pkt)

The ._file_id.pkt part is new. Dont know if that's just additional logging,
or if its relevant.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

On 07 Mar 2019 at 07:10a, Gryphon pondered and said...

@TID: Mystic BBS 1.12 A43
@MSGID: 21:1/120 cb46cdd4
@REPLY: 21:1/108 3e77772d
@TZUTC: -0800
@PATH: 1/120 100

Well, I know I *am* getting out, because I've had responses to my test posts.

Confirmed this one worked fine and was tossed via 1/100 without issue.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Well, I know I *am* getting out, because I've had responses to my test posts.

Ahh okay, I see stuff in GEN but not in MYS

I upgraded to the a43 from yesterday's prealpha, and I'm seeing a new addition to the mail scan log.

ERROR: Unable to find echonode 0 while bundling (._file_id.pkt)

I think I added in a piece of logging there but I've since added even more,
so I don't even know what I was logging there lol Figures.

It almost seems to me like you have a file_id.diz stuck in your temputil directory or its getting placed there somehow maybe? Or Mystic thinks there
is something there for some reason? Could you check /mystic/temputil to see
if there is a .file_id.diz or something?

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

Well, I know I *am* getting out, because I've had responses to my tes posts.

Confirmed this one worked fine and was tossed via 1/100 without issue.

Yeah his MYS connection seems to be making it to me now.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 08 Mar 2019 &4, g00r00 said the following...

I upgraded to the a43 from yesterday's prealpha, and I'm seeing a new addition to the mail scan log.

ERROR: Unable to find echonode 0 while bundling (._file_id.pkt)

I think I added in a piece of logging there but I've since added even more, so I don't even know what I was logging there lol Figures.

It almost seems to me like you have a file_id.diz stuck in your temputil directory or its getting placed there somehow maybe? Or Mystic thinks there is something there for some reason? Could you check /mystic/temputil to see if there is a .file_id.diz or something?

True enough. I have a hidden file there. Of course it is ._file_id.pkt. It's been sitting there since April.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

It almost seems to me like you have a file_id.diz stuck in your temputil directory or its getting placed there somehow maybe? Or Mystic thinks there is something there for some reason? Could you check /mystic/temputil to see if there is a .file_id.diz or something?

I just looked and I have one in mine!

bbs@duo:~/mystic/temputil$ ls
bbs@duo:~/mystic/temputil$ ls -a
. .. ._file_id.diz
bbs@duo:~/mystic/temputil$ cat ._file_id.diz
Mac OS X 2â–’â–’ATTRâ–’â–’)â–’)com.apple.quarantineq/0082;58958434;Commander\x20One\x20P RO;bbs@duo:~/mystic/temputil$ PuTTY

Immortal

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

I just looked and I have one in mine!

bbs@duo:~/mystic/temputil$ ls
bbs@duo:~/mystic/temputil$ ls -a
. .. ._file_id.diz
bbs@duo:~/mystic/temputil$ cat ._file_id.diz

Awesome! Now we just have to figure out how you each got that file there!

I think maybe what happened is there is a .ZIP file that has a ".file_id.diz" in it and so when Mystic unzipped it, it left that file there. In Linux a
file that begins with a period is hidden, so Mystic was probably unable to delete the file.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 09 Mar 2019, g00r00 said the following...

Awesome! Now we just have to figure out how you each got that file
there!

I think maybe what happened is there is a .ZIP file that has a ".file_id.diz" in it and so when Mystic unzipped it, it left that file there. In Linux a file that begins with a period is hidden, so Mystic
was probably unable to delete the file.

That sounds like what I think happened as well. Looking at that FILE_ID.DIZ
it seems to be something Mac OS X related that presumably came in over the network (Fsx and Fido are all I have set up here). I'll see if I can track down which file it came from.

Immortal

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

I think maybe what happened is there is a .ZIP file that has a ".file_id.diz" in it and so when Mystic unzipped it, it left that file there. In Linux a file that begins with a period is hidden, so Mystic
was probably unable to delete the file.

I had a dodgy file in my /mystic/temputil folder too, actually... didn't even know it was there, but in my logs I had a message similar where it said something about unknown node 267... the file I found was "._retronet.267" so
I moved it to another folder, and now no more odd log entries.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÄ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)

On 08 Mar 2019 at 02:39a, g00r00 pondered and said...

Well, I know I *am* getting out, because I've had responses to m posts.

Confirmed this one worked fine and was tossed via 1/100 without issue

Yeah his MYS connection seems to be making it to me now.

It's been a strange one, certainly nothing amiss at the HUB end as far as I
can tell.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I had a dodgy file in my /mystic/temputil folder too, actually... didn't even know it was there, but in my logs I had a message similar where it said something about unknown node 267... the file I found was "._retronet.267" so I moved it to another folder, and now no more odd
log entries.

Hmm okay. If you ever come up with any theories on how it got there let me know. Obviously something needs to be cleaned up!

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 09 Mar 2019 &4, g00r00 said the following...

I just looked and I have one in mine!

bbs@duo:~/mystic/temputil$ ls
bbs@duo:~/mystic/temputil$ ls -a
. .. ._file_id.diz
bbs@duo:~/mystic/temputil$ cat ._file_id.diz

Awesome! Now we just have to figure out how you each got that file
there!

I think maybe what happened is there is a .ZIP file that has a ".file_id.diz" in it and so when Mystic unzipped it, it left that file there. In Linux a file that begins with a period is hidden, so Mystic
was probably unable to delete the file.

But this file started with a '_', as in _file_id.diz. It makes me wonder if something else is going on. Its likley that came from the same file since the same files get tossed to all the nodes in the same network.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

I think maybe what happened is there is a .ZIP file that has a ".file_id.diz" in it and so when Mystic unzipped it, it left that fil there. In Linux a file that begins with a period is hidden, so Mysti was probably unable to delete the file.

But this file started with a '_', as in _file_id.diz. It makes me wonder if something else is going on. Its likley that came from the same file since the same files get tossed to all the nodes in the same network.

Ahh okay, well that theory is shot then :)

If you notice that it happens again let me know. Or if you have any ideas
how it might have happened. Its happened to two people so far, so there must be something that I can fix. I guess it could have been something that I've already fixed too.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Sector 7 (21:1/108)