Well that was interesting...

Early this AM I received a bad packet that apparently led to the entire echomail/in directory structure being destroyed somehow. Subsequent packets were getting rejected from the hosts since MIS couldn't find anywhere to put them. One minute it's processing echomail fine and then less than 5 minutes later the echomail/in directory is just gone.

Found in the badfile directory was a zero-size "dgelf.tic" file, a zero-size ".tic" file (yes, just the extension) and a packet from 21:4/111 containing a single echomail "Re: Missing Prompt" in FSX_MYS. After recreating the directory structure I retossed the echomail packet and it proceeded to process just fine.

----------------- MUTIL v1.12 A38 2018/01/01 Sun, Feb 18 2018 (loglevel 1)
+ Feb 18 01:51:25 Startup using import.ini
+ Feb 18 01:51:25 Process: Toss FDN/TIC Files
+ Feb 18 01:51:25 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.00s
+ Feb 18 01:51:25 Process: Importing EchoMail
+ Feb 18 01:51:25 Results: 1 echo, 0 net, 0 dupes, 0 tossed in 0.07s
+ Feb 18 01:51:25 Process: Linking Messages
+ Feb 18 01:51:26 Results: Linked 0 msgs in 1.30s
+ Feb 18 01:51:26 Shutdown Normal (0)

----------------- MUTIL v1.12 A38 2018/01/01 Sun, Feb 18 2018 (loglevel 1)
+ Feb 18 01:56:00 Startup using import.ini
+ Feb 18 01:56:00 Process: Toss FDN/TIC Files
+ Feb 18 01:56:00 File Area From 0:0/0
! Feb 18 01:56:00 Bad from address; Moved to /opt/mystic/files/badfile/
+ Feb 18 01:56:00 Results: 0 import, 0 toss, 0 hatch, 1 bad in 0.00s
+ Feb 18 01:56:00 Process: Importing EchoMail
+ Feb 18 01:56:00 Results: Inbound path does not exist in 0.00s
! Feb 18 01:56:00 Status: FATAL
+ Feb 18 01:56:00 Process: Linking Messages
+ Feb 18 01:56:02 Results: Linked 0 msgs in 1.27s
+ Feb 18 01:56:02 Shutdown Normal (0)

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)