Okay, now that I've got myself connected to FSXNET and everything, I've got a few things I need a hand with.

First of all, how do I populate my filebases for FSXNET with files? I assume
I have to do %RESCAN or something along those lines?

Secondly, I had a foulup with my initial fidopoll of FSXNET, and it returned corrupt data. I deleted the old message bases both in mystic and their associated files under /mystic/msgs, but when I did a rescan with AreaFix, it all got dumped into my Dupes message base. How do I remedy that?

Finally (sorry for so many questions), How do I import the infopack/nodelist automatically into Mystic?

Thanks,
Nodoka

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
* Origin: NeoCincinnati BBS (21:2/106)

First of all, how do I populate my filebases for FSXNET with files? I assume I have to do %RESCAN or something along those lines?

%rescan doesn't work for file areas. Files will arrive when they are hatched. You'll see a post in FSX_GEN and the files will be close behind. You can also grab files from other fsxnet connected BBSs that have been connected for a while and import them into your filebase.

Secondly, I had a foulup with my initial fidopoll of FSXNET, and it returned corrupt data. I deleted the old message bases both in mystic and their associated files under /mystic/msgs, but when I did a rescan with AreaFix, it all got dumped into my Dupes message base. How do I remedy that?

There is a file that tracks dupes in your data directory. In your case you'll need to delete that file and do another rescan. Sorry I forget the filename.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:3/107)

Thanks for the info Al, however, I've tried numerous times collecting old messages from Hub 2 with no luck, every time I send Rescan to Areafix, the
same messages always come back corrupt, even though I've nuked their
respective bases every time before even sending out the AREAFIX request. Some come back with corrupt metadata, and one I recall just had a ANSI smiley face in the message area with no other data. Could this be on my end?

===================
Born too late to experience the 90s.
Born too early to go back in time.
Born just right to see the comeback.
NeoCinci BBS SYSOP

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

Thanks for the info Al, however, I've tried numerous times collecting old messages from Hub 2 with no luck, every time I send Rescan to Areafix, the same messages always come back corrupt, even though I've nuked their respective bases every time before even sending out the AREAFIX request. Some come back with corrupt metadata, and one I recall just had a ANSI smiley face in the message area with no other data. Could this be on my end?

There is some kind of problem there, that's for sure.

What kind of corruption? I'd have a look at the incoming .pkt files first and if they are in good condition when they arrive (I'm almost certain they are) then we need to look eslewhere.

If you send me one of your incoming .pkt files I'll have a look and see if they
are OK.

My email address is agianson(at)gmail(dot)com.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:3/107)

Thanks for the info Al, however, I've tried numerous times collecting old messages from Hub 2 with no luck, every time I send Rescan to Areafix, the same messages always come back corrupt, even though I've nuked their respective bases every time before even sending out the AREAFIX request. Some come back with corrupt metadata, and one I recall just had a ANSI smiley face in the message area with no other data. Could this be on my end?

After thinking about this for a time.. ;)

Mystic has some new encryption/SSL options. You may need to talk to your hub and ask him if he has a password set for your node. If he does you'll need to set that password on your side as well.

You should be able to netmail him from Avon's BBS or email him if you know his email address.

If that is the issue it's an easy fix.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:3/107)

Sorry for the delay in responding but thanks for the info. I'll probably get
a hold of Solaris on his email and ping him about the issue.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
* Origin: NeoCincinnati BBS (21:2/106)

Sorry for the delay in responding but thanks for the info.

No worries..

I'll probably get a hold of Solaris on his email and ping him about the issue.

I'm not certain that is the issue but I think that's quite possibly it.

Once you and he are on the same page setup wise I think things will go better and if not we can take it from there.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:3/107)