It looks to me like this is pretty clearly a razor bug. The log file is created by razor, not spamassassin.
As a work around, enabling syslog logging would probably avoid this.
The problem appears to be in lib/Razor2/Client/Config.pm around lines 99 - 105, but I lack the Perl to know for sure or to fix it.
It looks to me like this is pretty clearly a razor bug. The log file is created by razor, not spamassassin.
As a work around, enabling syslog logging would probably avoid this.
The problem appears to be in lib/Razor2/ Client/ Config. pm around lines 99 - 105, but I lack the Perl to know for sure or to fix it.