> > It would be cool to integrate mailgraph (or something like it) into
> > qpsmtpd.
> > http://www.onlamp.com/pub/a/onlamp/2004/08/12/mailgraph.html
>
> Interesting! My boss just last week suggested we need to do some
> internal promoting and maintain some uptime graphs of the various
> systems. This seems like a good addition to that goal. I'll try and
> take a look at it to see how easy it would be modify to understand
> qpsmtpd's log files...
I don't really like the idea of parsing qpsmtpd's log files, because
in high debug modes (like we run) there's a ton of "garbage" in
there.
Maybe we need some sort of "log_entry" or "statistics" plugin hook or
something to allow for dynamic logging and statistics gathering.
It gets weirder when you do odder things like we're doing in our
installation. We don't reject certain things (in order to not create
more noise) and just silently absorb them -- but don't pass them on.
This is something we'd want to record, but the log rules would have to
be custom.
Here's an expansion on this.
- We create a transaction_end hook, that _always_ gets run at the
end of a transaction
- We teach plugins to record things.. so spamassassin could do
something like $qp->transaction->notes( 'stats_spam' => 1 ); or
something.
- The transaction_end hook would then write that out somewhere.
-R
