<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>FAQforge &#187; ISPConfig 3</title> <atom:link href="http://www.faqforge.com/tag/ispconfig3/feed/" rel="self" type="application/rss+xml" /><link>http://www.faqforge.com</link> <description>Just another WordPress weblog</description> <lastBuildDate>Fri, 03 Feb 2012 13:47:23 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Debugging of ISPConfig 3 server actions in case of a failure</title><link>http://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/</link> <comments>http://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/#comments</comments> <pubDate>Fri, 13 Jan 2012 09:03:18 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[CentOS]]></category> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Ubuntu]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1627</guid> <description><![CDATA[The follwing article describes the steps that can be taken to debug the ISPConfig 3 server scripts. Enable the debug Loglevel in ISPConfig Login to the ISPConfig intterface and set the log level to Debug under System &#62; System &#62; Server Config (see also chapter 4.9.2.2 of the ISPConfig 3 manual) for the affected server. After [...]]]></description> <content:encoded><![CDATA[<p>The follwing article describes the steps that can be taken to debug the ISPConfig 3 server scripts.</p><p><strong>Enable the debug Loglevel in ISPConfig</strong></p><p>Login to the ISPConfig intterface and set the log level to Debug under System &gt; System &gt; Server Config (see also chapter 4.9.2.2 of the ISPConfig 3 manual) for the affected server. After one or two minutes, there should be more detailed messages in ISPConfig&#8217;s system log (Monitor &gt; System State (All Servers) &gt; Show System-Log).</p><p><strong>Disable the server.sh cronjob</strong></p><p>Go to the command line of the server on which the error happens (on multiserver systems, it is often the slave and not the master) and run (as root):</p><p
class="command">crontab -e</p><p>Comment out the server.sh cron job:</p><p><span
class="system">#* * * * * /usr/local/ispconfig/server/server.sh &gt; /dev/null >> /var/log/ispconfig/cron.log</span></p><p><strong>Run the server script manually to get detailed debug output</strong></p><p>Then run the command:</p><p
class="command">/usr/local/ispconfig/server/server.sh</p><p>This will display any errors directly on the command line which should help you to fix the error. If you have fixed<br
/> the error, please don&#8217;t forget to uncomment the server.sh cron job again.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>nginx server error: 413 Request Entity Too Large</title><link>http://www.faqforge.com/linux/nginx-server-error-413-request-entity-too-large/</link> <comments>http://www.faqforge.com/linux/nginx-server-error-413-request-entity-too-large/#comments</comments> <pubDate>Mon, 21 Nov 2011 11:34:10 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Debian]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[nginx]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1316</guid> <description><![CDATA[The nginx webserver has a max. body size limit of 1 MB for requests as default. This might be too low for file uploads in scripts and you will see the following error message when you try to upload a file:  413 Request Entity Too Large The configuration variable for this option is &#8220;client_max_body_size&#8221; and [...]]]></description> <content:encoded><![CDATA[<p>The nginx webserver has a max. body size limit of 1 MB for requests as default. This might be too low for file uploads in scripts and you will see the following error message when you try to upload a file:</p><p
class="system"> 413 Request Entity Too Large</p><p>The configuration variable for this option is &#8220;<span
class="system">client_max_body_size</span>&#8221; and it can be set in the <span
class="system">http, server</span> and<span
class="system"> location</span> sections of the nginx configuration file. To set the Limit globally to 25 MB, edit the nginx.conf file and add:</p><p
class="system">client_max_body_size 20M;</p><p>in the http section.</p><p>Example for Ubuntu Linux:</p><pre class="system" dir="ltr">user www-data;
worker_processes 4;
pid /var/run/nginx.pid;

events {
        worker_connections 768;
        # multi_accept on;
}

