Текущая версия |
Ваш текст |
Строка 167: |
Строка 167: |
| | | |
| | | |
− | ===8. Install Amavisd-new, SpamAssassin, And Clamav===
| + | I'm so glad I found my soltuion online. |
− | | |
− | To install amavisd-new, SpamAssassin, and ClamAV, we run
| |
− | <pre>
| |
− | apt-get install amavisd-new spamassassin clamav clamav-daemon zoo unzip bzip2 arj
| |
− | nomarch lzop cabextract apt-listchanges libnet-ldap-perl libauthen-sasl-perl clamav-docs
| |
− | daemon libio-string-perl libio-socket-ssl-perl libnet-ident-perl zip libnet-dns-perl
| |
− | </pre>
| |
− | | |
− | The ISPConfig 3 setup uses amavisd which loads the SpamAssassin filter library internally, so we can stop SpamAssassin to free up some RAM:
| |
− | /etc/init.d/spamassassin stop
| |
− | update-rc.d -f spamassassin remove
| |
− |
| |
| | | |
| ===9. Install Apache2, PHP5, phpMyAdmin, FCGI, suExec, Pear, And mcrypt=== | | ===9. Install Apache2, PHP5, phpMyAdmin, FCGI, suExec, Pear, And mcrypt=== |
Строка 715: |
Строка 703: |
| For download and usage instructions, please visit http://www.ispconfig.org/ispconfig-3/ispconfig-monitor-app-for-android/. | | For download and usage instructions, please visit http://www.ispconfig.org/ispconfig-3/ispconfig-monitor-app-for-android/. |
| | | |
− | ===17. Additional Notes===
| + | Whoa, whoa, get out the way with that good inoormatifn. |
− | | |
− | ====17.1 OpenVZ====
| |
− | If the Debian server that you've just set up in this tutorial is an OpenVZ container (virtual machine), you should do this on the host system (I'm assuming that the ID of the OpenVZ container is 101 - replace it with the correct VPSID on your system):
| |
− | | |
− | <pre>
| |
− | VPSID=101
| |
− | for CAP in CHOWN DAC_READ_SEARCH SETGID SETUID NET_BIND_SERVICE NET_ADMIN
| |
− | SYS_CHROOT SYS_NICE CHOWN DAC_READ_SEARCH SETGID SETUID NET_BIND_SERVICE NET_
| |
− | ADMIN SYS_CHROOT SYS_NICE
| |
− | do
| |
− | vzctl set $VPSID --capability ${CAP}:on --save
| |
− | done
| |
− | </pre>
| |
− | | |
− | ====17.2 SquirrelMail====
| |
− | Lots of people have reported problems (such as getting 404 Not Found errors) using the SquirrelMail webmail package in their web sites created through ISPConfig 3. This guide explains how to configure SquirrelMail on a Debian Squeeze server so that you can use it from within your web sites (created through ISPConfig).
| |
− | | |
− | SquirrelMail's Apache configuration is in the file /etc/squirrelmail/apache.conf, but this file isn't loaded by Apache because it is not in the /etc/apache2/conf.d/ directory. Therefore we create a symlink called squirrelmail.conf in the /etc/apache2/conf.d/ directory that points to /etc/squirrelmail/apache.conf and reload Apache afterwards:
| |
− | | |
− | <pre>
| |
− | cd /etc/apache2/conf.d/
| |
− | ln -s ../../squirrelmail/apache.conf squirrelmail.conf
| |
− | /etc/init.d/apache2 reload
| |
− | </pre>
| |
− | | |
− | Now open /etc/apache2/conf.d/squirrelmail.conf...
| |
− | vi /etc/apache2/conf.d/squirrelmail.conf
| |
− | | |
− | ... and add the following lines to the <Directory /usr/share/squirrelmail></Directory> container that make sure that mod_php is used for accessing SquirrelMail, regardless of what PHP mode you select for your website in ISPConfig:
| |
− | | |
− | <pre>
| |
− | [...]
| |
− | <Directory /usr/share/squirrelmail>
| |
− | Options FollowSymLinks
| |
− | <IfModule mod_php5.c>
| |
− | AddType application/x-httpd-php .php
| |
− | php_flag magic_quotes_gpc Off
| |
− | php_flag track_vars On
| |
− | php_admin_flag allow_url_fopen Off
| |
− | php_value include_path .
| |
− | php_admin_value upload_tmp_dir /var/lib/squirrelmail/tmp
| |
− | php_admin_value open_basedir /usr/share/squirrelmail:/etc/squirrelmail:
| |
− | /var/lib/squirrelmail:/etc/hostname:/etc/mailname:/var/spool/squirrelmail
| |
− | php_flag register_globals off
| |
− | </IfModule>
| |
− | <IfModule mod_dir.c>
| |
− | DirectoryIndex index.php
| |
− | </IfModule>
| |
− | # access to configtest is limited by default to prevent information leak
| |
− | <Files configtest.php>
| |
− | order deny,allow
| |
− | deny from all
| |
− | allow from 127.0.0.1
| |
− | </Files>
| |
− | </Directory>
| |
− | [...]
| |
− | </pre>
| |
− | | |
− | Create the directory /var/lib/squirrelmail/tmp...
| |
− | mkdir /var/lib/squirrelmail/tmp
| |
− | | |
− | ... and make it owned by the user www-data:
| |
− | chown www-data /var/lib/squirrelmail/tmp
| |
− | | |
− | Reload Apache again:
| |
− | /etc/init.d/apache2 reload
| |
− | | |
− | That's it already - /etc/apache2/conf.d/squirrelmail.conf defines an alias called /squirrelmail that points to SquirrelMail's installation directory /usr/share/squirrelmail.
| |
− | | |
− | You can now access SquirrelMail from your web site as follows:
| |
− | | |
− | http://www.example.com/squirrelmail
| |
− | | |
− | You can also access it from the ISPConfig control panel vhost as follows (this doesn't need any configuration in ISPConfig):
| |
− | | |
− | http://server1.example.com:8080/squirrelmail
| |
− | | |
− | If you'd like to use the alias /webmail instead of /squirrelmail, simply open /etc/apache2/conf.d/squirrelmail.conf...
| |
− | vi /etc/apache2/conf.d/squirrelmail.conf
| |
− | | |
− | ... and add the line Alias /webmail /usr/share/squirrelmail:
| |
− | | |
− | <pre>
| |
− | Alias /squirrelmail /usr/share/squirrelmail
| |
− | Alias /webmail /usr/share/squirrelmail
| |
− | [...]
| |
− | </pre>
| |
− | | |
− | Then reload Apache:
| |
− | /etc/init.d/apache2 reload
| |
− | | |
− | Now you can access Squirrelmail as follows:
| |
− | | |
− | http://www.example.com/webmail
| |
− | http://server1.example.com:8080/webmail
| |
− | | |
− | If you'd like to define a vhost like webmail.example.com where your users can access SquirrelMail, you'd have to add the following vhost configuration to /etc/apache2/conf.d/squirrelmail.conf:
| |
− | vi /etc/apache2/conf.d/squirrelmail.conf
| |
− | | |
− | <pre>
| |
− | [...]
| |
− | <VirtualHost 1.2.3.4:80>
| |
− | DocumentRoot /usr/share/squirrelmail
| |
− | ServerName webmail.example.com
| |
− | </VirtualHost>
| |
− | </pre>
| |
− | | |
− | Make sure you replace 1.2.3.4 with the correct IP address of your server. Of course, there must be a DNS record for webmail.example.com that points to the IP address that you use in the vhost configuration. Also make sure that the vhost webmail.example.com does not exist in ISPConfig (otherwise both vhosts will interfere with each other!).
| |
− | | |
− | Now reload Apache...
| |
− | /etc/init.d/apache2 reload
| |
− | | |
− | ... and you can access SquirrelMail under http://webmail.example.com!
| |
| | | |
| ===18. Links=== | | ===18. Links=== |