I am using amavisd-new 2.0 to call spamassassin and when I start amavisd in debug-sa mode, all helper-apps test fine, including pyzor: ========== debug: Pyzor is available: /usr/bin/pyzor debug: entering helper-app run mode debug: setuid: helper proc 20615: ruid=3000 euid=3000 debug: Pyzor: got response: 66.250.40.33:24441 (200, 'OK') 0 0 debug: leaving helper-app run mode ==========
And when piping a test message into SA, all is fine, as well: spamassassin -dtD < test.msg ========== debug: Pyzor is available: /usr/bin/pyzor debug: entering helper-app run mode debug: setuid: helper proc 2513: ruid=0 euid=0 debug: Pyzor: got response: 66.250.40.33:24441 (200, 'OK') 47 0 debug: leaving helper-app run mode ========== However, once amavisd-new has fully started and mail is received, pyzor times out on every message: ========== debug: Pyzor is available: /usr/bin/pyzor debug: entering helper-app run mode debug: setuid: helper proc 2602: ruid=3000 euid=3000 debug: leaving helper-app run mode debug: Pyzor -> check timed out after 10 secs. ========== Pyzor works fine with SA 2.61, and all other helper-apps (Razor & DCC) work fine with 2.61 and 3.0, and I can still ping the pyzor server - "pyzor ping" comes back with: ========== 66.250.40.33:24441 (200, 'OK') ========== I am cross-posting this to both the SA and Amavis lists since I am not sure where the issues is. Any feedback or suggestions are most welcome. Regards, Bill
