Right now my echomail/in has a lot of files stuck in it. My normal mailin
won't handle it and shows the error:
Importing EchoMail Unsecured path does not exist FATAL
What's the best thing to do?

bcw@lenotv2:/mystic$ ls echomail/in

00000002.1.mo0 00000002.1.we1 00000002.moe 00000002.tu8 00000002.we2 00000002.1.mo1 00000002.1.we2 00000002.mof 00000002.tu9 00000002.we3 00000002.1.mo2 00000002.mo0 00000002.mog 00000002.tua 00000002.we4 00000002.1.mo3 00000002.mo1 00000002.moh 00000002.tub 00000002.we5 00000002.1.mo4 00000002.mo2 00000002.moi 00000002.tuc 00000002.we6 00000002.1.mo5 00000002.mo3 00000002.moj 00000002.tud 00000002.we7 00000002.1.mo6 00000002.mo4 00000002.mok 00000002.tue 00000002.we8 00000002.1.mo7 00000002.mo5 00000002.mol 00000002.tuf 00000002.we9 00000002.1.mo8 00000002.mo6 00000002.tu0 00000002.tug 00000002.wea 00000002.1.mo9 00000002.mo7 00000002.tu1 00000002.tuh 00000002.web 00000002.1.tu0 00000002.mo8 00000002.tu2 00000002.tui 00000004.1.mo0 00000002.1.tu1 00000002.mo9 00000002.tu3 00000002.tuj 00000004.mo0 00000002.1.tu2 00000002.moa 00000002.tu4 00000002.tuk NETAPPLY10B5.1.ZIP 00000002.1.tu3 00000002.mob 00000002.tu5 00000002.tul
00000002.1.tu4 00000002.moc 00000002.tu6 00000002.we0
00000002.1.we0 00000002.mod 00000002.tu7 00000002.we1

I guess it's been going on since Monday from the above stuff. It's not my
main system, it's a .2 (AlphaTest). So I guess I can delete it all and rescan for the last 3 days.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 10/18/17, bcw142 pondered and said...

Importing EchoMail Unsecured path does not exist FATAL What's the best thing to do?

Do you have an unsecured path created?

Check your configuration > system paths :)

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

On 10/19/17, Avon said the following...

On 10/18/17, bcw142 pondered and said...

Importing EchoMail Unsecured path does not exist FATAL What's the best thing to do?

Do you have an unsecured path created?

Check your configuration > system paths :)

Path was there, something seems to have deleted the unsecure directory. Recreated it and did ./mutil mailin.ini and it all went to the right place except that one retronet zip that got in their somehow.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 10/19/17, bcw142 pondered and said...

Path was there, something seems to have deleted the unsecure directory. Recreated it and did ./mutil mailin.ini and it all went to the right
place except that one retronet zip that got in their somehow.

Ah good stuff, glad you could sort it easily..

Best, Paul

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