Subj : Echomail not importing
To   : All
From : metalhead
Date : Fri Jan 01 2021 12:07:22

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)

.