Difference between revisions of "Exchange Server"
m |
m (Reverted edits by Atekysepiko (Talk); changed back to last version by Admin) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 32: | Line 32: | ||
== Exchange FS Structure and File Locations == | == Exchange FS Structure and File Locations == | ||
| − | C:\Program Files\Exchsrvr | + | C:\Program Files\Exchsrvr default installation path |
| − | C:\Program Files\Exchsrvr\Mailroot | + | C:\Program Files\Exchsrvr\Mailroot default user mailboxes |
| + | C:\Program Files\Exchsrvr\Mailroot\vsi 1 | ||
| + | C:\Program Files\Exchsrvr\Mailroot\vsi 1\BadMail | ||
| + | |||
| + | === badmail === | ||
| + | |||
| + | * C:\Program Files\Exchsrvr\Mailroot\vsi 1\BadMail | ||
| + | |||
| + | In Microsoft Exchange versions prior to 2003, all mail that cannot be delivered ends up in the Badmail directory. This folder grows infinitely till it runs out of disk space | ||
| + | |||
| + | Exchange 2000: The Badmail folder contains messages that cannot be delivered into your organisation, and also cannot be returned back to the sender. Therefore, the folder typically contains spam, and the files within the folder can usually just be deleted. | ||
| + | |||
| + | Exchange 2003: Badmail is not kept in Exchange 2003 SP1. With SP1 and above tools, it's easy to maintain a "Badmail-free" Exchange environment, or control how big the Badmail folder gets. There are registry keys to modify the behavor of badmail in 2003. | ||
| | ||
Latest revision as of 11:49, 24 November 2010
Contents
AUTOCOMPLETE IN OUTLOOK 2000 FAILS WHEN MOVED TO EXCHANGE SERVER
Outlook needs to know whether or not autocomplete should match from the local client contacts or the Global Address List on the Exchange Server.
Click TOOLS, SERVICES to bring up the Services dialog box. Click the ADDRESSING tab. Use the following values for Outlook 2000 connected to MS Exchange email server with Global Address List:
Show this address list first: Global Address List Keep personal addresses in: Contacts When checking mail, che...: Global Address List (first) Contacts (2nd)
If the user doesn't use local contacts or doesn't care about local contact autocompletion then remove local contacts from the 3rd.
Groups in Exchange
Global groups, in which all the users must come from the same domain.
Domain local groups, in which members can be drawn from any domain in the forest, but permissions can only be granted to the local domain (that is, the domain where the group account resides).
Universal groups, in which members can be drawn from any domain in the forest and be granted permissions anywhere in the forest.
ref: Group Scope
Outlook Web Access
OWA O.W.A. or Outlook Web Access
Microsoft Outlook
This document relates directly to the Outlook All Versions page.
Exchange FS Structure and File Locations
C:\Program Files\Exchsrvr default installation path C:\Program Files\Exchsrvr\Mailroot default user mailboxes C:\Program Files\Exchsrvr\Mailroot\vsi 1 C:\Program Files\Exchsrvr\Mailroot\vsi 1\BadMail
badmail
- C:\Program Files\Exchsrvr\Mailroot\vsi 1\BadMail
In Microsoft Exchange versions prior to 2003, all mail that cannot be delivered ends up in the Badmail directory. This folder grows infinitely till it runs out of disk space
Exchange 2000: The Badmail folder contains messages that cannot be delivered into your organisation, and also cannot be returned back to the sender. Therefore, the folder typically contains spam, and the files within the folder can usually just be deleted.
Exchange 2003: Badmail is not kept in Exchange 2003 SP1. With SP1 and above tools, it's easy to maintain a "Badmail-free" Exchange environment, or control how big the Badmail folder gets. There are registry keys to modify the behavor of badmail in 2003.
