So I'm still pretty new to this but I've got 4 networks working, apparently, perfectly, including fsxNet. I followed Avon's videos online, and I set things up so Mystic would auto-create message and file bases, as opposed to creating them myself or doing an import of an .NA file. I like this as it allowed me to gradually check each one, match each against Infopacks which listed policies about certain echoes needing to be real names only, or Sysop-only.

Micronet's (FTN) message bases work fine. What it is not doing is creating file bases. It is one of three networks I've just added which aren't doing this. Which sounds like, whatever I did wrong, I did wrong for all three, but I cannot figure out what.

Focusing on Micronet then, the first thing I notice in my logs is this Unused Key business which I don't see for fsxNet, FidoNet (same hub as for Micronet), tqwNet, or Agoranet.

----------------- MUTIL v1.12 A47 2021/06/28 Sat, Jul 17 2021 (loglevel 3)
+ Jul 17 18:27:55 Startup using mailin.ini
- Jul 17 18:27:55 EXEC FileToss
- Jul 17 18:27:55 EXEC ImportEchoMail
- Jul 17 18:27:55 EXEC MergeNodeLists
+ Jul 17 18:27:55 Process: Toss FDN/TIC Files
+ Jul 17 18:27:55 Waiting for BUSY nodes
+ Jul 17 18:27:55 Tossing ti_00bgl.tic
- Jul 17 18:27:55 Unused Key (CREATED) Value (Created by TickIT 2.0)
- Jul 17 18:27:55 Unused Key (ORIGIN) Value (Origin 618:618/1)
- Jul 17 18:27:55 Unused Key (MAGIC) Value (Magic MINLIST)
- Jul 17 18:27:55 Unused Key (DATE) Value (Date 1626422700)
- Jul 17 18:27:55 Unused Key (LDESC) Value (Ldesc Micronet Information Network nodelist for)
- Jul 17 18:27:55 Unused Key (LDESC) Value (Ldesc 16 July 2021 (day 197). A friendly)
- Jul 17 18:27:55 Unused Key (LDESC) Value (Ldesc and active international BBS mail network.)
- Jul 17 18:27:55 Unused Key (LDESC) Value (Ldesc Info on how to join is in the nodelist.)
- Jul 17 18:27:55 Unused Key (PATH) Value (Path 618:618/1 1626422702 Fri Jul 16 08:05:02 2021 UTC)
- Jul 17 18:27:55 Unused Key (PATH) Value (Path 618:300/16 1626422916 Fri, 16 Jul 2021 08:08:35 GMT; TickIT 2.0)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:100/1)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:200/1)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:250/1)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/1)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:500/1)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:510/1)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:520/1)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:618/1)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/12)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/18)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/26)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/32)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/34)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/36)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/38)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/40)
- Jul 17 18:27:55 Unused Key (SEENBY) Value (Seenby 618:300/42)

---snip---

Now we get to the more concering port:

+ Jul 17 18:27:55 File micronet.zip Area MIN_LIST From 618:300/16
! Jul 17 18:27:55 Bad from address; Moved to /mystic/files/fsx/badfile/

Note where it is trying to move that. In the YouTube videos, in mailin.ini, this was set up in mailin.ini:

in [FileToss]:

bad_dir=/mystic/files/fsx/badfile

However, this shouldn't happen, because:

; Micronet

618:300/1_bad_dir = /mystic/files/micronet/badfile
618:300/1_dir_prefix = /mystic/files/micronet/
618:300/1_allow_replace = true
618:300/1_acs_list = s10z5
618:300/1_acs_ftp = s255z5
618:300/1_acs_download = s20z5
618:300/1_acs_upload = s255z5
618:300/1_acs_hatch = s255z5
618:300/1_acs_sysop = s255z5

Should it not skip that sort of default placeholder directive and follow the Micronet section and move it into /mystic/files/micronet/badfile?

That "z5" is correct, by the way.

The logs try to toss it a second time:

Tossing ti_00bgu.tic:

<same Unused Key complaints>

But it ends differently now:

