Some Notes on the Machines

Try this:

http://www.itexperience.net/2009/03/24/fix-your-message-wasnt-delivered-because-of-security-policies-in-exchange-2007/

Also, check the properties of the distribution group.  Under “delivery restrictions”, the default is to permit only if senders are within the domain.

J.E.B.

Here is some very good documentation:

http://technet.microsoft.com/en-us/library/bb691363(EXCHG.80).aspx

This has to be done on a 32-bit OS client machine with Outlook 2007 or 2010 installed.  It cannot be done on a 64-bit OS.

Here:

http://help.yahoo.com/l/us/yahoo/mail/postmaster/defer.html

is a page with lots of interesting links, one of which is to request permission to broadcast email to yahoo.com recipients.

Recently wrestled a major problem with six Blackberry in a BES/Exchange environment.  Here is a checklist which emerged.

1. Email has to go from ..blackberry.net and *.blackberry.com to the BES admin’s email box, and quickly.  Make sure Internet email will go to the BES admin email box. If it doesn’t go quickly, solve that problem first.
2. The BB tech said that a recreation of encryption password, is a good thing to try.  It’s the least invasive, and least destructive.
3. Another good thing to try is a removal and reactivation.  This is not a wipe!  Just remove the entry in the Blackberry server and say yes to the second removal step also, add it again, set the activation password to something simple (one letter is good), and then go through activation on the handheld itself.
4. Regardless as to whether it is an encryption re-creation or a reactivation you are trying, the user’s mailbox will receive an email from something.something.blackberry.net, which the Blackberry server has to pull automatically out of the user’s mailbox.  This is done by MAPI.  So MAPI has to be working well in server mode on both the Blackberry server and the Exchange server…which means you had better not have ever installed Outlook on either one, this can be a cause of difficulty.  If for any cause MAPI is failing, the re-creation or activation email will stay in the user’s mailbox.

If your Exchange server’s stores won’t mount, try the following.

1. Turn off all of your Exchange services, and copy the stores to a backup location of some sort, including both logs and .edb files if you have them both.  We won't touch these.
2. See if you can recover using the logs.  Go to command prompt, CD to the location of the stores. If the logs are there, there will be a file with a short name in there, on many systems it's just "E00".  The log files themselves have extension ".log", but not that one.  Run the following command to try to recover using logs, where "AAA" needs to be replaced with that short three-letter name:

ESEUTIL /R AAA

The above may or may not work, or be possible.  The logs may also have been moved to a different location. And even if it does work, it’s a good idea to continue down this list.

3. We will now perform a step which repairs certain kinds of corruption in the database file(s).  Run the following command for each .edb file you have, replacing “databasename.edb” with the name of the file:

ESEUTIL /P databasename.edb 

4. The next step is a “defragment” of the same database files.  This is more than a defragment; this is really a rebuild of structure, and a means of eliminating more forms of corruption.  Run the following command for each .edb file you have, replacing “databasename.edb” with the name of the file:

ESEUTIL /D databasename.edb

5. Now start all of the appropriate Exchange services (usually, all the ones marked “automatic”), but do not yet try to mount the stores.  We have more corruption cleanup to do which requires the Exchange services running, with stores unmounted.  While the server is in this state, do this:

isinteg -s servername -fix -test alltests

6. Run the above command, replacing “servername” with the DNS hostname of your server.  When run, it will give you the option of choosing each of your stores, if you have more than one.  The first time you run it for a given store, it will probably say that it has corrected errors.  Run the same command on the same store, over and over, until it reports that it did not correct anything.  Do that to all of your stores. Then mount them, you are done!

There is a way to accelerate updates in Exchange.  One can change the “Mailbox Cache Age Limit” from the default 2 hours to 15 minutes, as briefly discussed near the end here:

http://support.microsoft.com/kb/327378

This just in.  It has been seen, that Outlook on Windows 7, trying to reach Exchange on Server 2003, sometimes runs into mysterious trouble.  The solution found, is to manually set up WINS and NetBIOS on the Windows 7 box.

Two interesting things.

1. This appears to be a feature in Outlook (Tools menu, Out of Office Assistant), but it’s not.  It’s a feature in Exchange, automatically loaded as an extension to Outlook when Outlook is configured for the server, and you’ll see it differently depending on which version of Exchange you have.
2. Since it is a feature in Exchange, if you run into problems, it’s almost certainly something to be fixed or changed on the Exchange server.  Here is just one example:
   http://www.adminspy.com/Windows-Tips/Microsoft-Outlook-Out-Of-Office-doesnt-work.html

See here:

http://www.msexchange.org/tutorials/Outlook_2003_Connect_Exchange_2003.html

Browse to https://servername/remote; if it doesn’t go, that’s step 1. Then study the info in the link ‘Configure your computer to use Outlook via the Internet’, and make sure it is all correct. Lastly, check certificates.