http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5148
Summary: [patch] make SA work with multiple pyzor servers
Product: Spamassassin
Version: 3.1.6
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P5
Component: Plugins
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
I have a patch (see attachment) against the pyzor plugin in SpamAssassin 3.1.6.
It loops over the responses from 'pyzor check' and picks the max.
The server that 'pyzor discover' comes up with is heavily loaded and times out a
LOT. Milton Cyrus (on the pyzor-users mailing list) added a new pyzor server
earlier this year. Thanks to Milton's server and this patch, SA is using pyzor
effectively again to contribute to the spam score.
If you do put more than one server in ~/.pyzor/servers, you should
also either lengthen the SA timeout (pyzor_timeout) from the default
5... or shorten the default pyzor timeout of 5.
I did the latter:
% cat ~/.pyzor/servers
82.94.255.100:24441
66.250.40.33:24441
% cat ~/.pyzor/config
[client]
ServersFile = servers
Timeout = 3
So when 66.250.40.33 times out (which it does a lot), it won't cause SA to
invalidate other legit responses from other servers by making SA time out
waiting for the slow server.
This patch has some extra debug in it and was intentionally not
re-indented in order to highlight just the substantive changes.
If it goes into SA,
- fix it to conform to the right indent/coding style and be less hacky
- possibly consider a different algorithm than "pick the max count
from all responding servers"
- change the default plugin timeout to be a bit more than the default
pyzor timeout.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
