In my laptop with 128GB SSD C: drive,
c:\ProgramData\Avast Software\Avast\Spamconf\log.txt has over 15.5GByte.
I tried to delete it and it wouldn’t let me do so as apparently some other process had it open.
Is there any way to clean this file up to reduce space?
I’m running Windows 7 SP1,
Avast Internet Security,
Program version:11.2.2261
Virus definition version: 160418-0
Numberof definitions: 3861678
I tried to disable Mail shield permanently, that’s ok, but still couldn’t do anything to the log file.
So I copied it to another drive and inspected the contents - mostly logs saying which version of spamconf it’s at etc.
in the end I booted up Windows in safe mode with command prompt and deleted the thing.
After reboot everything was fine and I saw the log.txt file come back to 200kb at first boot and continues to grow again, without me doing a thing (up to 233 kb in 5 minutes).
Apparently it is still running.
Somewhere when I inspected the content of this log file, it said “verbose = on”.
So I assume the log mode has been set to verbose. Any idea on changing to log mode to errors only? or something like that?
I’m not entirely sure if this spamconf log is directly related to the Mail Shield, but the anti-spam feature and again I don’t know if this is linked to MS Outlook or not.
For sure I don’t believe any log should be set to Verbose by default as it would be collecting masses of data as you found.
I would love to be able to tell you where to set that verbose back to off, but I don’t know what function it is linked to, anti-spam or mail shield or the avast outlook plugin/add-on. But there doesn’t appear to be a verbose mode for the Mail Shield in the settings Report File and its log file is EmailShield.txt so it doesn’t look it is that.
wow, that is truly enormous. Thanks for the catch, we are now tracking this issue under number AV-9911 in our bug tracking system. If you kill our self-defense module, you should be able to delete it.
Hi Kai33,
just disable self-defense module, delete huge log.txt file and delete spamcatcher.conf also.
I will track down how you got this conf file in release build because it should be presented only in our internal builds.