Howdy!

I'm working on getting FTN file areas working but I'm getting this
message:

2024-06-24 09:03:45 [4956] ERROR: ftn/in_sec\Z1DAILY.tic for unconfigured
area DAILYLIST

Postie setup:

[postie]
inbound = "ftn/in"
protinbound = "ftn/in_sec"
outbound = "ftn/out"
packetdir = "ftn/packets"

[[address]]
aka = "1:124/5019"

[[link]]
aka = "1:124/5014"
ouraka = "1:124/5019"
archiver = "zip"
areafixpwd = "*"
ticpwd = "TX1845"

[[route]]
aka = "1:124/5014"
pattern = "1:* 2:* 3:* 4:* 5:*"

[[filearea]]
aka = "1:124/5019"
file_path = "c:/bbs/dloads/fidonet/dailylist"
database = "fb_fido_dailylist"
tag = "DAILYLIST"
links = "1:124/5014"

---

File area setup:

[[filearea]]
name = "Fidonet Daily Nodelist"
database = "fb_fido_dailylist"
file_path = "c:/bbs/dloads/fidonet/dailylist"
upload_sec_level = 99
download_sec_level = 10
visible_sec_level = 10

I am receiving FTN from Fido and FSX. Tic password is correct. Any ideas
are appreciated.



--- Talisman v0.53-dev (Windows/x64)
* Origin: A Mysterious BBS (21:1/128)

Quoting Parcho to All <=-

2024-06-24 09:03:45 [4956] ERROR: ftn/in_sec\Z1DAILY.tic for
unconfigured area DAILYLIST

I'm still waiting to get my BBS image back from where it was hosted, but
the only thing that stood out was above in the error. ftn/in_sec\
Not sure if it's a log bug or if there is an error elsewhere in the path causing the /\ to both be there.

Shawn

... I say we nuke the site from orbit, it's the only way to be sure
--- SBBSecho 3.20-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)

2024-06-24 09:03:45 [4956] ERROR: ftn/in_sec\Z1DAILY.tic for unconfigured area DAILYLIST

I'm still waiting to get my BBS image back from where it was hosted,
but
the only thing that stood out was above in the error. ftn/in_sec\
Not sure if it's a log bug or if there is an error elsewhere in the
path causing the /\ to both be there.

That stood out to me also. It appears that Parcho might be running
Talisman on a windows box. Should the slashes in the config file still
be in the unix '/' style or should they be changed to '\'?



--- Talisman v0.53-dev (Linux/armv7l)
* Origin: possumso.fsxnet.nz * telnet:24/ssh:2122/ftelnet:80 (21:4/134)

I'm still waiting to get my BBS image back from where it was hosted, but the only thing that stood out was above in the error. ftn/in_sec\
Not sure if it's a log bug or if there is an error elsewhere in the path causing the /\ to both be there.

Hey Shawn,

I did check and the slash is there and I have removed it. Same result but I was tossing mail during the testing so that doesn't seem to cause much problem. With the windows version, we can still us / on Windows 10 and above.

It seems to ignore the tag="DAILY" bit in the config and I haven't figured out why. I also set this up on Linux and had the same result so I'm sure it's something to do with the config.

I'll circle back to this once I'm done playing around with the code to see if I can see what it really wants.

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/32)
* Origin: theotherrealmbbs.com 21:1/128 (21:1/128)

That stood out to me also. It appears that Parcho might be running Talisman on a windows box. Should the slashes in the config file still
be in the unix '/' style or should they be changed to '\'?

As I recall both work in Talisman. I believe for back slash you need to
do two of them. c:\\doors\\ or c:/doors/ would do the same thing.



Shawn

--- Via Silver Xpress V4.5/P [Reg]
* Origin: Another Millennium - Canada - another.tel (21:1/162)

Lawrence L Stockman III was heard saying....

LLSI>I'll circle back to this once I'm done playing around with the code to
LLSI>see if I can see what it really wants.

Let us know. Once I get my old talisman setup back (one of these days)
I'll be able to help more.



Shawn

--- Via Silver Xpress V4.5/P [Reg]
* Origin: Another Millennium - Canada - another.tel (21:1/162)