> I don't understand why this is especially useful (and it indeed seems to be
> a duplication of existing log information).
Yes, all the data is logged already, but that information is unusable.
First this data is logged with a very high loglevel, so you need to setup
your own loglevel way up to get this information logged. But this also
causes the logfile to be filled with a lots of other debug information.
Second the available data is unreliable. E.g. the recipient address supplied
by the client is logged even if a plugin denies it.
Third all the data for a single mail is spit over the logfile, probably
mixed with other log data. If you are searching for a specific mail this is
annoying.
My 'multilog' plugin logs all the relevant information at a single point
(data_post, should be the last in chain) and prints them out in a very human
readable format. In my setup i log qmail and qpsmtpd to the same logfile,
and using multilog i have the data about the incoming mail (especially where
it came from, ip, host, relayuser? and hopefully in future the username) and
what qmail did with it at a glance.
> Patches welcome. You'd want to store this in the transaction notes. The
> Auth.pm file does log authentication success if your loglevel is high
> enough, but it doesn't note the username (seems like a moderately useful
> feature).
The feature will prove to be very helpful, if you want to track down abuse
by your users, e.g. sending uce with forged headers etc.
-kju
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
