>From David B Funk
> Suggestions; completely kill and restart Amavis-new, see if it loads and
> uses the new LibClamAV library. If that doesn't fix it, find -all-
> instances of LibClamAV on your system, remove them, re-do the 0.96
> install and restart. If it still isn't working, ask your questio
> On 4/26/10, Christian Gonzalez wrote:
>
>> Hence I had to disable Amavis-new/Clamav in order to keep receiving my
>> emails but this also disabled SpamAssassin. I would like to keep at
>> least
>> SpamAssassin working, I found some howtos and guides [1][2] about it but
>> none of them worked for
On 4/26/10, Christian Gonzalez wrote:
> Hence I had to disable Amavis-new/Clamav in order to keep receiving my
> emails but this also disabled SpamAssassin. I would like to keep at least
> SpamAssassin working, I found some howtos and guides [1][2] about it but
> none of them worked for me.
Unti
On Mon, 26 Apr 2010, Christian Gonzalez wrote:
> Hi,
>
> I have a mailserver running Slackware 12.1 with Postfix, Dovecot,
> Amavis-new, SpamAssassin and Clamav. It has been working fine for more
> than a year. I builded it following a howto from workaround.org. But like
> many others, I suffered
Hi,
I have a mailserver running Slackware 12.1 with Postfix, Dovecot,
Amavis-new, SpamAssassin and Clamav. It has been working fine for more
than a year. I builded it following a howto from workaround.org. But like
many others, I suffered Clamav 0.94 EOL process since 16th this month. I
managed to