Hi fsxnet people!

I'm having an issue with importing echomail from Fidonet.

I'm carrying 3 nets: Scinet, Metronet, and now I'm trying to carry Fidonet.

I've had 0 issues importing echomail from Scinet and Metronet, but for some reason the packets from Fidonet won't import.

I'll give a brief explanation of my configuration:

-Echomail Addresses section-
Address
Zone 1
Net 275
Node 99
Domain fidonet
Primary No (Scinet is primary)

-Echomail Nodes section-
Part 1:GENERAL
Active: Yes
Description: Fido
SysOp Name: (blank)
Address: 1:275/100
Domain: fidonet
Session Type: BinkP
Archive Type: ZIP
Export Type: Crash
Route Info: 1:* (Could this be the problem?)
Max PKT Size: 512
Max ARC Size: 2048
Use Filebox: No
Filebox Dir: (blank)
Crash Limiter: 0

Part 2:SECURITY
(Everything is blank - we're not using passwords)

Part 3:GROUPS
(Everything is None - I'm not using this feature)

Part 4:BINKP
BINKP Hostname: shenks.synchro.net
IP Type: IPV4
Password: (Blank - We're not using passwords)
Time Out: 30
Block Size: 16384
CRAM-MD5: Yes
Use SSL/TLS: No
Hide AKAs: No

Part 5:FTP (All blank - not using FTP, but Passive is set to yes (by default))

Part 6:DIR TOSS (All blank just like Scinet and Metronet)

-Message Base Editor Section-
Name: Fidonet Asian Links
Base Type: Echomail
Newsgroup (blank)
QWK Name: ASIAN_LINK
Echo Tag: ASIAN_LINK
File Name: asian_link
Path: /mystic/msgs
ACS Levels (should be just fine)
Net Address: 1:275/99
Export To: 1 node(s) (This is set to my Fido hub 1:275/100)

My mutil.ini has default/stock settings in all places, except I have Import Echomail and Export Echomail set to true.

I run ./fidopoll 1:275/100 and then I run ./mutil, and everything works perfectly for Scinet and Metronet, and my outgoing Fido echomail gets exported to the hub properly, but my incoming Fido echomail does not get imported to
my BBS.

I checked the mutil.log and here's what I see:

Startup using mutil.ini
Process: Importing EchoMail
Waiting for BUSY nodes
Extracting 00000001.FRO
Importing 01140418.PKT (1:275/100 to 1:275/99) <- That's Fido
Importing 01141811.PKT (1:275/100 to 1:275/99)
Importing 01142856.PKT (1:275/100 to 1:275/99)
Importing 01143310.PKT (1:275/100 to 1:275/99)
Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.03s
Process: Exporting EchoMail
Waiting for BUSY nodes
Scanning...
Results: 0 echo, 0 net, 0 skipped in 0.03s
Shutdown Normal (0)

I've tried these killbusy commands:
./fidopoll killbusy (then I did a fresh poll and ran mutil again)
./mis poll killbusy (screen turns black and freezes up until I do ctrl-z)

Other stuff I tried:
Check permissions on /msgs/echomail, /echomail/in, /echomail/out (all 755) Tried changing uppercase Echo Tag to lowercase
Tried changing Export Type from Crash to other options,
did a fresh ./fidopoll & ./mutil for each option
Tried changing Route Info to 1:* 2:* 3:* 4:* 5:*
Tried changing Route Info to 275:* (Changed back to 1:*)

I talked with a couple guys on Fidonet who suggested this:
Check the fidopoll log to make verify connection to the hub (It's good)
Try the killbusy commands, poll again, mutil again (I tried them)
They asked about packet password, I told them there's none.

They mentioned "Mystic won't toss or scan if there's busy nodes."

I ran nodespy and killed 3 users to clear them all up. They were probably port scanners.

But maybe "Waiting for BUSY nodes" means something else?

Let me know if you guys see anything else I can try. Thanks so much!

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

On 01 Jan 2021, metalhead said the following...

Let me know if you guys see anything else I can try. Thanks so much!

Looks like everything *should* be working based on what I'm seeing.

Might be worth setting loglevel=3 in the .ini file you use to import your mail to give us a little more info.

Do you have anything in mystic/echomail/bad?

If so, maybe move those files back into mystic/echomail/in after setting loglevel=3 and importing again to give us a hint in the logs.

Jay

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Do you have anything in mystic/echomail/bad?

If so, maybe move those files back into mystic/echomail/in after setting loglevel=3 and importing again to give us a hint in the logs.

I don't have the echomail/bad folder, but I changed the log level and found some interesting points: (I'm trying to find out why echomail isn't importing)

Process: Importing EchoMail
Waiting for BUSY nodes
LINKS:
Node 1 77:1/100@scinet
Node 2 25:25/0
(*** It seems like it should show Node 3 here but it don't)
Import from /home/admin/web/compufuck.xyz/public_html/mystic/echomail/in
Unknown inbound file 16d8ici7.tic
Unknown inbound file 16d8icg7.tic
Unknown inbound file 16d8ick7.tic
Unknown inbound file 16d8icn7.tic
Unknown inbound file scidiff.z94
Unknown inbound file scinet.z94
Unknown inbound file 16dlh0n7.tic
Unknown inbound file 16dlh0g7.tic
Unknown inbound file 16dlh0i7.tic
...hundreds of files in this list... then:
Extracting 00000001.FRO
unzip -oqqjC "/home/admin/web/compfuck.xyz/public_html/mystic/echomail/in/unsecure/00000001. FRO" "*.pkt" -d /home/admin/web/compufuck.xyz/public_html/mystic/temputil
Importing 01192625.PKT (1:275/100 to 1:275/99)
Skip unsecure echomail in FIDO-REQ
Skip unsecure echomail in ALLFIX_FILE
Skip unsecure echomail in MEMORIES
Skip unsecure echomail in FILEFIND
Importing 01193742.PKT (1:275/100 to 1:275/99)
Skip unsecure echomail in RBERRYPI
Skip unsecure echomail in FILEFIND
Importing 01193742.PKT (1:275/100 to 1:275/99)
Skip unsecure echomail in RBERRYPI
Skip unsecure echomail in FIDO-REQ
Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.03s
Process: Exporting EchoMail
Waiting for BUSY nodes
Scanning..
LINKS:
Node 1 77:1/100@scinet
Node 2 25:25/0@metronet

It says "Importing 01193742.PKT (1:275/100 to 1:275/99) and that looks correct. But there are 0 new messages in Fidonet on my BBS.

I set "Create Message Bases" to "true" in mutil and ran it again, and it added the "CROSSFIRE" echo. However, there is no echomail being imported to CROSSFIRE either.

The only other thing I can think of, to try, is to re-install Mystic and start fresh to see if that fixes it. But before I go to that extreme, let me know what you think about those logs?

Thanks!

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

On 01 Jan 2021 at 05:27p, metalhead pondered and said...

Importing 01192625.PKT (1:275/100 to 1:275/99)
Skip unsecure echomail in FIDO-REQ

There's your issue.

Your packets are landing in your unsecure echomail in folder when they arrive at Mystic

"/home/admin/web/compfuck.xyz/public_html/mystic/echomail/in/unsecure/0000

Mystic will toss in packets from systems it knows, so those files it's
tossing should be in

/home/admin/web/compfuck.xyz/public_html/mystic/echomail/in

Best to fix things by ensuring the packets land in the correct inbound folder from your mailer.. if they are landing there as a result of a BinkP
transaction then there's an issue in the session between both systems running BinkP in that passwords are not matching up so Mystic accepts the packets but dumps them in the unsecure folder as it treats the incoming system as
'unknown'

There's also this work around which you could enable in your ini file, I generally don't do it for unknown systems regarding echomail

; Toss packets from unsecure directory in addition to inbound?

unsecure_dir = true


Note: Mystic will alway toss netmail from systems known and unknown.

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

On 02 Jan 2021, Avon said the following...

Best to fix things by ensuring the packets land in the correct inbound folderfrom your mailer.. if they are landing there as a result of a BinkP transaction then there's an issue in the session between both systems runningBinkP in that passwords are not matching up so Mystic accepts the packets butdumps them in the unsecure folder as it treats the incoming system as'unknown'

I believe he mentioned in a previous message that he's not using a Bink password with his uplink. Would adding one fix this?

Jay

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

On 01 Jan 2021 at 09:52p, Warpslide pondered and said...

I believe he mentioned in a previous message that he's not using a Bink password with his uplink. Would adding one fix this?

It could well do, without a password the systems would likely treat other as unsecured...

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

Your packets are landing in your unsecure echomail in folder when they arrive at Mystic

"/home/admin/web/compfuck.xyz/public_html/mystic/echomail/in/unsecure

Thanks for pointing that out. I should have picked up on that, I apologize.

folder from your mailer.. if they are landing there as a result of a
BinkP transaction then there's an issue in the session between both systems running BinkP in that passwords are not matching up so Mystic accepts the packets but dumps them in the unsecure folder as it treats

My hub is a password-less system. Is that a problem for Mystic? That hub
serves mostly Synch boards. I left the password field blank for BinkP.

; Toss packets from unsecure directory in addition to inbound?

unsecure_dir = true

Thanks for this info too. I tried it, but the files in the unsecure folder still didn't get imported. I will mess around with mutil a little more and see if I've neglected anything else.

Thanks very much!

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)