We checked your error description on several centos installations and where not able to reproduce it, so it must be related to your installation and not ISPConfig in general.
thanks, but as I said before I'm not the only one getting this and it's fedora core 5 64bit version doing this as well as the 32bit version, following the perfect guide on the site, still does the exact same, so I fail to see how it can be my installation as other users in here are getting it and following the perfect guide as well still does it as well ?
I tested this on Fedora Core 5 32- and 64-bit as well as on CentOS 4.3 32-bit and had no problems at all...
Thanks for that falko. I've set a new download of fedora core 5 32bit & 64bit ISO's to download again, just incase something is wrong with my distro, will post back later on how I get on.
Hi, Just thought I'd post to let everyone know the update so far With my existing Fedora Core 5 32bit & 64bit operating system I've got the now, I uninstalled ISPConfig 2.2.6 and also any/all files etc related to it. Then I installed ISPConfig 2.2.7 and it works fine - scans fine as well no problems that I could see .......so far. So I uninstalled 2.2.7 version and put 2.2.6 back on and I still get the same errors as per my previous posts, so I did get new downloads of the fedora core 5 32bit & 64bit iso's from a completely different ISO place from the previous place I downloaded before. and installed as per the perfect guides from the site to the letter and installed 2.2.6 and still got the same errors, but when I uninstalled 2.2.6 and installed 2.2.7 it worked fine straight away, so to me still looks like an issue with 2.2.6 somewhere ?
Thats all a bit strange as we did not change anything between 2.2.6 and 2.2.7 in this area. But the good news is that the problem seems to be solved in 2.2.7
still happening... clamscan error 50 still rearing it's ugly head. I'm on debian 3.1 and apache 2.0.5.1 I believe it is. Using ispconfig 2.2.9...... it's a real bummer too. The main reason I need a control panel is to setup and admin email accounts easily. Setting up multiple domains on apache2 is easy, but if I can't admin email accounts easily, all is for nought.... X-Security: The postmaster has not enabled quarantine of poisoned messages. X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcdEW2PNEudSKp6rRDipeS1WGn/ZeA== X-Virus-Status: Failed X-Virus-Report: /home/admispconfig/ispconfig/tools/clamav/bin/clamscan error 50 X-Virus-Checker-Version: clamassassin 1.2.3 with clamscan / ClamAV 0.88.7/2501/Mon Jan 29 13:34:50 2007
error still I did a complete reinstall of my vps and ispconfig, same thing happens. I'm running debian 3.1, ispconfig 2.29, postfix and courier with maildirs. Code: uname -m gives me: :~# uname -m i686 Code: ls -la /bin reports: ~# ls -la /bin total 3412 drwxr-xr-x 2 root root 4096 Feb 1 16:03 . drwxr-xr-x 20 root root 4096 Feb 1 15:59 .. -rwxr-xr-x 1 root root 2816 Sep 18 2005 arch -rwxr-xr-x 1 root root 625228 Dec 19 2004 bash -rwxr-xr-x 1 root root 16504 Jul 16 2004 cat -rwxr-xr-x 1 root root 31404 Jul 16 2004 chgrp -rwxr-xr-x 1 root root 31212 Jul 16 2004 chmod -rwxr-xr-x 1 root root 34572 Jul 16 2004 chown -rwxr-xr-x 1 root root 51212 Jul 16 2004 cp -rwxr-xr-x 1 root root 51724 Oct 2 2005 cpio lrwxrwxrwx 1 root root 21 Dec 30 18:12 csh -> /etc/alternatives/csh -rwxr-xr-x 1 root root 83960 May 11 2005 dash -rwxr-xr-x 1 root root 42764 Jul 16 2004 date -rwxr-xr-x 1 root root 28588 Jul 16 2004 dd -rwxr-xr-x 1 root root 31724 Jul 16 2004 df -rwxr-xr-x 1 root root 75948 Jul 16 2004 dir -rwxr-xr-x 1 root root 4320 Sep 18 2005 dmesg -rwxr-xr-x 1 root root 10740 Dec 18 2003 dnsdomainname -rwxr-xr-x 1 root root 13912 Jul 16 2004 echo -rwxr-xr-x 1 root root 39544 Apr 2 2003 ed -rwxr-xr-x 1 root root 33 Nov 21 2004 egrep -rwxr-xr-x 1 root root 11640 Jul 16 2004 false -rwxr-xr-x 1 root root 5568 Feb 5 2005 fgconsole -rwxr-xr-x 1 root root 33 Nov 21 2004 fgrep -rwxr-xr-x 1 root root 18944 May 25 2004 fuser -rwxr-xr-x 1 root root 75692 Nov 21 2004 grep -rwxr-xr-x 1 root root 53676 Sep 16 17:38 gunzip -rwxr-xr-x 1 root root 4870 Sep 16 17:38 gzexe -rwxr-xr-x 1 root root 53676 Sep 16 17:38 gzip -rwxr-xr-x 1 root root 10740 Dec 18 2003 hostname -rwxr-xr-x 1 root root 130232 Feb 1 2005 ip lrwxrwxrwx 1 root root 21 Dec 30 18:11 kernelversion -> ../sbin/kernelversion -rwxr-xr-x 1 root root 12044 Apr 13 2004 kill -rwxr-xr-x 1 root root 23096 Jul 16 2004 ln -rwxr-xr-x 1 root root 36856 Feb 5 2005 loadkeys -rwsr-xr-x 1 root root 35512 Aug 12 13:05 login -rwxr-xr-x 1 root root 75948 Jul 16 2004 ls -rwxr-xr-x 1 root root 20888 Jul 16 2004 mkdir -rwxr-xr-x 1 root root 19180 Jul 16 2004 mknod -rwxr-xr-x 1 root root 5576 Jul 12 2004 mktemp -rwxr-xr-x 1 root root 26520 Sep 18 2005 more -rwsr-xr-x 1 root root 68440 Sep 18 2005 mount -rwxr-xr-x 1 root root 4916 Jan 4 2005 mountpoint lrwxrwxrwx 1 root root 20 Dec 30 18:12 mt -> /etc/alternatives/mt -rwxr-xr-x 1 root root 15076 Oct 2 2005 mt-gnu -rwxr-xr-x 1 root root 55340 Jul 16 2004 mv -rwxr-xr-x 1 root root 113944 Apr 9 2005 nano -rwxr-xr-x 1 root root 98156 Apr 22 2004 netstat lrwxrwxrwx 1 root root 16 Dec 30 18:11 pidof -> ../sbin/killall5 -rwsr-xr-x 1 root root 30764 Dec 22 2003 ping -rwsr-xr-x 1 root root 26604 Dec 22 2003 ping6 -rwxr-xr-x 1 root root 65356 Apr 13 2004 ps -rwxr-xr-x 1 root root 13848 Jul 16 2004 pwd lrwxrwxrwx 1 root root 4 Dec 30 18:11 rbash -> bash -rwxr-xr-x 1 root root 13848 Jul 16 2004 readlink -rwxr-xr-x 1 root root 30712 Jul 16 2004 rm -rwxr-xr-x 1 root root 13848 Jul 16 2004 rmdir -rwxr-xr-x 1 root root 11036 Jul 12 2004 run-parts -rwxr-xr-x 1 root root 41048 Nov 30 2004 sed lrwxrwxrwx 1 root root 4 Dec 30 18:11 sh -> bash -rwxr-xr-x 1 root root 14424 Jul 16 2004 sleep -rwxr-xr-x 1 root root 36856 Jul 16 2004 stty -rwsr-xr-x 1 root root 23416 Aug 12 13:05 su -rwxr-xr-x 1 root root 12216 Jul 16 2004 sync -rwxr-xr-x 1 root root 164044 Nov 30 16:31 tar -rwxr-xr-x 1 root root 302476 May 19 2004 tcsh -rwxr-xr-x 1 root root 5620 Jul 12 2004 tempfile -rwxr-xr-x 1 root root 30360 Jul 16 2004 touch -rwxr-xr-x 1 root root 11640 Jul 16 2004 true -rwsr-xr-x 1 root root 40920 Sep 18 2005 umount -rwxr-xr-x 1 root root 13848 Jul 16 2004 uname -rwxr-xr-x 1 root root 53676 Sep 16 17:38 uncompress -rwxr-xr-x 1 root root 75948 Jul 16 2004 vdir -rwxr-xr-x 1 root root 53676 Sep 16 17:38 zcat -rwxr-xr-x 1 root root 1974 Sep 16 17:38 zcmp -rwxr-xr-x 1 root root 1974 Sep 16 17:38 zdiff -rwxr-xr-x 1 root root 3030 Sep 16 17:38 zegrep -rwxr-xr-x 1 root root 3030 Sep 16 17:38 zfgrep -rwxr-xr-x 1 root root 1525 Sep 16 17:38 zforce -rwxr-xr-x 1 root root 3030 Sep 16 17:38 zgrep -rwxr-xr-x 1 root root 103 Sep 16 17:38 zless -rwxr-xr-x 1 root root 1886 Sep 16 17:38 zmore -rwxr-xr-x 1 root root 3518 Sep 16 17:38 znew
in my case I don't have access to a dedicated server in my situation, the vps is my delving into the realm of linux and web serving, etc. Is that going to be a limitation, or will there be a workaround other than turning off scanning??
mail acc size 24 MB X-Virus-Status: No X-Virus-Checker-Version: clamassassin 1.2.3 with clamscan / ClamAV 0.88.7/2522/Sat Feb 3 23:30:44 2007 mail acc size 23 MB X-Virus-Status: Failed X-Virus-Report: /home/admispconfig/ispconfig/tools/clamav/bin/clamscan error 50 X-Virus-Checker-Version: clamassassin 1.2.3 with clamscan / ClamAV 0.88.7/2522/Sat Feb 3 23:30:44 2007 for me , I need to use mail account atlease 24MB that'll solve this problem. I use ubuntu 6.10 32/64bit
that did it! Thanks a bunch, that did indeed work for me as well........ nice catch.... Is that in the manual somewhere, or an 'undocumented feature'
Please post the output of: repquota -a | grep username where you replace username with the username of the mailbox owner. How large was the email that you send to this user?
root@thost:/# repquota -a | grep web1_23 web1_23 -- 32 23552 24576 8 0 0 root@thost:/# repquota -a | grep web1_24 web1_24 -- 32 24576 25600 8 0 0 root@thost:/# I dont' understand Account: web1_24 - email size24@mydomain web1_23 - email size23@mydomain I sent mail test to these account. only txt word message testing
:~# repquota -a | grep web2_user1 web2_user1 -- 176 25600 26624 37 0 0 ~# repquota -a | grep web2_user2 web2_user2 -- 36 25600 26624 10 0 0 I sent just a small couple lines of text in my test emails as well. In my case, I'm on a vps, and they already have quota installed and enabled, and when I tried to run any of the commands in the install directions regarding quota I'd get a warning about how it could destroy some data, so I pretty much skipped the quota install/configure part, but it does seem to be installed and working....
I have really no Idea why it does not work with a smaller quota amount on your server as you have plenty of free space in the accounts and you used a small test email
huh..... so I'm wondering if it's a vps issue, or just a few who set mailbox size smaller than 24 megs...... At least it's working now.... might become an issue further down the road if I decide to let clients use the control panels, and space starts to become an issue, or clients setting it below 24 megs...... I'm happy it's working now, and I am able to use it fully. I've been looking around and trying all the cp's. I just need to be able to manage my dozen or so sites reasonably easy. This is a bit more than I need, but it is all working, so I am going with it for now. ISPConfig, Ravencore and vhcs2 were what I finally narrowed down my choices to. Ravencore wouldn't start httpd on my system, so I never really got to test it, and vhcs2 worked out of the box, but it's lst update was a year ago and the devs have gone their seperate ways. A couple of em are working on updating it and rewriting it in the future, but I need something now.... and ISPconfig is going to be it. Thanks for the nice panel guys.....
I've just started getting the "clamscan error 50" error in my email headers. I was getting a "clamscan error 40" some time ago, but fixed that and emails were being scanned. I don't understand the fix above - where do I set 'mail acc size'? Also, does anyone understand why this is a problem, or is it just guesswork? I'm running ISPconfig 2.2.10 on Centos 4 Cheers, Porjo.
The clamscan error 50 means that there is a problem with the antivirus database. Please post the output of: ls -la /tmp/ | grep clam