On 11/20/2015 10:17 PM, John Hardin wrote:
On Fri, 20 Nov 2015, Kevin A. McGrail wrote:
What user is clamd running as because why would it have access to
/home/dan?
Overall you appear to have a basic clamd functionality issue.
If it *is* a problem with clamd functionality, I'd suggest there's
still a bug in SA. It should not be emitting a
"HASH(mumble)->whatever" string in the error header; that looks to me
like the code that tries to capture the error message from clamd is
slightly b0rked (e.g. it captures an indirect method pointer converted
to a human-readable string, rather than the data returned by calling
that method properly).
Sorry John but I disagree. The project has no responsibility for a 3rd
party plugin -- from the 3.3.0 announcement file:
- due to changes in some internal data structures (like Bug 6185, 6254),
some third-party plugins may need to be updated. One such example is
the ClamAVPlugin plugin - please find a fresh version, which can be used
with both SpamAssassin versions 3.2.5 and 3.3.0, on its wiki page at
http://wiki.apache.org/spamassassin/ClamAVPlugin
So yes, X-Spam-Virus: Error (File::Scan::ClamAV=HASH(0x3a092c8)->errstr())
should be more human readable.
The fix appears to be some logic here:
if (!$code) {
my $errstr = $clamav->errstr();
$header = "Error ($errstr)";
But I could also argue it's a bug in File::Scan::ClamAV because
http://search.cpan.org/~cfaber/File-Scan-ClamAV-1.06/lib/File/Scan/ClamAV.pm#errstr%28%29
says:
errstr()
Return the last error message.
It references nothing about returning a hash, etc.
regards,
KAM
