On 09/04/16, rEApZ pondered and said...

Hey guys,
Just wondering if anyone could help me with my fidonet setup. Echo mail looks like its all coming through fine but I cannot receive any
nodelists or files or anything. I have setup all the file areas to autocreate in Mystic and looks similar to both my fsxnet and retronet setup (which both work fine and have been creating file areas). I have
set to receive all the file bases through filefix. I'm just at a bit of
a loss here why it isn't creating folders. Any help would be appreciated
I feel like i'm going around in circles!
Cheers,
Steve

OK let's see if we can suss this :)

Can you post MUTIL level 3 logging to show what is (or is not) happening when you run MUTIL?

Also, what have you set up in the filetoss stanza for the echonode sending
you files?

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | New Zealand | agency.bbs.geek.nz (21:1/101)

Can you post MUTIL level 3 logging to show what is (or is not) happening when you run MUTIL?

G'day Paul, In level 3 mutil this is the problem:

+ Sep 02 03:36:49 Process: Toss FDN/TIC Files
+ Sep 02 03:36:49 Results: 0 imported, 0 tossed, 0 bad in 0.01s
+ Sep 02 03:36:49 Process: Importing EchoMail
+ Sep 02 03:36:49 Waiting for BUSY nodes
- Sep 02 03:36:49 LINKS:
- Sep 02 03:36:49 Node 1 21:1/100@fsxnet
- Sep 02 03:36:49 Node 2 3:633/280@fidonet
- Sep 02 03:36:49 Node 3 80:774/0@retronet
! Sep 02 03:36:49 Import from /mystic/echomail/in/
! Sep 02 03:36:49 Unknown inbound file nodelist.239
! Sep 02 03:36:49 Unknown inbound file areamgr.help
+ Sep 02 03:36:49 Importing 56730a3f.pkt (3:633/280 to 3:633/412)
+ Sep 02 03:36:49 Import #158 to COOKING
+ Sep 02 03:36:49 Results: 1 echo, 0 net, 0 dupes, 0 tossed in 0.06s
+ Sep 02 03:36:49 Shutdown Normal (0)

those 2 Unknown files don't seem to be getting through I think.

Also, what have you set up in the filetoss stanza for the echonode
sending you files?

; Create FidoNet file areas when sent from fidonet HUB 3:633/280

3:633/280_bad_dir = /mystic/files/fido/badfile/
3:633/280_dir_prefix = /mystic/files/fido/
3:633/280_allow_replace = true
3:633/280_acs_list = s20z7
3:633/280_acs_ftp = s255z7
3:633/280_acs_download = s20z7
3:633/280_acs_upload = s255z7
3:633/280_acs_comment = s255z7
3:633/280_acs_sysop = s255z7

It all looks good to me not sure what the problem is.
Thanks in advance
Steve

ÄÄÄÄÄ Â¿Ú¿ Ú¿ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
²±°Û ¿à ôڿÚÙ DatanetBBS.net:23 ÛÛ²±°
ÄÄÄÄÄ Á ÁÙÙÀÅÙÀÙ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Datanet BBS (21:1/166)

On 09/04/16, rEApZ pondered and said...

! Sep 02 03:36:49 Import from /mystic/echomail/in/
! Sep 02 03:36:49 Unknown inbound file nodelist.239
! Sep 02 03:36:49 Unknown inbound file areamgr.help

This means the files are sitting there in your inbound but have no associated .TIC with each and as such Mystic does not know what to do with them. They
may well have been sent by another system as a filebox style transfer so they just end up in your inbound. But unless the system that sent them to you has hatched then with accompanying .TIC files they are never going to be touched
by MUTIL etc. as a filetoss process.

Best thing would be to manually move them out of the inbound echomail directory. Check the nodelist into the correct filebase and run /U from your BBS file menu to manually import it. Take the .help file and stick in in a
dir you use for stuff like that to refer to. :)

; Create FidoNet file areas when sent from fidonet HUB 3:633/280

3:633/280_bad_dir = /mystic/files/fido/badfile/

Yep all looks good for the way you have that set up.

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)