Search results for query: *

Delivery restrictions on the restricted objects is what you need to look at. Depending on the number of people you are talking about you might want to create a distribution list and have that as the "reject messages from" object rather than individual users.

You will need to ensure that you have message tracking enabled on the IS and also any connectors i.e. X.400, IMS that you are using. Exchange will then start creating entries in YYYYMMDD.LOG files in the <exchsrvr>\tracking.log folder. The logs are a pain to parse but there are a number of...

Search through Books OnLine and/or Help for the &quot;Address Book Views&quot; subject. ABV gives you a mechanism for displaying the GAL, on a client, in a more &quot;logical&quot; order as per your own requirements.

Standard and enterprise can co-exist is the same site. I do not have any docs or a case study, you might want to try in the Exchange 2000 forum to if someone there can help.

Sounds a reasonable plan to me and I don't see any reason why it should not work.

The Linux sendmail shouldn't have anything to do with this because all it will do is to receive the mail and say &quot;okay that's for @bdomain.com I need to send this on to this address&quot; and unless it's doing something &quot;strange&quot; it will just pass the message on as one message no...

The first server in a site has a special role within Exchange and there are important things you need to do before removing this. If at all possible you should try to get the server backup again and then take yourself to the following page at M$ support for info about what to do when you want to...

Do you have message tracking enabled on both servers, if not then you should enable it on the IS, the IMS and the MTA which will allow us to do some basic message tracking. To make sure I correctly understand the problem you have the following situation: You have an Exchange server with a...

How are messages routed between the two Exchange servers, via an Exchange connector or out via the public internet ?

You can mix and match as much as you like and put connectors, mailboxes etc on either version but if you want Exchange cluster support then you need the Enterprise version.

Enterprise

The tracking logs are what you are after as they contain details of all messages, NDR's, PF & DirRep messages sent/received (assuming you have message tracking enabled of course). There are a number of third party products available that will provide that sort of report, Exchange itself doesn't...

#3 Support for clustering, multiple databases on the same server, chat services etc. Migration from Exch 5.5 to E2K is normally done by having E2K on a seperate server and using the AD connector but you can do a &quot;single server&quot; upgrade (if you are brave). Take a look at...

Are you talking about the tracking logs ? You can open them using Excel (the fields are seperated by a tab character) but they are still a pig to parse and it depends on what you are trying to do.

Joshua1, 1. Both Exchange standard and enterprise can co-exist within both the Exchange site and organization as much as you might like. 2. It depends. For something like a bridgehead server that doesn't have any mailboxes on it you should be able to just install over the top to upgrade. With...

Mannga, I'm guessing here but I assume you are talking external email address, in which case you would add them as custom recipients (I normally add a new recipients container for CR's just to keep things tidy) and then create a distribution list which contains those twenty. If this is not the...

Client OS: XP SP1 Outlook Version: XP (2002) Exchange Server: 5.5 Enterprise I have to log in locally, not to a domain because I am connecting to a customers domain via VPN. I have configured an account for myself on the customers domain with exactly the same username and password as the...

Bhavesh, The IMS is easy. Just create and configure a new one on one of the other servers. Once you know it's working okay remove any &quot;Address Space&quot; entries from the old server and all smtp mail will be routed via the new IMS. Don't forget to update any inbound routing i.e. MX...

Get something like a broadband router that provides an always on connection to your LAN and then you can just use standard TCP/IP rather than dialup (I do this at home with my mail server). Let me know if you need any more info.

Do you get some sort of error when you try to forward to internal addresses, in fact do you get any sort of errors at all, either in a message or in the Event Log ? Also how is this forwarding done, by an external application or rules in Outlook or whatever ?