http {
        geoip_country  /etc/nginx/geoip/GeoIP.dat; # the country IP database
        geoip_city     /etc/nginx/geoip/GeoLiteCity.dat; # the city IP database
        ##
        # Basic Settings
        ##

        sendfile on;
        tcp_nopush on;
        tcp_nodelay on;
        keepalive_timeout 65;
        types_hash_max_size 2048;</pre><pre dir="ltr">        client_max_body_size 20M;

        include /etc/nginx/mime.types;
        default_type application/octet-stream;

        ##
        # Logging Settings
        ##

        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;

        ##
        # Gzip Settings
        ##

        gzip on;
        gzip_disable "msie6";

        ##
        # Virtual Host Configs
        ##

        include /etc/nginx/conf.d/*.conf;
        include /etc/nginx/sites-enabled/*;
}</pre>]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/nginx-server-error-413-request-entity-too-large/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Enhanced e-mail SPAM protection in ISPConfig 3</title><link>http://www.faqforge.com/linux/enhanced-e-mail-spam-protection-in-ispconfig-3/</link> <comments>http://www.faqforge.com/linux/enhanced-e-mail-spam-protection-in-ispconfig-3/#comments</comments> <pubDate>Mon, 21 Nov 2011 10:22:41 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[CentOS]]></category> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[Email]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[postfix]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1312</guid> <description><![CDATA[The command below enables a stricter SPAM handling for postfix on ISPConfig 3 servers. In Detail: Reject sender hostnames with invalid syntax Reject sender hostnames that are no fully qualified domains (e.g. reject &#8220;server1&#8243; but allow server1.domain.tld) Reject sender domains that have no DNS records Check sender IP addresses against realtime blacklists. First make a [...]]]></description> <content:encoded><![CDATA[<p>The command below enables a stricter SPAM handling for postfix on ISPConfig 3 servers.</p><p>In Detail:</p><ul><li>Reject sender hostnames with invalid syntax</li><li>Reject sender hostnames that are no fully qualified domains (e.g. reject &#8220;server1&#8243; but allow server1.domain.tld)</li><li>Reject sender domains that have no DNS records</li><li>Check sender IP addresses against realtime blacklists.</li></ul><p>First make a backup of the postfix main.cf file in case that you want to reverse the changes later:</p><p
class="command">cp -pf /etc/postfix/main.cf /etc/postfix/main.cf.bak</p><p>Then execute this command to enable the additional spam protection functions (the command is one line!).</p><p
class="command">postconf -e &#8216;smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_hostname, reject_non_fqdn_hostname, reject_unknown_recipient_domain, reject_non_fqdn_recipient, reject_unauth_destination, reject_non_fqdn_sender, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_rbl_client cbl.abuseat.org,reject_rbl_client dul.dnsbl.sorbs.net,reject_rbl_client ix.dnsbl.manitu.net, check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, reject_unauth_destination&#8217;</p><p>Then restart postfix:</p><p
class="command">/etc/init.d/postfix restart</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/enhanced-e-mail-spam-protection-in-ispconfig-3/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>How to change the welcome email message text in ISPConfig 3</title><link>http://www.faqforge.com/linux/controlpanels/how-to-change-the-welcome-email-message-text-in-ispconfig-3/</link> <comments>http://www.faqforge.com/linux/controlpanels/how-to-change-the-welcome-email-message-text-in-ispconfig-3/#comments</comments> <pubDate>Thu, 10 Nov 2011 11:00:05 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Email]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Server]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1262</guid> <description><![CDATA[As of ISPConfig 3.0.4, the text of the welcome email message that is sent to new email accounts is stored in the folder /usr/local/ispconfig/server/conf/mail/. The message has this format: &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212; From: ISPConfig &#60;postmaster@localhost.localdomain&#62; Subject: Welcome to your new email account. Welcome to your new email account. Your webmaster. &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212; The first line starts with &#8220;From: [...]]]></description> <content:encoded><![CDATA[<p>As of ISPConfig 3.0.4, the text of the welcome email message that is sent to new email accounts is stored in the folder <span
class="system">/usr/local/ispconfig/server/conf/mail/</span>.</p><p>The message has this format:</p><p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br
/> From: ISPConfig &lt;postmaster@localhost.localdomain&gt;<br
/> Subject: Welcome to your new email account.</p><p>Welcome to your new email account. Your webmaster.<br
/> &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p><p>The first line starts with &#8220;From: &#8221; followed by the sender email address. The second line starts with &#8220;Subject: &#8221; followed by the email subject. The third line should be empty. All following lines are the email text.</p><p>The email text files are named &#8220;welcome_email_&lt;language&gt;.txt&#8221; where &lt;language&gt; has to be replaced with the system language like &#8220;en&#8221; for English or &#8220;de&#8221; for German language, e.g. &#8220;welcome_email_en.txt&#8221; for the english welcome email.</p><p>The customized language file should be stored in the folder<span
class="system"> /usr/local/ispconfig/server/conf-custom/mail/</span> so that it does not get overwritten by ISPConfig updates.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/how-to-change-the-welcome-email-message-text-in-ispconfig-3/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to change the language of AWStats statistics on Debian Linux (ISPConfig 3)</title><link>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-change-the-language-of-awstats-statistics-on-debian-linux-ispconfig-3/</link> <comments>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-change-the-language-of-awstats-statistics-on-debian-linux-ispconfig-3/#comments</comments> <pubDate>Mon, 24 Jan 2011 15:04:37 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Webserver]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=551</guid> <description><![CDATA[To change the language of the website statistics generated by AWStats on a Debian Linux server to e.g. german (de), edit the /etc/awstats/awstats.conf file: nano /etc/awstats/awstats.conf and change the value of the &#8220;Lang&#8221; variable. To change the languge to e.g. German, cahnge: Lang=&#8221;auto&#8221; to Lang=&#8221;de&#8221; The website statistics are generated nightly on a ISPConfig 3 [...]]]></description> <content:encoded><![CDATA[<p>To change the language of the website statistics generated by AWStats on a Debian Linux server to e.g. german (de), edit the /etc/awstats/awstats.conf file:</p><p
class="command">nano /etc/awstats/awstats.conf</p><p>and change the value of the &#8220;Lang&#8221; variable. To change the languge to e.g. German, cahnge:</p><p
class="system">Lang=&#8221;auto&#8221;</p><p>to</p><p
class="system">Lang=&#8221;de&#8221;</p><p>The website statistics are generated nightly on a ISPConfig 3 server, so it may take up to 24 hours until the statistics will show up in German language.</p><p>Thanks to <a
href="http://www.planetfox.de/" target="_blank">PlaNet Fox</a> for this FAQ.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-change-the-language-of-awstats-statistics-on-debian-linux-ispconfig-3/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Solve the warning: connect to mysql server 127.0.0.1: Too many connections</title><link>http://www.faqforge.com/linux/controlpanels/solve-the-warning-connect-to-mysql-server-127-0-0-1-too-many-connections/</link> <comments>http://www.faqforge.com/linux/controlpanels/solve-the-warning-connect-to-mysql-server-127-0-0-1-too-many-connections/#comments</comments> <pubDate>Tue, 07 Sep 2010 19:06:55 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[Email]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[MySQL]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=512</guid> <description><![CDATA[If you get the error message &#8220;connect to mysql server 127.0.0.1: Too many connections&#8221; in a log file, e.g. the mail.log file, then the max. number of mysql database connections on your server is reached. To increase the max. number of simultanious connections, edit the MySQL my.cnf file: vi /etc/mysql/my.cnf and add or change the [...]]]></description> <content:encoded><![CDATA[<p>If you get the error message &#8220;connect to mysql server 127.0.0.1: Too many connections&#8221; in a log file, e.g. the mail.log file, then the max. number of mysql database connections on your server is reached. To increase the max. number of simultanious connections, edit the MySQL my.cnf file:</p><p
class="command">vi /etc/mysql/my.cnf</p><p>and add or change the lines for mysql max_connections and max_user_connections in the [mysqld] section of the my.cnf file:</p><p><span
class="system">[mysqld]<br
/> &#8230;&#8230;<br
/> max_connections        = 500<br
/> max_user_connections        = 500<br
/> &#8230;&#8230;.</span></p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/solve-the-warning-connect-to-mysql-server-127-0-0-1-too-many-connections/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Secure /tmp and /dev/shm directories in a OpenVZ enviroment</title><link>http://www.faqforge.com/linux/controlpanels/ispconfig2/secure-tmp-and-devshm-directories-in-a-openvz-enviroment/</link> <comments>http://www.faqforge.com/linux/controlpanels/ispconfig2/secure-tmp-and-devshm-directories-in-a-openvz-enviroment/#comments</comments> <pubDate>Tue, 31 Aug 2010 09:06:27 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Virtualisation]]></category> <category><![CDATA[OpenVZ]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=504</guid> <description><![CDATA[The /tmp and /dev/shm directories of a OpenVZ virtual machine shall be mounted without suid and exec permissions. To achieve this, create a a shell script on the host server for every virtual machine which contains the commands to remount the directories. This script will be started automatically by openvz when the VM is started. [...]]]></description> <content:encoded><![CDATA[<p>The /tmp and /dev/shm directories of a OpenVZ virtual machine shall be mounted without suid and exec permissions. To achieve this, create a a shell script on the host server for every virtual machine which contains the commands to remount the directories. This script will be started automatically by openvz when the VM is started.</p><p>I will use VPSID as placeholder for the ID of the virtual machine in the commands and the script. Replace VPSID with the id of the virtual machine that you want to create the script for, e.g. replace VPSID with 101.</p><p>Create the script:</p><p
class="command">vi /etc/vz/conf/VPSID.mount</p><p>and insert the following lines:</p><p
class="system">#!/bin/bash<br
/> mount -n &#8211;bind -onosuid,noexec /vz/vps/VPSID/tmp /vz/root/VPSID/tmp<br
/> mount -n &#8211;bind -onosuid,noexec /vz/vps/VPSID/shm /vz/root/VPSID/dev/shm<br
/> exit ${?}</p><p>now make the sscript executable:</p><p
class="command">chmod 700 /etc/vz/conf/VPSID.mount</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/ispconfig2/secure-tmp-and-devshm-directories-in-a-openvz-enviroment/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Migrate physical server system to OpenVZ virtual machine</title><link>http://www.faqforge.com/linux/controlpanels/migrate-physical-server-system-to-openvz-virtual-machine/</link> <comments>http://www.faqforge.com/linux/controlpanels/migrate-physical-server-system-to-openvz-virtual-machine/#comments</comments> <pubDate>Tue, 31 Aug 2010 08:51:13 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Virtualisation]]></category> <category><![CDATA[OpenVZ]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=501</guid> <description><![CDATA[In case you plan to virtualize your server infrastructure and migrate physical servers to OpenVZ virtual machines, you may find this tutorial helpful: http://wiki.openvz.org/Physical_to_container I used this to migrate a ISPConfig Debian system to OpenVZ successfully.]]></description> <content:encoded><![CDATA[<p>In case you plan to virtualize your server infrastructure and migrate physical servers to OpenVZ virtual machines, you may find this tutorial helpful:</p><p><a
href="http://wiki.openvz.org/Physical_to_container" target="_blank">http://wiki.openvz.org/Physical_to_container</a></p><p>I used this to migrate a ISPConfig Debian system to OpenVZ successfully.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/migrate-physical-server-system-to-openvz-virtual-machine/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to disable spamfilter- and antivirus functions in ISPConfig 3</title><link>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-disable-spamfilter-and-antivirus-functions-in-ispconfig-3/</link> <comments>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-disable-spamfilter-and-antivirus-functions-in-ispconfig-3/#comments</comments> <pubDate>Wed, 14 Jul 2010 12:52:27 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[Email]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[Amavisd]]></category> <category><![CDATA[ClamAV]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=490</guid> <description><![CDATA[If you use a mailserver wil very low ram (&#60; 500 MB) and a slow CPU then it might be nescessary to disable the spam- and antivirus filter functions in ISPConfig 3 as amavisd and clamav might be too heavy for your server hardware. The steps to disable clamav and amavisd are: Edit postfix main.cf [...]]]></description> <content:encoded><![CDATA[<p>If you use a mailserver wil very low ram (&lt; 500 MB) and a slow CPU then it might be nescessary to disable the spam- and antivirus filter functions in ISPConfig 3 as amavisd and clamav might be too heavy for your server hardware. The steps to disable clamav and amavisd are:</p><p>Edit postfix main.cf file</p><p
class="command">vi /etc/postfix/main.cf</p><p>and comment out these lines by adding a &#8220;#&#8221; in front of them:</p><p
class="system"># content_filter = amavis:[127.0.0.1]:10024<br
/> # receive_override_options = no_address_mappings</p><p>Then restart postfix:</p><p
class="command">/etc/init.d/postfix restart</p><p>Now stop and disable the services. The following commands are for Debian and Ubuntu, the commands for other Linux distributions may vary</p><p
class="command">/etc/init.d/clamav-daemon stop<br
/> /etc/init.d/clamav-freshclam stop<br
/> /etc/init.d/amavis stop</p><p
class="command">update-rc.d -f clamav-daemon remove<br
/> update-rc.d -f clamav-freshclam remove<br
/> update-rc.d -f amavis remove</p><p>P The normal mail receive and send functions will still work after this modification. But please be aware that disabling amavisd and clamav will disable all spam-  and antivirus filtering so that the spamfiltering options that can be configured in the ispconfig interface will have any effect on mail delivery and no spam and viruses will get filtered.</p><p>The changes in postfix main.cf will get overwitten by a ispconfig software update when you select to reconfigure services during upadte, so you should comment out the lines again after you install a ispconfig update.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-disable-spamfilter-and-antivirus-functions-in-ispconfig-3/feed/</wfw:commentRss> <slash:comments>8</slash:comments> </item> <item><title>How to solve the ClamAV error &#8220;This version of the ClamAV engine is outdated&#8221; on Debian 5.0 (Lenny)</title><link>http://www.faqforge.com/linux/how-to-solve-the-clamav-error-this-version-of-the-clamav-engine-is-outdated-on-debian-5-0-lenny/</link> <comments>http://www.faqforge.com/linux/how-to-solve-the-clamav-error-this-version-of-the-clamav-engine-is-outdated-on-debian-5-0-lenny/#comments</comments> <pubDate>Fri, 16 Apr 2010 14:16:28 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[Email]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Amavisd]]></category> <category><![CDATA[ClamAV]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=442</guid> <description><![CDATA[As of today, all ClamAV 0.94 or older installs will stop working. The Debian project has not released updates for their current stable release (5.0) yet to solve this, but there is a workaround. The Debain volatile project provides newer clamav versions. The installation steps to install ClamAV 0.95.3 on Debian lenny are: 1) Add [...]]]></description> <content:encoded><![CDATA[<p>As of today, all ClamAV 0.94 or older installs will stop working. The Debian project has not released updates for their current stable release (5.0) yet to solve this, but there is a workaround. The Debain volatile project provides newer clamav versions. The installation steps to install ClamAV 0.95.3 on Debian lenny are:</p><p>1) Add the debian volatile repository to the sources list:</p><p
class="command">echo &#8220;deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib non-free&#8221; >> /etc/apt/sources.list</p><p>2) Update the sources and install the new clamav package:</p><p
class="command">apt-get update<br
/> apt-get install clamav<br
/> apt-get -u upgrade</p><p>3) If you use amavisd-new (e.g. if you use a ISPConfig 3 server) then restart amavisd:</p><p
class="command">/etc/init.d/amavis restart</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/how-to-solve-the-clamav-error-this-version-of-the-clamav-engine-is-outdated-on-debian-5-0-lenny/feed/</wfw:commentRss> <slash:comments>11</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)
Database Caching 1/45 queries in 0.049 seconds using disk: basic
Object Caching 1556/1650 objects using disk: basic

Served from: www.faqforge.com @ 2012-02-04 23:20:08 -->
