RHEL5.2 SendMail + dovecot Mail System Configuration tutorial

I believe no one knows the role of the email system for an enterprise. Currently, the mainstream email systems include SendMail, exchange, Lotus Notes, Qmail, and Postfix. Microsoft Exchange can only run on Windows platforms and must be based on active directories. Although exchange does have some advantages in functionality, such as user management, high integration with other Microsoft products such as office, but the operating cost is too high. Lotus n

I believe no one knows the role of the email system for an enterprise. Currently, the mainstream email systems include SendMail, exchange, Lotus Notes, Qmail, and Postfix.

Microsoft Exchange can only run on Windows platforms and must be based on active directories. Although exchange does have some advantages in functionality, such as user management, high integration with other Microsoft products such as office, but the operating cost is too high.

Lotus Notes does not need to be mentioned as the performance and functions of IBM products, but I always think that IBM products share a common feature, that is, only when running on IBM's software and hardware platforms can their functions be maximized.

SendMail can run on almost all Unix-like platforms with powerful functions. Of course, SendMail also has some problems, but it has greatly improved with the upgrade of its version.

This article mainly introduces how to build a mail system platform through SendMail in RHEL 5.2, use dovecot to implement pop3/IMAP4, and use OpenWebMail to implement client access to the mail system through a browser. The following network topology is used during the presentation.

 

1. install and configure DNS.

I believe that the role of DNS does not need to be described too much. If an enterprise's mail server needs to receive emails sent to the public network, it needs to have a public IP address and a domain name, the DNS resolution work is provided by the ISP. In the configuration in this article, we assume that the email system is only used within the enterprise, so we need to configure DNS.

1. Install bind and related software packages.

yum -y install bind-chroot.i* caching-nameserver.i*

2. There is a global configuration example file in the/var/named/chroot/etc directory, and rename it named. conf. For example, you must add-a (or-p) to the copy operation. If the owner group of the global configuration file is not named, the BIND service cannot run.

 

3. Edit the named. conf file and modify the location as shown in.

 

4. In the/var/named/chroot/etc directory, copy a master configuration example file and change it to example. zqin. zone. For example, you must add-a during replication. If the owner Group of the master configuration file is not named, the BIND service cannot run.

 

5. Add the content at the end of the example. zqin. zones file.

 

6. There is an example in the forward and reverse directions of/var/named/chroot/var/named. Copy and modify the two examples, for example, you must add-a to the copy, because the BIND service cannot run if the owning group of the regional configuration file is not named.

 

7. Edit the forward resolution file example. zqin. zero and add the content as shown in.

 

8. Edit the reverse resolution file 0.168.192.local and add the content.

9. Start bind and set it to run automatically.

service named restart chkconfig named on