Hi. Please forgive this long critique of Installing ClamAV [1].
I actually wanted to send an email about an error path using old
versions of ClamAV, but the mailing list [2]
subscription rules said to read the faq first.
I'm aware that the FAQ has some relation to a github repository, some
proble
There are google hits indicating that people get this message:
> WARNING: Your ClamAV installation is OUTDATED!
> WARNING: Local version: {something} Recommended version: {newer}
> DON'T PANIC! Read http://www.clamav.net/support/faq
I've gotten that message with a different version.
I'm not tryin
Reindl Harald wrote:
> see attachment - a simple file-upload piping a eml-file through 2 different
> clamd-instances (different signatures and spamassassin-scorings) and finally
> also to spamd to verify rule/score changes of previously received mails
If you included an attachment, I'm pretty sur
> Firefox reports:
>> "bugs.clamav.net uses an invalid security certificate. The certificate is
>> only valid for bugzilla.clamav.net Error code: SSL_ERROR_BAD_CERT_DOMAIN"
>> You can bypass the warning if desired.
(FWIW, Chrome also allows this)
Benny Pedersen wrote:
> worst advise you ever hav
Reindl Harald wrote:
> don't matter - instead of writing a mail that should have been just fixed
I'm pretty sure the author was "filing a bug report" and not in a
position to fix it...
I'd hope that user MLs would not be particularly hostile to users
reporting things that need to be fixed...
> i
Joel Esler wrote:
> This is fantastic feedback.
> I’ve incorporated the fixes (and missing pages!) you’ve suggested below.
Thanks, it's much better now!
I'll use PRs for the rest.
I might come back this week with actual problems/bugs, now that I can
claim to have read the instructions and not fo