From: Matthyw T. <MT...@fl...> - 2003-11-19 21:12:46
|
My 2c: Matthyw Thomas BSc.Eng Project Engineer BMT Fleet Technology Limited 311 Legget Drive Kanata, Ontario, Canada K2K 1Z8 Tel: +1 613 592-2830 ext. 341 Fax: +1 613 592-4950 mt...@fl... >>> jh...@cp... 11/19/03 01:17PM >>> >>1. ASSP-Statistics accessible by anonymous >Hmm... That should be doable, but I'm sure not everyone would want it. = I'll >have to think about that. I have a little script that parses out the statistics and emails them to = whoever is interested. It's pretty easy, and seems to do the job. Any = takers? >>it would be nice if the active maillog-name stays the same >I understand this. I'll look at doing it that way. They'd be named by the >end of the file, not the start, but that's not a hard change. Why not have a subdirectory in the assp folder called "logs" - when it's = time to cut off a logfile, rename it to reflect the date of the last = entry, move it to the subdirectory, and restart a fresh maillog.txt. =20 >> b) What if the email report-process would scan the whitelist and if the >> not-detected mail has addresses on the whitelist it would then scan all >> available maillogs (or perhaps only the logs from the last xxx days) = for >>an >> entry like "whitelist addition: %whitelisted-address%" and then report = the >> line to an administrator, so that he can see, what user has put them on >>the >> whitelist and got probably somekind of responder oder forward in place. > >ASSP is single threaded, so doing anything computationally expensive like >this is not going to happen. One could write a separate script and run it = on >a timer to do that sort of thing. If you write it, I'll include it with = the >ASSP distribution. :-) I have something like this written.. I'll pass it along soon. |