Translation of INSTALL section in "Life with QMail"
2. QMAIL installation
This part uses to guide QMAIL installation. If you are an experienced system administrator, you can install qmail according to the installation wizard in the install file in the qmail source code. The installation wizard is the QMAIL's official installation wizard, and they complicate than the installation wizard in Lift with QMail, and They assume that the reader is an experienced system and mail administrator. In addition, they are also outdated and are not recommended by BernStein.
-------------------------------------------------- -------------------------------------------------- -------------
Note:
If you choose to install the following wizard, you should read each part of the cover section for familiarity with the comprehensive process.
-------------------------------------------------- -------------------------------------------------- ----------------
2.1. Installation release
2.1.1 Comparison of binary and source code
Since the binary version is limited by the QMAIL license, it is usually installed from the source code. If you don't escape the difference between the source code and the binary, imagine your predetermined big pie. The "binary" version of the big pie can be eaten after it. The "Source Code" version of the big pie will include the corresponding supporting components: flour, yeast, cheese, spicy sauce, the above modification, and way to guide you to make a big pie. The source code installation is to give you more work, but if you carefully follow the operating wizard, the result is the same - or, more improved. Baked big pie will be more fresh, and you can adjust the above-in-law according to your hobbies, you can also get a lot of knowledge about the pie, and understand its "work" mechanism.
2.1.2. Comparison of TARBALL and OS_SPECIFIC (Automatic Installation Pack)
Some operating systems provide mechanism packages that automatically install the source code. Also returned to the big pie, they provide a package of package ingredients and production methods, you can make the pie through your button.
It sounds quite good, but does not use this method?
In practice, it may be a good idea. First aggregate these packages are quite difficult, and if you don't set them they will do anything. They are software, and they may have faults like any software. However, even if they are free, the convenience they provide will also be in cost. You have lost most of your own roast tart: Adjust the ability of the top decoration of the pie, the knowledge of the tart, the work mechanism of the pie.
If qmail is more than the big pie, then you can do this. This method is still feasible. It is: Qmail system is a very complex system, the installer and the maintainer need to know the system very well. The automatic installation version of QMAIL is easier to install than the user version, but the user version is more likely to form and process. Once you have a QMAIL system installed, you will have a lot of opportunities to reconfigure it or find out why it doesn't work in a way you envisage. For this reason, I suggest that the source code is manually installed without the "RPM" package or other automatic installation package of the red hat.
2.2. Installation Preparation
Before installing qmail, especially for the first time QMAIL, there are some things that you need to take care of you seriously.
If possible, install qmail on the "Double Machine" system. This will give you a correction error without losing important emails or interrupts the opportunity to provide mail services from your users. If you don't have a backup, and your system has installed Sendmail, SMAIL, or some other MTA mail systems, you can install or test qmail without interfering with other existing mail systems. When the mail system of other MTA is transferred to qmail, even if you have some QMAIL experience, it is recommended that you still have a list of plans. 2.3. System requirements
Qmail will be installed and run in UNIX or class UNIX system, but there are also some necessary conditions:
About 10 megabye hard disk space. After installation, you can release the 4 mega of space by except for the destination file.
A fully supportible C language compiled by the C compiler, system header function, and library. Installation usage will let you know how you get these necessary components.
Some spaces used to save binary files, documents and profiles
Prepare enough disk space for running ranks. Small single-user system only requires 2 megabytes. A large server requires a 2 Gigabit group.
A compatible operating system. Most of the tools of UNIX can run normally. There is a list of compatible versions in the EADME file in the source code.
A domain name server (DNS) is highly recommended.
Lack of any of the above, QMAIL can only send a remote system that has been configured in the configuration file of its mail transmission path.
Cooperable network connection. Qmail must be installed on a system with a good function, so you may not be able to install qmail on a message list server with only 28.8K connection speed.
Serialmail is set to make QMAIL to run on a machine that is not very good in connectivity performance. About the relevant information appendix about the part of the Serialmail.
2.4. Download source code
Ok, download your system has met the necessary conditions for installing qmail ready.
The first step is to download QMAIL and any source code for any other auxiliary tool.
You will need qmail, of course, you should also get UCSPI-TCP and daemontools:
Qmail, ftp://cr.yp.to/software/qmail-1.03.tar.gz
UCSPI-TCP, ftp://cr.yp.to/ucspi-tcp/ucspi-tcp-0.88.tar.gz
Daemontools, ftp://cr.yp.to/daemontools/daemontools-0.76.tar.gz
Get these source files through your browser or through the FTP tool.
-------------------------------------------------- -------------------------------------------------- -------------
Note:
If any one of the connections fails, it may be adapted to the packet has been updated.
In this case, you should go to http://cr.yp.to/software.html, download the latest version.
The updated version may not be compatible with other tools, be sure to read the "Update from the Old Release" section in the release version.
-------------------------------------------------- -------------------------------------------------- ----------------
2.5. Build a source code
2.5.1. Verify the construction environment
The first thing you need to do is to ensure that the tools needed to compile.
How to determine if the tool is depends on whether the tool does it exist? Although the tool does not necessarily exist, the easiest way is to try it.
-------------------------------------------------- -------------------------------------------------- ------------
Note:
If each test can pass, you can stop and jump to the next part. -------------------------------------------------- -------------------------------------------------- ------------
AT A Command Line Prompt, Type CC and Press Enter:
Enter CC and knocked back to the CC:
$ CC
CC: No Input Files Specified
$
If you get a similar answer, there is a C compiler in your road.
If not, it doesn't mean you have no installation. Maybe it is not included in your path. Of course, it may be that you have not installed at all.
Try these:
/ usr / bin / cc
/ usr / bin / gcc
/ usr / local / bin / cc
/ usr / local / bin / gcc
/ usr / ccs / bin / cc
If these can't run, you have to try the hair style of other platforms. According to your operating system,
Enter one of the following commands at the prompt
Red Hat Linux: (Free UNIX operating system for PC):
RPM -QA | GREP GCC or RPM -QA | GREP EGCS
FreeBSD (a Unix operating system that can be used):
INCLUDES GCC by DEFAULT
If you can't find a C compiler installed, then you have to find and install it.
And your operating system sales company or other operating system support channel contact.
In this section we will introduce the actual steps to compile QMAIL - the way to handle clipping-replication, which can be omitted.
2.5.2. Open the source file package
If you want to perform this step, you have already running the normal C compiler and copy source of the source code. Next, copy or move the source file to your work directory, it is recommended to put qmail in / usr / local UCSPI-TCP and Daemontool in / src directory are placed in / package.
At this time, you should become a root (superuser) identity, if you are still not.
Perform the following command:
SU
Umask 022
MKDIR -P / USR / local / src
MV qmail-1.03.tar.gz ucspi-tcp-0.88.tar.gz / usr / local / src
MKDIR -P / PACKAGE
CHMOD 1755 / PACKAGE
Now you can expand the source file package:
CD / USR / Local / SRC
Gunzip QMAIL-1.03.tar.gz
TAR XPF QMAIL-1.03.tar
Gunzip ucspi-tcp-0.88.tar.gz
TAR XPF UCSPI-TCP-0.88.tar
Rm * .tar # Note: Optional, unless space is tight
CD / package
Gunzip daemontools-0.76.tar.gz
TAR XPF daemontools-0.76.tar
Rm * .tar # Note:
The directory path of the source file is /usr/local/src/qmail-1.03, /us r/local/src/ucspi-tcp-0.88, and /package/admin/daemontools-0.76.
2.5.3. Create a directory
Since Qmail's installer will create the required subdirectory, you just need to make QMail's "master" folder.
MKDIR / VAR / Qmail
Ok, continue the next part.
-------------------------------------------------- -------------------------------------------------- --------------Note:
If you want to install qmail in other directories (not / var), you can implement it by creating a system connection in / var / qmail.
E.g:
A distributed design will be created by the following command:
MKDIR / VAR / Qmail
LN -S / USR / MAN / VAR / QMAIL / MAN
MKDIR / ETC / QMAIL
Ln -s / etc / qmail / var / qmail / control
LN -S / usr / sbin / var / qmail / bin
-------------------------------------------------- -------------------------------------------------- ------------
2.5.4. Create users and groups
The easiest way to create the necessary users and groups is to make a small script file to help you create.
In the source folder you will find files called install.ids.
It includes a command line that supports many platforms, so it can easily copy it to another file and edit it.
CD /usR/local/src/qmail-1.03 cp install.ids IDS
Then, use your favorite editor to delete those parts you don't need.
For example, the following is the content editing for FreeBSD (a Unix Operating System that can be used):
PW GroupAdd Nofiles
PW useradd alias -g nofiles -d / var / qmail / alias -s / nonnexistent
PW useradd qmails -g nofiles -d / var / qmail -s / nonexistent
PW useradd qmaill -g nofiles -d / var / qmail -s / nonnexistent
PW useradd qmailp -g nofiles -d / var / qmail -s / nonnexistent
PW GroupAdd qmail
PW useradd qmailq -g qmail -d / var / qmail -s / nonnexistent
PW useradd qmailr -g qmail -d / var / qmail -s / nonexistent
PW useradd qmails -g qmail -d / var / qmail -s / nonnexistent
Then run it, execute chmod to make it execute, or run it with the SH program:
The first way:
CHMOD 700 IDS
./IDS
The second way:
/ BIN / SH IDS
When the script is running, all your users and groups have been created, and you can continue the next part.
However, if your system is not in install.ids, what should you do?
You will have to create them with manual.
Open your favorite editor and edit / etc / group
You need to add 2 rows of 2 lines at the end of the file:
QMail: *: 2107:
NOFILES: *: 2108:
-------------------------------------------------- -------------------------------------------------- ---------------
Note:
Confirmation 2107 and 2108 are not used.
If they have been used, select Other Numbers that are not used.
-------------------------------------------------- ------------------------------ Next, use VIPW (most system with it, or edit your editor File / etc / passwd) Add below:
Alias: *: 7790: 2108 :: / var / qmail / alias: / bin / true
QMAILD: *: 7791: 2108 :: / var / qmail: / bin / true
QMAILL: *: 7792: 2108 :: / var / qmail: / bin / true
QMAILP: *: 7793: 2108 :: / var / qmail: / bin / true
QMAILQ: *: 7794: 2107 :: / var / qmail: / bin / true
QMAILR: *: 7795: 2107 :: / var / qmail: / bin / true
QMAILS: *: 7796: 2107 :: / var / qmail: / bin / true
-------------------------------------------------- -------------------------------------------------- -------------
Note:
Confirmation 7790-7796 is not used, and 2107 and 2108 are the ID number of the same group.
If a certain one of these UID has been used, the number is not being used.
-------------------------------------------------- -------------------------------------------------- -----------
You are not more simple to explain its easiest way than adding these rows to these files.
Now ready, continue to advance the next part.
2.5.5. Began construction
Now you can start building qmail. Change the directory to /usr/local/src/qmail-1.03 directory, then it is built:
CD /usR/local/src/qmail-1.03
In the verification building environment section, you get your C compiler.
If it is not called CC, or it is not in your path environment variable, you will need to edit CONF-CC and CONF-LD.
Make sure your compiler is GCC, and it is in your Path (environment variable).
Only edit the CONF-CC and CONF-LD, replace "CC" with "GCC".
Now enter the following command:
Make setup check
After compiling, you will need to configure your email.
Two scripts are provided make this work easier.
If your DNS is already configured, this manuscript should be all you need at this point:
./config
IF, for Some Reason, Config Can't Find your hostname in DNS, You'll Have to Run The Config-Fast Script:
If you cannot find your host name in the Domain Name Server (DNS), you will have to run the config-fast script:
./config-fast Your host full name
For example, your domain name is eXample.com, and if your computer's host name is Dolphin, your config-fast commands will be:
./config-fast dolphin.example.com
Now Qmail is installed on your system, ready to run!
The next section takes step by step to guide you to start and run qmail.
2.6. Install UCSPI-TCP
Very simple, you expand QMAIL, UCSPI-TCP, and Daemontool Source Circle. Now change the directory to the UCSPI-TCP folder:
CD /usr/local/src/ucspi-tcp-0.88
In the build section, if you modify the CONF CC and CONF-LD files, do the same processing here.
Then, do:
Make make setup check
In this way, UCSPI-TCP is successfully installed.
2.7. Install daemontools
Change the directory to folder daemOLS:
CD /PACKAGE/Admin/daemontools-0.76
Again, if you modify the CONF-CC and CONF-LD files when you install QMail and UCSPI-TCP, you will need to do the same change here.
Then, do:
Package / Install
On the BSD system (no file / etc / inittab), you will need to restart the system to run SVSCAN to manage these background tools.
Use "PS-EF | GREP SVSCAN" or "PS Waux | GREP SVSCAN" to verify that SVSCAN is running.
Appendix: Only 1-7 sections of Chapter 2 (Installation) in "Life with Mail".
