Yes, you can delete these large files. These files contain copies of all the inbound and outbound messages sent through the IMS; the IMS logs this traffic when you have SMTP diagnostic logging turned on. To stop these files from accumulating, turn diagnostic logging down on the Diagnostic Logging tab in the IMS Properties dialog box, then stop and restart the IMS. After it restarts, remove the Lnnnnnnn.log files from \exchsrvr\imcdata\log and you'll be in good shape.
What's the easiest way to add a disclaimer to every outgoing SMTP message?
In general, I discourage the use of such disclaimers because by adding a disclaimer to every message, you might be giving up rather than gaining the protection you seek. If you label every message as confidential, how can you expect anyone to take seriously the notion that some messages really are confidential? Also, long disclaimers (and most are long) annoy recipients.
If you must have disclaimers on an Exchange Server 5.5 server, the easiest way to add them is to use the IMS Extension DLL that Microsoft Consulting Services released some time ago. In "Using the IMS Extension DLL," http://www.exchangeadmin.com, InstantDoc ID 8259, Joseph Neubauer explains how to install and use the tool. (You can obtain a copy of the tool from http://www.exchangefaq.org/content/0001.php3, or perform a Web search for disclaimer.zip.) This free but unsupported tool lets you append a disclaimer to each outbound message. For Exchange 2000 Server, you need to either install your own transport event sink (as the article at http://www.exchangefaq.org/platinum/0006.php3 describes) or buy a third-party product such as GFI's Mail Essentials for Exchange 2000.
Which protocol uses the most bandwidth: Messaging API (MAPI), POP3, or IMAP4?
MAPI uses the most bandwidth—by a significant amount. MAPI is a more flexible and capable protocol than either POP3 or IMAP4, but it also has the most on-the-wire overhead of the three protocols.
When you look at the back-and-forth communications that each protocol uses to retrieve one 10KB message, you'll see an astonishing difference between MAPI and the other protocols. POP3 and IMAP4 add almost no overhead. (POP3, for example, requires only about 32 bytes to log on to a mailbox and retrieve that 10KB message.) MAPI, by contrast, can use several kilobytes before you even start downloading the message.
We're trying to split up administrative tasks so that some of our Help desk staff can manage mailboxes. How can we restrict their access to mailboxes homed on one server?
To restrict access easily, you need Exchange 2000 Server. Exchange Server 5.5 defines permissions at the organization, site, and configuration level, so you can't put permissions on just one server. Exchange 2000 lets you use fine-grained permissions. If your company doesn't have Exchange 2000, you can try two alternative methods:
- Put users in recipient containers, then assign permissions on the containers. I don't like this alternative because it increases the difficulty of moving users.
- Put each server in a separate site. Because you can assign permissions at the site level, you control permissions on each server—at the cost of some extra management overhead (e.g., you must manually add connectors to enable intersite messaging and replication).
Can users on a Windows NT 4.0 server running Exchange Server 5.5 use an Exchange 2000 Server machine for their public folder server?
Sure! In fact, you can use Exchange 2000 with Exchange 5.5 in several ways. Exchange 2000 can provide several services to mailboxes homed on Exchange 5.5 servers:
- public folders, either replicas of folders from Exchange 5.5 or folders that exist only on the Exchange 2000 server
- URL access to public-folder data
- Outlook Web Access (OWA) to public folders
- Exchange conferencing (if you're running Exchange 2000 Conferencing Server—ECS)
- instant messaging
Can I alter the default text in Exchange Server nondelivery report (NDR) messages?
Users had hoped that Microsoft would offer this feature in Exchange 2000 Server, but it didn't materialize. Neither does Microsoft support a way for users to change the default text.
One cool thing you might do in Exchange 2000 is to write some event sink code to send a custom message when Exchange processes an NDR. However, writing this code might be more trouble than it's worth to you.
End of Article
Prev. page
1
2
[3]
next page -->
