<?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 2</title> <atom:link href="http://www.faqforge.com/category/linux/controlpanels/ispconfig2/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>Update to latest Spamassassin filter rules in ISPConfig 2</title><link>http://www.faqforge.com/linux/update-to-latest-spamassassin-filter-rules-in-ispconfig-2/</link> <comments>http://www.faqforge.com/linux/update-to-latest-spamassassin-filter-rules-in-ispconfig-2/#comments</comments> <pubDate>Thu, 27 Oct 2011 13:32:26 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Spamassassin]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1059</guid> <description><![CDATA[The ISPConfig 2 controlpanel installs its own copy of Spamassassin in the folder /home/admispconfig/ispconfig/tools/spamassassin . To update the Spamassassin filter rules in ISPConfig 2, run this command as root user: /home/admispconfig/ispconfig/tools/spamassassin/usr/bin/sa-update To test if Spamassassin works with the new ruleset, run this command: /home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin &#8211;lint If it does not return an error message, then Spamassassin is [...]]]></description> <content:encoded><![CDATA[<p>The ISPConfig 2 controlpanel installs its own copy of Spamassassin in the folder /home/admispconfig/ispconfig/tools/spamassassin . To update the Spamassassin filter rules in ISPConfig 2, run this command as root user:</p><p
class="command">/home/admispconfig/ispconfig/tools/spamassassin/usr/bin/sa-update</p><p>To test if Spamassassin works with the new ruleset, run this command:</p><p
class="command">/home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin &#8211;lint</p><p>If it does not return an error message, then Spamassassin is working correctly.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/update-to-latest-spamassassin-filter-rules-in-ispconfig-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Webalizer: Error Opening file /usr/share/GeoIP/GeoIP.dat on Debian Linux</title><link>http://www.faqforge.com/linux/webalizer-error-opening-file-usrsharegeoipgeoip-dat-on-debian-linux/</link> <comments>http://www.faqforge.com/linux/webalizer-error-opening-file-usrsharegeoipgeoip-dat-on-debian-linux/#comments</comments> <pubDate>Tue, 25 Oct 2011 14:06:44 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[apache]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[webalizer]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1030</guid> <description><![CDATA[The webalizer package in Debain 6 has currently small bug as the required package for the  GeoIP database is not installed automatically when webalizer is isntalled. The symptoms are that webalizer statistics are not created and this error message is displayed when webalizer is run: Error Opening file /usr/share/GeoIP/GeoIP.dat The solution is to install the [...]]]></description> <content:encoded><![CDATA[<p>The webalizer package in Debain 6 has currently small bug as the required package for the  GeoIP database is not installed automatically when webalizer is isntalled. The symptoms are that webalizer statistics are not created and this error message is displayed when webalizer is run:</p><p
class="system">Error Opening file /usr/share/GeoIP/GeoIP.dat</p><p>The solution is to install the missing package manually:</p><p
class="command">apt-get install geoip-database</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/webalizer-error-opening-file-usrsharegeoipgeoip-dat-on-debian-linux/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Send all outgoing email trough one IP address in postfix</title><link>http://www.faqforge.com/linux/send-all-outgoing-email-trough-one-ip-address-in-postfix/</link> <comments>http://www.faqforge.com/linux/send-all-outgoing-email-trough-one-ip-address-in-postfix/#comments</comments> <pubDate>Tue, 25 Oct 2011 13:59:05 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Basics]]></category> <category><![CDATA[CentOS]]></category> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[Email]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[bind]]></category> <category><![CDATA[postfix]]></category> <category><![CDATA[smtp_bind_address]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1028</guid> <description><![CDATA[When a server has more then one IP address, then postfix will use all IP addresses randomly to send out emails. This can cause your emails to be listed as SPAM on other servers because the sending IP does not match the reverse IP of the server hostname. The solution is to bind postfix to [...]]]></description> <content:encoded><![CDATA[<p>When a server has more then one IP address, then postfix will use all IP addresses randomly to send out emails. This can cause your emails to be listed as SPAM on other servers because the sending IP does not match the reverse IP of the server hostname. The solution is to bind postfix to the primary IP address of the server.</p><p>Edit the postfix main.cf file:</p><p
class="command">vi /etc/postfix/main.cf</p><p>and add the line:</p><p
class="command">smtp_bind_address = 192.168.0.1</p><p>were 192.168.0.1 has to be replaced with the primary IP address of the server. Then restart postfix:</p><p
class="command">/etc/init.d/postfix restart</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/send-all-outgoing-email-trough-one-ip-address-in-postfix/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Fix for Courier IMAP Error: check for configuration errors with the FAM/Gamin library</title><link>http://www.faqforge.com/linux/fix-for-courier-imap-error-check-for-configuration-errors-with-the-famgamin-library/</link> <comments>http://www.faqforge.com/linux/fix-for-courier-imap-error-check-for-configuration-errors-with-the-famgamin-library/#comments</comments> <pubDate>Mon, 17 Oct 2011 14:19:33 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[courier]]></category> <category><![CDATA[fam]]></category> <category><![CDATA[gamin]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=893</guid> <description><![CDATA[I&#8217;ve got the following error message on Debian Linux (6.0) with Courier IMAP server: Filesystem notification initialization error -- contact your mail administrator (check for configuration errors with the FAM/Gamin library) when I tried to access a IMAP share. The resaon for the problem seems to be that the &#8220;fam&#8221; package was not working correctly. [...]]]></description> <content:encoded><![CDATA[<p>I&#8217;ve got the following error message on Debian Linux (6.0) with Courier IMAP server:</p><pre>Filesystem notification initialization error -- contact your mail
administrator (check for configuration errors with the FAM/Gamin library)</pre><p>when I tried to access a IMAP share. The resaon for the problem seems to be that the &#8220;fam&#8221; package was not working correctly. The solution is to install the gamin package which can replace fam in a courier setup:</p><p
class="command">apt-get install gamin</p><p>Dont worry when you get a message from apt that libfam0 gets uninstalled but is required by courier. This had no geative effects on my server.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/fix-for-courier-imap-error-check-for-configuration-errors-with-the-famgamin-library/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Prevent DOS attacks on apache webserver for DEBIAN linux with mod_evasive</title><link>http://www.faqforge.com/linux/prevent-dos-attacks-on-apache-webserver-for-debian-linux-with-mod_evasive/</link> <comments>http://www.faqforge.com/linux/prevent-dos-attacks-on-apache-webserver-for-debian-linux-with-mod_evasive/#comments</comments> <pubDate>Mon, 07 Mar 2011 13:23:21 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 2]]></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[apache]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=559</guid> <description><![CDATA[The following guide explains the installation of the apache module &#8220;mod_evasive&#8221;. Mod_evasive tracks the number of requests of files at the apache webserver and blocks the delivery in case that a certain limit has been reached. Installation apt-get install libapache2-mod-evasive Create the log directory for mod_evasive mkdir -p /var/log/apache2/evasive chown -R www-data:root /var/log/apache2/evasive Now we [...]]]></description> <content:encoded><![CDATA[<p>The following guide explains the installation of the apache module &#8220;mod_evasive&#8221;. Mod_evasive tracks the number of requests of files at the apache webserver and blocks the delivery in case that a certain limit has been reached.</p><p><strong>Installation</strong></p><p
class="command">apt-get install libapache2-mod-evasive</p><p>Create the log directory for mod_evasive</p><p
class="command">mkdir -p /var/log/apache2/evasive<br
/> chown -R www-data:root /var/log/apache2/evasive</p><p>Now we add the configuration for the module at the end of the file /etc/apache2/mods-available/mod-evasive.load</p><p
class="command">vi /etc/apache2/mods-available/mod-evasive.load</p><p>so that it looks like this:</p><p
class="command">LoadModule evasive20_module /usr/lib/apache2/modules/mod_evasive20.so<br
/> <IfModule
mod_evasive20.c><br
/> DOSHashTableSize 3097<br
/> DOSPageCount 2<br
/> DOSSiteCount 50<br
/> DOSPageInterval 5<br
/> DOSSiteInterval 1<br
/> DOSBlockingPeriod 10<br
/> DOSLogDir &#8220;/var/log/apache2/evasive&#8221;<br
/> </IfModule></p><p>and restart apache:</p><p
class="command">/etc/init.d/apache2 restart</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/prevent-dos-attacks-on-apache-webserver-for-debian-linux-with-mod_evasive/feed/</wfw:commentRss> <slash:comments>5</slash:comments> </item> <item><title>How to solve the PHP XCache error: /dev/zero: No space left on device</title><link>http://www.faqforge.com/linux/controlpanels/how-to-solve-the-php-xcache-error-devzero-no-space-left-on-device/</link> <comments>http://www.faqforge.com/linux/controlpanels/how-to-solve-the-php-xcache-error-devzero-no-space-left-on-device/#comments</comments> <pubDate>Wed, 01 Sep 2010 10:19:51 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[Virtualisation]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[OpenVZ]]></category> <category><![CDATA[XCache]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=508</guid> <description><![CDATA[If you get the error &#8220;/dev/zero: No space left on device&#8221; in the apache error.log on a OpenVZ virtual machine, then the shared memory size in the xcache.ini is too high or the xcache.mm_path is set wrong. Edit the file /etc/php5/conf.d/xcache.ini vi /etc/php5/conf.d/xcache.ini and check the mm_path. On a OpenVZ virtual machine it should be [...]]]></description> <content:encoded><![CDATA[<p>If you get the error &#8220;<span
class="system">/dev/zero: No space left on device</span>&#8221; in the apache error.log on a OpenVZ virtual machine, then the shared memory size in the xcache.ini is too high or the xcache.mm_path is set wrong.</p><p>Edit the file /etc/php5/conf.d/xcache.ini</p><p
class="command">vi /etc/php5/conf.d/xcache.ini</p><p>and check the mm_path. On a OpenVZ virtual machine it should be set to &#8220;/tmp/xcache&#8221; as /dev/zero might not work correctly in a virtual machine:</p><p
class="system">xcache.mmap_path = &#8220;/tmp/xcache&#8221;</p><p>Then restart apache2:</p><p
class="command">/etc/init.d/apache2 restart</p><p>and check if the error has been resolved.</p><p>If the roor still occurs after some time, you will have to reduce the xcache.size.</p><p>Edite the xcache.ini file:</p><p
class="command">vi /etc/php5/conf.d/xcache.ini</p><p>and set xcache.size to e.g. 8 MB</p><p
class="system">xcache.size  =                8M</p><p>Then restart apache2:</p><p
class="command">/etc/init.d/apache2 restart</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/how-to-solve-the-php-xcache-error-devzero-no-space-left-on-device/feed/</wfw:commentRss> <slash:comments>0</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 update Spamassassin on ISPConfig 2</title><link>http://www.faqforge.com/linux/controlpanels/how-to-update-spamassassin-on-ispconfig-2/</link> <comments>http://www.faqforge.com/linux/controlpanels/how-to-update-spamassassin-on-ispconfig-2/#comments</comments> <pubDate>Thu, 27 May 2010 11:21:18 +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 2]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=462</guid> <description><![CDATA[The spamassassin installation on a ISPConfig 2 server is normally updated together with ISPConfig. Here are the steps iIf you want to update spamassassin manually without updating ISPConfig 2: Download the latest Spamassassin sources and unpack the tar.gz file cd /tmp wget http://ftp.fernuni-hagen.de/ftp-dir/pub/mirrors/\ www.apache.org/spamassassin/source/Mail-SpamAssassin-3.3.1.tar.gz tar xfz Mail-SpamAssassin-3.3.1.tar.gz Configure, make and install spamassassin cd Mail-SpamAssassin-3.3.1 perl [...]]]></description> <content:encoded><![CDATA[<p>The spamassassin installation on a ISPConfig 2 server is normally updated together with ISPConfig. Here are the steps iIf you want to update spamassassin manually without updating ISPConfig 2:</p><p>Download the latest Spamassassin sources and unpack the tar.gz file</p><p
class="command">cd /tmp<br
/> wget http://ftp.fernuni-hagen.de/ftp-dir/pub/mirrors/\<br
/> www.apache.org/spamassassin/source/Mail-SpamAssassin-3.3.1.tar.gz<br
/> tar xfz Mail-SpamAssassin-3.3.1.tar.gz</p><p>Configure, make and install spamassassin</p><p
class="command">cd Mail-SpamAssassin-3.3.1<br
/> perl Makefile.PL PREFIX=/home/admispconfig/ispconfig/tools/\<br
/> spamassassin/usr SYSCONFDIR=/home/admispconfig/ispconfig/\<br
/> tools/spamassassin/etc<br
/> make<br
/> make install</p><p>Cleanup</p><p
class="command">cd ..<br
/> rm -f Mail-SpamAssassin-3.3.1.tar.gz<br
/> rm -rf Mail-SpamAssassin-3.3.1</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/how-to-update-spamassassin-on-ispconfig-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to enable port 587 (submission) in postfix</title><link>http://www.faqforge.com/linux/how-to-enable-port-587-submission-in-postfix/</link> <comments>http://www.faqforge.com/linux/how-to-enable-port-587-submission-in-postfix/#comments</comments> <pubDate>Mon, 26 Apr 2010 09:36:13 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[Email]]></category> <category><![CDATA[ISPConfig 2]]></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=458</guid> <description><![CDATA[Some internet access providers have port 25 disabled in their routers to prevent spam. If you run your own mailserver in a datacenter, you might have to enable the submission port (587) in postfix to be able to send emails from your local email client to your own mailserver. To enable port 587, edit the [...]]]></description> <content:encoded><![CDATA[<p>Some internet access providers have port 25 disabled in their routers to prevent spam. If you run your own mailserver in a datacenter, you might have to enable the submission port (587) in postfix to be able to send emails from your local email client to your own mailserver.</p><p>To enable port 587, edit the file /etc/postfix/master.cf</p><p
class="command">vi /etc/postfix/master.cf</p><p>and remove the # in front of the line:</p><p
class="system">#submission inet n      &#8211;       n       &#8211;       &#8211;       smtpd</p><p>so that it looks like this:</p><p
class="system">submission inet n      &#8211;       n       &#8211;       &#8211;       smtpd</p><p>and restart postfix:</p><p
class="command">/etc/init.d/postfix restart</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/how-to-enable-port-587-submission-in-postfix/feed/</wfw:commentRss> <slash:comments>4</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/40 queries in 0.036 seconds using disk: basic
Object Caching 1484/1629 objects using disk: basic

Served from: www.faqforge.com @ 2012-02-04 23:42:07 -->
