Subj : Re: CrashMail
To   : ACCESS DENIED
From : AVON
Date : Thu Jan 31 2019 19:20:24

On 09/06/14, Access Denied pondered and said...
 
 AD> My suggestion would be to only toss netmail, and leave the rest
 AD> untouched in the unsecure directory. All a sysop would need to do if
 AD> they wished to process that tic and file and/or echomail, would be to
 AD> move them to the secure inbound directory.

I support this, it's the best way forward IMHO.

 AD> to be able to process any netmail. Just recently there were instances
 AD> where netmail ended up in someone's unsecure folder, and they didn't
 AD> find it there for more than a week until someone mentioned sending
 AD> something to that person. But like you said, if it's only that, and

This brings me to the other thing on my mind about all of this and that's
something I'd find useful. If MUTIL can be configured to produce reports that
could be auto posted to nominated message bases around these kinds of activity.

1. The following files were received today (secure files report)
2. The following files were received today (unsecure files report)
3. The following files failed to toss (.tic bad files report)

If we could link these reports to a template and then be able to customise it
and then inject the output to nominated message areas it would be cool. Then
as a sysop I could see at a glance in a s255 message area if I had an issue to
deal with... as like AD I have found .tic's in the bad dir that have failed to
toss files hatched out only by chance when looking into the dir weeks later.


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.10 A51 (Windows)
 * Origin: Agency BBS | telnet://agency.bbs.geek.nz (46:3/103)
 þ Synchronet þ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)

.