[dev] Patch for imp/lib/Maillog.php (and a question)

Gary Windham windhamg at email.arizona.edu
Tue Dec 9 16:39:49 PST 2003


Quoting Michael M Slusarz <slusarz at bigworm.colorado.edu>:

> Quoting Gary Windham <windhamg at email.arizona.edu>:
>
> | That leads me to a question: are there any thoughts, advice, etc, on how
> | to
> | manage the proliferation of data in the 'horde_categories' and
> | 'horde_category_attributes' tables, caused by the history-logging
> | mechanisms
> | now present in modules such as IMP and Kronolith?  I can see these tables
> | growing to many thousands (if not millions) of rows in fairly short
> | order, given
> | a large user base (we have ~50K users).
>
> I was going to code in an (optional) preference that would garbage collect
> _all_ entries after a certain period of time (i.e. 6 months, 1 year, etc.)
> in IMP.  Thus, an admin could tell their users they would keep
> reply/forward/bounce information for a year, at which point it would no
> longer be available.
>
> Don't know if this is what you were driving at.

Yes, that's pretty much what I was driving at.

> Had the same concern as you - that this info could pile up pretty quickly
> (it's why I coded the fairly CPU/resource expensive "remove maillog entry
> when deleting" stuff into IMP in the first place).

I couldn't seem to find any sign of this code in CVS...was it there at some
point and then removed?

> Then again, the information could be fairly valuable (e.g. a year from now if
> something comes up and I want to know if I ever did reply to that person, that
> info could sure come in handy) so it definitely seems like something that will
> need to be tweaked on a per installation basis.

I agree.  While I really like the IMP history logging,  I wonder if it is more
than offset by the huge volume of data we will be accumulating, as well as the
fact that a lot of it will be stale/unreferenced (e.g., thousands of students
come and go each semester, people delete their mail from other clients, etc). 
A configuration option to enable/disable IMP history logging would be (at least
to me) very attractive.  Anyone else think so?

Thanks,
--
Gary Windham
Systems Programmer, Principal
The University of Arizona, CCIT



More information about the dev mailing list