> >> No. majordomo, for one, doesn't retain any header information at all.
>
> > Next question... Who would be in a position to remedy this obviously
> > substantial and serious shortcoming?
>
> majordomo-workers@greatcircle.com, but you should be aware that the
> current 1.9.x versions are basically under a code freeze while 2.0 is
> being worked on. Only bug fixes are going in. The new 2.0 version will
> probably include this too (it's including most everything), but it's still
> a good ways from being released.
Detailed discussion of this should be on the majordomo-workers or
majordomo-users list, but you don't need a code change
to effect this. All you have to do is add the address
"|/usr/local/mail/majordomo/wrapper archive2.pl -f
/usr/local/mail/logs/majordomo.incoming -m -a"
(modify pathnames to suit, of course) to the majordomo
alias in your aliases file and, voila, header logs. Add the logs
to your daily or weekly compressing/roll-over list, and there you
are. That's what we do at greatcircle.com.
Now, if you wanted amore sophisticated interface to the log, or
have Majordomo remember "state" with respect to certain addresses or
lists, that's a programming project, of course. But simply logging
all incoming list requests goes a long way toward discovering and
tracking down abuse. And the files compress very nicely.
--
Michael C. Berch
mcb@postmodern.com / mcb@greatcircle.com
Follow-Ups:
References:
|
|
