exchangefaq.org
brought to you by Simpler-Webb

Table of Contents

  1. Administrivia
  2. Definitions
  3. Administration
  4. Setup/Upgrade
  5. Migration/Interoperability
  6. Transport
  7. Store
  8. Clustering
  9. ADC
  10. OWA
  11. OMA
  12. Outlook 2003
  13. What's New
  14. Tracking Log EventIDs
  15. Logon Modifications for OWA Users
  16. OWA Segmentation


Other FAQs

Exchange 2003 FAQ
Exchange 2000 FAQ
Exchange 5.5 FAQ


Exchange Resource Manager

Find out how you can manage rooms and resources though Exchange with out the hassles and complications of scripting!

» Download a free trial today

FAQs / Exchange 2003 / Transport

01


All the system queues like the failed message retry queue, DNS messages pending submission, and messages queued for deferred delivery are now exposed to enhance trouble shooting.

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1082)
Categories: Exchange 2003/Transport |

02


On a single Exchange server deployment, there is no 100% reliable way to accomplish this with an SMTP Transport Event Sink; even though KB273233 suggests that creating a second SMTP Virtual Server works. However, at startup the Exchange Information Store binds to the SMTP Virtual Server that starts first and you can not rely on the routing of the mail from SMTP VS 1 to SMTP VS 2 as the KB273233 proposes. Also note that under special circumstances the database can become corrupted if you use an SMTP Transport Event Sink to manipulate outgoing (MAPI) message contents. This is currently under investigation by Microsoft and a QFE to prevent the store corruption is under development. ****

There are 3rd party products that will do this too.

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1040)
Categories: Exchange 2003/Administration | Exchange 2003/Transport |

03


You can do it, however, see there are limitations. It reliably works only on a border server, which can be either a Windows 2000 or 2003 SMTP Server with or without Exchange 2000/2003 installed. For more information, see KB317327 and KB317680

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1041)
Categories: Exchange 2000/Administration & Maintenance | Exchange 2003/Administration | Exchange 2003/Transport |

04


Yes, in the new Queue Viewer in the Exchange 2003 System Manager.

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1085)
Categories: Exchange 2003/Transport |

05


Exchange 2003 allows you to change the location of queue directories for SMTP virtual servers and X.400.

The Directions are in the document entitled “Exchange Titanium Getting Started Guide”

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1087)
Categories: Exchange 2003/Transport |

06


DNS messages pending submission - Contains delivery status notifications (DSN), also known as non-delivery reports that are ready to be delivered by Exchange. The Delete All Messages (no NDR) and Delete All Messages (NDR) functions are unavailable for this queue.

Messages queued for deferred delivery – Contains the messages marked by the client for deferred delivery or messages simply awaiting delivery at a different time.

Failed message retry - Contains messages that have been marked as retry due to a delivery failure. This queue also does not have the NDR functions mention in the DNS messages pending submission queue.

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1083)
Categories: Exchange 2003/Transport |

07


Enabling connection filter involves two steps:
  1. Create the recipient filter using the Connection Filtering tab on the Message Delivery Properties under Global Settings.
  2. Apply the filter at the SMTP virtual server level.

    The Directions are in the document entitled “Exchange Titanium Getting Started Guide”



Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1086)
Categories: Exchange 2003/Transport |

08


Exchange 2003 does not have any built-in function to accomplish that. Either look for a third party tool or develop your own Windows SMTP Transport Event Sink.

See http://www.cdolive.net/download/SMTPTransportEvent-AttachmentFilter.zip and http://www.cdolive.net/download/SMTPTransportEvent-SenderFilter.zip for two samples to get you started. More information about Windows SMTP Transport Event Sinks can be found at http://msdn.microsoft.com

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1088)
Categories: Exchange 2003/Transport |

09


You have to use the MaxMessageObjects registry key. For more information, see KB258748

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1089)
Categories: Exchange 2000/Administration & Maintenance | Exchange 2003/Transport |

10


You can do this through a registry entry. But there are two drawbacks. Once this is done, the details that are necessary to display the notification in the preview pane are stripped, and the originator of the message cannot use the Send Again option. For more information, see KB308303

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1090)
Categories: Exchange 2000/Administration & Maintenance | Exchange 2003/Transport |

11


Submissions can be restricted to a limited number of security principles though the standard Windows Discretionary Access Control List (DACL). This feature prevents non-trusted senders, such as unauthorized Internet users, from sending mail to an internal only distribution list. An example of this would be an “All Employees” distribution list which should not be available to anyone outside the company (by spoofing or otherwise). Note Restricted distribution lists will only work on the bridgehead servers or SMTP gateway servers running Exchange 2003.

To set restrictions on a distribution list

  1. Click Start, point to All Programs, point to Microsoft Exchange, and then click Active Directory Users and Computers.
  2. Expand your organizational unit container, and double-click Users.
  3. Right-click the distribution list for which you want to restrict submissions, and then click Properties.
  4. Click the Exchange General tab.
  5. Under Message Restrictions, under Accept messages, select one of the following options:
  • Click From everyone to allow anyone to send to this distribution list. This includes anonymous users from the Internet.
  • Click From authenticated users only to allow only authenticated users to send mail to this distribution list.
  • Click Only from to specify a select set of users or groups that can send to this group and then click Add to specify the users or groups that you want to permit to send mail to this distribution list.
  • Click From everyone except to allow everyone but a select set of users or groups to send to this distribution group and then click Add to specify the list of users or groups that you want to restrict from sending to this distribution list.


Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1084)
Categories: Exchange 2003/Transport |