[Qvcs-CVS] qvcs-guide Makefile,1.12,1.13 qvcs-guide.xml,1.8,1.9
Brought to you by:
graf25
Menu
▾
▴
[Qvcs-CVS] qvcs-guide Makefile,1.12,1.13 qvcs-guide.xml,1.8,1.9
|
From: <gr...@us...> - 2003-07-11 03:03:39
|
Update of /cvsroot/qvcs-guide/qvcs-guide In directory sc8-pr-cvs1:/tmp/cvs-serv2245 Modified Files: Makefile qvcs-guide.xml Log Message: I think I'm ready for a beta run. Index: Makefile =================================================================== RCS file: /cvsroot/qvcs-guide/qvcs-guide/Makefile,v retrieving revision 1.12 retrieving revision 1.13 diff -C2 -d -r1.12 -r1.13 *** Makefile 20 Jun 2003 20:41:53 -0000 1.12 --- Makefile 11 Jul 2003 03:03:35 -0000 1.13 *************** *** 1,8 **** # $Id$ ! PDFTEX=/usr/bin/pdflatex RSYNC=/usr/bin/rsync RSYNCFLAGS=-avz ! REMOTELOC=gr...@sh...:/home/groups/q/qv/qvcs-guide/htdocs/ HELPERSV=2.0.0 HELPERSDIR=qvcs-helpers-$(HELPERSV) --- 1,8 ---- # $Id$ ! XMLTO=/usr/bin/xmlto RSYNC=/usr/bin/rsync RSYNCFLAGS=-avz ! REMOTELOC=norbert.linux.duke.edu:~/qvcs-guide/ HELPERSV=2.0.0 HELPERSDIR=qvcs-helpers-$(HELPERSV) *************** *** 10,38 **** all: site qvcs-helpers ! pdf: ! for FILE in *.tex; do $(PDFTEX) $$FILE; $(PDFTEX) $$FILE; done ! rm -f *.toc *.aux *.log ! ! clean-all: clean clean-site clean-helpers ! ! clean: ! rm -f *.pdf *.toc *.aux *.log *.dvi ! find -name '*~' -exec rm -f {} \; ! clean-site: clean ! rm -rf site ! site: pdf ! mkdir -p site/bsd cp html/*.html html/*.css site/ ! cp qvcs-guide-bsd.tex site/bsd/qvcs-guide.tex ! mv qvcs-guide-bsd.pdf site/bsd/qvcs-guide.pdf ! for FILE in *.sh.bsd; do \ ! NEWFILE=`echo $$FILE | sed 's/.sh.bsd/.sh.txt/g'`; \ ! cp $$FILE site/bsd/$$NEWFILE; \ ! done ! mkdir -p site/rhl ! cp qvcs-guide-rh7.tex site/rhl/qvcs-guide.tex ! mv qvcs-guide-rh7.pdf site/rhl/qvcs-guide.pdf site-commit: site --- 10,23 ---- all: site qvcs-helpers ! qvcs-guide.pdf: ! $(XMLTO) pdf qvcs-guide.xml ! qvcs-guide.html: ! $(XMLTO) xhtml-nochunks qvcs-guide.xml ! site: qvcs-guide.pdf qvcs-guide.html ! mkdir -p site/ cp html/*.html html/*.css site/ ! cp qvcs-guide.xml qvcs-guide.html qvcs-guide.pdf site/ site-commit: site *************** *** 45,48 **** --- 30,42 ---- tar czvf $(HELPERSDIR).tar.gz $(HELPERSDIR) rm -rf $(HELPERSDIR) + + clean-all: clean clean-site clean-helpers + + clean: + rm -f *.pdf *.html + find -name '*~' -exec rm -f {} \; + + clean-site: + rm -rf site clean-helpers: Index: qvcs-guide.xml =================================================================== RCS file: /cvsroot/qvcs-guide/qvcs-guide/qvcs-guide.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -C2 -d -r1.8 -r1.9 *** qvcs-guide.xml 10 Jul 2003 22:26:49 -0000 1.8 --- qvcs-guide.xml 11 Jul 2003 03:03:35 -0000 1.9 *************** *** 596,603 **** install <command>nano</command> by using yum. Nano is a successor to pico and inherits all of its shortcuts. ! <programlisting> &prompt; <userinput>yum install nano</userinput> ! </programlisting> </para> </tip> <para> --- 596,611 ---- install <command>nano</command> by using yum. Nano is a successor to pico and inherits all of its shortcuts. ! </para> ! <programlisting> &prompt; <userinput>yum install nano</userinput> ! </programlisting> ! <para> ! It is useful to know that calling nano with a "-w" ! flag will turn off automatic line wrapping. Good for files ! where you have to type a very long line without it wrapping: </para> + <programlisting> + &prompt; <userinput>nano -w filename.conf</userinput> + </programlisting> </tip> <para> *************** *** 822,831 **** </sect1> <sect1> ! <title>Backup</title> ! <para>I NEED CONTENT!</para> ! </sect1> ! <sect1> ! <title>Restore</title> ! <para>I NEED CONTENT!</para> </sect1> <sect1> --- 830,853 ---- </sect1> <sect1> ! <title>Keeping in Time</title> ! <para> ! It is important for a mailserver to have its clock set ! correctly, otherwise there may be problems with messages being ! timestamped incorrectly. This will help keep your clock in ! sync with the central network time authority. Create a file ! <filename>/etc/cron.hourly/rdate.cron</filename> and put the ! following in it: ! </para> ! <programlisting> ! #!/bin/sh ! # Synchronize the time with nist.gov ! (/usr/bin/rdate -s time.nist.gov) && (/sbin/hwclock --systohc) ! </programlisting> ! <para> ! Then set the execute permissions: ! </para> ! <programlisting> ! &prompt; <userinput>chmod 755 /etc/cron.hourly/rdate.cron</userinput> ! </programlisting> </sect1> <sect1> *************** *** 849,852 **** --- 871,995 ---- </para> </sect1> + <sect1> + <title>Backup</title> + <para> + There are many backup systems out there, so I will not cover + them in this little foray. Instead, I will tell you which + parts to back up, and it will be up to you to come up with a + method. + </para> + <para> + The following files and/or directories need to be backed up in + a cookie-cutter &qvcs; system. If you make additions or + modifications, you will need to make sure they are reflected + in this list. + </para> + <note> + <para> + Some of the files in this list include the ones created or + modified in the advanced section. If you did not add + advanced features, your system may lack some of these + entries. + </para> + </note> + <programlisting> + /etc/passwd + /etc/shadow + /etc/group + /etc/sslcert.pem + /etc/sysconfig/spamassassin + /etc/sysconfig/iptables + /etc/hosts.* + /etc/xinetd.d/smtp + /etc/ssh/*_key* + /etc/httpd + /etc/vadmin + /etc/squirrelmail + /etc/qmail + /etc/courier-imap + /etc/vmailmgr + /var/lib/vadmin + /var/lib/squirrelmail + /var/qmail/queue + /home/dom + /root + </programlisting> + </sect1> + <sect1> + <title>Restore</title> + <para> + If your system has crashed and you have to reinstall + everything from scratch, here is how you would go about it. + </para> + <procedure> + <step> + <para> + <emphasis>Install a vanilla system</emphasis>. + Just create a vanilla &rhl; &ver; setup. DO NOT use the + kickstart provided with the guide, as there are some + delicate issues with qmail usernames having to match the + userids. + </para> + </step> + <step> + <para> + <emphasis>Restore the backup files</emphasis>. Restore + them over the existing tree. For example, if your backup + is in <filename>/home/bak.tar.gz</filename>, then you + would restore it like this: + </para> + <programlisting> + &prompt; <userinput>cd /</userinput> + &prompt; <userinput>tar xzvf /home/bak.tar.gz</userinput> + </programlisting> + </step> + <step> + <para> + <emphasis>Run qvcs-init</emphasis>. Refer to the install + section of this guide. It will wordily complain about + creating .rpmnew files, but that's exactly what you want. + </para> + </step> + <step> + <para> + <emphasis>Run qvcs-install</emphasis>. However, skip all + sections except the last two -- where it enables/disables + services and removes sendmail. + </para> + </step> + <step> + <para> + If your system utilized advanced features + </para> + <substeps> + <step> + <para> + <emphasis>Reinstall the custom qmail + RPM</emphasis>. If you have backed up your + custom-built Qmail RPM, you should install it now, + otherwise download and rebuild again. Refer to the + appropriate section of this guide. + </para> + </step> + <step> + <para> + <emphasis>Reinstall the filter group</emphasis>. + Perform the following actions: + </para> + <programlisting> + &prompt; <userinput>yum groupinstall "QVCS Filter"</userinput> + &prompt; <userinput>chkconfig spamassassin on</userinput> + &prompt; <userinput>service spamassassin start</userinput> + &prompt; <userinput>qmail-scanner-reconfigure --assumeyes</userinput> + </programlisting> + </step> + </substeps> + </step> + </procedure> + <para> + This should be it. After these steps are done, your system + should be reinstalled. + </para> + </sect1> </chapter> <!-- #################################################################### --> *************** *** 894,898 **** download, so prepare to be patient. Once all these steps are complete, you have successfully installed a modified version ! of qmail, necessary for the advanced configurations. </para> </sect2> --- 1037,1044 ---- download, so prepare to be patient. Once all these steps are complete, you have successfully installed a modified version ! of qmail, necessary for the advanced configurations. You ! might find it useful to backup this custom RPM, so in case ! you have to reinstall your system you don't have to go ! through this again. </para> </sect2> *************** *** 1400,1408 **** </sect1> <sect1> ! <title>Thank you and good luck! ;)</title> <para> If you found this Guide useful, please let me know by executing: </para> ! v <programlisting> &prompt; <userinput>uname -a | mail qvc...@mr... -s 'Thanks'</userinput> </programlisting> --- 1546,1554 ---- </sect1> <sect1> ! <title>Report your success</title> <para> If you found this Guide useful, please let me know by executing: </para> ! <programlisting> &prompt; <userinput>uname -a | mail qvc...@mr... -s 'Thanks'</userinput> </programlisting> *************** *** 1425,1430 **** clean. </para> <sect1> ! <title>Upgrading via Upgrading</title> <para> This path will let you upgrade your system using Red Hat --- 1571,1580 ---- clean. </para> + <para> + In either case the process should take hardly more than an hour, + largely dependent on your network speed. + </para> <sect1> ! <title>Upgrading via an Upgrade</title> <para> This path will let you upgrade your system using Red Hat *************** *** 1465,1628 **** </programlisting> </sect2> <sect2> ! <title>Migrating the configs</title> <para> ! Several packages have changed their configurations pretty ! dramatically, most notably SquirrelMail (version change from ! 1.2 to 1.4), Vadmin (from 1.0 to 1.9), Courier-IMAP (from ! 1.4 to 2.0), and Apache (from 1.3 to 2.0). Migrating your ! configurations is going to take some effort. </para> ! <sect3> ! <title>Apache</title> ! <para> ! You cannot use the old httpd configs at all, so you will ! need to do the following: ! </para> ! <programlisting> &prompt; <userinput>cd /etc/httpd/conf</userinput> &prompt; <userinput>mv httpd.conf httpd.conf.old</userinput> &prompt; <userinput>mv httpd.conf.rpmnew httpd.conf</userinput> ! </programlisting> ! <para> ! If your 7.3 system was being used ! <emphasis>solely</emphasis> as a cookie-cutter &qvcs; ! install, that's all you have to do -- the rest will be ! taken care of by <command>qvcs-install</command>. If, ! however, you have been serving some things other than just ! webmail from your webserver, you will need to peruse your ! old apache configuration file and manually migrate ! settings from there to the Apache-2.0 new configuration ! format. ! </para> ! <note> ! <para> ! It is no longer necessary to add an ! <varname>Include</varname> statement for vadmin in your ! httpd.conf -- it is now done automatically in the ! <filename>/etc/httpd/conf.d</filename> directory. ! </para> ! </note> ! </sect3> ! <sect3> ! <title>SquirrelMail</title> ! <para> ! If you have been using any additional plugins for ! Squirrelmail that you have installed on your own, you will ! need to check if newer versions exist that are known to ! work on Squirrelmail-1.4. Other than that, you should not ! have to change anything -- configuration will be taken ! care of by <command>qvcs-install</command>. ! </para> ! <para> ! It is also worthy of mention that SquirrelMail now lives ! in <filename>/usr/share/squirrelmail</filename> instead of ! <filename>/var/www/squirrelmail</filename>, so be sure to ! make appropriate edits if you have any software (like ! extra plugins) that expect to find squirrelmail in the old ! location. ! </para> ! </sect3> ! <sect3> ! <title>Vadmin</title> ! <para> ! This one is going to take a little effort. Storage format ! has changed between 1.0 and 1.9 (2.0 beta), so a few ! things need to be taken care of before your old ! preferences can be used. ! </para> <para> ! First of all, go into <filename>/etc/vadmin</filename> and ! perform the following: </para> ! <programlisting> &prompt; <userinput>cd /etc/vadmin</userinput> &prompt; <userinput>mv apache.inc.rpmsave /etc/httpd/conf.d/vadmin.conf</userinput> ! </programlisting> ! <para> ! Now open ! <filename>/etc/httpd/conf.d/vadmin.conf</filename> in your ! editor and change the path in the ! <varname>Directory</varname> directive from ! <filename>/var/www/squirrelmail/plugins/vadmin</filename> ! to the new location of squirrelmail install: ! </para> ! <programlisting> <Directory "/usr/share/squirrelmail"> ! </programlisting> ! <para> ! Now do the following to set some permissions that ! vadmin-1.9 expects to find. ! </para> ! <programlisting> &prompt; <userinput>chown -R root:apache /var/lib/vadmin</userinput> &prompt; <userinput>chmod -R g+w /var/lib/vadmin</userinput> ! </programlisting> ! <para> ! Now, finally, open ! <filename>/etc/vadmin/vadmin.conf</filename> in your ! editor and change the following things: in the ! <varname>[auth]</varname> section change the ! <varname>elvis</varname> setting to reflect the real ! elvises that vadmin has defined (if you don't remember, ! look in <filename>/var/lib/vadmin/cross-admins/</filename> ! for any username files that contain "elvis" as ! the only thing in it. After that, locate a commented-out ! <varname>[upgrade]</varname> section and remove all ! semicolons to enable the upgrading of domain preferences ! on the fly. ! </para> ! </sect3> ! <sect3> ! <title>Courier-IMAP</title> ! <para> ! Only a small edit is required: ! </para> ! <programlisting> &prompt; <userinput>cd /etc/courier-imap</userinput> &prompt; <userinput>mv imapd-ssl.rpmnew imapd-ssl</userinput> &prompt; <userinput>mv pop3d-ssl.rpmnew pop3d-ssl</userinput> ! </programlisting> ! </sect3> ! <sect3> ! <title>Iptables</title> ! <para> ! Firewalling software has largely migrated from ipchains to ! iptables, so do the following: ! </para> ! <programlisting> &prompt; <userinput>chkconfig ipchains off</userinput> &prompt; <userinput>chkconfig iptables on</userinput> ! </programlisting> ! </sect3> ! <sect3> ! <title>qvcs-install</title> ! <para> ! Now that you have done all of the above, you can run ! <command>qvcs-install</command> to take care of various ! little settings that are needed for &qvcs;. Every step of ! the program will ask you for confirmation before making ! any changes, so if you are sure you don't want it to touch ! certain things, you can skip those parts. ! </para> ! <programlisting> &prompt; <userinput>qvcs-install</userinput> ! </programlisting> ! </sect3> ! <sect3> ! <title>Done</title> ! <para> ! That should be it! Reboot now and once your machine comes ! up, you should be able to continue using it as if nothing ! happened. If something is not working, please send email ! to the support mailing list so your problem can be looked ! into. ! </para> ! </sect3> </sect2> <sect2> ! <title>Upgrading via a Reinstall</title> <para> ! I NEED CONTENT! </para> </sect2> --- 1615,1850 ---- </programlisting> </sect2> + </sect1> + <sect1> + <title>Upgrading Via a Reinstall</title> + <para> + Besides leaving your system nice and squeaky-clean, it also + allows you to minimize your downtime if you leave the old + system running while you install and prepare the new one. + </para> <sect2> ! <title>Preparing</title> <para> ! Before you reinstall, you will need to prepare and back up ! your data. Before you back up, perform the following ! operation (this is not mandatory, but this is better for me, ! since after the reinstall and restore the upgraded and ! reinstalled systems will be in the same state with regards ! to saved config files): </para> ! <programlisting> ! &prompt; <userinput>rpm -e vadmin php-mcrypt squirrelmail vmailmgr-php qvcs-helpers</userinput> ! </programlisting> ! <para> ! Now back up the data and store it somewhere safe. To see ! which files you should back up, refer to the ! "Backup" section of this guide -- the files are ! pretty much identical, except some of them will be missing ! on your system, since it's an earlier setup. ! </para> ! </sect2> ! <sect2> ! <title>Reinstalling</title> ! <para> ! Reinstall the machine using the "Installation" ! section of this guide. DO NOT use kickstart for this, as you ! will run into qmail username problems when you start ! restoring the data. Just install a vanilla &rhl; &ver; ! system. ! </para> ! </sect2> ! <sect2> ! <title>Restoring</title> ! <para> ! Once your fresh installation boots up, log in as root, copy ! over your backup data (a good place to put it is in ! <filename>/home</filename> since that partition usually has ! plenty of space) and then restore it over your existing ! tree. For example, if your backup is in ! <filename>/home/bak.tar.gz</filename>, you would use the ! following to restore: ! </para> ! <programlisting> ! &prompt; <userinput>cd /</userinput> ! &prompt; <userinput>tar xzvf /home/bak.tar.gz</userinput> ! </programlisting> ! <para> ! Now run <command>qvcs-init</command>: ! </para> ! <programlisting> ! &prompt; <userinput>wget &qvcsbase;/qvcs-init</userinput> ! &prompt; <userinput>sh qvcs-init</userinput> ! </programlisting> ! <para> ! It will complain loudly about creating tons of .rpmnew ! files, but that's to be expected. Once ! <command>qvcs-init</command> finishes, you should be more or ! less at the same point as if you upgraded your system, so ! proceed with migrating the configs. ! </para> ! </sect2> ! </sect1> ! <sect1> ! <title>Migrating the configs</title> ! <para> ! Several packages have changed their configurations pretty ! dramatically, most notably SquirrelMail (version change from ! 1.2 to 1.4), Vadmin (from 1.0 to 1.9), Courier-IMAP (from 1.4 ! to 2.0), and Apache (from 1.3 to 2.0). Migrating your ! configurations is going to take some effort. ! </para> ! <sect2> ! <title>Apache</title> ! <para> ! You cannot use the old httpd configs at all, so you will ! need to do the following: ! </para> ! <programlisting> &prompt; <userinput>cd /etc/httpd/conf</userinput> &prompt; <userinput>mv httpd.conf httpd.conf.old</userinput> &prompt; <userinput>mv httpd.conf.rpmnew httpd.conf</userinput> ! </programlisting> ! <para> ! If your 7.3 system was being used ! <emphasis>solely</emphasis> as a cookie-cutter &qvcs; ! install, that's all you have to do -- the rest will be taken ! care of by <command>qvcs-install</command>. If, however, you ! have been serving some things other than just webmail from ! your webserver, you will need to peruse your old apache ! configuration file and manually migrate settings from there ! to the Apache-2.0 new configuration format. ! </para> ! <note> <para> ! It is no longer necessary to add an ! <varname>Include</varname> statement for vadmin in your ! httpd.conf -- it is now done automatically in the ! <filename>/etc/httpd/conf.d</filename> directory. </para> ! </note> ! </sect2> ! <sect2> ! <title>SquirrelMail</title> ! <para> ! If you have been using any additional plugins for ! Squirrelmail that you have installed on your own, you will ! need to check if newer versions exist that are known to ! work on Squirrelmail-1.4. Other than that, you should not ! have to change anything -- configuration will be taken ! care of by <command>qvcs-install</command>. ! </para> ! <para> ! It is also worthy of mention that SquirrelMail now lives ! in <filename>/usr/share/squirrelmail</filename> instead of ! <filename>/var/www/squirrelmail</filename>, so be sure to ! make appropriate edits if you have any software (like ! extra plugins) that expect to find squirrelmail in the old ! location. ! </para> ! </sect2> ! <sect2> ! <title>Vadmin</title> ! <para> ! This one is going to take a little effort. Storage format ! has changed between 1.0 and 1.9 (2.0 beta), so a few things ! need to be taken care of before your old preferences can be ! used. ! </para> ! <para> ! First of all, go into <filename>/etc/vadmin</filename> and ! perform the following: ! </para> ! <programlisting> &prompt; <userinput>cd /etc/vadmin</userinput> &prompt; <userinput>mv apache.inc.rpmsave /etc/httpd/conf.d/vadmin.conf</userinput> ! </programlisting> ! <para> ! Now open <filename>/etc/httpd/conf.d/vadmin.conf</filename> ! in your editor and change the path in the ! <varname>Directory</varname> directive from ! <filename>/var/www/squirrelmail/plugins/vadmin</filename> to ! the new location of squirrelmail install: ! </para> ! <programlisting> <Directory "/usr/share/squirrelmail"> ! </programlisting> ! <para> ! Now do the following to set some permissions that vadmin-1.9 ! expects to find. ! </para> ! <programlisting> &prompt; <userinput>chown -R root:apache /var/lib/vadmin</userinput> &prompt; <userinput>chmod -R g+w /var/lib/vadmin</userinput> ! </programlisting> ! <para> ! Now, finally, open ! <filename>/etc/vadmin/vadmin.conf</filename> in your editor ! and change the following things: in the ! <varname>[auth]</varname> section change the ! <varname>elvis</varname> setting to reflect the real elvises ! that vadmin has defined (if you don't remember, look in ! <filename>/var/lib/vadmin/cross-admins/</filename> for any ! username files that contain "elvis" as the only ! thing in it. After that, locate a commented-out ! <varname>[upgrade]</varname> section and remove all ! semicolons to enable the upgrading of domain preferences on ! the fly. ! </para> ! </sect2> ! <sect2> ! <title>Vmailmgr</title> ! <para> ! This step is only relevant if you have reinstalled, not ! upgraded. A very small edit is needed: ! </para> ! <programlisting> ! &prompt; <userinput>cd /etc/vmailmgr</userinput> ! &prompt; <userinput>mv socket-file.rpmnew socket-file</userinput> ! </programlisting> ! </sect2> ! <sect2> ! <title>Courier-IMAP</title> ! <para> ! Only a small edit is required here as well: ! </para> ! <programlisting> &prompt; <userinput>cd /etc/courier-imap</userinput> &prompt; <userinput>mv imapd-ssl.rpmnew imapd-ssl</userinput> &prompt; <userinput>mv pop3d-ssl.rpmnew pop3d-ssl</userinput> ! </programlisting> ! </sect2> ! <sect2> ! <title>Iptables</title> ! <para> ! This step is only relevant is you have upgraded instead of ! doing a full reinstall. Firewalling software has largely ! migrated from ipchains to iptables, so do the following: ! </para> ! <programlisting> &prompt; <userinput>chkconfig ipchains off</userinput> &prompt; <userinput>chkconfig iptables on</userinput> ! </programlisting> ! </sect2> ! <sect2> ! <title>qvcs-install</title> ! <para> ! Now that you have done all of the above, you can run ! <command>qvcs-install</command> to take care of various ! little settings that are needed for &qvcs;. Every step of ! the program will ask you for confirmation before making any ! changes, so if you are sure you don't want it to touch ! certain things, you can skip those parts. ! </para> ! <programlisting> &prompt; <userinput>qvcs-install</userinput> ! </programlisting> </sect2> <sect2> ! <title>Done</title> <para> ! That should be it! Reboot now and once your machine comes ! up, you should be able to continue using it as if nothing ! happened. If something is not working, please send email to ! the support mailing list so your problem can be looked into. </para> </sect2> *************** *** 1708,1714 **** <para> <application>libmcrypt</application>: This is a set of ! encryption libraries used by vadmin plugin. Vadmin uses ! libmcrypt to encrypt the passwords before storing them on ! the hard drive for enhanced security. </para> </listitem> --- 1930,1944 ---- <para> <application>libmcrypt</application>: This is a set of ! encryption libraries used by vadmin plugin. Vadmin can ! optionally use libmcrypt to encrypt the passwords before ! storing them on the hard drive for enhanced security. By ! default it uses a builtin rc4 function. ! </para> ! </listitem> ! <listitem> ! <para> ! <application>libmcrypt-devel</application>: This package is ! not installed by default and is only provided for the sake ! of completeness. </para> </listitem> *************** *** 1728,1736 **** <listitem> <para> ! <application>vadmin</application>: Vadmin is a plugin for ! squirrelmail which makes administering vmailmgr virtual ! domains a part of squirrelmail. It has some very nice ! features like the ability to add/remove users, set quotas or ! account expiration dates, etc. </para> </listitem> --- 1958,1966 ---- <listitem> <para> ! <application>squirrelmail-vadmin</application>: Vadmin is a ! plugin for squirrelmail which makes administering vmailmgr ! virtual domains a part of squirrelmail. It has some very ! nice features like the ability to add/remove users, set ! quotas or account expiration dates, etc. </para> </listitem> *************** *** 1745,1750 **** <para> <application>qvcs-helpers</application>: This package has a ! few helper scripts which come with this guide. They will be ! explained later. </para> </listitem> --- 1975,1979 ---- <para> <application>qvcs-helpers</application>: This package has a ! few helper scripts which come with this guide. </para> </listitem> *************** *** 1754,1757 **** --- 1983,2021 ---- and installer that makes installing software and keeping your server updated very easy. + </para> + </listitem> + <listitem> + <para> + <application>bglibs</application>: This package is not + installed by default, but is needed to build several other + packages. Unless you rebuild some packages from source RPMs, + you do not need this. + </para> + </listitem> + <listitem> + <para> + <application>nano</application>: This is a small editor + written to mimic <application>pico</application> which is no + longer shipping with many systems. + </para> + </listitem> + <listitem> + <para> + <application>maildrop</application>: Part of the qvcs-filter + package set, it is used by qmail-scanner. + </para> + </listitem> + <listitem> + <para> + <application>tnef</application>: A small application that + will unpack Microsoft-style attachments. Useful for virus + and spam scanning. Part of the qvcs-filter set. + </para> + </listitem> + <listitem> + <para> + <application>qmail-scanner</application>: An alternative + qmail-queue implementation that allows invoking spamassassin + and various virus scanners. Part of the qvcs-filter package set. </para> </listitem> |
