On 23 Dec 2020 at 06:00a, paulie420 pondered and said...

Man... heres whats going on: theres NO TIC files. :/ They are just .ZIPs and .zXX files... somewhere I've lost the TICs for them. Hmmmm..

Does anyone know; is there a way to have the FTN send new TICs or - are those just dead files now?

Dead files, but you could move them to their respective file bases and tun a manual import on them. I would not bother with the nodelist or infopack files as they update weekly and usually replace the one you have in your base
anyways

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: FTN help; unknown inbound files.
By: paulie420 to All on Tue Dec 22 2020 10:41 am

Hey Paulie,

However the question that is currently pressing is... I have a bunch of files, for fsxNet and tqwNet, that are
logging as 'unknown inbound files'.

Unknown inbound files are files sent to you by somebody who didnt authenticate.

You should see messages in your mailer log confirming who sent the file and whether they authenticated.

...ëîåï

... Living with a saint is more gruelling than being one.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Dead files, but you could move them to their respective file bases and
tun amanual import on them. I would not bother with the nodelist or infopack filesas they update weekly and usually replace the one you have in your baseanyways

Ok, so I absolutely know this is a dumb question and.. in fact I bet I could answer it myself:

Can I just delete them all and %RESCAN even FTN file bases?

My answer: I think so... and I'm positive any idiot could just fire up mystic -cfg and go read the FILELIST help file in Mystic. So, thats what I'm gonna do BUT... I bet someone else wonders this too. I wanna make sure I'm carrying ALL the fsxnet files in the fsx file areas.

Lulz...



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Hey Paulie,
Unknown inbound files are files sent to you by somebody who didnt authenticate.

You should see messages in your mailer log confirming who sent the file andwhether they authenticated.
...ëîåï

I could go check, but I'm fairly sure these are all left over from the beginning of fsxNet, when I didn't carry, nor import, file areas...



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 26 Dec 2020 at 01:55p, paulie420 pondered and said...

Can I just delete them all and %RESCAN even FTN file bases?

You can delete them but the Mystic HUB you are connected to at NET 2 does not support file base rescans - sorry.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Can I just delete them all and %RESCAN even FTN file bases?

You can delete them but the Mystic HUB you are connected to at NET 2
does notsupport file base rescans - sorry.

No worries... I copied some over, and noticed that others were like... filename.1.zip filename.2.zip, etc etc... I assume that over time, while I didn't have file areas setup, they just sat there and collected. I did, however, shoot all the .zip&.tic files from /badfiles back in echomail/in and they tossed all the ones that I missed the first time round.

So, I'm fairly certain that I'm carrying all the fsxNet files now. With fsxNet, I followed yer video to a tee - and therefore left the file areas out for another day. :P It's easy enough to throw them in... else you end up with an issue like I created.

All is well again.... thanks Avon.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)