+ Jul 17 18:27:55 File mininfo.zip Area MIN_INFO From 618:300/16
! Jul 17 18:27:55 Bad filename; Moved to /mystic/files/fsx/badfile/
! Jul 17 18:27:55 Failed moving file
+ Jul 17 18:27:55 Scanning Hatches
+ Jul 17 18:27:55 Results: 0 import, 0 toss, 0 hatch, 2 bad in 0.01s
+ Jul 17 18:27:55 Process: Importing EchoMail
+ Jul 17 18:27:55 Waiting for BUSY nodes
! Jul 17 18:27:55 Import from /mystic/echomail/in/
+ Jul 17 18:27:55 Extracting 0000ffd7.TH0
- Jul 17 18:27:55 Execute Res: 0 Cmd: unzip -oqqjC "/mystic/echomail/in/0000ffd7.TH0" "*.pkt" -d /mystic/temputil/ /dev/null 2>&1
+ Jul 17 18:27:55 Importing 60f12350.pkt (618:300/1 to 618:300/42)
+ Jul 17 18:27:55 Import #6 to MIN_TEST
! Jul 17 18:27:55 Unknown inbound file MININFO.ZIP

The contents of /mystic/files/fsx/badfile is now:

-rw-rw-r-- 1 mystic mystic 9232 Jul 15 08:42 TWITLIST.ZIP
-rw-rw-r-- 1 mystic mystic 1011 Jul 15 08:47 TWITLIST.ZIP.tic
-rw-rw-r-- 1 mystic mystic 9605 Jul 16 09:05 micronet.zip
-rw-rw-r-- 1 mystic mystic 998 Jul 16 08:08 micronet.zip.tic
-rw-rw-r-- 1 mystic mystic 1005 Jul 16 08:08 mininfo.zip.tic

There remains a copy of MININFO.ZIP in:

--- Mystic BBS v1.12 A47 2021/06/28 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

(pt2):

There is a copy of micronet.zip in /mystic/echomail/in along with related .tic files:

-rw-rw-r-- 1 mystic mystic 9232 Jul 15 08:42 TWITLIST.ZIP
-rw-rw-r-- 1 mystic mystic 1011 Jul 15 08:47 TWITLIST.ZIP.tic
-rw-rw-r-- 1 mystic mystic 9605 Jul 16 09:05 micronet.zip
-rw-rw-r-- 1 mystic mystic 998 Jul 16 08:08 micronet.zip.tic
-rw-rw-r-- 1 mystic mystic 1005 Jul 16 08:08 mininfo.zip.tic

Any ideas?

--- Mystic BBS v1.12 A47 2021/06/28 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

On 17 Jul 2021 at 07:35p, DustCouncil pondered and said...

+ Jul 17 18:27:55 File micronet.zip Area MIN_LIST From 618:300/16
! Jul 17 18:27:55 Bad from address; Moved to /mystic/files/fsx/badfile/

Note where it is trying to move that. In the YouTube videos, in mailin.ini, this was set up in mailin.ini:

in [FileToss]:

bad_dir=/mystic/files/fsx/badfile

However, this shouldn't happen, because:

; Micronet

618:300/1_bad_dir = /mystic/files/micronet/badfile
618:300/1_dir_prefix = /mystic/files/micronet/

I wonder if this is because the last few lines point to 300/1 and not 300/16?

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

618:300/1_bad_dir = /mystic/files/micronet/badfile
618:300/1_dir_prefix = /mystic/files/micronet/

I wonder if this is because the last few lines point to 300/1 and not 300/16?

That was MeaTLoTioN's observation too. I wrote the hub sysop to see what he says. He confirmed /1 was the address I should be using as the hub address previously. His BBS is /16. So I am unsure how that is configured on the hub side.

--- Mystic BBS v1.12 A47 2021/06/28 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

On 17 Jul 2021 at 11:12p, DustCouncil pondered and said...

That was MeaTLoTioN's observation too. I wrote the hub sysop to see
what he says. He confirmed /1 was the address I should be using as the hub address previously. His BBS is /16. So I am unsure how that is configured on the hub side.

yeah, it could be his BBS is acting as HUB and BBS? Running Mystic?

I think it would come down to the AKA he set in his file bases... I think
that could be the factor determining what is tossed downstream with which AKA

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

Hello DustCouncil!

