Editor's Note: We need your help to make this and other email newsletters from Windows & .NET Magazine as useful to you as they can be. To help us with our editorial planning, please answer the Windows & .NET Magazine Network Email Newsletter & Web Site Survey, available at the following URL. If you provide your email address at the end of the survey, we'll put your name in a drawing for a Windows & .NET Magazine T-shirt. Thank you! We appreciate your help.
http://www.zoomerang.com/survey.zgi?qn1v072pthga5pgs9r9lgr5r
Exchange and Outlook UPDATE, Exchange Edition—brought to you by Exchange & Outlook Administrator, a print newsletter from Windows & .NET Magazine that contains practical advice, how-to articles, tips, and techniques to help you do your job today.
http://www.exchangeadmin.com
THIS ISSUE SPONSORED BY
Esker Software
http://www.esker.com/exchange0502
SPONSOR: ESKER SOFTWARE
Tightly integrated with Microsoft Exchange Server, Pulse for Fax allows users to send and receive faxes directly from their Outlook or Exchange client — providing a single messaging platform. Pulse for Fax streamlines document exchange, accelerates business processes, and increases user productivity. From the same scalable server, Pulse for Fax enables high-volume fax from any mainframe or midrange host. Pulse for Fax also provides a seamless upgrade path to Pulse for expanded document delivery capabilities including web, email, distributed print, and wireless — in addition to fax. Request your FREE Pulse for Fax information kit today at:
http://www.esker.com/exchange0502
June 21, 2002—In this issue:
1. COMMENTARY
- SMTP: Then and Now
2. ANNOUNCEMENTS
- Struggling with IIS and Web Administration Concerns?
- Special 2-for-1 Subscription Offer!
3. HOT RELEASE (ADVERTISEMENT)
- NEW!! PROMODAG Reports for MS Exchange Server V5
4. RESOURCES
- Exchange HOWTO: Track Messages on Exchange Server by Using Windows Management Instrumentation
- Featured Thread: Slowness After Upgrading
5. NEW AND IMPROVED
- Appliance Can Eliminate the Need for an Email VPN
6. CONTACT US
- See this section for a list of ways to contact us.
1. COMMENTARY
Why is SMTP in Exchange 2000 Server so difficult to figure out? SMTP in Exchange Server 5.5 and earlier versions is relatively easy to understand and set up: For the most part, you have just one SMTP service, called the Internet Mail Service (IMS) or Internet Mail Connector (IMC) for Exchange Server 4.0. Configuration of this service is rather straightforward, and the service usually does exactly what you tell it to do. Exchange 2000, however, greatly complicates the process, using SMTP virtual servers, SMTP connectors, and a new Routing service. In fact, SMTP configuration is one of the leading Exchange 2000 topics for Microsoft Product Support Services (PSS—see Microsoft's Exchange 2000 Server Support Center site at http://support.microsoft.com/default.aspx?scid=fh;en-us;exch2k ). Therefore, I want to take a moment to look at how SMTP has evolved in Exchange 2000.
First, be aware that comparing SMTP in Exchange 2000 with SMTP in earlier Exchange versions isn't exactly an apples-to-apples comparison. In Exchange 5.5 and earlier versions, SMTP is simply an add-on connectivity protocol option; X.400 is the core Message Transfer Agent (MTA) protocol. Exchange 2000 reverses this arrangement (sort of): SMTP is the core MTA protocol and X.400 support is the add-on connector option. Part of the reason that SMTP is so easy to understand in Exchange 5.5 and earlier versions is because it isn't the core delivery mechanism. Now that Exchange 2000 relies on SMTP as its core transport and delivery mechanism—in Exchange 2000, all message delivery is SMTP-based by default—figuring out SMTP's role and configuration options is much more daunting.
SMTP in Exchange 2000 is based on three key components or objects: SMTP connectors, SMTP virtual servers, and the Routing service. An SMTP connector has the same role as the IMS in Exchange 5.5 and earlier versions. The reasons for using SMTP connectors in Exchange 2000 (e.g., SMTP connectivity, ETRN/TURN and HELO/EHLO support, SMTP security settings, message delivery and content restrictions, address spaces) are the same as the reasons for using the IMS in Exchange 5.5. When configuring an SMTP connector in Exchange 2000, you'll recognize some of the same settings and configuration options that you find when configuring the IMS in earlier Exchange versions. You use SMTP connectors for specific outbound connectivity within your organizations and to the outside world (i.e., the Internet). By default, you don't need any configured SMTP connectors for email to flow around your Exchange 2000 organization. That's where SMTP virtual servers and the Routing service come in.
In Exchange 2000, Microsoft IIS SMTP virtual servers and the Exchange 2000 Routing service replace the core X.400-based MTA found in Exchange 5.5 (and earlier versions). Exchange 2000 no longer hosts the SMTP protocol but relies on IIS to provide this functionality through SMTP virtual servers. These virtual servers are dedicated to providing SMTP service to Exchange (through TCP port 25). Together with the Routing service—which is a routing, categorization, and resolving service—SMTP virtual servers provide the core message delivery system for Exchange 2000.
So, how does all this apply to how we run our Exchange 2000 deployments? When you want to manage how messages flow into your Exchange 2000 organization, concentrate on SMTP virtual servers, which receive messages (both external and internal), and the Routing service, which handles how to get messages where they need to go. When you want to send messages to another organization or to the Internet, concentrate on SMTP connectors, which are hosted by SMTP virtual servers and control this connectivity. (You can also use SMTP connectors to link Exchange 2000 Routing Groups, but that process is outside the scope of this discussion.)
At first look, SMTP support in Exchange 2000 might seem a bit confusing in comparison to the simple and straightforward approach you're used to in earlier versions of Exchange. But although Exchange 2000's SMTP configuration and management might be more complex, the power of SMTP in Exchange 2000 brings many advantages in terms of functionality, manageability, and reliability. If you're planning a migration to Exchange 2000 or are in the middle of one, it might be worth your time to take a close look at the changes in SMTP support.
2. ANNOUNCEMENTS
(brought to you by Windows & .NET Magazine and its partners)
Discover Windows Web Solutions online, the Web site with articles, tips, and more to help you manage and overcome the security, performance, and maintenance concerns Web site administrators deal with every day. Don't miss this article: "15 Tips for Troubleshooting VPN Connections" ( http://www.windowswebsolutions.com/articles/index.cfm?articleid=8290 ). Check it out!
http://www.windowswebsolutions.com
Windows & .NET Magazine can help you find the right answer to an urgent problem, discover better ways to manage your enterprise, or prepare for an important migration. How can we improve on a resource this good? Subscribe now at our regular rate, and bring on a friend or colleague for free! This is a limited time offer, so act now!
http://www.winnetmag.com/sub.cfm?code=21ap2f21
3. HOT RELEASE (ADVERTISEMENT)
Analyze, Report, Strategize and Optimize your messaging system with V5 of the #1 reporting tool. Simplicity of use is the main asset of PROMODAG Reports. New reports: individual reports, storage/traffic costs, distribution list usage and more. Download Version 5!
http://www.promodag.com/indexwinnetmag_hr210602.asp
4. RESOURCES
Each week, Microsoft posts several Exchange Server how-to articles to its Knowledge Base. This week, learn how to use a script to connect to a remote Exchange server and track messaging events.
http://support.microsoft.com/default.aspx?scid=kb;en-us;q313527
Joe recently moved his Exchange Server 5.5 Service Pack 4 (SP4) organization to new, faster servers running Windows 2000 SP2. Now, users complain that opening messages with attachments takes from 30 seconds to 1 minute and that sending entries with attachments can take as many as 5 minutes. To offer your advice or join the discussion, go to the following URL:
http://www.exchangeadmin.com/forums/thread.cfm?cfapp=72&thread_id=107142&mc=10
5. NEW AND IMPROVED
(contributed by Bob Kretschman, [email protected])
Whale Communications released the e-Gap Webmail Appliance for Microsoft Exchange, a device that enables secure browser-based access to Exchange Server systems. The device lets you access Outlook Web Access (OWA) from any browser and can eliminate the need for VPNs devoted to accessing email. The appliance is secure and ensures that your internal network remains sealed from intruders. Throughput is more than 100Mbps and is scalable for high availability. For pricing and other information, email [email protected].
http://www.whalecommunications.com
6. CONTACT US
Here's how to reach us with your comments and questions:
- ABOUT THE COMMENTARY — [email protected]
- ABOUT THE NEWSLETTER IN GENERAL — [email protected]
(please mention the newsletter name in the subject line)
- TECHNICAL QUESTIONS — http://www.winnetmag.net/forums
- PRODUCT NEWS — [email protected]
- QUESTIONS ABOUT YOUR EXCHANGE & OUTLOOK UPDATE SUBSCRIPTION?
Customer Support — [email protected]
- WANT TO SPONSOR EXCHANGE & OUTLOOK UPDATE?
[email protected]
This email newsletter is brought to you by Exchange & Outlook Administrator, the print newsletter with practical advice, tips, and techniques covering migration, backup and restoration, security, and much more. Subscribe today!
http://www.exchangeadmin.com/sub.cfm?code=neei23xxup
Receive the latest information about the Windows and .NET topics of your choice. Subscribe to our other FREE email newsletters.
http://www.winnetmag.net/email
Thank you for reading Exchange & Outlook UPDATE.
Editor's Note: We need your help to make this and other email newsletters from Windows & .NET Magazine as useful to you as they can be. To help us with our editorial planning, please answer the Windows & .NET Magazine Network Email Newsletter & Web Site Survey, available at the following URL. If you provide your email address at the end of the survey, we'll put your name in a drawing for a Windows & .NET Magazine T-shirt. Thank you! We appreciate your help.
http://www.zoomerang.com/survey.zgi?qn1v072pthga5pgs9r9lgr5r
Exchange and Outlook UPDATE, Exchange Edition—brought to you by Exchange & Outlook Administrator, a print newsletter from Windows & .NET Magazine that contains practical advice, how-to articles, tips, and techniques to help you do your job today.
http://www.exchangeadmin.com
THIS ISSUE SPONSORED BY
Esker Software
http://www.esker.com/exchange0502
SPONSOR: ESKER SOFTWARE
Tightly integrated with Microsoft Exchange Server, Pulse for Fax allows users to send and receive faxes directly from their Outlook or Exchange client — providing a single messaging platform. Pulse for Fax streamlines document exchange, accelerates business processes, and increases user productivity. From the same scalable server, Pulse for Fax enables high-volume fax from any mainframe or midrange host. Pulse for Fax also provides a seamless upgrade path to Pulse for expanded document delivery capabilities including web, email, distributed print, and wireless — in addition to fax. Request your FREE Pulse for Fax information kit today at:
http://www.esker.com/exchange0502
June 21, 2002—In this issue:
1. COMMENTARY
- SMTP: Then and Now
2. ANNOUNCEMENTS
- Struggling with IIS and Web Administration Concerns?
- Special 2-for-1 Subscription Offer!
3. HOT RELEASE (ADVERTISEMENT)
- NEW!! PROMODAG Reports for MS Exchange Server V5
4. RESOURCES
- Exchange HOWTO: Track Messages on Exchange Server by Using Windows Management Instrumentation
- Featured Thread: Slowness After Upgrading
5. NEW AND IMPROVED
- Appliance Can Eliminate the Need for an Email VPN
6. CONTACT US
- See this section for a list of ways to contact us.
1. COMMENTARY
Why is SMTP in Exchange 2000 Server so difficult to figure out? SMTP in Exchange Server 5.5 and earlier versions is relatively easy to understand and set up: For the most part, you have just one SMTP service, called the Internet Mail Service (IMS) or Internet Mail Connector (IMC) for Exchange Server 4.0. Configuration of this service is rather straightforward, and the service usually does exactly what you tell it to do. Exchange 2000, however, greatly complicates the process, using SMTP virtual servers, SMTP connectors, and a new Routing service. In fact, SMTP configuration is one of the leading Exchange 2000 topics for Microsoft Product Support Services (PSS—see Microsoft's Exchange 2000 Server Support Center site at http://support.microsoft.com/default.aspx?scid=fh;en-us;exch2k ). Therefore, I want to take a moment to look at how SMTP has evolved in Exchange 2000.
First, be aware that comparing SMTP in Exchange 2000 with SMTP in earlier Exchange versions isn't exactly an apples-to-apples comparison. In Exchange 5.5 and earlier versions, SMTP is simply an add-on connectivity protocol option; X.400 is the core Message Transfer Agent (MTA) protocol. Exchange 2000 reverses this arrangement (sort of): SMTP is the core MTA protocol and X.400 support is the add-on connector option. Part of the reason that SMTP is so easy to understand in Exchange 5.5 and earlier versions is because it isn't the core delivery mechanism. Now that Exchange 2000 relies on SMTP as its core transport and delivery mechanism—in Exchange 2000, all message delivery is SMTP-based by default—figuring out SMTP's role and configuration options is much more daunting.
SMTP in Exchange 2000 is based on three key components or objects: SMTP connectors, SMTP virtual servers, and the Routing service. An SMTP connector has the same role as the IMS in Exchange 5.5 and earlier versions. The reasons for using SMTP connectors in Exchange 2000 (e.g., SMTP connectivity, ETRN/TURN and HELO/EHLO support, SMTP security settings, message delivery and content restrictions, address spaces) are the same as the reasons for using the IMS in Exchange 5.5. When configuring an SMTP connector in Exchange 2000, you'll recognize some of the same settings and configuration options that you find when configuring the IMS in earlier Exchange versions. You use SMTP connectors for specific outbound connectivity within your organizations and to the outside world (i.e., the Internet). By default, you don't need any configured SMTP connectors for email to flow around your Exchange 2000 organization. That's where SMTP virtual servers and the Routing service come in.
In Exchange 2000, Microsoft IIS SMTP virtual servers and the Exchange 2000 Routing service replace the core X.400-based MTA found in Exchange 5.5 (and earlier versions). Exchange 2000 no longer hosts the SMTP protocol but relies on IIS to provide this functionality through SMTP virtual servers. These virtual servers are dedicated to providing SMTP service to Exchange (through TCP port 25). Together with the Routing service—which is a routing, categorization, and resolving service—SMTP virtual servers provide the core message delivery system for Exchange 2000.
So, how does all this apply to how we run our Exchange 2000 deployments? When you want to manage how messages flow into your Exchange 2000 organization, concentrate on SMTP virtual servers, which receive messages (both external and internal), and the Routing service, which handles how to get messages where they need to go. When you want to send messages to another organization or to the Internet, concentrate on SMTP connectors, which are hosted by SMTP virtual servers and control this connectivity. (You can also use SMTP connectors to link Exchange 2000 Routing Groups, but that process is outside the scope of this discussion.)
At first look, SMTP support in Exchange 2000 might seem a bit confusing in comparison to the simple and straightforward approach you're used to in earlier versions of Exchange. But although Exchange 2000's SMTP configuration and management might be more complex, the power of SMTP in Exchange 2000 brings many advantages in terms of functionality, manageability, and reliability. If you're planning a migration to Exchange 2000 or are in the middle of one, it might be worth your time to take a close look at the changes in SMTP support.
2. ANNOUNCEMENTS
(brought to you by Windows & .NET Magazine and its partners)
Discover Windows Web Solutions online, the Web site with articles, tips, and more to help you manage and overcome the security, performance, and maintenance concerns Web site administrators deal with every day. Don't miss this article: "15 Tips for Troubleshooting VPN Connections" ( http://www.windowswebsolutions.com/articles/index.cfm?articleid=8290 ). Check it out!
http://www.windowswebsolutions.com
Windows & .NET Magazine can help you find the right answer to an urgent problem, discover better ways to manage your enterprise, or prepare for an important migration. How can we improve on a resource this good? Subscribe now at our regular rate, and bring on a friend or colleague for free! This is a limited time offer, so act now!
http://www.winnetmag.com/sub.cfm?code=21ap2f21
3. HOT RELEASE (ADVERTISEMENT)
Analyze, Report, Strategize and Optimize your messaging system with V5 of the #1 reporting tool. Simplicity of use is the main asset of PROMODAG Reports. New reports: individual reports, storage/traffic costs, distribution list usage and more. Download Version 5!
http://www.promodag.com/indexwinnetmag_hr210602.asp
4. RESOURCES
Each week, Microsoft posts several Exchange Server how-to articles to its Knowledge Base. This week, learn how to use a script to connect to a remote Exchange server and track messaging events.
http://support.microsoft.com/default.aspx?scid=kb;en-us;q313527
Joe recently moved his Exchange Server 5.5 Service Pack 4 (SP4) organization to new, faster servers running Windows 2000 SP2. Now, users complain that opening messages with attachments takes from 30 seconds to 1 minute and that sending entries with attachments can take as many as 5 minutes. To offer your advice or join the discussion, go to the following URL:
http://www.exchangeadmin.com/forums/thread.cfm?cfapp=72&thread_id=107142&mc=10
5. NEW AND IMPROVED
(contributed by Bob Kretschman, [email protected])
Whale Communications released the e-Gap Webmail Appliance for Microsoft Exchange, a device that enables secure browser-based access to Exchange Server systems. The device lets you access Outlook Web Access (OWA) from any browser and can eliminate the need for VPNs devoted to accessing email. The appliance is secure and ensures that your internal network remains sealed from intruders. Throughput is more than 100Mbps and is scalable for high availability. For pricing and other information, email [email protected].
http://www.whalecommunications.com
6. CONTACT US
Here's how to reach us with your comments and questions:
- ABOUT THE COMMENTARY — [email protected]
- ABOUT THE NEWSLETTER IN GENERAL — [email protected]
(please mention the newsletter name in the subject line)
- TECHNICAL QUESTIONS — http://www.winnetmag.net/forums
- PRODUCT NEWS — [email protected]
- QUESTIONS ABOUT YOUR EXCHANGE & OUTLOOK UPDATE SUBSCRIPTION?
Customer Support — [email protected]
- WANT TO SPONSOR EXCHANGE & OUTLOOK UPDATE?
[email protected]
This email newsletter is brought to you by Exchange & Outlook Administrator, the print newsletter with practical advice, tips, and techniques covering migration, backup and restoration, security, and much more. Subscribe today!
http://www.exchangeadmin.com/sub.cfm?code=neei23xxup
Receive the latest information about the Windows and .NET topics of your choice. Subscribe to our other FREE email newsletters.
http://www.winnetmag.net/email
Thank you for reading Exchange & Outlook UPDATE.
