Daily Logwatch error on connection to Pyzor
Every day Logwatch is sending a message of very large size, probably because things error inside and CRON likes to report when that happens.
The most notable of these which I want to reverse engineer is the following:
UDP_OUT has 24441:
Please provide some guidance who is this Pyzor thing and how can I get to know it better? So far I found this documentation on Pyzor with how to test: //&1 | less
However can't find spamassassin binary on server anywhere? EDIT: I found the outgoing port on UDP and removed the fact that I thought it's on TCP_OUT Added link to Apache docs
"Did not receive a response from the pyzor server public.pyzor.org:24441 for 3.5 seconds!"UDP_OUT has 24441:
20,21,53,113,123,873,6277,24441Please provide some guidance who is this Pyzor thing and how can I get to know it better? So far I found this documentation on Pyzor with how to test: //&1 | less
However can't find spamassassin binary on server anywhere? EDIT: I found the outgoing port on UDP and removed the fact that I thought it's on TCP_OUT Added link to Apache docs
-
The correct command for this would be to call SpamAssassin directly as follows: echo "test" | /usr/local/cpanel/3rdparty/bin/spamassassin -D pyzor 2>&1 | less0 -
Feedback on this is the above echo test
command works. I believe Logwatch must be timing up because it's in the middle of a four hour backup. I can see no other explanation than the 3.5 second timeout is too small during a backup. I'll shift the backup a few hours away from Logwatch and report back again on the forum but this is going to have to go through change control first.0
Please sign in to leave a comment.
Comments
2 comments