SA Bugzilla – Bug 901
Razor reporting doesn't use razor_timeout setting
Last modified: 2002-09-20 13:30:41 UTC
I was just noticing that there's a hard coded 10 second alarm when reporting to Razor, but lookups use a razor_timeout setting (which defaults to 10 seconds).
Created attachment 336 [details] look at the razor_timeout setting, not hardcoded.
I'm finding a number of changes for Razor, DCC, and Pyzor, both checking and reporting (mostly reporting). So I'm going to include them all here, please don't apply the first patch yet.
Created attachment 339 [details] Patch to solve several problems with Razor, DCC, and Pyzor
Ok, this second patch fixes a bunch of stuff: - razor_report now uses razor_timeout - Reporter.pm now uses the is_{dcc,pyzor}_available from Dns.pm, ported. Solves the same "{dccproc,pyzor}: command not found" bug when people use "spamassassin -r". - {dcc,pyzor}_report now users {dcc,pyzor}_timeout and the configured {dcc,pyzor}_path instead of `{dccproc,pyzor}` - Minor annoying bits in Dns.pm where is_{dcc,pyzor}_available had crufty bits not displaying anything - Minor indentation issue in Reporter.pm This should be applied with the patch for bug 900 (fixes Razor2 reporting response value). :)
committed