Top 5 Exchange 2003 configuration mistakes

Exchange is one of the largest distributed email and group servers in the market today. As a consultant, these are the five biggest mistakes most and IT consultants make when they are switching online.

1. 1) Misconfigured MX files.

MX file is a DNS file that defines the host ready to accept email for the domain. Most of the inactive environments either completely lack their MX file or have used IP addresses as an MX file. MX records, but MX records should always be defined using FQDN, such as

2. 2) Port 25 is not sent.

In most cases, a server server will be sitting behind a firewall. Many users and IT consultants will not forward port 25. Since the server to the email server communicates at port 25, it will be impossible to send an email without turning on this firewall.

3. 3) Deleted Items Recovery

Exchange Server 2003 offers amazing service to the Outlook client called "Deleted Item Recovery", which allows users to recover email incorrectly deleted items instead of calling receivers to restore your email from backup. To enable this service, simply launch Microsoft Exchange System Manager. Bid down to the mailbox, not the server icon. Right click, properties, now select the Limits tab. Drop down are: Delete settings. Keep deleted items for (days), the next window. It is recommended that this setting be set no later than 7 days and no more than 30 days for maximum performance.

4. 4) Inappropriate DNS Settings

Reverse DNS is an important anti-spam checker enabled on most mail servers, if the public IP address server has not correctly set back and forward DNS settings, many popular e-mail services will refuse email as spam. The most popular mail server and mail service requires forwarding DNS and reverse DNS to resolve at the same address, for example, if your public IP address is and it resolves on then will be resolved to 222.222. 2222.222, this setting may need to be organized by your ISP.

5. 5) Asynchronous Connection Filter

Exchange Server 2003 offers a feature called "Connection Filtering", also known as "Real Time Block Lists", which allows the server to check if the sender IP address appears in RBL (real-time block list) to Enabling this feature can help to significantly reduce the number of SPAM users in the company.

See the following Microsoft KB article for more information about how to configure RBL support: .kb/823866

The result is that These are the most common types of misunderstandings or improper settings by setting up an Exchange 2003 server.

Source by Brian Carpio

Leave a Reply

Your email address will not be published. Required fields are marked *