To provide e-mail services to users, you can use the Post Office Protocol 3 (POP3) and Simple Mail Transfer Protocol (SMTP) components included with the Windows Server 2003 family. The POP3 service implements the standard POP3 protocol for mail retrieval, and you can pair it with the SMTP service to enable mail transfer. If you plan to have clients connect to this POP3 server and download e-mail to local computers by using a POP3 capable mail client, configure this server as a mail server.
After configuring the mail server role, you can do the following:
Use the POP3 service to store and manage e-mail accounts on the mail server.
Enable user access to the mail server so that users can retrieve e-mail from their local computer by using an e-mail client that supports the POP3 protocol (for example, Microsoft Outlook).
For more information about implementing this server role, see Mail server role: Configuring a mail server.
Before you configure your computer as a mail server, verify whether or not:
The server on which you intend to install e-mail services has a working Internet connection.
There is an NTFS partition available. With an NTFS partition, you can take advantage of the increased security provided by disk quotas. For more information about disk quotas, see Configuring disk quotas for the POP3 service.
You have a registered e-mail domain name. Contact your Internet Service Provider for assistance in registering an e-mail domain name.
A Mail eXchanger (MX) record for your e-mail domain name exists and matches the name of your server. Contact your Internet service provider (ISP) to create an MX record.
You have configured your server for static addressing. Contact your Internet Service Provider for the information necessary to configure your server for static addressing. For more information on how to configure your mail server with a static IP address, see To configure TCP/IP for static addressing.
The following table lists the information that you need to know to before you add a mail server role.
Before adding a mail server role Comments
Determine the appropriate level of security for this server. A server in this role may be targeted by attackers because of its exposure to the Internet and other networks. To ensure the security of this server, it is recommended that you implement security precautions, such as firewalls and Internet Protocol security (IPSec), before placing it in a production environment. For more information, see Internet Protocol security (IPSec) and Securing your network with Basic Firewall.
Determine the appropriate authentication method for your configuration. You must choose an authentication method before you create any e-mail domains on the mail server. The authentication method can be changed only if there are no existing e-mail domains on the mail server.
If the computer that you are configuring as a mail server is either a member server or a domain controller, the authentication method setting defaults to Active Directory authentication. Otherwise, the setting defaults to local Windows accounts authentication.
Determine that you have a registered e-mail domain name. The e-mail domain must be a registered domain name and it must match the Mail eXchanger (MX) record created by your ISP. If you do not already have an e-mail domain name, contact your ISP for assistance in registering a domain name.
365 ADDS...
365 add 2
In the client/server programming model, a server is a program that awaits and fulfills requests from client programs in the same or other computers. A given application in a computer may function as a client with requests for services from other programs and also as a server of requests from other programs.
DEAR FRIENDS THIS SITE WILL TELL YOU EVERY SETTINGS & DETAILS WHICH ARE NEEDED TO SET A SERVER HEAR YOU WILL ALSO GET INFORMATION ABOUT THE DIFFERENT TYPE OF SERVER LIKE FILE SERVER, PRINT SERVER, MAIL SERVER, DHCP SERVER, TERMINAL SERVER, PROXY SERVER, WINS SERVER NETBIOS SERVER AND DIFFERENT SOFTWARE'S WHICH ARE NEEDED FOR SERVER SETTING & SHARING MANY MORE...
SO ITS A MAIN PLACE THAT'S SERVER PLACE...
he operating system is configured correctly. In the Windows Server 2003 family, file services depend on the appropriate configuration of the operating system and its services. If you have a new installation of a Windows Server 2003 operating system, you can use the default service settings. No further action is necessary. If you upgraded to a Windows Server 2003 operating system or you want to confirm that your services are configured correctly for best performance and security, verify your service settings by comparing them to the table in Default settings for services.
The computer is joined to an Active Directory domain as a member server. If you want to authenticate clients or publish a shared folder to Active Directory, the file server must be joined to a domain. If you do not need to perform either of these tasks, the file server does not need to be joined to a domain.
All available disk space is allocated. You can use Disk Management or DiskPart.exe to create a new partition out of unallocated space. For more information see, To create a partition or logical drive.
All existing disk volumes use the NTFS file system. FAT32 volumes are not secure, and they do not support file and folder compression, disk quotas, file encryption, or individual file permissions.
The following table lists the information that you need to know before you add a file server role.
Before adding a file server role Comments
Determine whether you want to configure disk quotas. Use disk quotas to track and control disk space usage for NTFS volumes on a per-volume basis. Quotas prevent users from exceeding the designated disk space by logging an event when a user exceeds a specified disk space limit.
Determine whether you want to use Indexing Service. Indexing Service creates indexes of the contents and properties of documents located on your local hard drive or on shared network drives. These indexes enable users to perform faster, easier searches. Indexing Service can slow down the server, so use it only if users frequently search the contents of files on this server.
Identify the folders that you want to share on the computer, and specify a folder name and description. Users view the shared resources on this file server based on file name. It is recommended that you create share names that are easy to remember and indicative of the folder contents. For example, suppose users are provided with 2 gigabytes (GB) each for storing their private information on the file server. You might name the top-level folder on your file server Personal Folders, and then name each of the subfolders according to the user's domain name.
Determine what type of permissions you want to set on the folders. Assign the most restrictive permissions that still allow users to perform required tasks. Access control on the NTFS file system provides more security than share permissions alone.
The computer is joined to an Active Directory domain as a member server. If you want to authenticate clients or publish a shared folder to Active Directory, the file server must be joined to a domain. If you do not need to perform either of these tasks, the file server does not need to be joined to a domain.
All available disk space is allocated. You can use Disk Management or DiskPart.exe to create a new partition out of unallocated space. For more information see, To create a partition or logical drive.
All existing disk volumes use the NTFS file system. FAT32 volumes are not secure, and they do not support file and folder compression, disk quotas, file encryption, or individual file permissions.
The following table lists the information that you need to know before you add a file server role.
Before adding a file server role Comments
Determine whether you want to configure disk quotas. Use disk quotas to track and control disk space usage for NTFS volumes on a per-volume basis. Quotas prevent users from exceeding the designated disk space by logging an event when a user exceeds a specified disk space limit.
Determine whether you want to use Indexing Service. Indexing Service creates indexes of the contents and properties of documents located on your local hard drive or on shared network drives. These indexes enable users to perform faster, easier searches. Indexing Service can slow down the server, so use it only if users frequently search the contents of files on this server.
Identify the folders that you want to share on the computer, and specify a folder name and description. Users view the shared resources on this file server based on file name. It is recommended that you create share names that are easy to remember and indicative of the folder contents. For example, suppose users are provided with 2 gigabytes (GB) each for storing their private information on the file server. You might name the top-level folder on your file server Personal Folders, and then name each of the subfolders according to the user's domain name.
Determine what type of permissions you want to set on the folders. Assign the most restrictive permissions that still allow users to perform required tasks. Access control on the NTFS file system provides more security than share permissions alone.
365 Add..
|
||||||||
