Comment 7 for bug 1783632

Marc,
I manually changed clamd.conf. There was no indication from the installer that there was any changes to clamd.conf. The only indication I had was when the Thunderbird extension, clamrib, complained it couldn't connect to clamd. I checked clamd and indeed it was not running. I tried to restart it using the System V init script. It complained about an unknown option StatsEnabled. So I commented out StatsEnabled. and tried to start clamd. It compained about the option StatsTimeout. So I commented it out and repeated this process until clamd started.
Releasing an update warning about changes for user modified clamd.conf should be a good solution.
Thanks for the prompt work on this.