> What version of spamdyke are you using? Older versions didn't log > every message, especially if the connection was whitelisted. Newer > versions should log everything.
3.1.1 installed this morning in place of 3.1.0 > Also, how busy is your server? syslogd will drop messages if the > server is overloaded; I believe this is why DJB didn't use it for qmail. This server is a lot cooler since spamdyke was installed :-) Thanks a lot for spamdyke, sam, it works perfectly on 6+ servers (and counting) and stops loads of spam : 710000 smtp connections refused on about 730000 incoming connections on the biggest server (a day), not bad at all :-) > With the latest version of spamdyke, you can use the "log-target" > directive to make spamdyke avoid syslog. Its messages will appear in > the same files as your qmail logs. I'd be very interested to know if > that solves the problem. ouch. This would break my munin plugin and a couple of scripts I use to extract statistics. I'll try to modify them to handle multilog log files and tai timestamps one of these days -- Sébastien Guilbaud _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
