http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5148
------- Additional Comments From [EMAIL PROTECTED] 2006-12-05 10:41 ------- p.s. I know I recommended that we raise the default timeout in my original description. So part of my last message might seem contradictory. I'd say it's best to have a default pyzor timeout (in the pyzor config, not SA) of say, 2 or 3. This timeout is per server. So in order not to short circuit that timeout, it's best for the pyzor_timeout in SA to be something like N * pyzor's timeout + 1 (N because the pyzor lookups are not threaded, but end to end). Unfortunately, pyzor code doesn't take this config setting on the command line. So SA has no way of knowing pyzor's timeout without reading the pyzor config. Maybe it's just best to document a recommended setup. My recommendation would be 2 or 3 seconds for the pyzor (not SA) timeout and for SA's pyzor_timeout, use 3 or 4 seconds (and document how that interacts with pyzor's config). This would accomodate one pyzor server timing out. Document that bumping up the overall SA pyzor_timeout might be useful the more pyzor servers you use. What we really want is to check 1 or 2 very reliable pyzor servers and report to as many as possible. You could do this with command line args to pyzor pointing it at different config/server files. But now we're beyond the intent of my original patch (to just get SA working) and may be overcome by events when people get together and sync pyzor servers (ala DCC perhaps). ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
