Subj : Re: CrashMail
To   : AVON
From : ACCESS DENIED
Date : Thu Jan 31 2019 07:20 pm

Hello Avon,

On 07 Sep 14 13:46, Avon wrote to Access Denied:

 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
 AD>> if they wished to process that tic and file and/or echomail,
 AD>> would be to move them to the secure inbound directory.

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

Maybe. There's still flaws in it I think. It may just be better to do as g00 
has already done, and leave ALL unsecure stuff to the sysop for manual 
intervention. If there's a better way of doing it, I'm all ears!

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

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

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

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

There is a LOT of statistical stuff I would like to see. But getting the main 
functionality of it all working first is a definite must.

Here, at the moment, I only use a binkd log analizer that produces the 
statistics you see in AGN_HUB. If it weren't for that, all hell probably would 
have broken loose by now with all the door game packet tossing that goes on in 
this network. When I see someone failing connections for a week or more, I say 
something to them. Otherwise I would have to analize the log myself, which I 
probably wouldn't do.

The Husky software suite has all sorts of log analizers.. 
echomail/netmail/files/link statistics, etc. I just don't use it as my main 
hub, so I can't use any of it. I've definitely tinkered with it on my 
Golded+/hpt/htick node though, and it's impressive.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
 * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (46:1/701)
 þ Synchronet þ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)

.