John Peacock wrote:
John Peacock wrote:
So, please check out the current CVS and test it and let us know what you see.
Second call! I went back and checked for other recent patches which hadn't been applied (and fixed the auth_vpopmail_sql code that I had just patched ;). I'm putting HEAD into production today myself, so I'm happy to start pressuring Ask to release 0.29 and move to Subversion. ;)
That's the stick, here's the carrot:
I want to rewrite the logging subsystem to make it pluggable (shouldn't be too hard), so that I can write a new log plugin which will support multilevel logging. I only want to see a single log line (FROM: and TO: and remote IP should be enough) for messages that succeed. On the other hand, if a message fails, I want to see why it failed in full detail, somewhat similar to what Michael Holzt's denylog plugin does:
http://qpsmtpd.kju.de/qpsmtpd/created_by_me/denylog/denylog.README
John
I go to my non-gui(no X) box, type "m"(for menu), enter, scroll down(i.e. descend to the level of unperlish perversity) to the lusted for bashism, which is called "read_qp_plugins_deny", enter, and it runs this base, crude, utterly degenerate, jugular and crotch sucker-punching, shin-kicking, vile, ignorant, boxho bashism--
read_qp_plugins_deny() {
sed -n -e '/ Plugin /s/^[^P]*Plugin //p' /var/log/qpsmtpd/current |\
sed -e 's/^extra:://1' -e 's/^virus:://1' | tee /var/www/xqme.com/deny.log | less
}
Perl might be able to do that. Of course for spamassassin there's a need to grep on something different than " Plugin ", so maybe that's when I get beyond prototyping and use perl.
-Bob
