See my logterse plugin. It implements exactly what you want, and also
includes a summarisation tool that works with multilog
It's in the contrib section, or you can get it here:
http://www.ncc.com.au/qpsmtpd/logterse/
Enjoy!
On 31/10/2007, at 02:25, David Summers wrote:
QPSMTPD is fantastic! Thanks!
I just got it working this last weekend on CentOS 4 and 5 on home
server, parent's home business server, and my server here at work and
am working on getting it working on Solaris 9 for a community service
organization that is being hit hard by SPAM on qmail.
I also implemented my first plugin to verify that From: lines aren't
forged as those were the only SPAM messages that were making it
through TMDA.
Now for the questions:
I like the different logging levels in QPSMTPD but the INFO level
seems to provide a bit too much and the NOTICE level doesn't seem to
provide enough.
I'm looking for a way to basically get a thorough summarization of
each email, where it came from, the recipents, and the disposition of
the email (what happened to it) without a lot of the other (more
debug?) type messages like:
"cleaning up after 21871"
"250-example.com ESMTP qpsmtpd 0.40 ready; send us your mail, but not
your spam."
"250-PIPELINING"
"250-8BITMIME"
"dispatching EHLO somewhere.com"
and (other) things like that.
I know I can hack the current plugins to do more of that but I was
wondering if there was any development work to both reduce the amount
of
logging and/or make it more concise?
It would always be nice to know when exceptional things happened, of
course.
Also, it would be nice to know which plugin generated the message in
the log. For instance, in my new plugin, each log message started
with the name of the plugin and then gave the message so I could tell
it was coming from that plugin.
Would things like that be accepted as patches/changes into the project
if I could generalize that and discuss with the developers what needed
to be done/changed?
I saw the /etc/qpsmtpd/log file but don't know really what it is for?
I haven't (yet) found any plugin or core file that uses it.
Is it just to document the different log levels?
Other than these small nitpicks I'm REALLY IMPRESSED!
I'm going to be working on some changes to the RPM SPEC files to work
on
both RHEL/CentOS and Solaris and try to improve the dependencies but
it was fairly easy to figure out what perl packages were needed
because it woouldn't start correctly without all the needed perl
modules.
Thank! I'm looking forward to trying to contribute to this project in
the future and hopefully help improve the documentation as well.
QMAIL/QPSMTD/TMDA/(CourierIMAP|BincIMAP) combination provides a
dynamite and customizable mail server and SPAM prevention package.
- David Summers
