Re: [qmailtoaster] Re: can't open/parse clamd.conf

2009-10-26 Thread Jake Vickers
John wrote: Ok, dumb. I got the above errors because I was in the directory and the script removed it. So I cd'd into a safe directory and tried again. Upgrade of a few packages: qmail-toaster, clamav, and squirrelmail (since that's not working, either). Upgrades/rebuilds went smoothly.

Re: [qmailtoaster] Re: can't open/parse clamd.conf

2009-10-26 Thread John
John wrote: Ok, dumb. I got the above errors because I was in the directory and the script removed it. So I cd'd into a safe directory and tried again. Upgrade of a few packages: qmail-toaster, clamav, and squirrelmail (since that's not working, either). Upgrades/rebuilds went

Re: [qmailtoaster] Re: can't open/parse clamd.conf

2009-10-26 Thread Andreas Galatis
Hi John, m...@wir:~ ls -ld /etc/ drwxr-xr-x 85 root root 8192 2009-10-23 08:06 /etc/ Am Monday 26 October 2009 20:33:45 schrieb John: John wrote: Ok, dumb. I got the above errors because I was in the directory and the script removed it. So I cd'd into a safe directory and tried

Re: [qmailtoaster] Re: can't open/parse clamd.conf

2009-10-26 Thread John
Thanks. I just looked at another system and it has same as you for /etc permissions. So I update and email works again! I just wonder what other permissions got whacked on this server... It's not entirely over, unfortunately. squirrelmail interface is there again (no more blank page), but

[qmailtoaster] Re: can't open/parse clamd.conf

2009-10-26 Thread Eric Shubert
This sounds to me like your server may be p0wned. IOW, your toaster might have been cracked/compromised. John wrote: Thanks. I just looked at another system and it has same as you for /etc permissions. So I update and email works again! I just wonder what other permissions got whacked on this

Re: [qmailtoaster] Re: can't open/parse clamd.conf

2009-10-26 Thread John
Seems everything is resolved at this point, and sqirrelmail works fine. Since the logs complained about the compatibility plugin, I followed instructions I found and removed the plugin via conf.pl, renamed the directory, downloaded a current version, decompressed it, untarred it, moved it to