|
From: John H. <joh...@pl...> - 2006-06-27 16:06:25
|
On Tue, 2006-06-27 at 09:43 -0600, John E Hein wrote: > > Yes, you _can_ look in the logs, but you don't have to. > I put this in my ~/.spamassassin/user_prefs > > add_header all Pyzor _PYZOR_ > > This puts the X-Spam-Pyzor header in each mail. > > You see headers like this: > > X-Spam-Pyzor: > > X-Spam-Pyzor: Reported 0 times. > > X-Spam-Pyzor: Reported 26 times. > > The first one happens when pyzor times out (there are lots of those). > The second one happens when pyzor responds that this mail has not > been reported to pyzor. > The third one... well you get the picture. > There is a threshold (5 reports by default) where SA fires the > PYZOR_CHECK rule and awards spam points to the email. > Not sure I follow this. So how does that help a sysadmin know if pyzor is generally working or not? He/she would have to manually look through a mail message's headers to see what was happening. Not something that I would do very often. To generally monitor pyzor it would probably be easier to run in cron something like 'pyzor ping|egrep -i timeout', and let cron mail that to the sysadmin. > But responsiveness is typically spotty... > > sh -c 'i=10;while [ $i -gt 0 ]; do pyzor ping; i=$(expr $i - 1); done' > 66.250.40.33:24441 TimeoutError: > 66.250.40.33:24441 TimeoutError: > Why isn't this showing the second server? For me 'pyzor ping' tries both servers: pyzor ping 66.250.40.33:24441 TimeoutError: 82.94.255.100:24441 (200, 'OK') John. -- --------------------------------------------------------------- John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914 E-mail: Joh...@pl... Fax: +44 (0)1752 233839 |