http://bugzilla.spamassassin.org/show_bug.cgi?id=3828
------- Additional Comments From [EMAIL PROTECTED] 2004-11-12 07:27 -------
tom, what version of spamasassin are you running??
i had build 51813 running, and found that razor2 was not honoring the alaram
$timeout because it was not being set correctly due to the conf being
razor2_timeout instead of razor_timeout in Plugin/Razor2.pm.
old code...
$self->{razor2_available} = 0;
$mailsaobject->{conf}->{razor2_timeout} = 10;
if razor2 had problems, it never received a SIGALM... not sure if this could
have caused the long processing times that i was seeing or not... but it could
be. i saw a system that had razor2 outbound ports blocked, and spamd would not
even start... it would hang trying to prepare_objects() because $timeout was
null. couple debug lines i added..
debug: generic: create new razor2 client
debug: generic: prepare objects timeout set to []
CTRL+C
#
once i hard-coded that timeout, it started up just fine. any ways, i just
thought i'd share that. I'm going to make sure the boxes that i normally see
spamd acting up on are correctly setting razor_timeout.
d
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