On 17 Jul 2021, DustCouncil said the following...

Focusing on Micronet then, the first thing I notice in my logs is this Unused Key business which I don't see for fsxNet, FidoNet (same hub as for Micronet), tqwNet, or Agoranet.

These can be ignored; they are just added fields in the TIC files that mutil doesn't care about. :)

Now we get to the more concering port:
+ Jul 17 18:27:55 File micronet.zip Area MIN_LIST From 618:300/16

618:300/1_bad_dir = /mystic/files/micronet/badfile
618:300/1_dir_prefix = /mystic/files/micronet/

The reason for the error is that the TIC file is from 618:300/16 instead of
the expected 618:300/1. Perhaps your uplink can change the address it is using when creating those?

Best regards
Zip

--- Mystic BBS v1.12 A47 2021/07/06 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

DustCouncil wrote to Avon <=-

That was MeaTLoTioN's observation too. I wrote the hub sysop to see
what he says. He confirmed /1 was the address I should be using as the hub address previously. His BBS is /16. So I am unsure how that is configured on the hub side.

Hey, that's me! DC, I netmailed you this as well, but to get everyone on the same page:

I'm running Synchronet and TickIt. Tickit should be pulling from my
Synchronet config (which lists 300/1 before 300/16) and using "smart AKA matching".

I did some digging around and found a SourceAddress line I could add to my tickit config file. I've told Tickit explicitly to use the source address 300/1 instead of AKA matching, let's see what that does.




... Wait, this is a *scene*?
--- MultiMail/DOS v0.52
* Origin: realitycheckBBS.org -- information is power. (21:4/122)

Hey, that's me! DC, I netmailed you this as well, but to get everyone on the same page:
I'm running Synchronet and TickIt. Tickit should be pulling from my Synchronet config (which lists 300/1 before 300/16) and using "smart AKA matching".

If I haven't said it already, I really appreciate you and all of the other people who keep these networks running, and the work you put into it.

--- Mystic BBS v1.12 A47 2021/06/28 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

On 18 Jul 2021 at 10:29a, poindexter FORTRAN pondered and said...

I'm running Synchronet and TickIt. Tickit should be pulling from my Synchronet config (which lists 300/1 before 300/16) and using "smart AKA matching".

I did some digging around and found a SourceAddress line I could add to
my tickit config file. I've told Tickit explicitly to use the source address 300/1 instead of AKA matching, let's see what that does.

Best wishes for this one, I'm curious to know how you guys get on.

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

DustCouncil wrote to poindexter FORTRAN <=-

Hey, that's me! DC, I netmailed you this as well, but to get everyone on the same page:
I'm running Synchronet and TickIt. Tickit should be pulling from my Synchronet config (which lists 300/1 before 300/16) and using "smart AKA matching".

If I haven't said it already, I really appreciate you and all of the
other people who keep these networks running, and the work you put into it.

Thanks!




... Which parts can be grouped?
--- MultiMail/DOS v0.52
* Origin: realitycheckBBS.org -- information is power. (21:4/122)

Avon wrote to poindexter FORTRAN <=-

I'm running Synchronet and TickIt. Tickit should be pulling from my Synchronet config (which lists 300/1 before 300/16) and using "smart AKA matching".

I did some digging around and found a SourceAddress line I could add to
my tickit config file. I've told Tickit explicitly to use the source address 300/1 instead of AKA matching, let's see what that does.

Best wishes for this one, I'm curious to know how you guys get on.

I think I figured it out. I use 618:300/1 (my hub address) instead of 618:300/16 (my node address) for file/echomail in Micronet. The "Best AKA Match" logic apparently prioritizes regular node addresses over hub/administrative addresses, which makes sense.

I use my node address for Fidonet and tickit determines the correct AKA to use.

Let's hope adding the source address to the area definition overrides the
From address as expected.


... Where is the edge?
--- MultiMail/DOS v0.52
* Origin: realitycheckBBS.org -- information is power. (21:4/122)

On 19 Jul 2021 at 08:18a, poindexter FORTRAN pondered and said...

Let's hope adding the source address to the area definition overrides
the From address as expected.

Fingers crossed. Thanks for letting me know :)

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